Re: [xrblock] Unclear paragraph in draft-ietf-xrblock-rtcp-xr-discard-13

Qin Wu <bill.wu@huawei.com> Mon, 20 May 2013 06:20 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 B007F21F8FDF for <xrblock@ietfa.amsl.com>; Sun, 19 May 2013 23:20:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 osL04Z04VVmg for <xrblock@ietfa.amsl.com>; Sun, 19 May 2013 23:20:33 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5FC5D21F8FC4 for <xrblock@ietf.org>; Sun, 19 May 2013 23:20:33 -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 ASY51341; Mon, 20 May 2013 06:20:31 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 20 May 2013 07:20:26 +0100
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 20 May 2013 07:20:29 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.43]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.01.0323.007; Mon, 20 May 2013 14:20:23 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Thread-Topic: [xrblock] Unclear paragraph in draft-ietf-xrblock-rtcp-xr-discard-13
Thread-Index: AQHOUvKzqRb0P9qqIUiuhsYFKntj4ZkNQ07QgAAFUUD//8higIAAjH8g
Date: Mon, 20 May 2013 06:20:22 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA43B300C2@nkgeml501-mbs.china.huawei.com>
References: <5196160D.2060105@ericsson.com> <B8F9A780D330094D99AF023C5877DABA43B2F016@nkgeml501-mbs.china.huawei.com> <5199BA9B.3020509@ericsson.com>
In-Reply-To: <5199BA9B.3020509@ericsson.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.149]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "xrblock@ietf.org" <xrblock@ietf.org>
Subject: Re: [xrblock] Unclear paragraph in draft-ietf-xrblock-rtcp-xr-discard-13
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: Mon, 20 May 2013 06:20:42 -0000

Hi, Gonzalo:
Your proposed change looks good to me, I will implement this change into this draft.
Thanks.

Regards!
-Qin
-----Original Message-----
From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com] 
Sent: Monday, May 20, 2013 1:55 PM
To: Qin Wu
Cc: xrblock@ietf.org; Glen Zorn
Subject: Re: [xrblock] Unclear paragraph in draft-ietf-xrblock-rtcp-xr-discard-13

Hi Qin,

thanks for the clarification. Additionally, I would fix the language of
that paragraph (prepositions, articles, verbs, typos, ...). Something
along these lines:

   When a Discard Count Metrics Block is sent together with a Burst Gap
   Discard Metrics Block (defined in [BGDISCARD]) to the media sender or
   RTP based network management system, the information carried in the
   Discard Count Metrics Block and the Burst Gap Discard Metrics Block
   allows systems receiving the blocks to calculate burst gap
   summary statistics (e.g., the gap discard rate).

Feel free to edit the text if there is something you do not like.

Cheers,

Gonzalo

On 20/05/2013 4:15 AM, Qin Wu wrote:
> One small change to the proposed text:
> s/systems receiving the report/systems receiving the blocks
> 
> -----Original Message-----
> From: Qin Wu 
> Sent: Monday, May 20, 2013 9:03 AM
> To: 'Gonzalo Camarillo'; xrblock@ietf.org
> Cc: 'Glen Zorn'
> Subject: RE: [xrblock] Unclear paragraph in draft-ietf-xrblock-rtcp-xr-discard-13
> 
> Hi, Gonzalo:
> We believe you are referring to "them" in this paragraph not clear.
> "them" is corresponding to "media sender or RTP based network management system"
> in this paragraph.
> So how about the following change:
> OLD TEXT:
> "
>    In case of Discard Count Metrics Block sent together with Burst Gap
>    Discard Metrics Block defined in [BGDISCARD] to the media sender or
>    RTP based network management system, information carried in the
>    Discard Count Metrics Block and Burst Gap Discard Metrics Block
>    allows them calculate the some bust gap summary statistics, e.g., gap
>    discard rate.
> "
> NEW TEXT:
> "
>    In case of Discard Count Metrics Block sent together with Burst Gap
>    Discard Metrics Block defined in [BGDISCARD] to the media sender or
>    RTP based network management system, information carried in the
>    Discard Count Metrics Block and Burst Gap Discard Metrics Block
>    allows systems receiving the report to calculate the some bust gap 
>    summary statistics, e.g., gap discard rate.
> "
> Hope this clarifies.
> 
> Regards!
> -Qin & Glen
> -----Original Message-----
> From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On Behalf Of Gonzalo Camarillo
> Sent: Friday, May 17, 2013 7:36 PM
> To: xrblock@ietf.org
> Subject: [xrblock] Unclear paragraph in draft-ietf-xrblock-rtcp-xr-discard-13
> 
> Hi,
> 
> the following paragraph, in draft-ietf-xrblock-rtcp-xr-discard-13, is a
> bit unclear:
> 
>    In case of Discard Count Metrics Block sent together with Burst Gap
>    Discard Metrics Block defined in [BGDISCARD] to the media sender or
>    RTP based network management system, information carried in the
>    Discard Count Metrics Block and Burst Gap Discard Metrics Block
>    allows them calculate the some bust gap summary statistics, e.g., gap
>    discard rate.
> 
> Authors, could you please fix it (i.e., clarify it) so that I can
> initiate an IETF LC on this draft?
> 
> Thanks,
> 
> Gonzalo
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock
>