[Bridge-mib] RE: ieee8023-lag-mib : dot3adAggActorSystemPriority and dot3adAggPortActorSystemPriority definition
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Fri, 28 February 2003 01:49 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 UAA00210 for <bridge-archive@odin.ietf.org>; Thu, 27 Feb 2003 20:49:10 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1S1xQf06184 for bridge-archive@odin.ietf.org; Thu, 27 Feb 2003 20:59:26 -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 h1S1xFp06177; Thu, 27 Feb 2003 20:59:15 -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 h1S1wPp06153 for <bridge-mib@optimus.ietf.org>; Thu, 27 Feb 2003 20:58:25 -0500
Received: from iere.net.avaya.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00170 for <Bridge-mib@ietf.org>; Thu, 27 Feb 2003 20:47:38 -0500 (EST)
Received: from iere.net.avaya.com (localhost [127.0.0.1]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id h1S1mnB17127 for <Bridge-mib@ietf.org>; Thu, 27 Feb 2003 20:48:49 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id h1S1mmw17122 for <Bridge-mib@ietf.org>; Thu, 27 Feb 2003 20:48:49 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Fri, 28 Feb 2003 03:51:32 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F03009BB4@is0004avexu1.global.avaya.com>
Thread-Topic: ieee8023-lag-mib : dot3adAggActorSystemPriority and dot3adAggPortActorSystemPriority definition
Thread-Index: AcLefHhCKeEqWeyTRgO02M9l3dfKHAAT0uWw
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Les Bell <Les_Bell@eur.3com.com>, Rohit Rohit <Rohit.Rohit@worldwidepackets.com>
Cc: mibs@ops.ietf.org, Bridge-mib@ietf.org, David Law <David_Law@eur.3com.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h1S1wQp06154
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>
Content-Transfer-Encoding: 8bit
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
- [Bridge-mib] Re: ieee8023-lag-mib : dot3adAggActo… Les Bell
- [Bridge-mib] RE: ieee8023-lag-mib : dot3adAggActo… Romascanu, Dan (Dan)
- [Bridge-mib] RE: ieee8023-lag-mib : dot3adAggActo… Les Bell