Content Splicing for RTP Sessions
RFC 6828
|
Document |
Type |
|
RFC - Informational
(January 2013; No errata)
|
|
Author |
|
Jinwei Xia
|
|
Last updated |
|
2018-12-20
|
|
Replaces |
|
draft-xia-avtext-splicing-for-rtp
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
html
pdf
htmlized
bibtex
|
Stream |
WG state
|
|
Submitted to IESG for Publication
Other - see Comment Log
|
|
Document shepherd |
|
Magnus Westerlund
|
|
Shepherd write-up |
|
Show
(last changed 2012-10-01)
|
IESG |
IESG state |
|
RFC 6828 (Informational)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Gonzalo Camarillo
|
|
IESG note |
|
Magnus Westerlund (magnus.westerlund@ericsson.com) is the document shepherd.
|
|
Send notices to |
|
(None)
|
Internet Engineering Task Force (IETF) J. Xia
Request for Comments: 6828 Huawei
Category: Informational January 2013
ISSN: 2070-1721
Content Splicing for RTP Sessions
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. 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.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6828.
Xia Informational [Page 1]
RFC 6828 RTP Splicing January 2013
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction ....................................................2
2. System Model and Terminology ....................................3
3. Requirements for RTP Splicing ...................................6
4. Content Splicing for RTP Sessions ...............................7
4.1. RTP Processing in RTP Mixer ................................7
4.2. RTCP Processing in RTP Mixer ...............................8
4.3. Considerations for Handling Media Clipping at the
RTP Layer .................................................10
4.4. Congestion Control Considerations .........................11
4.5. Considerations for Implementing Undetectable Splicing .....13
5. Implementation Considerations ..................................13
6. Security Considerations ........................................14
7. Acknowledgments ................................................15
8. References .....................................................15
8.1. Normative References ......................................15
8.2. Informative References ....................................15
Appendix A. Why Mixer Is Chosen ...................................17
1. Introduction
This document outlines how content splicing can be used in RTP
sessions. Splicing, in general, is a process where part of a
multimedia content is replaced with other multimedia content and
delivered to the receivers for a period of time. The substitutive
content can be provided, for example, via another stream or via local
media file storage. One representative use case for splicing is
local advertisement insertion. This allows content providers to
replace national advertising content with their own regional
advertising content prior to delivering the regional advertising
content to the receivers. Besides the advertisement insertion use
case, there are other use cases in which the splicing technology can
Xia Informational [Page 2]
RFC 6828 RTP Splicing January 2013
be applied, for example, splicing a recorded video into a video
conferencing session or implementing a playlist server that stitches
pieces of video together.
Content splicing is a well-defined operation in MPEG-based cable TV
systems. Indeed, the Society for Cable Telecommunications Engineers
(SCTE) has created two standards, [SCTE30] and [SCTE35], to
Show full document text