RTP Archiving, Delivery, and Playback (RADPLAY) Extensions for SDP
draft-lanphier-radplay-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Rob Lanphier | ||
| Last updated | 2002-02-15 | ||
| 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
This document defines RTP Archiving, Delivery, and Playback (RADPLAY) extensions for the Session Description Protocol (SDP, [RFC 2327]). These extensions provide a standard means of archiving and delivering RTP streams via HTTP, using SDP and the commonly used 'rtpdump' file format. As a result of its design, it also provides a way of delivering generic RTP streams over HTTP, thus making it a suitable replacement for approaches which rely on network-unfriendly mechanisms such as 'HTTP tunneling'.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)