Skip to main content

Multicast Addresses for Documentation
RFC 6676

Yes

(Ron Bonica)

No Objection

(Barry Leiba)
(Gonzalo Camarillo)
(Martin Stiemerling)
(Ralph Droms)
(Robert Sparks)
(Russ Housley)
(Sean Turner)
(Stephen Farrell)
(Wesley Eddy)

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

(Ron Bonica; former steering group member) Yes

Yes (for -03)

                            

(Adrian Farrel; former steering group member) (was Discuss) No Objection

No Objection (2012-05-17)
I think it is a shame that the useful explanatory text is proposed for deletion from the IANA section. It would be nice to convert this into something that will record the motivation.

(Barry Leiba; former steering group member) No Objection

No Objection (for -03)

                            

(Benoît Claise; former steering group member) No Objection

No Objection (2012-05-07 for -03)
I would propose one text improvement:
OLD:

  GLOP [RFC3180] is a method for deriving IPv4 multicast group
   addresses from 16 bit AS numbers.


NEW:
   GLOP [RFC3180] can be used by anyone who owns a registered AS number
   to derive 256 global multicast addresses, by mapping the AS number in the
   middle 16 bits of the IPv4 multicast address 233/8.

(Brian Haberman; former steering group member) (was Discuss) No Objection

No Objection (2012-05-24)
I've cleared my DISCUSS.  Thanks for addressing these issues.

(Gonzalo Camarillo; former steering group member) No Objection

No Objection (for -03)

                            

(Martin Stiemerling; former steering group member) No Objection

No Objection (for -03)

                            

(Pete Resnick; former steering group member) No Objection

No Objection (2012-05-09 for -03)
I won't object given that RFC5737 and RFC3849 were both Informational, but shouldn't this kind of thing be BCP?

I agree that the IANA Considerations section needs serious rewriting. It needs to include the list of reserved addresses.

(Ralph Droms; former steering group member) No Objection

No Objection (for -03)

                            

(Robert Sparks; former steering group member) No Objection

No Objection (for -03)

                            

(Russ Housley; former steering group member) No Objection

No Objection (for -03)

                            

(Sean Turner; former steering group member) No Objection

No Objection (for -03)

                            

(Stephen Farrell; former steering group member) No Objection

No Objection (for -03)

                            

(Stewart Bryant; former steering group member) No Objection

No Objection (2012-05-10 for -03)
"The use of specific multicast addresses for documentation purposes has no impact on security."

Actually isn't it a security improvement?

(Wesley Eddy; former steering group member) No Objection

No Objection (for -03)