Definitions of Managed Objects for the DS3/E3 Interface Type
RFC 3896

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

(Bert Wijnen) Yes

(Harald Alvestrand) No Objection

(Steven Bellovin) No Objection

Comment (2004-04-27)
No email
send info
Move the appendices to the end; mve the Security Considerations section before the references.

(Margaret Cullen) (was Discuss, No Objection) No Objection

(Ted Hardie) No Objection

(Scott Hollenbeck) No Objection

Comment (2004-04-16)
No email
send info
The Section 3 subsections (which don't appear in the text as far as I can see) are mis-numbered in the table of contents.  If they are used in the ToC it would be helpful to have section numbers in the text, too.

An IANA Considerations section would be helpful, even if it were to say "there are no actions for IANA in this specification".

(Russ Housley) No Objection

Comment (2004-04-27)
No email
send info
  Section 1.1, paragraph (4): s/thenear end/the near/

  Does it make sence to include a URL to the WG charter in the ASN.1 module?
  We know that this will go away when the WG is finished with their work.

  The Copyright in the ASN.1 module DESCRIPTION has the wrong year.

(David Kessens) No Objection

(Allison Mankin) No Objection

(Thomas Narten) No Objection

(Jon Peterson) No Objection

(Alex Zinin) No Objection