Re: [xrblock] Last Call Review: draft-ietf-xrblock-rtcp-xr-post-repair-loss-count-07

"Huangyihong (Rachel)" <rachel.huang@huawei.com> Fri, 26 December 2014 01:04 UTC

Return-Path: <rachel.huang@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D61C1A1B1A; Thu, 25 Dec 2014 17:04:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AkkdmrDUBHWL; Thu, 25 Dec 2014 17:04:32 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D1FA1A1B17; Thu, 25 Dec 2014 17:04:31 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQM25267; Fri, 26 Dec 2014 01:04:29 +0000 (GMT)
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 26 Dec 2014 01:04:27 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.169]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.03.0158.001; Fri, 26 Dec 2014 09:04:22 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>, Gen Art <gen-art@ietf.org>, "draft-ietf-xrblock-rtcp-xr-post-repair-loss-count.all@tools.ietf.org" <draft-ietf-xrblock-rtcp-xr-post-repair-loss-count.all@tools.ietf.org>, "xrblock-chairs@tools.ietf.org" <xrblock-chairs@tools.ietf.org>, "xrblock@ietf.org" <xrblock@ietf.org>, Dan Romascanu <dromasca@avaya.com>
Thread-Topic: Last Call Review: draft-ietf-xrblock-rtcp-xr-post-repair-loss-count-07
Thread-Index: AQHQH+xxlg+sz2nR3UKYPgRhyojsNJyfzZPg///+0YCAAULTcA==
Date: Fri, 26 Dec 2014 01:04:22 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB862A1C01@nkgeml501-mbs.china.huawei.com>
References: <549B796F.30802@gmail.com> <51E6A56BD6A85142B9D172C87FC3ABBB862A1ADE@nkgeml501-mbs.china.huawei.com> <549C1531.2070602@gmail.com>
In-Reply-To: <549C1531.2070602@gmail.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.144]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/xrblock/iB97h6iQPVsa691KRG43BL0DU28
Subject: Re: [xrblock] Last Call Review: draft-ietf-xrblock-rtcp-xr-post-repair-loss-count-07
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.15
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, 26 Dec 2014 01:04:34 -0000

Hi Tom,

You're right. I'll fix it according to your suggestion.

BR,
Rachel


> -----Original Message-----
> From: Tom Taylor [mailto:tom.taylor.stds@gmail.com]
> Sent: Thursday, December 25, 2014 9:46 PM
> To: Huangyihong (Rachel); Gen Art;
> draft-ietf-xrblock-rtcp-xr-post-repair-loss-count.all@tools.ietf.org;
> xrblock-chairs@tools.ietf.org; xrblock@ietf.org; Dan Romascanu
> Subject: Re: Last Call Review:
> draft-ietf-xrblock-rtcp-xr-post-repair-loss-count-07
> 
> Replies with [PTT] below.
> 
> >>
> >> 4) Appendix A: The "Units of Measurement" are packets.
> >
> > [Rachel]: According to RFC6390, Section 5.4.5, there's an example to show
> how to define a metric. Here's how it defines the "Units of Measurement":
> > "
> > Units of Measurement:  This metric is expressed as a fixed-point number
> with the binary point at the left edge of the field.  For example, a metric value
> of 12 means a loss rate of approximately 5%.
> > "
> > I consulted it to specify mine.
> >
> [PTT] But what you are measuring according to your description and text in the
> preceding body of the document is number of packets, not a loss rate as shown
> in the RFC 6390 example. So what you should say is:
> 
>    "This metric is expressed as a 16-bit unsigned integer giving the number of
> packets ...".
> >>