Simple Network Management Protocol (SNMP) over IEEE 802 Networks
draft-schoenw-snmp-ether-02

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

Lars Eggert No Objection

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.

(Dan Romascanu; former steering group member) Yes

(Bill Fenner; former steering group member) No Objection

(Cullen Jennings; former steering group member) No Objection

This document seems to have no use of the RFC 2119 normative language but it should.

(David Kessens; former steering group member) No Objection

(Jari Arkko; former steering group member) No Objection

(Jon Peterson; former steering group member) No Objection

(Lisa Dusseault; former steering group member) No Objection

(Magnus Westerlund; former steering group member) No Objection

(Mark Townsley; former steering group member) (was Discuss, No Objection) No Objection

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.

(Russ Housley; former steering group member) No Objection