A Reliable Transport Mechanism for PIM
draft-ietf-pim-port-09
Yes
(Adrian Farrel)
No Objection
(Dan Romascanu)
(David Harrington)
(Gonzalo Camarillo)
(Jari Arkko)
(Pete Resnick)
(Ralph Droms)
(Robert Sparks)
(Ron Bonica)
(Russ Housley)
(Stewart Bryant)
(Wesley Eddy)
Note: This ballot was opened for revision 09 and is now closed.
Adrian Farrel Former IESG member
Yes
Yes
()
Unknown
Dan Romascanu Former IESG member
No Objection
No Objection
()
Unknown
David Harrington Former IESG member
No Objection
No Objection
()
Unknown
Gonzalo Camarillo Former IESG member
No Objection
No Objection
()
Unknown
Jari Arkko Former IESG member
No Objection
No Objection
()
Unknown
Pete Resnick Former IESG member
No Objection
No Objection
()
Unknown
Ralph Droms Former IESG member
No Objection
No Objection
()
Unknown
Robert Sparks Former IESG member
No Objection
No Objection
()
Unknown
Ron Bonica Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
Sean Turner Former IESG member
No Objection
No Objection
(2011-11-02)
Unknown
s3.1 and s3.2: Not being a PIM expert, I tripped up over how IPv6 addresses could fit in to TCP Connection ID and SCTP Connection ID. I kind of had to guess where I'd find more information about this, so a pointer to the xoring mechanism in RFC 4061 would have helped a lot.
Stephen Farrell Former IESG member
No Objection
No Objection
(2011-11-01)
Unknown
- Presumably if this experiment is a success then some method of doing automated key management would be required for a successor standards track document. I think just noting that in the security considerations section would be good. - I wondered why TLS wasn't considered as an additional option. Be good to explain why, esp if there's a reason it wouldn't work well enough.
Stewart Bryant Former IESG member
No Objection
No Objection
()
Unknown
Wesley Eddy Former IESG member
No Objection
No Objection
()
Unknown