Updates to the IPv6 Multicast Addressing Architecture
RFC 7371

Note: This ballot was opened for revision 07 and is now closed.

(Brian Haberman) Yes

(Jari Arkko) No Objection

(Richard Barnes) No Objection

Alissa Cooper No Objection

(Spencer Dawkins) No Objection

(Adrian Farrel) No Objection

Comment (2014-08-04 for -07)
No email
send info
I have no objection to the publication of this document, and just two
small issues you could look at as you progress the document.

---

Section 3 is titled "Flag Bits: A Recommendation" however, the text is
clear in its use of "MUST" and this a Standards Track document.

I think you should change the title to "Flag Bits: New Processing Rules"

Furthermore, in Section 1, you should not refer to this as a 
recommendation.

---

In Section 4 you have text referring to ff1 such as:

   X and Y may each be set to 0 or 1.

... but no indication as to how or why these bits might be set. Are they
or some specific use? Are they reserved like the r bits in ff2?

Adding some clue or reference would be good.

(Stephen Farrell) No Objection

(Joel Jaeggli) No Objection

Barry Leiba No Objection

Comment (2014-08-04 for -07)
No email
send info
-- Section 4.1.1 --

  X and Y may each be set to 0 or 1.

What does this addition mean?  What, specifically, is the change it's making?  I'd like to know the answer; more importantly, I think the document needs to be clear about it.  (And the same goes for the similar lines in Sections 4.2.1 and 4.2.2.)

(Ted Lemon) No Objection

(Kathleen Moriarty) No Objection

Comment (2014-08-04 for -07)
No email
send info
Thanks for addressing the comments from the SecDir review.
https://www.ietf.org/mail-archive/web/secdir/current/msg04886.html

I have no additional comments.

(Pete Resnick) No Objection

(Martin Stiemerling) No Objection