[avtext] FW: New Version Notification for draft-ietf-avtext-splicing-notification-09.txt

"Huangyihong (Rachel)" <rachel.huang@huawei.com> Wed, 03 August 2016 08:08 UTC

Return-Path: <rachel.huang@huawei.com>
X-Original-To: avtext@ietfa.amsl.com
Delivered-To: avtext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9705D12D1D2 for <avtext@ietfa.amsl.com>; Wed, 3 Aug 2016 01:08:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.508
X-Spam-Level:
X-Spam-Status: No, score=-5.508 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ab8Zybme_Ac2 for <avtext@ietfa.amsl.com>; Wed, 3 Aug 2016 01:08:44 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26198127078 for <avtext@ietf.org>; Wed, 3 Aug 2016 01:08:43 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CTR75576; Wed, 03 Aug 2016 08:08:40 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml706-cah.china.huawei.com (10.201.5.182) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 3 Aug 2016 09:07:52 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.179]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Wed, 3 Aug 2016 16:07:44 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: "avtext@ietf.org" <avtext@ietf.org>
Thread-Topic: [avtext]FW: New Version Notification for draft-ietf-avtext-splicing-notification-09.txt
Thread-Index: AQHR7V4dqsJ58JGLjUi87FUtQMH8Rg==
Date: Wed, 03 Aug 2016 08:07:45 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB86F1F2AE@nkgeml513-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.78.28]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.57A1A688.00C6, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.179, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 417d66335f0f0afe569d983b119fe19b
Archived-At: <https://mailarchive.ietf.org/arch/msg/avtext/RUebVRHrHOMLH4hHG2Wely7_Nhc>
Subject: [avtext] FW: New Version Notification for draft-ietf-avtext-splicing-notification-09.txt
X-BeenThere: avtext@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Extensions working group discussion list <avtext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avtext>, <mailto:avtext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avtext/>
List-Post: <mailto:avtext@ietf.org>
List-Help: <mailto:avtext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avtext>, <mailto:avtext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2016 08:08:46 -0000

Hi all,

This new version addresses two comments from Mirja:

1.  Using RFC6828 as an example.
2.  Changing the normative reference from RFC5285 to draft-ietf-avtcore-rfc5285-bis, where general RTP header extension methods including its sending frequency are specified.

BR,
Rachel


-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Wednesday, August 03, 2016 3:52 PM
To: Deng Lingli; Roni Even; Xiajinwei; Huangyihong (Rachel); Lingli Deng
Subject: New Version Notification for draft-ietf-avtext-splicing-notification-09.txt


A new version of I-D, draft-ietf-avtext-splicing-notification-09.txt
has been successfully submitted by Rachel Huang and posted to the IETF repository.

Name:		draft-ietf-avtext-splicing-notification
Revision:	09
Title:		RTP/RTCP extension for RTP Splicing Notification
Document date:	2016-08-03
Group:		avtext
Pages:		21
URL:            https://www.ietf.org/internet-drafts/draft-ietf-avtext-splicing-notification-09.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-avtext-splicing-notification/
Htmlized:       https://tools.ietf.org/html/draft-ietf-avtext-splicing-notification-09
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-avtext-splicing-notification-09

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. 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 RTCP packet that conveys the
   information out-of-band.

                                                                                  


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat