Re: [AVT] FW: New Version Notification for draft-xia-avt-splicing-for-rtp-00

Jinwei Xia <xiajinwei@huawei.com> Thu, 21 October 2010 06:32 UTC

Return-Path: <xiajinwei@huawei.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 845473A69A9 for <avt@core3.amsl.com>; Wed, 20 Oct 2010 23:32:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level:
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wbrfHChZijBY for <avt@core3.amsl.com>; Wed, 20 Oct 2010 23:32:03 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 6DEB63A6944 for <avt@ietf.org>; Wed, 20 Oct 2010 23:32:02 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LAM00IH5NJQ4O@szxga03-in.huawei.com> for avt@ietf.org; Thu, 21 Oct 2010 14:33:26 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LAM008F6NJQ5K@szxga03-in.huawei.com> for avt@ietf.org; Thu, 21 Oct 2010 14:33:26 +0800 (CST)
Received: from x65217 ([10.138.41.60]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LAM0056ONJQF6@szxml06-in.huawei.com> for avt@ietf.org; Thu, 21 Oct 2010 14:33:26 +0800 (CST)
Date: Thu, 21 Oct 2010 14:33:25 +0800
From: Jinwei Xia <xiajinwei@huawei.com>
In-reply-to: <F9549DE5-7760-40A5-9690-AEDFE1CB6E80@csperkins.org>
To: 'Colin Perkins' <csp@csperkins.org>
Message-id: <005c01cb70e9$ddfbd1f0$3c298a0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Thread-index: ActwXfOE1MgvvvDaTHGrv49r1tZLgQAY370g
Cc: 'IETF AVT WG' <avt@ietf.org>
Subject: Re: [AVT] FW: New Version Notification for draft-xia-avt-splicing-for-rtp-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 06:32:04 -0000

Hi Colin,

Thank your comments. The scenario description is given in problem statements
draft, it is unnecessary to repeat that in this draft. 

Indeed, a standard translator can handle splicing without any extension, and
it still needs instructions from media source to implement splicing. 

I will update the draft according to our maillist discussion. Any commets
from others are also very appreciated!


Thank you
Jinwei

> -----Original Message-----
> From: Colin Perkins [mailto:csp@csperkins.org] 
> Sent: Wednesday, October 20, 2010 9:52 PM
> To: Jinwei Xia
> Cc: 'IETF AVT WG'
> Subject: Re: [AVT] FW: New Version Notification for 
> draft-xia-avt-splicing-for-rtp-00
> 
> Hi Jinwei,
> 
> My impression is that this draft confuses the issue by 
> focussing too much on scenarios where the content to be 
> inserted is also delivered over RTP. Whether the content to 
> be inserted is delivered as a real-time RTP stream or fetched 
> from local file storage does not affect the insertion 
> process, and so doesn't need to be mentioned in the draft. I 
> still believe that a standard RTP translator is sufficient to 
> solve this problem, although there may be useful things to 
> say about how to efficiently implement such a translator. 
> 
> Colin
> 
> 
> On 16 Oct 2010, at 03:06, Jinwei Xia wrote:
> > Hi,
> > 
> > From the discussion on IETF 78th, there were some 
> misunderstandings of the scope of splicing draft. So we 
> discard previous problem statement draft while initiate new 
> solution draft. In this new draft, We emphysize content 
> insertion issue is indeed a RTP-generic rather than MPEG2 
> TS-specific. 
> > 
> > Hope the new draft can address most issues AVT concern, any 
> comments are very appreciated!
> > 
> > 
> > BR!
> > 
> > Jinwei
> > 
> >> -----Original Message-----
> >> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
> >> Sent: Saturday, October 16, 2010 9:58 AM
> >> To: xiajinwei@huawei.com
> >> Subject: New Version Notification for 
> >> draft-xia-avt-splicing-for-rtp-00
> >> 
> >> 
> >> A new version of I-D, draft-xia-avt-splicing-for-rtp-00.txt
> >> has been successfully submitted by Jinwei Xia and posted 
> to the IETF 
> >> repository.
> >> 
> >> Filename:	 draft-xia-avt-splicing-for-rtp
> >> Revision:	 00
> >> Title:		 Content Splicing for RTP Sessions
> >> Creation_date:	 2010-10-16
> >> WG ID:		 Independent Submission
> >> Number_of_pages: 12
> >> 
> >> Abstract:
> >> This memo outlines RTP splicing.  Splicing is a process 
> that allows a 
> >> new multimedia stream to be inserted into current 
> multimedia stream 
> >> and to be conveyed to receiver for a period of time.  This memo 
> >> discusses the requirements of RTP splicing.  In order to 
> satisfy the 
> >> requirements, this memo lists several existing 
> intermediary network 
> >> elements as alternatives and evaluates whether one of alternatives 
> >> can be used to perform RTP splicing.
> >> 
> >> 
> >> 
> >> 
> >> The IETF Secretariat.
> >> 
> >> 
> > 
> > _______________________________________________
> > Audio/Video Transport Working Group
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
> 
> 
> 
> -- 
> Colin Perkins
> http://csperkins.org/
> 
> 
>