Content Splicing for RTP Sessions
draft-xia-avt-splicing-for-rtp-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jinwei Xia | ||
| Last updated | 2011-03-03 (Latest revision 2010-10-16) | ||
| Replaced by | draft-xia-avtext-splicing-for-rtp | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-xia-avtext-splicing-for-rtp | |
| 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 memo outlines RTP splicing. Splicing is a process that allows a new multimedia stream to be inserted into current multimedia stream and to be conveyed to receiver for a period of time. This memo discusses the requirements of RTP splicing. In order to satisfy the requirements, this memo lists several existing intermediary network elements as alternatives and evaluates whether one of alternatives can be used to perform RTP splicing.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)