[Gen-art] Genart last call review of draft-ietf-ippm-metric-registry-20

Roni Even via Datatracker <noreply@ietf.org> Tue, 29 October 2019 08:24 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 300D21200DF; Tue, 29 Oct 2019 01:24:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Roni Even via Datatracker <noreply@ietf.org>
To: <gen-art@ietf.org>
Cc: last-call@ietf.org, ippm@ietf.org, draft-ietf-ippm-metric-registry.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.108.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roni Even <ron.even.tlv@gmail.com>
Message-ID: <157233748615.6543.10822415025321392095@ietfa.amsl.com>
Date: Tue, 29 Oct 2019 01:24:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/GrsXYg2_W9F7Z9onvuwoeQGIbUE>
Subject: [Gen-art] Genart last call review of draft-ietf-ippm-metric-registry-20
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: Tue, 29 Oct 2019 08:24:46 -0000

Reviewer: Roni Even
Review result: Almost 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

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-ippm-metric-registry-??
Reviewer: Roni Even
Review Date: 2019-10-29
IETF LC End Date: 2019-11-06
IESG Telechat date: Not scheduled for a telechat

Summary:
The document is almost ready for publication as a BCP document

Major issues:

Minor issues:
1. From reading the document it looks to me that the registration policy 
should be specification required which also requires expert review. 2. My
understanding is that for registration a document is required , not necessarily
and RFC, but in multiple places in the document ( 7.3, 7.3.1, 8.2 ,...) the
text talks about RFC and not document. 3. I am not sure if section 6 is needed
in the published document based on its content. If it will remain then in 6.1
first paragraph the reference should be to section 5 and not to section 6. 4.
In sections 10.2 and 10.3 there are guidance taken from this document. I think
that the for IANA it should say in the registry note that the registration must
comply with RFCXXX (this document), I assume that there is no need to repeat
all this text in these sections in the registry note.

Nits/editorial comments: