Multicast Addresses for Documentation
RFC 6676
Yes
No Objection
Note: This ballot was opened for revision 03 and is now closed.
(Ron Bonica; former steering group member) Yes
(Adrian Farrel; former steering group member) (was Discuss) No Objection
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
(Benoît Claise; former steering group member) No Objection
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
I've cleared my DISCUSS. Thanks for addressing these issues.
(Gonzalo Camarillo; former steering group member) No Objection
(Martin Stiemerling; former steering group member) No Objection
(Pete Resnick; former steering group member) No Objection
(Ralph Droms; former steering group member) No Objection
(Robert Sparks; former steering group member) No Objection
(Russ Housley; former steering group member) No Objection
(Sean Turner; former steering group member) No Objection
(Stephen Farrell; former steering group member) No Objection
(Stewart Bryant; former steering group member) No Objection
"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