[Bridge-mib] RE: ieee8023-lag-mib : dot3adAggActorSystemPriority and dot3adAggPortActorSystemPriority definition

"Les Bell" <Les_Bell@eur.3com.com> Fri, 28 February 2003 09:34 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18380 for <bridge-archive@odin.ietf.org>; Fri, 28 Feb 2003 04:34:00 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1S9iOl12416 for bridge-archive@odin.ietf.org; Fri, 28 Feb 2003 04:44:24 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1S9i3p12403; Fri, 28 Feb 2003 04:44:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1S9hYp12380 for <bridge-mib@optimus.ietf.org>; Fri, 28 Feb 2003 04:43:34 -0500
Received: from columba.www.eur.3com.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18338 for <Bridge-mib@ietf.org>; Fri, 28 Feb 2003 04:32:39 -0500 (EST)
Received: from toucana.eur.3com.com (toucana.EUR.3Com.COM [140.204.220.50]) by columba.www.eur.3com.com with ESMTP id h1S9bvNS011298; Fri, 28 Feb 2003 09:37:57 GMT
Received: from notesmta.eur.3com.com (eurmta1.EUR.3Com.COM [140.204.220.206]) by toucana.eur.3com.com with SMTP id h1S9bnQ09885; Fri, 28 Feb 2003 09:37:49 GMT
Received: by notesmta.eur.3com.com(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id 80256CDB.0034D6DE ; Fri, 28 Feb 2003 09:37:08 +0000
X-Lotus-FromDomain: 3COM
From: "Les Bell" <Les_Bell@eur.3com.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
cc: "Rohit Rohit" <Rohit.Rohit@worldwidepackets.com>, mibs@ops.ietf.org, Bridge-mib@ietf.org, "David Law" <David_Law@eur.3com.com>
Message-ID: <80256CDB.0034D1CD.00@notesmta.eur.3com.com>
Date: Fri, 28 Feb 2003 09:34:37 +0000
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: [Bridge-mib] RE: ieee8023-lag-mib : dot3adAggActorSystemPriority and dot3adAggPortActorSystemPriority definition
Sender: bridge-mib-admin@ietf.org
Errors-To: bridge-mib-admin@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Id: <bridge-mib.ietf.org>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=subscribe>



Yes, these fixes are going through the IEEE 802.3 maintenance mechanism.  I do
not know the maintenance reference number, but I provided them with the fixes.

Les...





"Romascanu, Dan (Dan)" <dromasca@avaya.com> on 28/02/2003 01:51:32

Sent by:  "Romascanu, Dan (Dan)" <dromasca@avaya.com>


To:   Les Bell/GB/3Com, "Rohit Rohit" <Rohit.Rohit@worldwidepackets.com>
cc:   mibs@ops.ietf.org, Bridge-mib@ietf.org, David Law/GB/3Com
Subject:  RE: ieee8023-lag-mib : dot3adAggActorSystemPriority and
      dot3adAggPortActorSystemPriority definition




Les,

Did you (or somebody else) propose these fixes through the IEEE 802.3
maintenance mechanism?

Dan


> -----Original Message-----
> From: Les Bell [mailto:Les_Bell@eur.3com.com]
> Sent: Thursday, February 27, 2003 6:17 PM
> To: Rohit Rohit
> Cc: mibs@ops.ietf.org; Bridge-mib@ietf.org; David Law
> Subject: Re: ieee8023-lag-mib : dot3adAggActorSystemPriority
> and dot3adAggPortActorSystemPriority definition
>
>
>
>
>
> This is a known bug in the MIB and a fix should appear in the
> next revision of
> the 802.3 spec.
> There are a number of similar objects with the same bug.  The
> range should be
> (0..65535) on all of them.  The proposed fix is to deprecate
> these objects and
> replace them with corrected equivalents.  There are some
> other fixes pending
> also.
>
> Les...
>
>
>
>
>
> "Rohit Rohit" <Rohit.Rohit@worldwidepackets.com> on
> 26/02/2003 22:55:29
>
> Sent by:  "Rohit Rohit" <Rohit.Rohit@worldwidepackets.com>
>
>
> To:   mibs@ops.ietf.org
> cc:    (Les Bell/GB/3Com)
> Subject:  ieee8023-lag-mib : dot3adAggActorSystemPriority and
>       dot3adAggPortActorSystemPriority definition
>
>
>
>
> Hi,
>
>   I am not sure if this is the right group for this question;
>   but mail to 'stds-802-3-trunking@majordomo.ieee.org' does not seem
>   to work.
>
>   I see the following inconsistency between the
> dot3adAggActorSystemPriority
>   and dot3adAggPortActorSystemPriority.
>
>   dot3adAggPortActorSystemPriority is defined to be 2 octets; but
>   its range is only from 0 to 255. ( IMHO, it should be 0 .. 65535 ).
>
>  > dot3adAggPortActorSystemPriority OBJECT-TYPE
>  >   SYNTAX       INTEGER (0..255)
>  >   MAX-ACCESS   read-write
>  >   STATUS       current
>  >   DESCRIPTION
>  >       "A 2-octet read-write value used to define the priority
>  >       value associated with the Actor's System ID."
>  >   REFERENCE
>  >       "IEEE 802.3 Subclause 30.7.2.1.2"
>  >   ::= { dot3adAggPortEntry 2 }
>
>
>   while dot3adAggActorSystemPriority is also defined to be
>   2 octets; but its range is from 0..65535.
>
>   Any reason for this inconsistency ?
>
> > dot3adAggActorSystemPriority OBJECT-TYPE
> >    SYNTAX       INTEGER (0..65535)
> >    MAX-ACCESS   read-write
> >    STATUS       current
> >    DESCRIPTION
> >        "A 2-octet read-write value indicating the priority
> >        value associated with the Actor's System ID."
> >    REFERENCE
> >        "IEEE 802.3 Subclause 30.7.1.1.5"
> >    ::= { dot3adAggEntry 3 }
>
>
> Thanks
> Rohit
>
>
>
>
>
>
>




_______________________________________________
Bridge-mib mailing list
Bridge-mib@ietf.org
https://www1.ietf.org/mailman/listinfo/bridge-mib