IS-IS Cryptographic Authentication
RFC 5304
Yes
No Objection
Recuse
Note: This ballot was opened for revision 03 and is now closed.
Lars Eggert No Objection
(Ross Callon; former steering group member) Yes
(Chris Newman; former steering group member) (was Discuss) No Objection
This does not appear to have a mechanism for hash function transition. That problem should be considered in the event a future revision of this specification is prepared.
(Dan Romascanu; former steering group member) No Objection
(Jon Peterson; former steering group member) No Objection
(Lisa Dusseault; former steering group member) No Objection
(Magnus Westerlund; former steering group member) No Objection
(Mark Townsley; former steering group member) No Objection
(Pasi Eronen; former steering group member) (was No Record, Discuss) No Objection
(Ron Bonica; former steering group member) No Objection
This is a no-objection with point raised. I'm not willing to block the document over this point, but think that you should address it in the future. What happens when a NOC guy who knew the shared secret leaves the company? Do you have to bounce all of the ISIS adjacencies so that you can change the secret. It would be great if you could change the shared secret without bouncing the adjacency.
(Tim Polk; former steering group member) No Objection
(David Ward; former steering group member) Recuse