RFC 6828: Content Splicing for RTP Sessions
In plain English — editorial summary, not part of the RFC
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. Splicing is commonly used for insertion of local advertisements by cable operators, whereby national advertisement content is replaced with a local advertisement. This memo describes some use cases for content splicing and a set of requirements for splicing content delivered by RTP. It provides concrete guidelines for how an RTP mixer can be used to handle content splicing. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6828
- Published
- January 2013
- Authors
- J. Xia
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 17
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6838Media Type Specifications and Registration ProceduresUpdated
January 2013
- RFC 6839Additional Media Type Structured Syntax SuffixesUpdated
January 2013
- RFC 6843RTP Control Protocol (RTCP) Extended Report (XR) Block for Delay Metric ReportingCurrent
January 2013
- RFC 6809Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)Current
November 2012
- RFC 6849An Extension to the Session Description Protocol (SDP) and Real-time Transport Protocol (RTP) for Media LoopbackCurrent
February 2013
- RFC 6798RTP Control Protocol (RTCP) Extended Report (XR) Block for Packet Delay Variation Metric ReportingCurrent
November 2012
- RFC 6871Session Description Protocol (SDP) Media Capabilities NegotiationCurrent
February 2013
- RFC 6878IANA Registry for the Session Initiation Protocol (SIP) "Priority" Header FieldCurrent
March 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?