[Gen-art] Genart last call review of draft-ietf-6man-rfc4941bis-10

[Russ Housley via Datatracker <[e-mail]>]

Reviewer: Russ Housley
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
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-6man-rfc4941bis-10
Reviewer: Russ Housley
Review Date: 2020-09-11
IETF LC End Date: 2020-09-23
IESG Telechat date: unknown


Summary: Almost Ready


Major Concerns:

In Section 2.2, the discussion of DNS names comes out of the blue.  In
RFC 4941, there was context for this discussion that has been dropped
from this document.  Some context is needed.


Minor Concerns:

The Abstract says: "This document describes an extension that ...".
It should state what protocol is being extended.  I believe this is an
extension for SLAAC.


Nits:

Section 1, first paragraph says: "... in [RFC7721],[RFC7217], and
RFC7707."  All three should be references.

In addition, essentially this same sentence appears at the end of
Section 2.1.  I'm not sure the second one adds value.

Section 1.1, last paragraph says: '... and not to "globally reachable"
as defined in [RFC8190].'  I think you want to say that this term does
not imply "globally reachable" as defined in [RFC8190].  That is, it
might be globally reachable, but it might not.


IDnits reports:

** The document seems to lack an IANA Considerations section.  (See Section
   2.2 of https://www.ietf.org/id-info/checklist for how to handle the case
   when there are no actions for IANA.)

== The 'Obsoletes: ' line in the draft header should list only the
   _numbers_ of the RFCs which will be obsoleted by this document (if
   approved); it should not include the word 'RFC' in the list.