[Gen-art] Genart last call review of draft-ietf-ippm-initial-registry-12

Joel Halpern via Datatracker <noreply@ietf.org> Fri, 01 November 2019 16:55 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EF80B120978; Fri, 1 Nov 2019 09:55:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern via Datatracker <noreply@ietf.org>
To: gen-art@ietf.org
Cc: last-call@ietf.org, draft-ietf-ippm-initial-registry.all@ietf.org, ippm@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.108.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Joel Halpern <jmh@joelhalpern.com>
Message-ID: <157262730194.31927.5524715609259531175@ietfa.amsl.com>
Date: Fri, 01 Nov 2019 09:55:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/rSbGKoy0VHYIQGhWDF5gVhJ602U>
Subject: [Gen-art] Genart last call review of draft-ietf-ippm-initial-registry-12
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Nov 2019 16:55:02 -0000

Reviewer: Joel Halpern
Review result: Ready

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 treat these comments just
like any other last call comments.

For more information, please see the FAQ at


Document: draft-ietf-ippm-initial-registry-12
Reviewer: Joel Halpern
Review Date: 2019-11-01
IETF LC End Date: 2019-11-06
IESG Telechat date: Not scheduled for a telechat

Summary: This document is ready for publication as a Proposed Standard

Side note: I presume that as part of the process for
draft-ietf-ippm-metric-registry (the normative reference the defines the
structure used in this document) there has been discussion with IANA explicitly
about the fact that this registry has an extremely large number of columns,
some with extremely verbose content, and it will likely take some work for IANA
to determine how to present this in a human-readable fashion?  And the lesser
point that is probably covered by existing procedures, but I wanted to check,
that IANA is prepared to fill in the URLs scattered throughout the document?

Second note:  I did not review the accuracy of the descriptions of the metrics,
but only looked for clarity.  This is material well known to the WG, and mostly
derived from other documents this or closely related working groups have

Major issues: N/A

Minor issues:
    For those entries that are defining two (or more) closely related metrics,
    should the document actually have two (or more) lines for URL, since the
    text says that IANA is to assign two URLs.  (And the list of differing
    fields should presumably include URL?)

    In the first part of section 5, there is a note about potentially splitting
    the registry entry into two registry entries.  I can not understand the
    note.  The registry is either defined with one entry or defined with two
    entries.  Is this still an open item?  (If so, my "ready" above clearly
    should be "Ready with issues.")  I think it is just an erroneous retention
    of text from earlier?

Nits/editorial comments:
    If there are no roles to define in 5.3.6, shouldn't it say "N/A"

    Some comments and remarks say "None" which makes sense.  Some say
    "Additional (Informational) details for this entry" which seems to be text
    left over from the template that should say "None"?