metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 8286: RTP/RTCP Extension for RTP Splicing Notification

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 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.

Document record

Document ID
RFC8286
Published
October 2017
Authors
J. Xia; R. Even; R. Huang; L. Deng
Status
PROPOSED STANDARD
Stream
IETF
Area
art
Pages
22
Also known as
—

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/8286-rtp-rtcp-extension-for-rtp-splicing-notification