Content Splicing for RTP Sessions
draft-ietf-avtext-splicing-for-rtp-08

The information below is for an old version of the document
Document Type Active Internet-Draft (avtext WG)
Last updated 2012-07-11 (latest revision 2012-07-09)
Replaces draft-xia-avtext-splicing-for-rtp
Stream IETF
Intended RFC status Informational
Formats plain text pdf html
Stream WG state WG Document
Other - see Comment Log
Consensus Unknown
Document shepherd Magnus Westerlund
Shepherd write-up Show (last changed 2012-02-20)
IESG IESG state IESG Evaluation::External Party
Telechat date
Needs a YES.
Responsible AD Gonzalo Camarillo
IESG note Magnus Westerlund (magnus.westerlund@ericsson.com) is the document shepherd.
Send notices to avtext-chairs@tools.ietf.org, draft-ietf-avtext-splicing-for-rtp@tools.ietf.org
AVTEXT Working Group                                              J. Xia
Internet-Draft                                                    Huawei
Intended status: Informational                              July 9, 2012
Expires: January 10, 2013

                   Content Splicing for RTP Sessions
                 draft-ietf-avtext-splicing-for-rtp-08

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 local advertisement insertion by
   cable operators, replacing a national advertisement content 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 a RTP mixer can be used to handle content
   splicing.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 10, 2013.

Copyright Notice

   Copyright (c) 2012 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

Xia                     Expires January 10, 2013                [Page 1]
Internet-Draft                RTP splicing                     July 2012

   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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
   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.  Media Clipping Considerations  . . . . . . . . . . . . . . 10
     4.4.  Congestion Control Considerations  . . . . . . . . . . . . 11
     4.5.  Processing Splicing in User Invisibility Case  . . . . . . 12
   5.  Implementation Considerations  . . . . . . . . . . . . . . . . 13
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 13
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 14
   8.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 14
   9.  10. Appendix- Why Mixer Is Chosen  . . . . . . . . . . . . . . 14
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
     10.1. Normative References . . . . . . . . . . . . . . . . . . . 15
     10.2. Informative References . . . . . . . . . . . . . . . . . . 15
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 16

Xia                     Expires January 10, 2013                [Page 2]
Internet-Draft                RTP splicing                     July 2012

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, allowing content providers to replace
   the national advertising content with its 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 splicing technology can be applied.  For
Show full document text