Description of the Resource Reservation Protocol - Traffic-Engineered (RSVP-TE) Graceful Restart Procedures
draft-ietf-ccamp-gr-description-04
Yes
(David Ward)
(Ross Callon)
No Objection
(Chris Newman)
(Jari Arkko)
(Lars Eggert)
(Mark Townsley)
(Pasi Eronen)
(Russ Housley)
(Tim Polk)
Note: This ballot was opened for revision 04 and is now closed.
David Ward Former IESG member
Yes
Yes
()
Unknown
Ross Callon Former IESG member
Yes
Yes
()
Unknown
Chris Newman Former IESG member
No Objection
No Objection
()
Unknown
Jari Arkko Former IESG member
No Objection
No Objection
()
Unknown
Lars Eggert Former IESG member
No Objection
No Objection
()
Unknown
Mark Townsley Former IESG member
No Objection
No Objection
()
Unknown
Pasi Eronen Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
()
Unknown
Tim Polk Former IESG member
No Objection
No Objection
(2009-02-12)
Unknown
I know this is a nit, but there are extraneous commas in the two most important sentences in this specification. To remove ambiguity, I would suggest the following substitution in Section 6: OLD After a node restarts its control plane, it should ignore and silently drop all RSVP-TE messages, except Hello messages, it receives from any neighbor to which, no HELLO session has been established. NEW After a node restarts its control plane, it should ignore and silently drop all RSVP-TE messages, except Hello messages, it receives from any neighbor to which no HELLO session has been established. OLD The restarting node should follow [RFC3209] to establish Hello sessions with its neighbors, after its control plane becomes operational. NEW The restarting node should follow [RFC3209] to establish Hello sessions with its neighbors after its control plane becomes operational.