Re: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06.txt

Qin Wu <bill.wu@huawei.com> Fri, 21 December 2012 06:11 UTC

Return-Path: <bill.wu@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 D31DA21F8991 for <xrblock@ietfa.amsl.com>; Thu, 20 Dec 2012 22:11:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.727
X-Spam-Level:
X-Spam-Status: No, score=-4.727 tagged_above=-999 required=5 tests=[AWL=0.119, BAYES_00=-2.599, 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 Stkzfd-r8Z6A for <xrblock@ietfa.amsl.com>; Thu, 20 Dec 2012 22:11:06 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 40F3021F88B4 for <xrblock@ietf.org>; Thu, 20 Dec 2012 22:11:05 -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 AMR89687; Fri, 21 Dec 2012 06:11:03 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 21 Dec 2012 06:10:28 +0000
Received: from SZXEML453-HUB.china.huawei.com (10.82.67.196) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 21 Dec 2012 14:10:35 +0800
Received: from w53375 (10.138.41.149) by SZXEML453-HUB.china.huawei.com (10.82.67.196) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 21 Dec 2012 14:10:28 +0800
Message-ID: <2E885C53170048A5A0AA54F4237990F3@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, <xrblock@ietf.org>
References: <9904FB1B0159DA42B0B887B7FA8119CA032A09@AZ-FFEXMB03.global.avaya.com> <9904FB1B0159DA42B0B887B7FA8119CA045014@AZ-FFEXMB04.global.avaya.com>
Date: Fri, 21 Dec 2012 14:10:27 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
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: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06.txt
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: Fri, 21 Dec 2012 06:11:07 -0000

Thank you, we will fix these in the update.

Regards!
-Qin
----- Original Message ----- 
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <xrblock@ietf.org>
Sent: Thursday, December 20, 2012 10:05 PM
Subject: Re: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06.txt


> Hi,
> 
> The document is in good shape. I have however a number of comments and questions, please address them.
> 
> 1. In Section 1.1, the second sentence in the second paragraph has a broken syntax. I suggest: 
> 
> s/ Burst/Gap metrics are typically used in Cumulative reports however MAY be used in Interval reports./ Burst/Gap metrics are typically used in Cumulative reports, however they also MAY be used in Interval reports./
> 
> 2. It would be good to provide an example or a reference to the 'stream repair means' mentioned in section 1.4.
> 
> 3. In Section 3.1 at the Interval Metric flag definition - I guess that the last phrase means 'Sampled Value (I=01) MUST not be used.' 
> 
> One more thing is missing here - what is the behavior of the receiver when receiving I=01 or I=00 which is undefined? I believe these need to be specified. 
> 
> 4. The behavior of the receiver if a report with block length different than 5 is received is not defined. Please define. 
> 
> 5. In the definitions of Sum of Burst Durations, Packets lost in bursts, and Total packets expected in bursts, we have:
> 
>      If the measured value exceeds 0xFFFFFD, the value 0xFFFFFE SHOULD
>      be reported to indicate an over-range measurement.  If the
>      measurement is unavailable, the value 0xFFFFFF SHOULD be reported.  
> 
> What is the reasons that these are SHOULD? If there are exceptions, please specify these, if not s/SHOULD/MUST/
> 
> 6. In the definitions of Number of bursts, we have:
> 
>      If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD
>      be reported to indicate an over-range measurement.  If the
>      measurement is unavailable, the value 0xFFFF SHOULD be reported.  
> 
> What is the reasons that these are SHOULD? If there are exceptions, please specify these, if not s/SHOULD/MUST/
> 
> 7. In the definitions of Sum of Squares of Burst Durations, we have:
> 
>      If the measured value exceeds 0xFFFFFFFD, the value 0xFFFFFFFE SHOULD
>      be reported to indicate an over-range measurement.  If the
>      measurement is unavailable, the value 0xFFFFFFFF SHOULD be reported.  
> 
> What is the reasons that these are SHOULD? If there are exceptions, please specify these, if not s/SHOULD/MUST/
> 
> 8. In Section 3.3: 
> 
> s/These metrics provides information/These metrics provide information/
> 
> 9. In Section 4 please expand PCM.
> 
> 
> Thanks and Regards,
> 
> Dan
> 
> 
>> -----Original Message-----
>> From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On
>> Behalf Of Romascanu, Dan (Dan)
>> Sent: Thursday, December 06, 2012 2:20 PM
>> To: xrblock@ietf.org
>> Subject: [xrblock] WGLC for draft-ietf-xrblock-rtcp-xr-burst-gap-loss-
>> 06.txt
>> 
>> This is a (second) Working Group Last Call for http://www.ietf.org/id/
>> draft-ietf-xrblock-rtcp-xr-burst-gap-loss-06.txt.
>> 
>> Please read and review this document, and send your comments, questions
>> and concerns to the WG list before December 20, 2012. If you read the
>> document, 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