Re: [AVTCORE] FW: I-D Action: draft-ietf-avtcore-idms-07.txt
Qin Wu <bill.wu@huawei.com> Mon, 22 October 2012 01:35 UTC
Return-Path: <bill.wu@huawei.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 077A221F891F for <avt@ietfa.amsl.com>; Sun, 21 Oct 2012 18:35:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.392
X-Spam-Level:
X-Spam-Status: No, score=-0.392 tagged_above=-999 required=5 tests=[AWL=-4.407, BAYES_00=-2.599, FRT_STOCK1=3.988, FRT_STOCK2=3.988, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z0BDLmJSnLCt for <avt@ietfa.amsl.com>; Sun, 21 Oct 2012 18:35:12 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7C1E021F87B1 for <avt@ietf.org>; Sun, 21 Oct 2012 18:35:11 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ALW44545; Mon, 22 Oct 2012 01:35:10 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 22 Oct 2012 02:35:07 +0100
Received: from SZXEML401-HUB.china.huawei.com (10.82.67.31) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 22 Oct 2012 02:35:10 +0100
Received: from w53375 (10.138.41.149) by szxeml401-hub.china.huawei.com (10.82.67.31) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 22 Oct 2012 09:34:57 +0800
Message-ID: <A7C07B626CC8484F974C6F911E4950E5@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: Kevin Gross <kevin.gross@avanw.com>, avt@ietf.org
References: <20121011071900.24901.9484.idtracker@ietfa.amsl.com><FCC100FC8D6B034CB88CD8173B2DA1581C6C8504@EXC-MBX03.tsn.tno.nl> <CALw1_Q3j8t7k=E3ZdCQ5Fs7xZqkbY7cukErK7h0EK7Jy7QuT+g@mail.gmail.com>
Date: Mon, 22 Oct 2012 09:34:56 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0349_01CDB038.7F61B7A0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Originating-IP: [10.138.41.149]
X-CFilter-Loop: Reflected
Subject: Re: [AVTCORE] FW: I-D Action: draft-ietf-avtcore-idms-07.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 22 Oct 2012 01:35:15 -0000
Hi, Kevin: I agree wth your comparision analysis between draft-wu-xrblock-rtcp-xr-one-way-delay and draft-ietf-avtcore-idms-07. Thank for your clarification. Regards! -Qin ----- Original Message ----- From: Kevin Gross To: avt@ietf.org Sent: Saturday, October 20, 2012 4:02 AM Subject: Re: [AVTCORE] FW: I-D Action: draft-ietf-avtcore-idms-07.txt Ray has asked me to add to his comments and assure AVTCORE members that in preparing this revision the authors also considered the following issues discussed at IETF 84: Which packet to report on - We decided to allow flexibility in which RTP packet is used to report network delay. Flexibility allows implementations to optimize reporting to get the most useful information to the MSAS quickly. We do not believe interoperability or performance is compromised by this flexibility. draft-wu-xrblock-rtcp-xr-one-way-delay - We considered whether this proposal could be used instead of the application-specific reporting mechanism proposed in our draft. We found this unsuitable for the following reasons. 1.. The IDMS proposal directly reports one-way delay of the RTP packets of the stream under control by IDMS. The one-way-delay proposal measures one-way delay using RTCP packets. RTP delay is what we care about for proper IDMS operation. RTCP packets are likely to experience different (shorter) delay due to their different (smaller) size. 2.. The one-way-delay proposal does not include a Media Stream Correlation Identifier. The MSAS requires this information to do its job. If it is not included in the XR, it will need to be signaled through another means significantly altering and complicating the system. 3.. The one-way-delay proposal does not include a presentation timestamp making the precise synchronization required by some IDMS applications difficult or impossible. Kevin Gross +1-303-447-0517 Media Network Consultant AVA Networks - www.AVAnw.com, www.X192.org On Thu, Oct 11, 2012 at 1:24 AM, Brandenburg, R. (Ray) van <ray.vanbrandenburg@tno.nl> wrote: Hi all, I've just uploaded a new version of the IDMS draft. This new version includes the comments received during the WGLC which were not yet included in the -06 version and a solution to the packet reporting issue that we discussed in Vancouver. I believe that with this version all WGLC comments have been addressed. Best regards, Ray van Brandenburg -----Original Message----- From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org Sent: donderdag 11 oktober 2012 9:19 To: i-d-announce@ietf.org Cc: avt@ietf.org Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-idms-07.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Audio/Video Transport Core Maintenance Working Group of the IETF. Title : Inter-destination Media Synchronization using the RTP Control Protocol (RTCP) Author(s) : Ray van Brandenburg Hans Stokking Oskar van Deventer Fernando Boronat Mario Montagud Kevin Gross Filename : draft-ietf-avtcore-idms-07.txt Pages : 24 Date : 2012-10-11 Abstract: This document gives information on an RTP Control Protocol (RTCP) Packet Type and RTCP Extended Report (XR) Block Type including associated Session Description Protocol (SDP) parameters for Inter- Destination Media Synchronization (IDMS). This document mandates the use of the RTCP XR Block Type 12, which is used to collect media playout information from participants in a group playing out (watching, listening, etc.) a specific RTP media stream. This RTCP XR Block Type is specified and registered with IANA by ETSI. The RTCP packet type specified by this document is used to distribute a common target playout point to which all the distributed receivers, sharing a media experience, can synchronize. Typical use cases in which IDMS is usefull are social TV, shared service control (i.e. applications where two or more geographically separated users are watching a media stream together), distance learning, networked video walls, networked loudspeakers, etc. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avtcore-idms There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avtcore-idms-07 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-idms-07 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ Audio/Video Transport Core Maintenance avt@ietf.org https://www.ietf.org/mailman/listinfo/avt This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/emaildisclaimer _______________________________________________ Audio/Video Transport Core Maintenance avt@ietf.org https://www.ietf.org/mailman/listinfo/avt ------------------------------------------------------------------------------ _______________________________________________ Audio/Video Transport Core Maintenance avt@ietf.org https://www.ietf.org/mailman/listinfo/avt
- [AVTCORE] I-D Action: draft-ietf-avtcore-idms-07.… internet-drafts
- [AVTCORE] FW: I-D Action: draft-ietf-avtcore-idms… Brandenburg, R. (Ray) van
- Re: [AVTCORE] FW: I-D Action: draft-ietf-avtcore-… Kevin Gross
- Re: [AVTCORE] FW: I-D Action: draft-ietf-avtcore-… Qin Wu