GMPLS Signaling Procedure for Egress Control
RFC 4003

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

(Alex Zinin; former steering group member) Yes

Yes ()
No email
send info

(Bert Wijnen; former steering group member) No Objection

No Objection (2004-09-16)
No email
send info
RFC2119 must be a normative reference.

References {BCP78] and [BCP79] do not have any citations in the text

(Bill Fenner; former steering group member) No Objection

No Objection ()
No email
send info

(David Kessens; former steering group member) No Objection

No Objection ()
No email
send info

(Harald Alvestrand; former steering group member) No Objection

No Objection (2004-09-16)
No email
send info
Reviewed by Scott Brim, Gen-ART

(Jon Peterson; former steering group member) No Objection

No Objection (2004-09-16)
No email
send info
Probably, the boilerplate 2119 terminology import statement belongs in its own terminology section, not as the 2nd paragraph of section 2, "Egress Control Procedures".

(Margaret Cullen; former steering group member) No Objection

No Objection ()
No email
send info

(Russ Housley; former steering group member) (was Discuss) No Objection

No Objection (2004-09-14)
No email
send info
  ERO and RRO should be explained before the quoted portion of
  RFC 3473.

(Scott Hollenbeck; former steering group member) No Objection

No Objection ()
No email
send info

(Steven Bellovin; former steering group member) No Objection

No Objection (2004-09-10)
No email
send info
ERO is never defined.

(Thomas Narten; former steering group member) No Objection

No Objection ()
No email
send info

(Allison Mankin; former steering group member) No Record

No Record (2004-09-16)
No email
send info
With reference to the others' remarks:
to be consistent with how other specifications are treated by this esteemed body,
I hope that there will be an RFC Editor note for expanding the acronym and
information to the editor to be kinder to Readers