Sign in
Version 5.13.0, 2015-03-25
Report a bug

HTTP Fallback for RTP Media Streams

Document type: Expired Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-02-08 (latest revision 2012-08-07)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:


Almost all VoIP endpoints, especially SIP and RTCWEB ones, make use of RTP to tranport media frames in real-time and communicate with each other. Since RTP uses UDP, the presence of network elements that filter UDP packets and/or only allow some protocols like SMTP or HTTP to pass through would make such a communication very hard to accomplish, if not impossible. This draft describes a way to implement an HTTP Fallback for RTP media streams, that is, a way to effectively encapsulate RTP packets in HTTP messages in order to traverse proxies and firewalls.


Lorenzo Miniero <>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)