[xrblock] Review of Delay XR Block draft

Qin Wu <bill.wu@huawei.com> Tue, 11 October 2011 13:10 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 A84F721F84CD for <xrblock@ietfa.amsl.com>; Tue, 11 Oct 2011 06:10:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.661
X-Spam-Level:
X-Spam-Status: No, score=-4.661 tagged_above=-999 required=5 tests=[AWL=0.184, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yDrDQryxCDuD for <xrblock@ietfa.amsl.com>; Tue, 11 Oct 2011 06:10:29 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 3233F21F8B13 for <xrblock@ietf.org>; Tue, 11 Oct 2011 06:10:29 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSW003NVKL8Z3@szxga05-in.huawei.com> for xrblock@ietf.org; Tue, 11 Oct 2011 21:10:20 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSW007HSKL79H@szxga05-in.huawei.com> for xrblock@ietf.org; Tue, 11 Oct 2011 21:10:20 +0800 (CST)
Received: from szxeml205-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AEJ28445; Tue, 11 Oct 2011 21:10:19 +0800
Received: from SZXEML411-HUB.china.huawei.com (10.82.67.138) by szxeml205-edg.china.huawei.com (172.24.2.57) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 11 Oct 2011 21:10:17 +0800
Received: from w53375q (10.138.41.130) by szxeml411-hub.china.huawei.com (10.82.67.138) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 11 Oct 2011 21:10:09 +0800
Date: Tue, 11 Oct 2011 21:10:08 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: xrblock@ietf.org
Message-id: <049D3F8615A04A9AB2B6BA5E2A7D4700@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: multipart/alternative; boundary="Boundary_(ID_Aq0QnBuRpojdML7yu0/IUQ)"
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <E7587851C5284B198B63F64C76FDA3FA@china.huawei.com>
Subject: [xrblock] Review of Delay XR Block draft
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, 11 Oct 2011 13:10:30 -0000

I like to see this draft moving forward.
Here is my review to the Delay XR Block draft maintained at
http://tools.ietf.org/html/draft-ietf-avt-rtcp-xr-delay-02
1. Section 1
Remove th last pragraph since Measurement Identity block is not well defined yet.

2. Section 2
Remove the section 2 since the terms Numeric format is not used. and the Numeric format
definition should be moved to PDV XR Block draft with modification as follows:
"
2.  Definitions


      This report block makes use of binary fractions.  The terminology

      used is

   Numeric formats  S X:Y


      where S indicates a two's complement signed representation, X the

      number of bits prior to the decimal place and Y the number of bits

      after the decimal place.


      Hence 8:8 represents an unsigned number in the range 0.0 to

      255.996 with a granularity of 0.0039.  S7:8 would represent the

      range -128.000 to +127.996. 0:16 represents a proper binary

      fraction with range


      0.0 to 1 - 1/65536 = 0.9999847


      though note that use of flag values at the top of the numeric

      range slightly reduces this upper limit.  For example, if the 16-

      bit values 0xfffe and 0xffff are used as flags for "over-range"

      and "unavailable" conditions, a 0:16 quantity has range
"

3. Section 2
Replace the removed section 2 with new section 2 as follows:
"
2.  Terminology

2.1.  Standards Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].
"
This is becos reference RFC2119 in the reference section is not cited.

4. Section 3.1, figure 1
Add SSRC field next to Block Length field in the format of Report Block, since there was consesus to 
use SSRC to identify and correlate and group participants between reports.

5. Section 3.1 figure 1
Remove tag field from the format  of Report Block in the figure 1 since there was consesus to use SSRC to replace tag.

6. Section 3.1
Remove
 "
      Numerical values for both these intervals are provided in the

      Measurement Identifier block referenced by the tag field below.

"
from Interval Metric flag defintion.

7. Section 3.1
Add a defintion of  SSRC field after the figure 1.

8. Section 3.1

Remove the definition of tag field after the figure 1.

9. Section 9.1
Remove reference to  [MEASIDENT]  since Measurement Identity block is not needed in this draft.


Regards!
-Qin