[ippm] AD review of draft-ietf-ippm-initial-registry-11

Mirja Kuehlewind <ietf@kuehlewind.net> Tue, 27 August 2019 15:46 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3ABBD120145; Tue, 27 Aug 2019 08:46:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 48Zm5hyAtICD; Tue, 27 Aug 2019 08:46:44 -0700 (PDT)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (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 110AF12011B; Tue, 27 Aug 2019 08:46:41 -0700 (PDT)
Received: from [129.192.10.3] (helo=[10.149.1.52]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1i2dg5-0001ez-9J; Tue, 27 Aug 2019 17:46:37 +0200
From: Mirja Kuehlewind <ietf@kuehlewind.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Message-Id: <40A0B71C-4857-46F0-9096-6EE289E7404B@kuehlewind.net>
Date: Tue, 27 Aug 2019 17:46:35 +0200
Cc: IETF IPPM WG <ippm@ietf.org>, Michelle Cotton <michelle.cotton@iana.org>
To: draft-ietf-ippm-initial-registry.all@ietf.org
X-Mailer: Apple Mail (2.3445.104.11)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1566920804;d5c08124;
X-HE-SMSGID: 1i2dg5-0001ez-9J
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/M5RTqk6wnKMRZvZSia6lj2txrU4>
Subject: [ippm] AD review of draft-ietf-ippm-initial-registry-11
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2019 15:46:48 -0000

Hi authors, hi all,

We need to discuss at least one bigger question on the intended status before we  can move ahead. However, as you can seen I have more questions/comments below.

The bigger status question first:
The intended status is PS. The shepherd write-up does not provide any additional information about why this status is appropriate. I would assume that informational is actually more appropriate. I don’t recall out of my head if/when this was discussed and I thought I rather ask than searching the list archive and minutes… Is this the right status and why? And if so, please reflect in the write-up!
 

And then a couple more (hopefully) quicker comments/questions: 

- I know this was already reviewed by IANA (Michelle is also cc’ed), however, as far as I can see all Administrative Information (Status, Requestor, Revision, and Revision Date) and maybe even the ID don’t need to be part of the template because IANA will anyway assign them based on the instructions given in draft-ietf-ippm-metric-registry. Or did IANA explicitly request to also include these parts?

- Then for the Change Controller that should usually be the IESG rather than the IETF. Did IANA comment on that?

- And one minor point: I guess the secY part of the name could already be filled out, no? However, I should probably have asked that on review of draft-ietf-ippm-metric-registry already but I was actually wondering if the decision to include the RFC number and section in the metric name is appropriate. Can you maybe lay out what the reasons for this are (and maybe also explain in the draft as his might come up again during IESG review otherwise)…?


Then then on references again:

- This draft references two obsoleted RFCs (RFC2679 and RFC2680). I assume this is an oversight and the references need to be updated?

- Also given you rely heavily on [Trammell-14], I think this needs to be a normative reference (and maybe [Strowes] as well?). The more stable pointer for [Trammell-14] is actually here: 
https://link.springer.com/chapter/10.1007/978-3-642-54999-1_2
But to be honest the split between normative and informational isn’t actually very clear to me here…?


And on the shepherd write-up: 

It’s indicated that not all authors have replied to the IPR question. This need to be checked and respectively reflected in the shepherd write-up before we can move ahead!


And some smaller technical questions/nits:

- Is it correct that T0 in section 4 is defined in both subsections 4.3.5 and 4.4.2?

- Why is an URI given (only) in section 6.1.3? 
  Also section 7.1.3 and 8.1.3.: http:\\www.iana.org\ ... <name> -> I think this should be: http://www.iana.org/<name>/


Some more editorial comments/nits: 

- I find it actually unnecessary or rather confusing that most (not all) sections start with a sentence/paragraph explaining what the section is about (e.g. "Additional (Informational) details for this entry”). I would think this is sufficiently explained in draft-ietf-ippm-metric-registry and does not need to be repeated here (in this already long document). Also note that section 8.6 inconsistently doesn’t have any content while 10.6. says “None.”.

- Also these comments in section 7 and 8 are probably supposed to be removed:
" <insert name of the output type, raw or a selected summary statistic>” …?

- I found this in section 10.2.2: "@@@@@ others??”. I guess there is something missing? Also in this part, I don’t think SYN and FIN should be set at the same time, no? And rather than providing the Kind and Length of the TSopt, I would recommend to provide a pointer to the respective RFC.


And finally one/two/three more general question(s) at the end, that I probably should also have asked already on my review for draft-ietf-ippm-metric-registry:

Is it actually intended that basically all the text in this RFC gets copied into the registry? And what is expected to be on the URL page then? Wouldn’t it be necessary to also define a format for that page in order to be of any use?


Mirja