Skip to main content

RTP/RTCP Extension for RTP Splicing Notification
RFC 8286

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'Content splicing is a process that replaces the content of a main multimedia stream with other …
Received changes through RFC Editor sync (changed abstract to '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.')
2017-10-25
(System)
Received changes through RFC Editor sync (created alias RFC 8286, changed title to 'RTP/RTCP Extension for RTP Splicing Notification', changed abstract to 'Content splicing …
Received changes through RFC Editor sync (created alias RFC 8286, changed title to 'RTP/RTCP Extension for RTP Splicing Notification', changed abstract to '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.', changed pages to 22, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2017-10-25, changed IESG state to RFC Published)
2017-10-25
(System) RFC published