Simple Network Management Protocol (SNMP) over IEEE 802 Networks
RFC 4789

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

(Dan Romascanu) Yes

(Jari Arkko) No Objection

(Lisa Dusseault) No Objection

(Lars Eggert) No Objection

Comment (2006-09-26)
No email
send info
Section 3., paragraph 1:
>    This is an optional transport mapping.

  s/optional/OPTIONAL/


Section 3.2., paragraph 3:
>    It is recommended that implementations be capable of accepting
>    messages of up to 1472 octets in size.  Implementation of larger
>    values is encouraged whenever possible.

  s/recommended/RECOMMENDED/


Section 3415, paragraph 0:
>    Specifically, the use of the User-based Security Model STD 62, RFC
>    3414 [RFC3414] and the View-based Access Control Model STD 62, RFC
>    3415 [RFC3415] is recommended.

  Nit: Missing Reference: 'RFC3414' is mentioned on line 220, but not
  defined. Missing Reference: 'RFC3415' is mentioned on line 221, but
  not defined.

(Bill Fenner) No Objection

(Russ Housley) No Objection

(Cullen Jennings) No Objection

Comment (2006-09-24 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
This document seems to have no use of the RFC 2119 normative language but it should.

(David Kessens) No Objection

(Jon Peterson) No Objection

(Mark Townsley) (was Discuss, No Objection) No Objection

Comment (2006-09-28)
No email
send info
I'd like to ask in what situations someone would want to run SNMP directly over ethernet, and discuss whether or not to at least include one example to describe such motivations.

Magnus Westerlund No Objection