Re: [xrblock] Spencer Dawkins' No Objection on draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-09: (with COMMENT)

"Huangyihong (Rachel)" <rachel.huang@huawei.com> Tue, 22 May 2018 02:59 UTC

Return-Path: <rachel.huang@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 0C53E120724; Mon, 21 May 2018 19:59:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 kA5ZSesLPngY; Mon, 21 May 2018 19:59:50 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EB85120047; Mon, 21 May 2018 19:59:50 -0700 (PDT)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id AEFC0288B4692; Tue, 22 May 2018 03:59:47 +0100 (IST)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.382.0; Tue, 22 May 2018 03:59:48 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.192]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0382.000; Tue, 22 May 2018 10:59:42 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-xrblock-rtcweb-rtcp-xr-metrics@ietf.org" <draft-ietf-xrblock-rtcweb-rtcp-xr-metrics@ietf.org>, Shida Schubert <shida.at.ietf@gmail.com>, "xrblock-chairs@ietf.org" <xrblock-chairs@ietf.org>, "shida.at.ietf@gmail.com" <shida.at.ietf@gmail.com>, "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: Spencer Dawkins' No Objection on draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-09: (with COMMENT)
Thread-Index: AQHT8TiN/kF/2KF0CECr36LMlfC3paQ7Bbmw
Date: Tue, 22 May 2018 02:59:41 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB9C6F78CE@nkgeml513-mbx.china.huawei.com>
References: <152693032470.23757.12749012281387776509.idtracker@ietfa.amsl.com>
In-Reply-To: <152693032470.23757.12749012281387776509.idtracker@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.134.153.152]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/xrblock/97BRFo_z0Li0faZLWe7bnUFkAec>
Subject: Re: [xrblock] Spencer Dawkins' No Objection on draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-09: (with COMMENT)
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 22 May 2018 02:59:52 -0000

Hi Spencer,

Thanks for your comments. Please see inline.

BR,
Rachel

> -----Original Message-----
> From: Spencer Dawkins [mailto:spencerdawkins.ietf@gmail.com]
> Sent: Tuesday, May 22, 2018 3:19 AM
> To: The IESG
> Cc: draft-ietf-xrblock-rtcweb-rtcp-xr-metrics@ietf.org; Shida Schubert;
> xrblock-chairs@ietf.org; shida.at.ietf@gmail.com; xrblock@ietf.org
> Subject: Spencer Dawkins' No Objection on
> draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-09: (with COMMENT)
> 
> Spencer Dawkins has entered the following ballot position for
> draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-09: No Objection
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-xrblock-rtcweb-rtcp-xr-metrics/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Thanks for producing this document.
> 
> I did have one comment (and I apologize in advance that this is a particular
> hot button for me).
> 
> I understand that you can do things with these metrics that you can't do with
> previous metrics, but I wish there was a clearer description of "if you want to
> understand X, you should implement this metric" earlier in the document. The
> impression the reader is left with, is "if you're doing RTCWeb, you should
> implement this metric", but I'm guessing that at least some of these metrics
> would be useful for people who weren't doing RTCWeb, but need to measure
> something that people who are doing RTCWeb also need to measure, and if
> that's
> true, a short section that helped them figure that out would be helpful.
> 

[Rachel]: Would it be helpful if we add a new short paragraph in the section 1, after the 3rd para and before the last one, as following

"
Standards such as "RTP Control Protocol Extended Reports (RTCP XR)" [RFC3611] as well as other extensions standardized in the XRBLOCK working group have been produced for the purpose of collecting and reporting performance metrics from RTP endpoint devices that can be used to have a end-to-end service visibility and measure the delivering quality in various RTP services. These metrics are able to complement those in [RFC3550].
"