AD Evaluation: draft-ietf-6man-multicast-addr-arch-update

[Brian Haberman <[e-mail]>]

All,
     I have completed my AD Evaluation of
draft-ietf-6man-multicast-addr-arch-update as a part of the publication
process.  Please review these comments, discuss as necessary, and
resolve them.  Once a revision is available that addresses these
comments, the document can proceed to the next phase of the publication
process (IETF Last Call).


* Re-word the Abstract to remove explicit reference to the reserved bits
location.  Something like "...by re-defining the reserved bits as
generic..."

* Section 1 - This document updates the IPv6 addressing architecture
(not the multicast addressing architecture) to change the reserved bits
to flag bits.

* Sections 1 & 2 - If the text contains the actual offset of the bits
being changed, the document needs to indicate what reference point is
being used.  For example, RFC 4291 refers to "high-order bits" to
indicate the point of reference.

* Section 2

1. What is the rationale for the use of the term "so-called" in
reference to Embedded-RP?

2. I would suggest specifying that ff1 directly maps to flgs in 4291 & 3956.

* There is quite a bit of redundancy between sections 2 & 4, but not
information is contained in 2. I would suggest re-structuring these
sections so that one contains the rationale for this change and the
other contains the complete list of updates being made to the affected
documents.

* This may be nit-picky, but I would like to see the names listed in the
Acknowledgements be completely spelled out.

* idnits indicates issues that need to be addressed.


Regards,
Brian