RTP/RTCP extension for RTP Splicing Notification
draft-xia-avtext-splicing-notification-03
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Jinwei Xia , Roni Even , Rachel Huang , Deng Lingli | ||
Last updated | 2014-08-16 (Latest revision 2014-02-12) | ||
Replaced by | draft-ietf-avtext-splicing-notification | ||
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-notification | |
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
Content splicing is a process that replaces the content of a main multimedia stream with other multimedia content, and delivers the substitutive multimedia content to the receivers for a period of time. The RTP mixer is designed to handle RTP splicing in [RFC6828], but how the RTP mixer knows when to start and end the splicing is still unspecified. This memo defines two RTP/RTCP extensions to indicate the splicing related information to the RTP mixer: an RTP header extension that conveys the information in-band and an RTCP packet that conveys the information out-of-band.
Authors
Jinwei Xia
Roni Even
Rachel Huang
Deng Lingli
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)