Re: [xrblock] WGLC for draft-ietf-xrblock-rtcweb-rtcp-xr-metrics

Colin Perkins <csp@csperkins.org> Mon, 25 January 2016 12:51 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 677281A9069 for <xrblock@ietfa.amsl.com>; Mon, 25 Jan 2016 04:51:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham
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 On5NpkdbXaUO for <xrblock@ietfa.amsl.com>; Mon, 25 Jan 2016 04:51:32 -0800 (PST)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85DE31A9068 for <xrblock@ietf.org>; Mon, 25 Jan 2016 04:51:32 -0800 (PST)
Received: from [130.209.247.112] (port=56332 helo=mangole.dcs.gla.ac.uk) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1aNgcC-0005jM-Je; Mon, 25 Jan 2016 12:51:30 +0000
Content-Type: multipart/alternative; boundary="Apple-Mail=_E890FA1A-EE51-4324-8E07-12E49FC65954"
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <C13E5AD5-87FE-4E59-BC2A-CD3C4404BB48@ntt-at.com>
Date: Mon, 25 Jan 2016 12:51:23 +0000
Message-Id: <36FCAFB0-AEB8-4230-BA95-2BCB0338D3B6@csperkins.org>
References: <C13E5AD5-87FE-4E59-BC2A-CD3C4404BB48@ntt-at.com>
To: Shida Schubert <shida@ntt-at.com>
X-Mailer: Apple Mail (2.3112)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold = On =
Archived-At: <http://mailarchive.ietf.org/arch/msg/xrblock/E6eYcCMijARa8YKC1jIIfVLDmko>
Cc: xrblock <xrblock@ietf.org>
Subject: Re: [xrblock] WGLC for draft-ietf-xrblock-rtcweb-rtcp-xr-metrics
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.15
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, 25 Jan 2016 12:51:34 -0000

> On 20 Jan 2016, at 04:31, Shida Schubert <shida@ntt-at.com> wrote:
> 
> This message starts a Working Group Last Call for the draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-02.txt. 
> 
> http://tools.ietf.org/id/draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-02.txt <http://tools.ietf.org/id/draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-02.txt>
> 
> Even if you have no questions, comments or concern, if you have read the draft and agree that it’s ready for submission to IESG as a Standard Track, please send a message to the list indicating this. 
> 
> Obviously if you have any issues or questions please submit it to the list, if you are highlighting issues suggestions to fix the issues is always helpful.


I have two comments:

1) The draft uses RFC 2119 terms in lower case in a number of places. I think it would be clearer if these were changed to upper case where the intent is to use normative language, and rephrased to use alternative terms otherwise. 

2) The draft has a reasonable list of candidate metrics, but does not make a clear recommendation which metrics ought to be implemented. Is the intent that a WebRTC end-point implementor picks an arbitrary subset of these, or that all the metrics are implemented? If a subset is to be implemented, which subset? What are the most important to implement? Adding some further normative language would probably help clarify.

That said, I have no objection to sending this draft to the IESG for publication. It suggests a reasonable set of metrics, and is well enough written. 

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