Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification Statement
RFC 4558

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

(Alex Zinin) Yes

(Brian Carpenter) (was Discuss, No Objection) No Objection

Comment (2006-02-14)
No email
send info
From Gen-ART review by Spencer Dawkins, in case the document is
updated for any other reason:

There was one point that I wish was explained better - there are five different places in the draft where a statement like "use of Node-ID based Hello session is optimal for detecting signaling adjacency failure" is made , but "optimal" is never explained or put in context. I can guess what I think it means, but I'm guessing, and a sentence or two of explanation might make the document clearer for many readers.

(Margaret Cullen) No Objection

(Bill Fenner) No Objection

(Ted Hardie) No Objection

(Sam Hartman) No Objection

Comment (2006-02-15 for -)
No email
send info
This really seems more like a proposed standard than a BCP.  It seems
like there is implementable and testable behavior and that this
specification could advance along the standards track.  I'd like the
authors and possibly WG to consider this.  However I do not think it
appropriate to hold a discuss on this issue for this document.

(Scott Hollenbeck) No Objection

(Russ Housley) No Objection

(David Kessens) No Objection

(Allison Mankin) No Objection

(Jon Peterson) No Objection

(Mark Townsley) No Objection

Comment (2006-02-16 for -)
No email
send info
Abstract still refers to this document as a BCP, though it seems it is now going for PS.

>    Use of Node-ID based RSVP Hello messages is implied in a number of
>    cases, e.g., when data and control plan are separated, when TE links
>    are unnumbered. Furthermore, when link level failure detection is

s/data and control plan/the data and control plane

RSVP is expanded in the Abstract after it is used.

(Bert Wijnen) No Objection