[Gen-art] Re: Gen-ART review of draft-schoenw-snmp-ether-01.txt

Cullen Jennings <fluffy@cisco.com> Thu, 05 October 2006 02:17 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVIoB-0005fk-R4; Wed, 04 Oct 2006 22:17:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVIoA-0005ZT-LI for gen-art@ietf.org; Wed, 04 Oct 2006 22:17:58 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVIo8-0007N1-9p for gen-art@ietf.org; Wed, 04 Oct 2006 22:17:58 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 04 Oct 2006 19:17:55 -0700
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k952HtkA016187; Wed, 4 Oct 2006 19:17:55 -0700
Received: from [12.182.170.79] (sjc-vpn2-823.cisco.com [10.21.115.55]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k952Gmiu017130; Wed, 4 Oct 2006 19:17:53 -0700 (PDT)
In-Reply-To: <20060926113124.GA6341@boskop.local>
References: <AAB4B3D3CF0F454F98272CBE187FDE2F0B55B1BF@is0004avexu1.global.avaya.com> <20060926113124.GA6341@boskop.local>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <994F986E-0FB2-4138-8A3B-F783EB363169@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Date: Wed, 04 Oct 2006 15:20:47 -0700
To: j.schoenwaelder@iu-bremen.de
X-Mailer: Apple Mail (2.752.2)
DKIM-Signature: a=rsa-sha1; q=dns; l=2244; t=1160014675; x=1160878675; c=relaxed/simple; s=sjdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:Cullen=20Jennings=20<fluffy@cisco.com> |Subject:Re=3A=20Gen-ART=20review=20of=20draft-schoenw-snmp-ether-01.txt; X=v=3Dcisco.com=3B=20h=3DicUigk5CWBffaXDNdhgdpiIj5iA=3D; b=C6WCnGdTFkUyu8WDzc/DYmZ2y1lyeBA1sA5mBy1G/3G7FRCwIq+uL3rkHPg0SI3zzOKoAj5y +COUFYXPzVtcVlBhKcd/LN0JAyKc6p6ApjBAPVszeiRa3xeGxzfIVJ0c;
Authentication-Results: sj-dkim-1.cisco.com; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, gen-art@ietf.org, Black_David@emc.com, tony@jeffree.co.uk
Subject: [Gen-art] Re: Gen-ART review of draft-schoenw-snmp-ether-01.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Errors-To: gen-art-bounces@ietf.org

I only put a comment not a discuss so you can decide to do whatever  
you want with this and don't need to wait for me - in truth I don't  
see a risk in implementors actually implement the wrong thing so I  
don't care but .....

I like the stuff you proposed - also I would change

In
    When an SNMP entity uses this transport mapping, it MUST be capable
    of accepting SNMP messages up to and including 484 octets in size.
    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.

I would move recommended to RECOMMENDED

On Sep 26, 2006, at 4:31 AM, Juergen Schoenwaelder wrote:

> On Tue, Sep 26, 2006 at 02:26:43PM +0300, Romascanu, Dan (Dan) wrote:
>
>> Can you indicate exactly for the RFC Editor where you suggest this  
>> text
>> to be inserted?
>
> Section 3.2, second paragraph:
>
> OLD:
>
>    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), an Ethernet type field value of 33100 (hexadecimal
>    814C) is 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] is used.
>
> NEW:
>
>    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.
>
> /js
>
> -- 
> Juergen Schoenwaelder		    International University Bremen
> <http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen,  
> Germany

_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www1.ietf.org/mailman/listinfo/gen-art