[RTG-DIR] RtgDir review: draft-bchv-rfc6890bis-04

Dan Frost <frost@mm.st> Mon, 06 March 2017 10:21 UTC

Message-Id: <1488795712.121267.901697504.1EDD2548@webmail.messagingengine.com>
From: Dan Frost <frost@mm.st>
To: draft-bchv-rfc6890bis@ietf.org, rtg-ads@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
Date: Mon, 06 Mar 2017 10:21:52 +0000
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/o0wVKmUiLodDQbcaDPeRQ0hLpFM>
Cc: rtg-dir@ietf.org
Subject: [RTG-DIR] RtgDir review: draft-bchv-rfc6890bis-04
Precedence: list

Hello,

I have been selected as the Routing Directorate reviewer for this draft.
 The Routing Directorate seeks to review all routing or routing-related 
drafts as they pass through IETF last call and IESG review, and 
sometimes on special request. The purpose of the review is to provide 
assistance to the Routing ADs. For more information about the Routing 
Directorate, please see
http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir

Although these comments are primarily for the use of the Routing ADs, it
 would be helpful if you could consider them along with any other IETF 
Last Call comments that you receive, and strive to resolve them through 
discussion or by updating the draft.

Document:  draft-bchv-rfc6890bis-04
 Reviewer: Dan Frost
 Review Date: 2017-03-06
 IETF LC End Date: 2017-03-10
 Intended Status: Best Current Practices


Summary:

I have some minor concerns about this document that I think should be
resolved before publication.

Comments:

This draft aims to update the guidelines governing special-purpose IPv4
and IPv6 address block registrations (things like link-local, localhost,
and RFC1918 private-addressing) provided by RFC 6890.

Overall the draft is in good shape and the content is clear. However,
there are some structural issues that, while not critical, would make
the document easier to understand if addressed.

Major Issues:

No major issues found.

Minor Issues:

The main issue I found when reading the document is that it's not
obvious whether this is intended to be read as a patch on top of RFC
6890 or as a replacement for it. Since it proposes to obsolete RFC 6890,
presumably it's the latter. But in some ways it reads more like a patch.

More specifically, the abstract and introductory text focuses more on
the patch aspect (the clarification of the "global" field), and in so
doing, drops the overall context and v4/v6 balance of RFC 6890. The
abstract, for instance, only mentions v6.

If the authors do intend for this draft to replace RFC 6890, I think it
would substantially improve readability to frame this document first and
foremost as a complete reference on special-purpose address block
registration, and to single out the "global" clarification issue in its
own section.

Moreover, the manner in which this draft addresses the "global" issue is
also not obvious. Specifically, it doesn't explicitly call out  the
precise changes it makes over RFC 6890. The introduction states that it
"augments the fields contained within the registries in order to address
the confusion raised by the definition of "global"." What does this mean
exactly? As far as I can tell, the only change it makes is renaming the
field from "Global" to "Globally Reachable".

In sum, my recommendation would be to (1) frame the document as a
reference on special-purpose registration generally; (2) detail the
"global" issue in its own section; and (3) be explicit in that section
about the changes made over RFC 6890 and how they resolve the issue.

Nits:

The IPv6 Special-Purpose Address Registry URL listed at the beginning of
Section 3.2 has a typo("www,iana.org" with a comma after the www).

Cheers,
-d

[RTG-DIR] RtgDir review: draft-bchv-rfc6890bis-04 Dan Frost