Procedures for Modifying the Resource reSerVation Protocol (RSVP)
RFC 3936
Yes
No Objection
Note: This ballot was opened for revision 02 and is now closed.
(Allison Mankin; former steering group member) Yes
(Bill Fenner; former steering group member) Yes
(Thomas Narten; former steering group member) (was Discuss) Yes
(Alex Zinin; former steering group member) No Objection
(Bert Wijnen; former steering group member) No Objection
(Harald Alvestrand; former steering group member) No Objection
(Jon Peterson; former steering group member) No Objection
(Margaret Cullen; former steering group member) No Objection
The way this document is structured, the references occur before most of the document text (which is in the IANA Considerations section). There are also references used after the references section. This should really be cleaned up, but I think that the RFC editor will probably do it.
(Ned Freed; former steering group member) No Objection
Nits: No IPR boilerplate The ordering of the sections in the document ends up being screwy because effectively all of the content ended up in the IANA considerations section, which appears after the references and so forth. I suggest creating a section after the intro with the range information for each namespace in it and then have an IANA consideration section that refers to this new section.
(Russ Housley; former steering group member) No Objection
(Steven Bellovin; former steering group member) No Objection
(Ted Hardie; former steering group member) (was Discuss) No Objection