Juergen, Yes, that rephrased paragraph would be fine.
Thanks, --David > -----Original Message----- > From: Juergen Schoenwaelder [mailto:[EMAIL PROTECTED] > Sent: Monday, September 25, 2006 4:56 PM > To: Black, David > Cc: [email protected]; [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: Gen-ART review of draft-schoenw-snmp-ether-01.txt > > On Mon, Sep 25, 2006 at 09:22:09AM -0400, [EMAIL PROTECTED] wrote: > > > Comments: > > [...] > > > The -01 version would be ok to publish as-is, but I concur with > > Cullen Jennings's comment that use of RFC 2119 language is > > appropriate, and I specifically suggest a couple of "MUST"s in > > the second paragraph of Section 3.2 to require the use of EtherType > > hex 814C and use of SNAP with LLC. I happen to know from history > > that IEEE is somewhat sensitive about proper EtherType usage. > > Does the following rephrased text address your comment: > > When serialized SNMP messages are sent in IEEE 802.3 frames (and in > other IEEE 802 MAC frame types that can natively represent Ethernet > type values), the Ethernet type field value of 33100 (hexadecimal > 814C) MUST be used as the link layer protocol identifier. In IEEE > 802 LANs that use LLC as the means of link layer protocol > identification, such as IEEE 802.11 Wireless LANs, the SNAP > encapsulation method described in subclause 10.5 "Encapsulation of > Ethernet frames over LLC" in [IEEE802] MUST be used. > > > IANA needs clarification of what to do about SNMP domain > > registration - see the IANA comment in the I-D tracker. > > This is taken care of in the -02 version (which still sits in the > queue). > > Thanks, > > /js > > -- > Juergen Schoenwaelder International University Bremen > <http://www.eecs.iu-bremen.de/> P.O. Box 750 561, > 28725 Bremen, Germany > _______________________________________________ Gen-art mailing list [email protected] https://www1.ietf.org/mailman/listinfo/gen-art
