RTP/RTCP Extension for RTP Splicing Notification
RFC 8286, “RTP/RTCP Extension for RTP Splicing Notification”, is a Proposed Standard document published in October 2017 by J. Xia, R. Even, R. Huang, L. Deng. The canonical text is published by the RFC Editor.
Abstract
Content splicing is a process that replaces the content of a main multimedia stream with other multimedia content and that delivers the substitutive multimedia content to the receivers for a period of time. The splicer is designed to handle RTP splicing and needs to know when to start and end the splicing.
This memo defines two RTP/RTCP extensions to indicate the splicing-related information to the splicer: an RTP header extension that conveys the information "in band" and an RTP Control Protocol (RTCP) packet that conveys the information out of band.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8286 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8285 A General Mechanism for RTP Header Extensions
- RFC 8287 Label Switched Path Ping/Traceroute for Segment Routing IGP-Prefix and IGP-Adjacency Segment Identifiers with MPLS Data Planes
- RFC 8284 Lightweight Directory Access Protocol Schema for Supporting the Extensible Messaging and Presence Protocol in White Pages
- RFC 8288 Web Linking
- RFC 8283 An Architecture for Use of PCE and the PCE Communication Protocol in a Network with Central Control
- RFC 8282 Extensions to the Path Computation Element Communication Protocol for Inter-Layer MPLS and GMPLS Traffic Engineering
- RFC 8281 Path Computation Element Communication Protocol Extensions for PCE-Initiated LSP Setup in a Stateful PCE Model
- RFC 8291 Message Encryption for Web Push