A Reliable Transport Mechanism for PIM
RFC 6559
Yes
No Objection
Note: This ballot was opened for revision 09 and is now closed.
(Adrian Farrel; former steering group member) Yes
(Dan Romascanu; former steering group member) No Objection
(David Harrington; former steering group member) No Objection
(Gonzalo Camarillo; former steering group member) No Objection
(Jari Arkko; 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
(Ron Bonica; former steering group member) No Objection
(Russ Housley; former steering group member) (was Discuss) No Objection
(Sean Turner; former steering group member) No Objection
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 steering group member) No Objection
- 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 steering group member) No Objection
(Wesley Eddy; former steering group member) No Objection