Re: [xrblock] Mirja Kühlewind's Discuss on draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-09: (with DISCUSS and COMMENT)

"Huangyihong (Rachel)" <rachel.huang@huawei.com> Mon, 21 May 2018 01:47 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 4EF0D120227; Sun, 20 May 2018 18:47:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 E_AwzKGM1jXj; Sun, 20 May 2018 18:47:32 -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 5838B1201F2; Sun, 20 May 2018 18:47:32 -0700 (PDT)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 08D424328275A; Mon, 21 May 2018 02:47:29 +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; Mon, 21 May 2018 02:47:29 +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; Mon, 21 May 2018 09:47:25 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: Mirja Kühlewind <ietf@kuehlewind.net>, 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: Mirja Kühlewind's Discuss on draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-09: (with DISCUSS and COMMENT)
Thread-Index: AQHT7pposR5iteLPXEu7lJ3TlZHi0qQ5YqIQ
Date: Mon, 21 May 2018 01:47:25 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB9C6EE207@nkgeml513-mbx.china.huawei.com>
References: <152664249428.1496.6832537943897538630.idtracker@ietfa.amsl.com>
In-Reply-To: <152664249428.1496.6832537943897538630.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/gAft09K1PB5HEOiOzdGc54wLTCw>
Subject: Re: [xrblock] Mirja Kühlewind's Discuss on draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-09: (with DISCUSS and 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: Mon, 21 May 2018 01:47:35 -0000

Hi Mirja,

Thanks for the comments. Please see inline.

BR,
Rachel

> -----Original Message-----
> From: Mirja Kühlewind [mailto:ietf@kuehlewind.net]
> Sent: Friday, May 18, 2018 7:22 PM
> 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: Mirja Kühlewind's Discuss on
> draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-09: (with DISCUSS and COMMENT)
> 
> Mirja Kühlewind has entered the following ballot position for
> draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-09: Discuss
> 
> 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/
> 
> 
> 
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> For the AD: Please note that the intended status in the datatracker is
> "Proposed Standard" while the doc itself says "Informational". After reading
> the doc, I would find informational correct. However, please clarify what the
> intended status is supposed to be!
> 

[Rachel]: It intends to be informational but I don't know what happened in the datatracker. I'll leave Ben or others to respond.

> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Thanks for the well-written document. A few comments mostly on references:
> 
> - Maybe also provide an (informative) reference to
> draft-ietf-rtcweb-overview-19 on the first occurrence of WebRTC...?

[Rachel]: Make sense to me. Will do in the next version.

> 
> - Is ReportGroup defined in another RFC? If so, please provide reference in
> ther terminology section.
> 

[Rachel]: It's only defined here.

> - Maybe provide (informative) references for Mean Opinion Score (MoS) and
> Media
> Delivery Index (MDI), as well as "Media Loss Rate (MLR) of MDI" maybe.

[Rachel]: Will do in the next version.

> 
> - It seems to me that at least [W3C.WD-webrtc-stats-20161214] should be a
> normative reference.

[Rachel]: Can I know why? We put it in the informative reference was because this work only provides background of what happening in W3C, we didn't refer to the technologies in that work.

> 
> - I wonder if it would make sense to refer to some of the IPPM RFCs that define
> these or similar metrics?
> 

[Rachel]: I don't know. This document is only talking about the metrics in RTP layer. It didn't refer to any metrics in IPPM. So what kind of ippm metrics should be listed here in your mind?