IPv6 Multicast Address Scopes
RFC 7346
Yes
No Objection
Note: This ballot was opened for revision 05 and is now closed.
(Brian Haberman; former steering group member) Yes
(Ted Lemon; former steering group member) Yes
(Adrian Farrel; former steering group member) (was Discuss) No Objection
Thanks for addressing my Discuss
(Alia Atlas; former steering group member) No Objection
Agree with Adrian's discuss and Stephen's comments.
(Alissa Cooper; former steering group member) No Objection
(Barry Leiba; former steering group member) No Objection
1. Did you mean to change the text for scop=1 in the table, from "Interface-Local scope" to just "Interface"? I don't think so. 2. In Section 3 you say this: Section 5 gives the definition of scop 3 for IEEE 802.15.4 [IEEE802.15.4] networks. ...but then Section 4 immediately talks about Section 5 of RFC 4007. Just to make sure no one misunderstands, maybe Section 3 should say, "Section 5, below, gives...", yes? 3. I understand you're about to submit a revised I-D that clarifies this from the IANA Considerations: The registry will have a note associated with scope 3 listing all RFCs that define Realm-Local scoping rules that use scope 3. I await that update, and might comment further...
(Benoît Claise; former steering group member) No Objection
(Jari Arkko; former steering group member) No Objection
(Joel Jaeggli; former steering group member) No Objection
(Kathleen Moriarty; former steering group member) No Objection
I'm curious to see the response on Stephen's question. Also, the referenced security consideration sections don't talk about the global scope and any risk related to not having a boundary. Some text on that could be helpful or perhaps an explanation so I know why it is not needed would be helpful.
(Martin Stiemerling; former steering group member) No Objection
(Pete Resnick; former steering group member) No Objection
(Richard Barnes; former steering group member) No Objection
(Spencer Dawkins; former steering group member) No Objection
Ah, the glories of getting a late start on telechat reading. I would have balloted Discuss on approximately Stephen's point, but it's already being robustly discussed among people who understand the details better than I do, and seems close to converging. :D
(Stephen Farrell; former steering group member) No Objection
Pardon my multicast ignorance (I only used smcroute for the 1st time recently:-) but what happens if a router in the group supports two different technologies on different interfaces, each of which defines scop=3 to be something local(-ish) - do the packets get forwarded between technologies or not? If the answer to the above is "yes," then I think there's a security consideration to be stated here, which is that scop=3 does not mean that packets are limited to being seen by nodes running a specific technology but may go further via a router. That could be unexpected enough to be worth stating. If the answer is "no" then I think you need to change the draft to make that clearer, if you want people like me to understand that. Or maybe its just a dumb question:-)