Remote Network Monitoring (RMON) Protocol Identifiers for IPv6 and Multi Protocol Label Switching (MPLS)
RFC 3919

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

(Bert Wijnen) Yes

(Harald Alvestrand) No Objection

(Steven Bellovin) No Objection

(Margaret Cullen) No Objection

Comment (2004-04-15 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
Is it common for documents that define protocol identifiers to be informational?  Why not standards track?

(Ted Hardie) (was Discuss) No Objection

Comment (2004-04-14)
No email
send info
Not blocking for this document, but I note it has the following:

 REFERENCE 
         
        "RFC 2460 [RFC2460] defines the Internet Protocol version 6; The 
        following URL defines the authoritative repository for the 
        PROTOCOL NUMBERS Table: 
         
          http://www.iana.org/assignments/protocol-numbers" 


Long term, do we want the references in mibs to to relate to
entries in the params section of the IETF URN namespace, rather than
to the http retrieval URI?

(Scott Hollenbeck) No Objection

Comment (2004-04-07 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
It would be helpful if the RMON and MPLS acronyms were expanded in the title and the abstract (MPLS only in the abstract).

Section 6 (IPR statement) should be moved to the end and un-numbered.

Section 9 (security considerations) should be moved ahead of the references and re-numbered.

(Russ Housley) No Objection

(David Kessens) No Objection

(Allison Mankin) No Objection

Comment (2004-04-15 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
No further objection, but the url for the IANA considerations should be eliminated.