Re: [ippm] WG Last Call: draft-ietf-ippm-initial-registry & draft-ietf-ippm-metric-registry

worley@ariadne.com (Dale R. Worley) Fri, 15 February 2019 04:10 UTC

Return-Path: <worley@alum.mit.edu>
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 A51AC130EE9 for <ippm@ietfa.amsl.com>; Thu, 14 Feb 2019 20:10:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level:
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 ixLd9HeiRZFj for <ippm@ietfa.amsl.com>; Thu, 14 Feb 2019 20:10:06 -0800 (PST)
Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) (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 C2298130EEA for <ippm@ietf.org>; Thu, 14 Feb 2019 20:10:04 -0800 (PST)
Received: from resomta-ch2-07v.sys.comcast.net ([69.252.207.103]) by resqmta-ch2-09v.sys.comcast.net with ESMTP id uUp9golpSQNsNuUp9gtfsN; Fri, 15 Feb 2019 04:10:03 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1550203803; bh=02/A382ueAnrzZAg+Dcc+rSvF5jm7t5jrwyJW0NHoYo=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=fIgXSaOElJKvFZXQpHImmnwmriH+XF3T+R4QS9u1mFJe/XknZsWWpWGEEYr1Nvizm JGRDla+0B0smHpVmv78fG+rOq9J74Tvr7I6dRcGXnIAnY3FlGCBlEAFJ0+YS2zqXAU eRcuXiPACqZETDNh1TjgmidXwJ2FhoSeJJQvDGuozmaf7z3HF1cTtUY6XObOOK5A1Z yF/XtBcB3BFaHxfnmq/iPjPfy+iiYPSP7xphx/u26TdU2zfXNFiqdmvE7UfCSYneSp Zh9iaQs1DRdrJSA9jmEuy1AAtAWf76UVUbejX58XkkHaSl0wB8re+lcusUo5J7ObBZ xVpTjRtNLaJRQ==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-07v.sys.comcast.net with ESMTPA id uUp8gyNQd19IPuUp9gFRjX; Fri, 15 Feb 2019 04:10:03 +0000
X-Xfinity-VMeta: sc=0;st=legit
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id x1F3A5Oi026946; Thu, 14 Feb 2019 22:10:05 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id x1F3A5XI026943; Thu, 14 Feb 2019 22:10:05 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>
Cc: ippm@ietf.org, draft-ietf-ippm-initial-registry.all@ietf.org, draft-ietf-ippm-metric-registry.all@ietf.org
In-Reply-To: <BF3DDE1A-BD0B-43D0-8D7E-A3508E105083@apple.com> (tpauly=40apple.com@dmarc.ietf.org)
Sender: worley@ariadne.com
Date: Thu, 14 Feb 2019 22:10:05 -0500
Message-ID: <87wom1oigi.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/_xVaQoiM9lWrkyZz7EIQT4A0TJg>
Subject: Re: [ippm] WG Last Call: draft-ietf-ippm-initial-registry & draft-ietf-ippm-metric-registry
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: Fri, 15 Feb 2019 04:10:08 -0000

Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org> writes:
> We haven't received much feedback to the list on the metrics registry
> document. Please do take a look at the current revisions of the
> documents, and provide your opinion on whether or not the documents
> are ready to progress!

I haven't been following this work, but I've done quite a bit of
reviewing for Gen-Art.  And while I suspect the design and technical
work is probably quite solid by this point, I have to agree with Tom
Petch that the *document* isn't.  As he notes, the instructions to IANA
for setting up the registry are really difficult to read if you start
reading at the "IANA Considerations" section with the question, "What is
the structure of the registries?" and "What entries are to be added to
the registries?"

As a first example issue, what are the names of the registries?  I see
the text

   This document specifies the procedure for Performance Metrics Name
   Element Registry setup.  IANA is requested to create a new set of
   registries for Performance Metric Name Elements called "IETF URN Sub-
   namespace for Registered Performance Metric Name Elements"
   (urn:ietf:metrics:perf).  Each Registry, whose names are listed
   below:

      MetricType:
      [...]

Is the registry name "IETF URN Sub-namespace for Registered Performance
Metric Name Elements", or is it "MetricType"?  The section really ought
to recite each registry's name, its column names, and the meanings of
the column's values.

In addition, as Tom Petch points out, the documents specify a new
second-level URN namespaces under "ietf".  (See
file:///home/worley/www.iana.org/assignments/params/params.xhtml#urn-subnamespaces.)
But the drafts do not reference RFC 6924, which contains the
registration procedures for such second-level namespaces.  However, it
appears there are no particular requirements for this assignment other
than IETF review.

Dale