The Real Time Transport Protocol (RTP) Denial of Service (Dos) Attack and its Prevention(
draft-rosenberg-mmusic-rtp-denialofservice-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jonathan Rosenberg | ||
| Last updated | 2003-06-26 | ||
| 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
The Real Time Transport Protocol (RTP) provides unreliable transport of real time media from a sender to one or more recipients. RTP sessions are typically set up through signaling protocols such as the Session Initiation Protocol (SIP) or the Real Time Streaming Protocol (RTSP). When RTP is set up with these protocols, a potential Denial of Service (DoS) attack is introduced. This attack allows an attacker to cause a flood of RTP packets to be sent towards a target. We describe this attack, and also show how it is effectively prevented using Interactive Connectivity Establishment (ICE), first introduced as a means of handling Network Address Translator (NAT) traversal.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)