Re: [xrblock] WGLC fordraft-ietf-xrblock-rtcp-xr-burst-gap-discard-04.txt

Colin Perkins <csp@csperkins.org> Tue, 24 July 2012 08:59 UTC

Return-Path: <csp@csperkins.org>
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 81F1021F8601 for <xrblock@ietfa.amsl.com>; Tue, 24 Jul 2012 01:59:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.578
X-Spam-Level:
X-Spam-Status: No, score=-103.578 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 btjRrKkd89ht for <xrblock@ietfa.amsl.com>; Tue, 24 Jul 2012 01:59:51 -0700 (PDT)
Received: from lon1-msapost-2.mail.demon.net (lon1-msapost-2.mail.demon.net [195.173.77.181]) by ietfa.amsl.com (Postfix) with ESMTP id B79A021F85FC for <xrblock@ietf.org>; Tue, 24 Jul 2012 01:59:51 -0700 (PDT)
Received: from starkperkins.demon.co.uk ([80.176.158.71] helo=[192.168.0.11]) by lon1-post-2.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1Stay6-0005Gx-bV; Tue, 24 Jul 2012 08:59:50 +0000
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset="iso-8859-1"
From: Colin Perkins <csp@csperkins.org>
X-Priority: 3
In-Reply-To: <6DBD074E8D804E7CB6D977F9385C488A@china.huawei.com>
Date: Tue, 24 Jul 2012 09:59:49 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F1481A59-F216-4EA9-B894-850EC460CF82@csperkins.org>
References: <EDC652A26FB23C4EB6384A4584434A0407D54087@307622ANEX5.global.avaya.com> <EDB9A743-A51D-4872-B35A-49BC73421719@csperkins.org> <6DBD074E8D804E7CB6D977F9385C488A@china.huawei.com>
To: Qin Wu <bill.wu@huawei.com>
X-Mailer: Apple Mail (2.1278)
Cc: xrblock <xrblock@ietf.org>
Subject: Re: [xrblock] WGLC fordraft-ietf-xrblock-rtcp-xr-burst-gap-discard-04.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: Tue, 24 Jul 2012 08:59:52 -0000

On 24 Jul 2012, at 03:17, Qin Wu wrote:
> ----- Original Message ----- 
> From: "Colin Perkins" <csp@csperkins.org>
> To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> Cc: "xrblock" <xrblock@ietf.org>
> Sent: Monday, July 23, 2012 6:25 PM
> Subject: Re: [xrblock] WGLC fordraft-ietf-xrblock-rtcp-xr-burst-gap-discard-04.txt
> 
> 
>> Dan,
>> 
>> On 11 Jul 2012, at 15:48, Romascanu, Dan (Dan) wrote:
>>> This message initiates a Working Group Last Call for the Internet-Draft
>>> ' RTCP XR Report Block for Burst/Gap Discard metric Reporting '. Please
>>> read and send your comments, questions and concerns to the WG mail list
>>> before 7/25 COB. 
>>> 
>>> If you read the document and you believe it's just fine and ready for
>>> submission to the IESG please send a message stating this. 
>>> 
>>> The document is available at
>>> http://www.ietf.org/id/draft-ietf-xrblock-rtcp-xr-burst-gap-discard-04.txt. 
>> 
>> 
>> I've read this draft, and have no objection to it progressing. However, it might be useful to provide some clarification on how to calculate a sampled the burst/gap discard metric, since it's not obvious to me how this is derived.
> 
> [Qin]: I think burst gap discard draft does not support reporting sample metric since burst/gap discard metric is not measured at a time instant but over one or several reporting intervals. I can add the following statement to clarify this:
> "
>      In this document, Burst/Gap Discard Metric is not measured at a particular
>      time instant but over one or several reporting intervals.
>      Therefore Burst/Gap Discard Metric MUST not be chosen as Sampled
>      Metric.
> " 

Assuming you mean "MUST NOT" rather than "MUST not", fine. 


-- 
Colin Perkins
http://csperkins.org/