Hierarchical Join/Prune Attributes
draft-ietf-pim-hierarchicaljoinattr-08
Yes
(Alvaro Retana)
No Objection
(Alexey Melnikov)
(Alissa Cooper)
(Ben Campbell)
(Benoît Claise)
(Deborah Brungard)
(Jari Arkko)
(Joel Jaeggli)
(Mirja Kühlewind)
(Terry Manderson)
Note: This ballot was opened for revision 07 and is now closed.
Alvaro Retana Former IESG member
Yes
Yes
(for -07)
Unknown
Alexey Melnikov Former IESG member
No Objection
No Objection
(for -07)
Unknown
Alissa Cooper Former IESG member
No Objection
No Objection
(for -07)
Unknown
Ben Campbell Former IESG member
No Objection
No Objection
(for -07)
Unknown
Benoît Claise Former IESG member
No Objection
No Objection
(for -07)
Unknown
Deborah Brungard Former IESG member
No Objection
No Objection
(for -07)
Unknown
Jari Arkko Former IESG member
No Objection
No Objection
(for -07)
Unknown
Joel Jaeggli Former IESG member
No Objection
No Objection
(for -07)
Unknown
Kathleen Moriarty Former IESG member
No Objection
No Objection
(2016-04-19 for -07)
Unknown
I support Stephen's comments.
Mirja Kühlewind Former IESG member
No Objection
No Objection
(for -07)
Unknown
Stephen Farrell Former IESG member
No Objection
No Objection
(2016-04-19 for -07)
Unknown
Two related but minor points: - section 5, last para: can a router always know for sure that everyone who'll get a message sent on an interface knows about this new encoding? If not, the "MUST NOT" here is incorrect. One could implement a MUST NOT that said to only send this to routers who'd expressed the hello option, but saying that the MUST NOT applies to everyone accessible from the sender's interface is arguably not implementable. The real-world result would be the same though, even if one's code would better match the latter way of describing the MUST NOT, so not that big a deal. - section 6: If a router had a bug that caused it to crash (or do bad stuff) when it unexpectedly receives a message with this new encoding, then if I faked a message with the new hello option to a peer of that router, I might be able to cause someone else to crash the victim/target. There are probably other bad things I can do if I can fake a hello like that, but this is perhaps a new one. I'm not claiming that's worth a mention though, unless the authors/chairs/shepherd want to add it.
Suresh Krishnan Former IESG member
No Objection
No Objection
(2016-04-19 for -07)
Unknown
Section 5 contains the following text "Note that it also needs to include the Join-Attribute Hello option as specified in [RFC5384]." but it does not talk about what exactly happens if a message is received with the Hierarchical Join/Prune Attribute but without the Join-Attribute. Can you clarify what happens in this case? I would also prefer it if this can be reworded as a MUST.
Terry Manderson Former IESG member
No Objection
No Objection
(for -07)
Unknown