Description of the Resource Reservation Protocol - Traffic-Engineered (RSVP-TE) Graceful Restart Procedures
RFC 5495

Note: This ballot was opened for revision 04 and is now closed.

(Ross Callon) Yes

(David Ward) Yes

(Jari Arkko) No Objection

(Lars Eggert) No Objection

(Pasi Eronen) No Objection

(Russ Housley) No Objection

(Chris Newman) No Objection

(Tim Polk) No Objection

Comment (2009-02-12)
No email
send info
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.

(Mark Townsley) No Objection