Using Interactive Connectivity Establishment (ICE) in Web Real-Time Communications (WebRTC)
draft-thomson-mmusic-ice-webrtc-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Martin Thomson | ||
| Last updated | 2014-04-21 (Latest revision 2013-10-18) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Interactive Connectivity Establishment (ICE) has been selected as the basis for establishing peer-to-peer UDP flows between Web Real-Time Communication (WebRTC) clients. Using an unmodified ICE implementation in this context enables the use of the web platform as a denial of service platform. The risks and complications arising from this choice are discussed. A modified algorithm for sending ICE connectivity checks from the web platform is described.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)