Using Interactive Connectivity Establishment (ICE) in Web Real-Time Communications (WebRTC)
draft-thomson-mmusic-ice-webrtc-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Martin Thomson | ||
| Last updated | 2014-04-21 (latest revision 2013-10-18) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-thomson-mmusic-ice-webrtc-01.txt
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
Martin Thomson (martin.thomson@skype.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)