Re: [xrblock] Genart telechat review of draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-09

Robert Sparks <rjsparks@nostrum.com> Tue, 01 May 2018 16:21 UTC

Return-Path: <rjsparks@nostrum.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 BD0A11241F5; Tue, 1 May 2018 09:21:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level:
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, 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 VBwThUsWq-4g; Tue, 1 May 2018 09:21:49 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F5531200C1; Tue, 1 May 2018 09:21:49 -0700 (PDT)
Received: from unescapeable.local ([47.186.17.148]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w41GLehS044874 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 1 May 2018 11:21:41 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [47.186.17.148] claimed to be unescapeable.local
To: "Huangyihong (Rachel)" <rachel.huang@huawei.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Cc: "draft-ietf-xrblock-rtcweb-rtcp-xr-metrics.all@ietf.org" <draft-ietf-xrblock-rtcweb-rtcp-xr-metrics.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "xrblock@ietf.org" <xrblock@ietf.org>
References: <51E6A56BD6A85142B9D172C87FC3ABBB9C6BB7C2@nkgeml513-mbs.china.huawei.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <b099803f-99e2-a3bd-ced3-e5ecac3a7155@nostrum.com>
Date: Tue, 01 May 2018 11:21:39 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <51E6A56BD6A85142B9D172C87FC3ABBB9C6BB7C2@nkgeml513-mbs.china.huawei.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/xrblock/pOUgCVWiFph2eOJDSBAouWSXjvY>
Subject: Re: [xrblock] Genart telechat review of draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-09
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, 01 May 2018 16:21:52 -0000

Sorry for not seeing your earlier response (and for not spotting the 
change in the diff correctly).

Yes, this change is sufficient to address my comments.

RjS




On 5/1/18 11:15 AM, Huangyihong (Rachel) wrote:
> Hi Robert,
>
> I believe I have responded you in February, if you check the mail archive of xrblock.
>
> Follows was my response before. And I uploaded a new version to reflect that since I didn't get your further email. Sorry for assuming that you received my response.
>
> "
>      Hi Robert,
>
>      Thanks for the comment.
>
>       I propose to change the last paragraph of 5.2.2 from
>
>      "
>     The following metrics can also be considered for WebRTC's Statistics
>     API: number of discarded key frames, number of lost key frames,
>     number of discarded derived frames, number of lost derived frames.
>     These metrics can be used to calculate Media Loss Rate (MLR) of MDI.
>     Details of the definition of these metrics are described in
>     [RFC7003].  Additionally, the metric provides the rendered frame
>     rate, an important parameter for quality estimation.
>      "
>
>      To
>
>      "
>       The metrics in this category includes
>      : number of discarded key frames, number of lost key frames,
>     number of discarded derived frames, number of lost derived frames.
>     These metrics can be used to calculate Media Loss Rate (MLR) of MDI.
>     Details of the definition of these metrics are described in
>     [RFC7003].  Additionally, the metric provides the rendered frame
>     rate, an important parameter for quality estimation.
>      "
>
>      This change is to just talk about the metrics itself, so as to avoid any confusion that readers may have. The fact is that the W3C has already included the metrics, and made an informational reference to this document.
>
>      If the proposal looks good to you, we'll reflect it in the new version.
>
> "
>
> BR,
> Rachel
>
> -----邮件原件-----
> 发件人: Robert Sparks [mailto:rjsparks@nostrum.com]
> 发送时间: 2018年5月2日 0:04
> 收件人: gen-art@ietf.org
> 抄送: draft-ietf-xrblock-rtcweb-rtcp-xr-metrics.all@ietf.org; ietf@ietf.org; xrblock@ietf.org
> 主题: Genart telechat review of draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-09
>
> Reviewer: Robert Sparks
> Review result: Ready with Nits
>
> I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please wait for direction from your document shepherd or AD before posting a new version of the draft.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-09
> Reviewer: Robert Sparks
> Review Date: 2018-05-01
> IETF LC End Date: 2018-02-23
> IESG Telechat date: 2018-05-24
>
> Summary: Ready for publication as an Informational RFC, but with nits to consider before publication
>
> Note that this is identical to my last call review, which I don't think I've seen a response to.
>
> The document argues to include things in the W3C statistics API in the last paragraph of 5.2.2. Section 7 seems to say those have been included already. It would be good to rework both of these mentions to reflect what's true at the time of the publication of the RFC, in a way that the text will make sense when read years from now.
>