IANA Guidelines for the Registry of Remote Monitoring (RMON) MIB modules
draft-ietf-rmonmib-rmon-oid-assignments-01

[Ballot comment]
>    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?

[Ballot discuss]
I think this deserves an RFC Editor note....
Section 3 does not say when IANA will assign the identifier. The implication of the text is that it will be assigned after publication approval, and that the type of document does not matter; I suggest making this explicit.

Suggested note to RFC Editor:
In section 3, add the following sentence to the end of the section:

IANA will assign the number as part of the RFC publication process. This number is allocated under the "Specification Required" policy [RFC2434].

Also add RFC 2434 to "normative references".

[Ballot comment]
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?