IANA Guidelines for the Registry of Remote Monitoring (RMON) MIB modules
RFC 3737

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

(Randy Bush) Yes

(Ted Hardie) Yes

(Harald Alvestrand) (was Discuss) No Objection

(Steven Bellovin) No Objection

(Margaret Cullen) No Objection

(Bill Fenner) No Objection

(Ned Freed) (was Discuss) No Objection

Comment (2003-11-18 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
Minor typos:

"untill" -> "until" in section 2
"defuct" -> "defunct" in the table in section 2
"(1.3.6.1.2.1.16.20>" -> "(1.3.6.1.2.1.16.20)" in the table in section 2

Shouldn't the instructions in section 3 also call for the IANA
considerations section to make note of the needed assignment, or do
you think that having the note in the MIB is sufficient and having
a pointer in the IANA considerations section is unnecessary?

Shouldn't the various Internet Drafts referred to in the table in section 2
be included in the references list?

(Russ Housley) No Objection

Comment (2003-11-19 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
Typo in: ...mib-2.rmon.conformance (1.3.6.1.2.1.16.20>

   s/>/)/

(Allison Mankin) No Objection

(Thomas Narten) No Objection

Comment (2003-11-20 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
>    Working Group untill publication of RFC XXXX. Some (early)

s/untill/until/

>    This document was produced as a result of discussion between the
>    Operations and Management AD responsible for Network Management and
>    the WG chair for the RMONMIB Working Group. Thanks to Andy Bierman

any reason not to actually name the AD above?

(Jon Peterson) No Objection

(Alex Zinin) No Objection

(Bert Wijnen) Recuse