Content Splicing for RTP Sessions
draft-xia-avtext-splicing-for-rtp-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jinwei Xia | ||
| Last updated | 2011-10-10 (Latest revision 2011-08-25) | ||
| Replaces | draft-xia-avt-splicing-for-rtp | ||
| Replaced by | draft-ietf-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-ietf-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 replaces the content of the main multimedia stream with other multimedia content, and delivers the substitutive multimedia content to receiver for a period of time. This memo provides some RTP splicing use cases, then we enumerate a set of requirements and analyze whether an existing RTP level middlebox can meet these requirements, at last we provide concrete guidelines for how the chosen middlebox works to handle RTP splicing.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)