Re: [xrblock] WGLC - draft-ietf-xrblock-rtcp-xr-decodability-02

"Huangyihong (Rachel)" <rachel.huang@huawei.com> Tue, 18 December 2012 01:21 UTC

Return-Path: <rachel.huang@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACA9411E809A for <xrblock@ietfa.amsl.com>; Mon, 17 Dec 2012 17:21:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.449
X-Spam-Level:
X-Spam-Status: No, score=-5.449 tagged_above=-999 required=5 tests=[AWL=1.151, BAYES_00=-2.599, 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 MczSopvMF5+Z for <xrblock@ietfa.amsl.com>; Mon, 17 Dec 2012 17:21:12 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3348A11E80AE for <xrblock@ietf.org>; Mon, 17 Dec 2012 17:21:04 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AMO94748; Tue, 18 Dec 2012 01:21:03 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 18 Dec 2012 01:21:03 +0000
Received: from SZXEML446-HUB.china.huawei.com (10.82.67.184) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 18 Dec 2012 01:21:02 +0000
Received: from SZXEML554-MBX.china.huawei.com ([169.254.4.158]) by szxeml446-hub.china.huawei.com ([10.82.67.184]) with mapi id 14.01.0323.003; Tue, 18 Dec 2012 09:20:58 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: WGLC - draft-ietf-xrblock-rtcp-xr-decodability-02
Thread-Index: Ac3OL9JJ1DarvDWNSB6u3iE3PFj7mQLCTODgAOEtf8A=
Date: Tue, 18 Dec 2012 01:20:57 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB44D68C6C@SZXEML554-MBX.china.huawei.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA024828@AZ-FFEXMB04.global.avaya.com> <9904FB1B0159DA42B0B887B7FA8119CA03F8AC@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA03F8AC@AZ-FFEXMB04.global.avaya.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.104]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [xrblock] WGLC - draft-ietf-xrblock-rtcp-xr-decodability-02
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 01:21:16 -0000

Hi Dan,

Sorry for so late reply. Please see inline.

Best Regards!
Rachel

-----Original Message-----
From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
Sent: Thursday, December 13, 2012 10:06 PM
To: xrblock@ietf.org
Subject: Re: [xrblock] WGLC - draft-ietf-xrblock-rtcp-xr-decodability-02

Hi,

I have a few comments concerning this I-D: 

1. This document relies on ETSI work. Should we not send it to ETSI for review? Is the group were TR 101 290 developped still active? 

[Rachel]: TR101.290 has been published for 13 years. I suspect the group who produce this document has already been closed down.

2. In the definition of the Reserved field: 

>     This field is reserved for future definition.  In the absence of
      such a definition, the bits in this field MUST be set to zero and
      SHOULD be ignored by the receiver.

Why is the behavior of the receiver defined as a SHOULD and not a MUST?

[Rachel]: I agree with you that it should be "MUST".

3. In the definition of the block length field: 

>     The constant 11, in accordance with the definition of this field
      in Section 3 of RFC 3611.

What is the definition of the receiver if a value other than 11 is received? 

[Rachel]: Good point. We propose to add following texts:

"The block MUST be discarded if the block length is set to a different value.
"

4. For all count fields starting with TS_sync_loss_count - there is no definition or reference about what each metric means, and how the measurments or computation of the values are to be performed. Please provide this information for each field, I guess references to the respective sections in TR 101 290 would be fine. 

[Rachel]:  Okay, we will fix this based on your suggestion.

5. Usage of acronyms (excepting very obvious ones) is discouraged in the title of the documents. Please expand TS - Transport Stream in the title

[Rachel]: Okay.

6. Typo to fix in section 3: s/implentations/implementations/

[Rachel]: Okay.

Regards,

Dan


> -----Original Message-----
> From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On
> Behalf Of Romascanu, Dan (Dan)
> Sent: Thursday, November 29, 2012 2:48 PM
> To: xrblock@ietf.org
> Subject: [xrblock] WGLC - draft-ietf-xrblock-rtcp-xr-decodability-02
> 
> 
> This is a Working Group Last Call for http://www.ietf.org/id/draft-ietf-
> xrblock-rtcp-xr-decodability-02.txt.
> 
> Please read and review this document, and send your comments, questions
> and concerns to the WG list before December 13, 2012. If you have no
> comments and you believe that the document is ready for submission to
> the IESG as a Standards Track document please send a short message as
> well to help us in determining the level of review and consensus.
> 
> Thanks and Regards,
> 
> Dan
> 
> 
> 
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock
_______________________________________________
xrblock mailing list
xrblock@ietf.org
https://www.ietf.org/mailman/listinfo/xrblock