From bridge-mib-bounces@ietf.org  Sun Apr  3 17:34:05 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28099;
	Sun, 3 Apr 2005 17:34:05 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DICrE-0001Eo-4s; Sun, 03 Apr 2005 17:42:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DICbj-0004zQ-Gt; Sun, 03 Apr 2005 17:26:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DHTkc-0008Cc-3C
	for bridge-mib@megatron.ietf.org; Fri, 01 Apr 2005 16:32:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23280
	for <bridge-mib@ietf.org>; Fri, 1 Apr 2005 16:32:20 -0500 (EST)
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHTs0-0008NC-3t
	for bridge-mib@ietf.org; Fri, 01 Apr 2005 16:40:01 -0500
Received: from www by psg.com with local (Exim 4.44 (FreeBSD))
	id 1DHTkZ-000493-S5
	for bridge-mib@ietf.org; Fri, 01 Apr 2005 21:32:19 +0000
MIME-Version: 1.0
In-Reply-To: <rt-546@psg.com>
X-Mailer: Perl5 Mail::Internet v1.64
Message-ID: <rt-3.0.12-546-5528.14.5138912572828@psg.com>
Content-Type: text/plain; charset="utf-8"
RT-Originator: dbharrington@comcast.net
X-RT-Original-Encoding: utf-8
Managed-BY: RT 3.0.12 (http://www.bestpractical.com/rt/)
RT-Ticket: psg.com #546
Precedence: bulk
X-RT-Loop-Prevention: psg.com
From: rt+bridge-mib@rt.psg.com
Date: Fri, 01 Apr 2005 21:32:19 +0000
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4
X-Mailman-Approved-At: Sun, 03 Apr 2005 17:26:09 -0400
Subject: [Bridge-mib] [psg.com #546] ext-v2-02: editor affiliation
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Reply-To: rt+bridge-mib@rt.psg.com
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
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>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014

[dbharrington@comcast.net - Mon Oct 25 16:03:28 2004]:

corrected authors' addresses when available.


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


From bridge-mib-bounces@ietf.org  Sun Apr  3 17:34:06 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28117;
	Sun, 3 Apr 2005 17:34:06 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DICrE-0001Ep-25; Sun, 03 Apr 2005 17:42:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DICbj-0004zL-CL; Sun, 03 Apr 2005 17:26:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DHTkb-0008CB-Uy
	for bridge-mib@megatron.ietf.org; Fri, 01 Apr 2005 16:32:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23277
	for <bridge-mib@ietf.org>; Fri, 1 Apr 2005 16:32:19 -0500 (EST)
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHTrz-0008NB-Rt
	for bridge-mib@ietf.org; Fri, 01 Apr 2005 16:40:01 -0500
Received: from www by psg.com with local (Exim 4.44 (FreeBSD))
	id 1DHTkZ-00048z-Mf
	for bridge-mib@ietf.org; Fri, 01 Apr 2005 21:32:19 +0000
MIME-Version: 1.0
In-Reply-To: <rt-546@psg.com>
X-Mailer: Perl5 Mail::Internet v1.64
Message-ID: <rt-3.0.12-546-5528.10.6575857726324@psg.com>
Content-Type: text/plain; charset="utf-8"
RT-Originator: dbharrington@comcast.net
X-RT-Original-Encoding: utf-8
Managed-BY: RT 3.0.12 (http://www.bestpractical.com/rt/)
RT-Ticket: psg.com #546
Precedence: bulk
X-RT-Loop-Prevention: psg.com
From: rt+bridge-mib@rt.psg.com
Date: Fri, 01 Apr 2005 21:32:19 +0000
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4
X-Mailman-Approved-At: Sun, 03 Apr 2005 17:26:09 -0400
Subject: [Bridge-mib] [psg.com #546] ext-v2-02: editor affiliation
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Reply-To: rt+bridge-mib@rt.psg.com
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
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>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014

[dbharrington@comcast.net - Mon Oct 25 16:03:28 2004]:

corrected authors' addresses when available.


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


From bridge-mib-bounces@ietf.org  Sun Apr  3 17:34:19 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28141;
	Sun, 3 Apr 2005 17:34:19 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DICrR-0001FS-Id; Sun, 03 Apr 2005 17:42:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DICbj-0004zG-6r; Sun, 03 Apr 2005 17:26:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DHTiC-0007jc-Q4
	for bridge-mib@megatron.ietf.org; Fri, 01 Apr 2005 16:29:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23018
	for <bridge-mib@ietf.org>; Fri, 1 Apr 2005 16:29:50 -0500 (EST)
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHTpb-0008GF-F4
	for bridge-mib@ietf.org; Fri, 01 Apr 2005 16:37:31 -0500
Received: from www by psg.com with local (Exim 4.44 (FreeBSD))
	id 1DHTi7-0003jo-8E
	for bridge-mib@ietf.org; Fri, 01 Apr 2005 21:29:47 +0000
MIME-Version: 1.0
In-Reply-To: <rt-809@psg.com>
X-Mailer: Perl5 Mail::Internet v1.64
Message-ID: <rt-3.0.12-809-5526.12.4740999629188@psg.com>
Content-Type: text/plain; charset="utf-8"
RT-Originator: dbharrington@comcast.net
X-RT-Original-Encoding: utf-8
Managed-BY: RT 3.0.12 (http://www.bestpractical.com/rt/)
RT-Ticket: psg.com #809
Precedence: bulk
X-RT-Loop-Prevention: psg.com
From: rt+bridge-mib@rt.psg.com
Date: Fri, 01 Apr 2005 21:29:47 +0000
X-Spam-Score: 0.3 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
X-Mailman-Approved-At: Sun, 03 Apr 2005 17:26:09 -0400
Subject: [Bridge-mib] [psg.com #809] ext-v2-03: P-BRIDGE MODULE-IDENTITY
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Reply-To: rt+bridge-mib@rt.psg.com
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
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>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228

[dbharrington@comcast.net - Fri Jan 21 16:43:50 2005]:
> From John Flick:
> - LAST-UPDATED and REVISION dates need updating
>     - Need to keep the original REVISION clause from 2674 and just 
add
>       another revision for this version
>     - DESCRIPTION needs the required copyright boilerplate
>     - REVISION DESCRIPTION needs to identify changes made to this 
> module
>       since 2674 (one of Bert's favorite IESG Discusses...)
>     - CONTACT-INFO normally has editor's contact info


-04- 
includes original REVISION clause
updated the REVISION DESCRIPTION clause to identify changes
updated CONTACT-INFO to include the Bridge-mib@ietf.org and ietfmibs
updated CONTACT-INFO addresses
added abbreviated copyright
unusual circumstances have caused multiple changes of editors; current 
editors are not necessarily the best persons for interpretations.






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


From bridge-mib-bounces@ietf.org  Sun Apr  3 17:34:43 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28174;
	Sun, 3 Apr 2005 17:34:43 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DICrp-0001G0-IS; Sun, 03 Apr 2005 17:42:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DICbj-0004zB-14; Sun, 03 Apr 2005 17:26:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DHTiC-0007jX-Kr
	for bridge-mib@megatron.ietf.org; Fri, 01 Apr 2005 16:29:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23019
	for <bridge-mib@ietf.org>; Fri, 1 Apr 2005 16:29:50 -0500 (EST)
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHTpb-0008GG-FS
	for bridge-mib@ietf.org; Fri, 01 Apr 2005 16:37:31 -0500
Received: from www by psg.com with local (Exim 4.44 (FreeBSD))
	id 1DHTi7-0003jr-Dx
	for bridge-mib@ietf.org; Fri, 01 Apr 2005 21:29:47 +0000
MIME-Version: 1.0
In-Reply-To: <rt-809@psg.com>
X-Mailer: Perl5 Mail::Internet v1.64
Message-ID: <rt-3.0.12-809-5526.3.37577087053333@psg.com>
Content-Type: text/plain; charset="utf-8"
RT-Originator: dbharrington@comcast.net
X-RT-Original-Encoding: utf-8
Managed-BY: RT 3.0.12 (http://www.bestpractical.com/rt/)
RT-Ticket: psg.com #809
Precedence: bulk
X-RT-Loop-Prevention: psg.com
From: rt+bridge-mib@rt.psg.com
Date: Fri, 01 Apr 2005 21:29:47 +0000
X-Spam-Score: 0.3 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
X-Mailman-Approved-At: Sun, 03 Apr 2005 17:26:09 -0400
Subject: [Bridge-mib] [psg.com #809] ext-v2-03: P-BRIDGE MODULE-IDENTITY
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Reply-To: rt+bridge-mib@rt.psg.com
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
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>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228

[dbharrington@comcast.net - Fri Jan 21 16:43:50 2005]:
> From John Flick:
> - LAST-UPDATED and REVISION dates need updating
>     - Need to keep the original REVISION clause from 2674 and just 
add
>       another revision for this version
>     - DESCRIPTION needs the required copyright boilerplate
>     - REVISION DESCRIPTION needs to identify changes made to this 
> module
>       since 2674 (one of Bert's favorite IESG Discusses...)
>     - CONTACT-INFO normally has editor's contact info


-04- 
includes original REVISION clause
updated the REVISION DESCRIPTION clause to identify changes
updated CONTACT-INFO to include the Bridge-mib@ietf.org and ietfmibs
updated CONTACT-INFO addresses
added abbreviated copyright
unusual circumstances have caused multiple changes of editors; current 
editors are not necessarily the best persons for interpretations.






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


From bridge-mib-bounces@ietf.org  Wed Apr  6 21:51:53 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02542;
	Wed, 6 Apr 2005 21:51:53 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJMK0-0005Bm-TF; Wed, 06 Apr 2005 22:00:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJMA9-0003Jm-1b; Wed, 06 Apr 2005 21:50:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJMA8-0003Ja-9N
	for bridge-mib@megatron.ietf.org; Wed, 06 Apr 2005 21:50:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02459
	for <bridge-mib@ietf.org>; Wed, 6 Apr 2005 21:50:26 -0400 (EDT)
Message-Id: <200504070150.VAA02459@ietf.org>
Received: from sccrmhc14.comcast.net ([204.127.202.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJMIa-00059l-7h
	for bridge-mib@ietf.org; Wed, 06 Apr 2005 21:59:13 -0400
Received: from djyxpy41 (c-24-128-104-220.hsd1.nh.comcast.net[24.128.104.220])
	by comcast.net (sccrmhc14) with SMTP
	id <20050407015016014000ndcae>; Thu, 7 Apr 2005 01:50:16 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: "'Bridge-Mib \(E-mail\)'" <bridge-mib@ietf.org>
Date: Wed, 6 Apr 2005 21:50:13 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
thread-index: AcU7FCNbq/8hV2CZQMyQSU2FagW6fA==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit
Subject: [Bridge-mib] RSTP MIB resolutions
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dbharrington@comcast.net
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
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>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit

Hi,

A number of issues were raised during WGLC, which have now been
addressed in either the -05- revision or the -06- revision of the
draft.

RSTPMIB resolutions

-------------------------------
#536 references and boilerplates

updated in -05-
-------------------------------
#537: rstp-mib-04: dot1dStpPortPathCost vs dot1dStpPortPathCost32 
resolved in -05-
-------------------------------
#538 stpCompatible enum should start at 1, not 0

The values 0 ("STP Compatibility" mode) and 2 ("default, normal
version") are taken from the IEEE specification. 
Reference: IEEE 802.1D-2004 17.13.4

no change required
--------------------------------
#539: rstp-mib-04: dot1dStpPathCostDefault 
rewritten in -05-
-------------------------------
#540: rstp-mib-04: dot1dStpPortProtocolMigration
The text in -05- has been updated to reflect the behavior described by
802.1W 17.18.10 mcheck.
-------------------------------
#541: rstp-mib-04: rstpCompliance and rstpDefaultPathCostGroup

-------------------------------
#606: rstp-mib-04: autoedgeport 
this item will be deferred to IEEE.
-------------------------------
#613: rstp-mib-05:dependencies 
these need to be resolved.
-------------------------------
#759: smiv2-07: rstpMIB registration 
done

David Harrington
dbharrington@comcast.net




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


From bridge-mib-bounces@ietf.org  Thu Apr  7 17:06:23 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07981;
	Thu, 7 Apr 2005 17:06:23 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJeLQ-0002fT-T1; Thu, 07 Apr 2005 17:15:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJe42-0002xi-3k; Thu, 07 Apr 2005 16:57:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJLAA-0005hu-UM
	for bridge-mib@megatron.ietf.org; Wed, 06 Apr 2005 20:46:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27395
	for <bridge-mib@ietf.org>; Wed, 6 Apr 2005 20:46:23 -0400 (EDT)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJLIb-0003jJ-Ch
	for bridge-mib@ietf.org; Wed, 06 Apr 2005 20:55:10 -0400
Received: from zsc3c026.us.nortel.com (zsc3c026.us.nortel.com [47.81.138.26])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id j370k4m23465
	for <bridge-mib@ietf.org>; Wed, 6 Apr 2005 20:46:04 -0400 (EDT)
Received: by zsc3c026.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GWZNM104>; Wed, 6 Apr 2005 17:45:02 -0700
Message-ID: <0A11633F61BD9F40B43ABCC694004F930924FFE4@zsc3c026.us.nortel.com>
From: "David Levi" <dlevi@nortel.com>
To: bridge-mib@ietf.org
Date: Wed, 6 Apr 2005 17:44:53 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C53B0A.A45B2C7C"
X-Spam-Score: 0.6 (/)
X-Scan-Signature: a524c7c9e934f9a0c4cc31bc9e9e4c51
X-Mailman-Approved-At: Thu, 07 Apr 2005 16:57:20 -0400
Subject: [Bridge-mib] (no subject)
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
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>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 923866e691e2fd35ad8b399a2d23b59c

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C53B0A.A45B2C7C
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C53B0A.A45B2C7C"


------_=_NextPart_001_01C53B0A.A45B2C7C
Content-Type: text/plain

Hi,

Here is an updated RSTP-MIB ID, with changebars.

-Dave Levi

------------------------------------------------------------------------
David B. Levi             Nortel Networks    dlevi@nortelnetworks.com
Voice: +1 865 686 0432    ESN: 455-6004
------------------------------------------------------------------------ 


------_=_NextPart_001_01C53B0A.A45B2C7C
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE></TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Hi,</FONT>
</P>

<P><FONT SIZE=3D2>Here is an updated RSTP-MIB ID, with =
changebars.</FONT>
</P>

<P><FONT SIZE=3D2>-Dave Levi</FONT>
</P>

<P><FONT =
SIZE=3D2>---------------------------------------------------------------=
---------</FONT>
<BR><FONT SIZE=3D2>David B. =
Levi&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Nortel Networks&nbsp;&nbsp;&nbsp; dlevi@nortelnetworks.com</FONT>
<BR><FONT SIZE=3D2>Voice: +1 865 686 0432&nbsp;&nbsp;&nbsp; ESN: =
455-6004</FONT>
<BR><FONT =
SIZE=3D2>---------------------------------------------------------------=
--------- </FONT>
</P>

<P><FONT FACE=3D"Arial" SIZE=3D2 COLOR=3D"#000000"></FONT>&nbsp;

</BODY>
</HTML>
------_=_NextPart_001_01C53B0A.A45B2C7C--

------_=_NextPart_000_01C53B0A.A45B2C7C
Content-Type: text/plain;
	name="rstp.cb.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="rstp.cb.txt"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable





Internet Draft                  RSTP MIB                      April =
2005


Internet Draft                                                   V. =
Ngai
Expires October 2005                                  Enterasys =
Networks |
draft-ietf-bridge-rstpmib-06.txt                                 E. =
Bell |
                                                              3Com =
Corp.
                                                              April =
2005 |

               Definitions of Managed Objects for Bridges
                   with Rapid Spanning Tree Protocol

Status of this Memo

   By submitting this Internet-Draft, I certify that any applicable
   patent or other IPR claims of which I am aware have been disclosed,
   or will be disclosed, and any of which I become aware will be
   disclosed, in accordance with RFC 3668.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six =
months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on January 21, 2005.

Copyright Notice

   Copyright (C) The Internet Society (2004).  All Rights Reserved.

Abstract

   This memo defines an SMIv2 MIB module for managing the Rapid =
Spanning |
   Tree capability defined by the IEEE P802.1t and P802.1w amendments =
to |
   IEEE Std 802.1D-1998 for bridging between Local Area Network (LAN)   =
 |
   segments.  The objects in this MIB are defined to apply both to      =
 |
   transparent bridging and to bridges connected by subnetworks other   =
 |
   than LAN segments.                                                   =
 |





Ngai et. al               Expires October 2005                  [Page =
1]
=0C
Internet Draft                  RSTP MIB                      April =
2005


Table of Contents


   1 The Internet-Standard Management Framework ...................    =
3
   2 Overview .....................................................    =
3
   3 Relationship to IEEE 802.1t and 802.1w amendments ............    =
3
   4 Relation to the BRIDGE-MIB ...................................    =
4
   5 Definitions for RSTP-MIB .....................................    =
5
   6 Acknowledgments ..............................................   =
11
   7 IANA Considerations ..........................................   =
11
   8 Security Considerations ......................................   =
11
   9 Normative References .........................................   =
13
   10 Informative References ......................................   =
14
   11 Authors' Addresses ..........................................   =
15
    Intellectual Property Statement ...............................   =
16
    Disclaimer of Validity ........................................   =
16
    Copyright Statement ...........................................   =
16


































Ngai et. al               Expires October 2005                  [Page =
2]
=0C
Internet Draft                  RSTP MIB                      April =
2005


1.  The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [RFC3410].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  MIB objects are generally
   accessed through the Simple Network Management Protocol (SNMP).
   Objects in the MIB are defined using the mechanisms defined in the
   Structure of Management Information (SMI).  This memo specifies a =
MIB
   module that is compliant to the SMIv2, which is described in STD 58,
   RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
   [RFC2580].


2.  Overview

   This memo defines an SMIv2 MIB module for managing the Rapid =
Spanning |
   Tree (RSTP) capability defined by the IEEE P802.1t [802.1t] and      =
 |
   P802.1w [802.1w] amendments to IEEE Std 802.1D-1998 [802.1D-1998] =
for |
   bridging between Local Area Network (LAN) segments.  The objects in  =
 |
   this MIB are defined to apply both to transparent bridging and to    =
 |
   bridges connected by subnetworks other than LAN segments.            =
 |


3.  Relationship to IEEE 802.1t and 802.1w amendments

   This document defines managed object for the Rapid Spanning Tree     =
 |
   Protocol defined by the IEEE P802.1t and IEEE P802.1w amendments to  =
 |
   802.1d-1998.                                                         =
 |

   RSTP-MIB Name                       IEEE 802.1 Reference             =
 |

   dot1dStp
     dot1dStpVersion                   (w) 17.16.1  ForceVersion
     dot1dStpTxHoldCount               (w) 17.16.6  TxHoldCount
     dot1dStpExtPortTable                                               =
 -
       dot1dStpPortProtocolMigration   (w) 17.18.10 mcheck
       dot1dStpPortAdminEdgePort       (t) 18.3.3   adminEdgePort
       dot1dStpPortOperEdgePort        (t) 18.3.4   operEdgePort
       dot1dStpPortAdminPointToPoint   (w) 6.4.3    =
adminPointToPointMAC
       dot1dStpPortOperPointToPoint    (w) 6.4.3    operPointToPointMAC
       dot1dStpPortAdminPathCost       (D) 8.5.5.3  Path Cost

   Following are the references for the above objects in 802.1D-2004.   =
 |





Ngai et. al               Expires October 2005                  [Page =
3]
=0C
Internet Draft                  RSTP MIB                      April =
2005


   RSTP-MIB Name                       IEEE 802.1D-2004 Reference       =
 |

   dot1dStp                                                             =
 |
     dot1dStpVersion                   17.13.4  ForceVersion            =
 |
     dot1dStpTxHoldCount               17.13.12 TxHoldCount             =
 |
     dot1dStpExtPortTable                                               =
 |
       dot1dStpPortProtocolMigration   17.19.13 mcheck                  =
 |
       dot1dStpPortAdminEdgePort       17.13.1  adminEdgePort           =
 |
       dot1dStpPortOperEdgePort        17.19.17 operEdgePort            =
 |
       dot1dStpPortAdminPointToPoint   6.4.3    adminPointToPointMAC    =
 |
       dot1dStpPortOperPointToPoint    6.4.3    operPointToPointMAC     =
 |
       dot1dStpPortAdminPathCost       17.13.11 Path Cost               =
 |



4.  Relation to the BRIDGE-MIB                                          =
 -

   The Original BRIDGE-MIB [RFC1493] has been updated in an             =
 |
   SMIv2-compliant version [RFC1493bis]. Conformance statements have    =
 |
   been added and some description and reference clauses have been      =
 |
   updated. The interpretations of some objects were changed to         =
 |
   accommodate IEEE 802.1t and 802.1w amendments.                       =
 |

   The object dot1dStpPortPathCost32 was added to support IEEE 802.1t,  =
 |
   and the permissible values of dot1dStpPriority and                   =
 |
   dot1dStpPortPriority have been clarified for bridges supporting IEEE =
 |
   802.1t or IEEE 802.1w. The interpretation of                         =
 |
   dot1dStpTimeSinceTopologyChange has been clarified for bridges       =
 |
   supporting the RSTP.                                                 =
 |

   See the updated BRIDGE-MIB [RFC1493bis] for details.                 =
 |

   The objects in the RSTP-MIB supplement those defined in the Bridge   =
 |
   MIB [RFC1493bis].                                                    =
 |

















Ngai et. al               Expires October 2005                  [Page =
4]
=0C
Internet Draft                  RSTP MIB                      April =
2005


5.  Definitions for RSTP-MIB

RSTP-MIB DEFINITIONS ::=3D BEGIN

-- -------------------------------------------------------------
-- MIB for IEEE 802.1w Rapid Spanning Tree Protocol
-- -------------------------------------------------------------

IMPORTS
    MODULE-IDENTITY, OBJECT-TYPE, Integer32
        FROM SNMPv2-SMI
    TruthValue
        FROM SNMPv2-TC
    MODULE-COMPLIANCE, OBJECT-GROUP
        FROM SNMPv2-CONF
    dot1dBridge, dot1dStp, dot1dStpPortEntry
        FROM BRIDGE-MIB;

rstpMIB MODULE-IDENTITY
    LAST-UPDATED "200503190000Z"                                        =
 |
    ORGANIZATION "IETF Bridge MIB Working Group"
    CONTACT-INFO
        "Email: Bridge-mib@ietf.org"
    DESCRIPTION
        "The Bridge MIB Extension module for managing devices
         that support the Rapid Spanning Tree Protocol defined
         by IEEE 802.1w."
    REVISION     "200503190000Z"                                        =
 |
-- RFC Ed.: replace XXXX with RFC number and remove this note           =
 |
    DESCRIPTION
         "Initial revision, published as part of RFC XXXX"              =
 |
-- RFC Ed.: replace xxxx with IANA-assigned number and                  =
 |
--          remove this note                                            =
 |
    ::=3D { mib-2 xxxx }                                                =
   |

-- ---------------------------------------------------------- --        =
 |
-- subtrees in the RSTP-MIB                                             =
 |
-- ---------------------------------------------------------- --        =
 |

rstpNotifications OBJECT IDENTIFIER ::=3D { rstpMIB 0 }                 =
   |
rstpObjects       OBJECT IDENTIFIER ::=3D { rstpMIB 1 }                 =
   |
rstpConformance   OBJECT IDENTIFIER ::=3D { rstpMIB 2 }                 =
   |

-- -------------------------------------------------------------
-- Addition to the dot1dStp group
-- -------------------------------------------------------------





Ngai et. al               Expires October 2005                  [Page =
5]
=0C
Internet Draft                  RSTP MIB                      April =
2005


dot1dStpVersion OBJECT-TYPE
    SYNTAX      INTEGER {
                    stpCompatible(0),
                    rstp(2)
                }
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "The version of Spanning Tree Protocol the bridge is
         currently running.  The value 'stpCompatible(0)'
         indicates the Spanning Tree Protocol specified in
         IEEE 802.1D-1998 and 'rstp(2)' indicates the Rapid             =
 |
         Spanning Tree Protocol specified in IEEE 802.1w and            =
 |
         clause 17 of 802.1D-2004.  New values may be defined           =
 |
         as future versions of the protocol become available."          =
 |
    REFERENCE
        "IEEE 802.1w clause 14.8.1, 17.12, 17.16.1"
    DEFVAL      { rstp }
    ::=3D { dot1dStp 16 }

dot1dStpTxHoldCount OBJECT-TYPE
    SYNTAX      Integer32 (1..10)
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "The value used by the Port Transmit state machine to limit
         the maximum transmission rate."
    REFERENCE
        "IEEE 802.1w clause 17.16.6"
    DEFVAL      { 3 }
    ::=3D { dot1dStp 17 }

--                                                                      =
 |
-- { dot1dStp 18 } was used to represent dot1dStpPathCostDefault        =
 |
-- in an internet-draft version of this MIB.  It has since been         =
 |
-- obsoleted, and should not be used.                                   =
 |
--                                                                      =
 |

dot1dStpExtPortTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF Dot1dStpExtPortEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A table that contains port-specific Rapid Spanning Tree
         information."
    ::=3D { dot1dStp 19 }





Ngai et. al               Expires October 2005                  [Page =
6]
=0C
Internet Draft                  RSTP MIB                      April =
2005


dot1dStpExtPortEntry OBJECT-TYPE
    SYNTAX      Dot1dStpExtPortEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A list of Rapid Spanning Tree information maintained by
         each port."
    AUGMENTS    { dot1dStpPortEntry }
    ::=3D { dot1dStpExtPortTable 1 }

Dot1dStpExtPortEntry ::=3D
    SEQUENCE {
        dot1dStpPortProtocolMigration
            TruthValue,
        dot1dStpPortAdminEdgePort
            TruthValue,
        dot1dStpPortOperEdgePort
            TruthValue,
        dot1dStpPortAdminPointToPoint
            INTEGER,
        dot1dStpPortOperPointToPoint
            TruthValue,
        dot1dStpPortAdminPathCost
            Integer32
    }

dot1dStpPortProtocolMigration OBJECT-TYPE
    SYNTAX      TruthValue
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "When operating in RSTP (version 2) mode, writing TRUE(1)
         to this object forces this port to transmit RSTP BPDUs.
         Any other operation on this object has no effect and
         it always returns FALSE(2) when read."
    REFERENCE
        "IEEE 802.1w clause 14.8.2.4, 17.18.10, 17.26"
    ::=3D { dot1dStpExtPortEntry 1 }

dot1dStpPortAdminEdgePort OBJECT-TYPE
    SYNTAX      TruthValue
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "The administrative value of the Edge Port parameter. A
         value of TRUE(1) indicates that this port should be





Ngai et. al               Expires October 2005                  [Page =
7]
=0C
Internet Draft                  RSTP MIB                      April =
2005


         assumed as an edge-port and a value of FALSE(2) indicates
         that this port should be assumed as a non-edge-port.
         Setting this object will also cause the corresponding
         instance of dot1dStpPortOperEdgePort to change to the
         same value. Note that even when this object's value
         is true, the value of the corresponding instance of
         dot1dStpPortOperEdgePort can be false if a BPDU has
         been received."
    REFERENCE
        "IEEE 802.1t clause 14.8.2, 18.3.3"
    ::=3D { dot1dStpExtPortEntry 2 }

dot1dStpPortOperEdgePort OBJECT-TYPE
    SYNTAX      TruthValue
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The operational value of the Edge Port parameter. The
         object is initialized to the value of the corresponding
         instance of dot1dStpPortAdminEdgePort. When the
         corresponding instance of dot1dStpPortAdminEdgePort is
         set, this object will be changed as well. This object
         will also be changed to FALSE on reception of a BPDU."
    REFERENCE
        "IEEE 802.1t clause 14.8.2, 18.3.4"
    ::=3D { dot1dStpExtPortEntry 3 }

dot1dStpPortAdminPointToPoint OBJECT-TYPE
    SYNTAX      INTEGER {
                    forceTrue(0),
                    forceFalse(1),
                    auto(2)
                }
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "The administrative point-to-point status of the LAN segment
         attached to this port.  A value of forceTrue(0) indicates that
         this port should always be treated as if it is connected to
         a point-to-point link.  A value of forceFalse(1) indicates
         that this port should be treated as having a shared media
         connection.  A value of auto(2) indicates that this port is
         considered to have a point-to-point link if it is an =
Aggregator
         and all of its members are aggregatable, or if the MAC entity
         is configured for full duplex operation, either through
         auto-negotiation or by management means."





Ngai et. al               Expires October 2005                  [Page =
8]
=0C
Internet Draft                  RSTP MIB                      April =
2005


   REFERENCE
       "IEEE 802.1w clause 6.4.3, 6.5, 14.8.2"
   ::=3D { dot1dStpExtPortEntry 4 }

dot1dStpPortOperPointToPoint OBJECT-TYPE
    SYNTAX      TruthValue
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The operational point-to-point status of the LAN segment
         attached to this port.  It indicates whether a port is
         considered to have a point-to-point connection or not.
         The value is determined by management or by auto-detection,
         as described in the dot1dStpPortAdminPointToPoint object."
    REFERENCE
        "IEEE 802.1w clause 6.4.3, 6.5, 14.8.2"
    ::=3D { dot1dStpExtPortEntry 5 }

dot1dStpPortAdminPathCost OBJECT-TYPE
    SYNTAX      Integer32 (0..200000000)
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "The administratively assigned value for the contribution
         of this port to the path cost of paths towards the spanning
         tree root.

         Writing a value of '0' assigns the automatically calculated
         default Path Cost value to the port.  If the default Path
         Cost is being used, this object returns '0' when read.

         This complements the object dot1dStpPortPathCost or
         dot1dStpPortPathCost32, which returns the operational value
         of the path cost."
    REFERENCE
        "IEEE 802.1D-1998: Section 8.5.5.3"
    ::=3D { dot1dStpExtPortEntry 6 }

-- -------------------------------------------------------------
-- rstpMIB - Conformance Information
-- -------------------------------------------------------------

rstpGroups OBJECT IDENTIFIER ::=3D { rstpConformance 1 }                =
   -

rstpCompliances OBJECT IDENTIFIER ::=3D { rstpConformance 2 }






Ngai et. al               Expires October 2005                  [Page =
9]
=0C
Internet Draft                  RSTP MIB                      April =
2005


-- -------------------------------------------------------------
-- Units of conformance
-- -------------------------------------------------------------

rstpBridgeGroup OBJECT-GROUP
    OBJECTS {
        dot1dStpVersion,
        dot1dStpTxHoldCount
    }
    STATUS      current
    DESCRIPTION
        "Rapid Spanning Tree information for the bridge."
    ::=3D { rstpGroups 1 }

rstpPortGroup OBJECT-GROUP                                              =
 -
    OBJECTS {
        dot1dStpPortProtocolMigration,
        dot1dStpPortAdminEdgePort,
        dot1dStpPortOperEdgePort,
        dot1dStpPortAdminPointToPoint,
        dot1dStpPortOperPointToPoint,
        dot1dStpPortAdminPathCost
    }
    STATUS      current
    DESCRIPTION
        "Rapid Spanning Tree information for individual ports."
    ::=3D { rstpGroups 2 }                                              =
   |

-- -------------------------------------------------------------
-- Compliance statements
-- -------------------------------------------------------------

rstpCompliance MODULE-COMPLIANCE
    STATUS      current
    DESCRIPTION
        "The compliance statement for device support of Rapid           =
 |
         Spanning Tree Protocol (RSTP) bridging services."              =
 |
    MODULE
        MANDATORY-GROUPS {
            rstpBridgeGroup,
            rstpPortGroup
        }
    ::=3D { rstpCompliances 1 }                                         =
   -

END






Ngai et. al               Expires October 2005                 [Page =
10]
=0C
Internet Draft                  RSTP MIB                      April =
2005


6.  Acknowledgments                                                     =
 +

   This document was produced on behalf of the Bridge MIB Working Group
   in the Operations and Management area of the Internet Engineering
   Task Force.

   The authors wish to thank the members of the Bridge MIB Working
   Group, especially Alex Ruzin, for their comments and suggestions
   which improved this effort.



7.  IANA Considerations                                                 =
 +

   This document requires an OID assignment to be made by IANA:         =
 +

            Descriptor        OBJECT IDENTIFIER value                   =
 +
            ----------        -----------------------                   =
 +
            rstpMIB           { mib-2 xxxx }                            =
 +



8.  Security Considerations

   There are a number of management objects defined in this MIB that
   have a MAX-ACCESS clause of read-write and/or read-create.  Such
   objects may be considered sensitive or vulnerable in some network
   environments.  The support for SET operations in a non-secure
   environment without proper protection can have a negative effect on
   network operations.

   Writable objects that could be misused to cause network delays and   =
 +
   spanning tree instabilities include dot1dStpVersion,                 =
 +
   dot1dStpTxHoldCount, dot1dStpPortProtocolMigration,                  =
 +
   dot1dStpPortAdminEdgePort, and dot1dStpPortAdminPathCost.            =
 +

   The object dot1dStpVersion could be read by an attacker to identify  =
 +
   environments containing applications or protocols which are          =
 +
   potentially sensitive to RSTP mode.                                  =
 +

   The object dot1dStpPortAdminPointToPoint could be used to mislead an =
 +
   access control protocol, such as 802.1x, to believe that only one    =
 +
   other system is attached to a LAN segment and to enable network      =
 +
   access based on that assumption.  This situation could permit        =
 +
   potential man-in-the-middle attacks.                                 =
 +






Ngai et. al               Expires October 2005                 [Page =
11]
=0C
Internet Draft                  RSTP MIB                      April =
2005


   SNMPv1 by itself is not a secure environment.  Even if the network
   itself is secure (for example by using IPSec), even then, there is =
no
   control as to who on the secure network is allowed to access and
   GET/SET (read/change/create/delete) the objects in this MIB.

   It is recommended that the implementers consider the security
   features as provided by the SNMPv3 framework.  Specifically, the use
   of the User-based Security Model [USM] and the View-based Access
   Control Model [VACM] is recommended.










































Ngai et. al               Expires October 2005                 [Page =
12]
=0C
Internet Draft                  RSTP MIB                      April =
2005


9.  Normative References

[RFC2578]    McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
             Rose, M., and S. Waldbusser, "Structure of Management
             Information Version 2 (SMIv2)", STD 58, RFC 2578, April
             1999.

[RFC2579]    McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
             Rose, M., and S. Waldbusser, "Textual Conventions for
             SMIv2", STD 58, RFC 2579, April 1999.

[RFC2580]    McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
             Rose, M., and S. Waldbusser, "Conformance Statements for
             SMIv2", STD 58, RFC 2580, April 1999.

[RFC2674]    Bell, E., Smith, A., Langille, P., Rijhsinghani, A. and
             McCloghrie, "Definitions of Managed Objects for Bridges
             with Traffic Classes, Multicast Filtering and Virtual LAN
             Extensions", RFC 2674, August 1999.

[802.1D-1998]     "Information technology - Telecommunications and      =
 |
             information                                                =
 |
             exchange between systems - Local and metropolitan area
             networks - Common specifications - Part 3: Media Access
             Control (MAC) Bridges:  Revision.  This is a revision of
             ISO/IEC 10038: 1993, 802.1j-1992 and 802.6k-1992.  It
             incorporates P802.11c, P802.1p and P802.12e."  ISO/IEC
             15802-3: 1998.

[802.1D-2004]     IEEE Project 802 Local and Metropolitan  Area         =
 +
             Networks, "IEEE Standard 802.1D-2004 MAC Bridges", 2004.   =
 +

[RFC1493]  Decker, E., Langille, P., Rijsinghani, A. and K.  =
McCloghrie,
             "Definitions of Managed Objects for Bridges", RFC 1493,
             July 1993.

[RFC1493bis]  Bell, E. and Norseth, K., "Definitions of Managed Objects =
 +
             for Bridges", draft-ietf-bridge-bridgemib-smiv2-10.txt,    =
 +
             February 2005.  NOTE TO RFC EDITOR:  Replace the above ID  =
 +
             reference with the appropriate RFC.                        =
 +

[802.1t]     IEEE 802.1t-2001, "(Amendment to IEEE Standard 802.1D) =
IEEE
             Standard for Information technology - Telecommunications
             and information exchange between systems - Local and
             metropolitan area networks - Common specifications - Part
             3: Media Access Control (MAC) Bridges: Technical and





Ngai et. al               Expires October 2005                 [Page =
13]
=0C
Internet Draft                  RSTP MIB                      April =
2005


             Editorial Corrections".

[802.1w]     IEEE 802.1w-2001, "(Amendment to IEEE Standard 802.1D) =
IEEE
             Standard for Information technology--Telecommunications =
and
             information exchange between systems--Local and
             metropolitan area networks--Common Specifications--Part 3:
             Media Access Control (MAC) Bridges: Rapid Reconfiguation".


10.  Informative References

[RFC3410]    Case, J., Mundy, R., Partain, D. and B. Stewart,           =
 |
             "Introduction and Applicability Statements for Internet    =
 |
             Standard                                                   =
 |
             Management Framework", RFC 3410, December 2002.




































Ngai et. al               Expires October 2005                 [Page =
14]
=0C
Internet Draft                  RSTP MIB                      April =
2005


11.  Authors' Addresses

   Les Bell
   3Com Europe Limited
   eCom Centre, Boundary Way
   Hemel Hempstead
   Herts.  HP2 7YU
   UK

   Phone:  +44 1442 438025
   Email:  Les_Bell@3Com.com


   Vivian Ngai
   Enterasys Networks
   2691 South Decker Lake Lane
   Salt Lake City, UT 84119
   USA

   Phone: +1 801 556 5652
   Email: vivian_ngai@acm.org






























Ngai et. al               Expires October 2005                 [Page =
15]
=0C
Internet Draft                  RSTP MIB                      April =
2005


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed =
to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  =
Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use =
of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository =
at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Disclaimer of Validity

   This document and the information contained herein are provided on =
an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE =
REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Copyright Statement

   Copyright (C) The Internet Society (2004).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.










Ngai et. al               Expires October 2005                 [Page =
16]
=0C

------_=_NextPart_000_01C53B0A.A45B2C7C
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

------_=_NextPart_000_01C53B0A.A45B2C7C--



From bridge-mib-bounces@ietf.org  Thu Apr  7 22:34:16 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02019;
	Thu, 7 Apr 2005 22:34:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJjSm-0004Y0-3x; Thu, 07 Apr 2005 22:43:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJjJ1-0000gy-9p; Thu, 07 Apr 2005 22:33:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJjIz-0000g9-Hb
	for bridge-mib@megatron.ietf.org; Thu, 07 Apr 2005 22:33:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01984
	for <bridge-mib@ietf.org>; Thu, 7 Apr 2005 22:33:06 -0400 (EDT)
Message-Id: <200504080233.WAA01984@ietf.org>
Received: from sccrmhc12.comcast.net ([204.127.202.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJjRe-0004UR-Mx
	for bridge-mib@ietf.org; Thu, 07 Apr 2005 22:42:07 -0400
Received: from djyxpy41 (c-24-128-104-220.hsd1.nh.comcast.net[24.128.104.220])
	by comcast.net (sccrmhc12) with SMTP
	id <2005040802325801200rovjke>; Fri, 8 Apr 2005 02:32:58 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: "'Bridge-Mib \(E-mail\)'" <bridge-mib@ietf.org>
Date: Thu, 7 Apr 2005 22:32:54 -0400
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0061_01C53BC1.BE88CB10"
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcU7sr3v331NlFQ9R+65vozQL/jR1QAMGUHQ
X-Spam-Score: 1.3 (+)
X-Scan-Signature: 34474d0466a434d4c6281ffb0db1cdfa
Subject: [Bridge-mib] FW: RSTP MIB
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dbharrington@comcast.net
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
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>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 1.5 (+)
X-Scan-Signature: 5566bd7403e564923b19a8c565ff243c

This is a multi-part message in MIME format.

------=_NextPart_000_0061_01C53BC1.BE88CB10
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0062_01C53BC1.BE8D5EF0"


------=_NextPart_001_0062_01C53BC1.BE8D5EF0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

 



 Here  is an updated RSTP-MIB ID, with changebars. 

-Dave Levi 

----------------------------------------------------------------------
-- 
David B. Levi             Nortel Networks    dlevi@nortelnetworks.com 
Voice: +1 865 686 0432    ESN: 455-6004 
----------------------------------------------------------------------
-- 




------=_NextPart_001_0062_01C53BC1.BE8D5EF0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2604" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma>
  <P><FONT face=3DArial color=3D#0000ff></FONT><BR></FONT><FONT =
size=3D2><SPAN=20
  class=3D096583102-08042005><FONT face=3DArial =
color=3D#0000ff>&nbsp;Here=20
  &nbsp;</FONT></SPAN>is an updated RSTP-MIB ID, with changebars.</FONT> =

  </P></DIV>
  <P><FONT size=3D2>-Dave Levi</FONT> </P>
  <P><FONT=20
  =
size=3D2>----------------------------------------------------------------=
--------</FONT>=20
  <BR><FONT size=3D2>David B.=20
  =
Levi&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
  Nortel Networks&nbsp;&nbsp;&nbsp; dlevi@nortelnetworks.com</FONT> =
<BR><FONT=20
  size=3D2>Voice: +1 865 686 0432&nbsp;&nbsp;&nbsp; ESN: 455-6004</FONT> =
<BR><FONT=20
  =
size=3D2>----------------------------------------------------------------=
--------=20
  </FONT></P>
  <P><FONT face=3DArial color=3D#000000 size=3D2></FONT> =
</P></BLOCKQUOTE></BODY></HTML>

------=_NextPart_001_0062_01C53BC1.BE8D5EF0--

------=_NextPart_000_0061_01C53BC1.BE88CB10
Content-Type: text/plain;
	name="rstp.cb.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="rstp.cb.txt"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable





Internet Draft                  RSTP MIB                      April 2005


Internet Draft                                                   V. Ngai
Expires October 2005                                  Enterasys Networks =
|
draft-ietf-bridge-rstpmib-06.txt                                 E. Bell =
|
                                                              3Com Corp.
                                                              April 2005 =
|

               Definitions of Managed Objects for Bridges
                   with Rapid Spanning Tree Protocol

Status of this Memo

   By submitting this Internet-Draft, I certify that any applicable
   patent or other IPR claims of which I am aware have been disclosed,
   or will be disclosed, and any of which I become aware will be
   disclosed, in accordance with RFC 3668.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on January 21, 2005.

Copyright Notice

   Copyright (C) The Internet Society (2004).  All Rights Reserved.

Abstract

   This memo defines an SMIv2 MIB module for managing the Rapid Spanning =
|
   Tree capability defined by the IEEE P802.1t and P802.1w amendments to =
|
   IEEE Std 802.1D-1998 for bridging between Local Area Network (LAN)    =
|
   segments.  The objects in this MIB are defined to apply both to       =
|
   transparent bridging and to bridges connected by subnetworks other    =
|
   than LAN segments.                                                    =
|





Ngai et. al               Expires October 2005                  [Page 1]
=0C
Internet Draft                  RSTP MIB                      April 2005


Table of Contents


   1 The Internet-Standard Management Framework ...................    3
   2 Overview .....................................................    3
   3 Relationship to IEEE 802.1t and 802.1w amendments ............    3
   4 Relation to the BRIDGE-MIB ...................................    4
   5 Definitions for RSTP-MIB .....................................    5
   6 Acknowledgments ..............................................   11
   7 IANA Considerations ..........................................   11
   8 Security Considerations ......................................   11
   9 Normative References .........................................   13
   10 Informative References ......................................   14
   11 Authors' Addresses ..........................................   15
    Intellectual Property Statement ...............................   16
    Disclaimer of Validity ........................................   16
    Copyright Statement ...........................................   16


































Ngai et. al               Expires October 2005                  [Page 2]
=0C
Internet Draft                  RSTP MIB                      April 2005


1.  The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [RFC3410].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  MIB objects are generally
   accessed through the Simple Network Management Protocol (SNMP).
   Objects in the MIB are defined using the mechanisms defined in the
   Structure of Management Information (SMI).  This memo specifies a MIB
   module that is compliant to the SMIv2, which is described in STD 58,
   RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
   [RFC2580].


2.  Overview

   This memo defines an SMIv2 MIB module for managing the Rapid Spanning =
|
   Tree (RSTP) capability defined by the IEEE P802.1t [802.1t] and       =
|
   P802.1w [802.1w] amendments to IEEE Std 802.1D-1998 [802.1D-1998] for =
|
   bridging between Local Area Network (LAN) segments.  The objects in   =
|
   this MIB are defined to apply both to transparent bridging and to     =
|
   bridges connected by subnetworks other than LAN segments.             =
|


3.  Relationship to IEEE 802.1t and 802.1w amendments

   This document defines managed object for the Rapid Spanning Tree      =
|
   Protocol defined by the IEEE P802.1t and IEEE P802.1w amendments to   =
|
   802.1d-1998.                                                          =
|

   RSTP-MIB Name                       IEEE 802.1 Reference              =
|

   dot1dStp
     dot1dStpVersion                   (w) 17.16.1  ForceVersion
     dot1dStpTxHoldCount               (w) 17.16.6  TxHoldCount
     dot1dStpExtPortTable                                                =
-
       dot1dStpPortProtocolMigration   (w) 17.18.10 mcheck
       dot1dStpPortAdminEdgePort       (t) 18.3.3   adminEdgePort
       dot1dStpPortOperEdgePort        (t) 18.3.4   operEdgePort
       dot1dStpPortAdminPointToPoint   (w) 6.4.3    adminPointToPointMAC
       dot1dStpPortOperPointToPoint    (w) 6.4.3    operPointToPointMAC
       dot1dStpPortAdminPathCost       (D) 8.5.5.3  Path Cost

   Following are the references for the above objects in 802.1D-2004.    =
|





Ngai et. al               Expires October 2005                  [Page 3]
=0C
Internet Draft                  RSTP MIB                      April 2005


   RSTP-MIB Name                       IEEE 802.1D-2004 Reference        =
|

   dot1dStp                                                              =
|
     dot1dStpVersion                   17.13.4  ForceVersion             =
|
     dot1dStpTxHoldCount               17.13.12 TxHoldCount              =
|
     dot1dStpExtPortTable                                                =
|
       dot1dStpPortProtocolMigration   17.19.13 mcheck                   =
|
       dot1dStpPortAdminEdgePort       17.13.1  adminEdgePort            =
|
       dot1dStpPortOperEdgePort        17.19.17 operEdgePort             =
|
       dot1dStpPortAdminPointToPoint   6.4.3    adminPointToPointMAC     =
|
       dot1dStpPortOperPointToPoint    6.4.3    operPointToPointMAC      =
|
       dot1dStpPortAdminPathCost       17.13.11 Path Cost                =
|



4.  Relation to the BRIDGE-MIB                                           =
-

   The Original BRIDGE-MIB [RFC1493] has been updated in an              =
|
   SMIv2-compliant version [RFC1493bis]. Conformance statements have     =
|
   been added and some description and reference clauses have been       =
|
   updated. The interpretations of some objects were changed to          =
|
   accommodate IEEE 802.1t and 802.1w amendments.                        =
|

   The object dot1dStpPortPathCost32 was added to support IEEE 802.1t,   =
|
   and the permissible values of dot1dStpPriority and                    =
|
   dot1dStpPortPriority have been clarified for bridges supporting IEEE  =
|
   802.1t or IEEE 802.1w. The interpretation of                          =
|
   dot1dStpTimeSinceTopologyChange has been clarified for bridges        =
|
   supporting the RSTP.                                                  =
|

   See the updated BRIDGE-MIB [RFC1493bis] for details.                  =
|

   The objects in the RSTP-MIB supplement those defined in the Bridge    =
|
   MIB [RFC1493bis].                                                     =
|

















Ngai et. al               Expires October 2005                  [Page 4]
=0C
Internet Draft                  RSTP MIB                      April 2005


5.  Definitions for RSTP-MIB

RSTP-MIB DEFINITIONS ::=3D BEGIN

-- -------------------------------------------------------------
-- MIB for IEEE 802.1w Rapid Spanning Tree Protocol
-- -------------------------------------------------------------

IMPORTS
    MODULE-IDENTITY, OBJECT-TYPE, Integer32
        FROM SNMPv2-SMI
    TruthValue
        FROM SNMPv2-TC
    MODULE-COMPLIANCE, OBJECT-GROUP
        FROM SNMPv2-CONF
    dot1dBridge, dot1dStp, dot1dStpPortEntry
        FROM BRIDGE-MIB;

rstpMIB MODULE-IDENTITY
    LAST-UPDATED "200503190000Z"                                         =
|
    ORGANIZATION "IETF Bridge MIB Working Group"
    CONTACT-INFO
        "Email: Bridge-mib@ietf.org"
    DESCRIPTION
        "The Bridge MIB Extension module for managing devices
         that support the Rapid Spanning Tree Protocol defined
         by IEEE 802.1w."
    REVISION     "200503190000Z"                                         =
|
-- RFC Ed.: replace XXXX with RFC number and remove this note            =
|
    DESCRIPTION
         "Initial revision, published as part of RFC XXXX"               =
|
-- RFC Ed.: replace xxxx with IANA-assigned number and                   =
|
--          remove this note                                             =
|
    ::=3D { mib-2 xxxx }                                                 =
  |

-- ---------------------------------------------------------- --         =
|
-- subtrees in the RSTP-MIB                                              =
|
-- ---------------------------------------------------------- --         =
|

rstpNotifications OBJECT IDENTIFIER ::=3D { rstpMIB 0 }                  =
  |
rstpObjects       OBJECT IDENTIFIER ::=3D { rstpMIB 1 }                  =
  |
rstpConformance   OBJECT IDENTIFIER ::=3D { rstpMIB 2 }                  =
  |

-- -------------------------------------------------------------
-- Addition to the dot1dStp group
-- -------------------------------------------------------------





Ngai et. al               Expires October 2005                  [Page 5]
=0C
Internet Draft                  RSTP MIB                      April 2005


dot1dStpVersion OBJECT-TYPE
    SYNTAX      INTEGER {
                    stpCompatible(0),
                    rstp(2)
                }
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "The version of Spanning Tree Protocol the bridge is
         currently running.  The value 'stpCompatible(0)'
         indicates the Spanning Tree Protocol specified in
         IEEE 802.1D-1998 and 'rstp(2)' indicates the Rapid              =
|
         Spanning Tree Protocol specified in IEEE 802.1w and             =
|
         clause 17 of 802.1D-2004.  New values may be defined            =
|
         as future versions of the protocol become available."           =
|
    REFERENCE
        "IEEE 802.1w clause 14.8.1, 17.12, 17.16.1"
    DEFVAL      { rstp }
    ::=3D { dot1dStp 16 }

dot1dStpTxHoldCount OBJECT-TYPE
    SYNTAX      Integer32 (1..10)
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "The value used by the Port Transmit state machine to limit
         the maximum transmission rate."
    REFERENCE
        "IEEE 802.1w clause 17.16.6"
    DEFVAL      { 3 }
    ::=3D { dot1dStp 17 }

--                                                                       =
|
-- { dot1dStp 18 } was used to represent dot1dStpPathCostDefault         =
|
-- in an internet-draft version of this MIB.  It has since been          =
|
-- obsoleted, and should not be used.                                    =
|
--                                                                       =
|

dot1dStpExtPortTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF Dot1dStpExtPortEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A table that contains port-specific Rapid Spanning Tree
         information."
    ::=3D { dot1dStp 19 }





Ngai et. al               Expires October 2005                  [Page 6]
=0C
Internet Draft                  RSTP MIB                      April 2005


dot1dStpExtPortEntry OBJECT-TYPE
    SYNTAX      Dot1dStpExtPortEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A list of Rapid Spanning Tree information maintained by
         each port."
    AUGMENTS    { dot1dStpPortEntry }
    ::=3D { dot1dStpExtPortTable 1 }

Dot1dStpExtPortEntry ::=3D
    SEQUENCE {
        dot1dStpPortProtocolMigration
            TruthValue,
        dot1dStpPortAdminEdgePort
            TruthValue,
        dot1dStpPortOperEdgePort
            TruthValue,
        dot1dStpPortAdminPointToPoint
            INTEGER,
        dot1dStpPortOperPointToPoint
            TruthValue,
        dot1dStpPortAdminPathCost
            Integer32
    }

dot1dStpPortProtocolMigration OBJECT-TYPE
    SYNTAX      TruthValue
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "When operating in RSTP (version 2) mode, writing TRUE(1)
         to this object forces this port to transmit RSTP BPDUs.
         Any other operation on this object has no effect and
         it always returns FALSE(2) when read."
    REFERENCE
        "IEEE 802.1w clause 14.8.2.4, 17.18.10, 17.26"
    ::=3D { dot1dStpExtPortEntry 1 }

dot1dStpPortAdminEdgePort OBJECT-TYPE
    SYNTAX      TruthValue
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "The administrative value of the Edge Port parameter. A
         value of TRUE(1) indicates that this port should be





Ngai et. al               Expires October 2005                  [Page 7]
=0C
Internet Draft                  RSTP MIB                      April 2005


         assumed as an edge-port and a value of FALSE(2) indicates
         that this port should be assumed as a non-edge-port.
         Setting this object will also cause the corresponding
         instance of dot1dStpPortOperEdgePort to change to the
         same value. Note that even when this object's value
         is true, the value of the corresponding instance of
         dot1dStpPortOperEdgePort can be false if a BPDU has
         been received."
    REFERENCE
        "IEEE 802.1t clause 14.8.2, 18.3.3"
    ::=3D { dot1dStpExtPortEntry 2 }

dot1dStpPortOperEdgePort OBJECT-TYPE
    SYNTAX      TruthValue
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The operational value of the Edge Port parameter. The
         object is initialized to the value of the corresponding
         instance of dot1dStpPortAdminEdgePort. When the
         corresponding instance of dot1dStpPortAdminEdgePort is
         set, this object will be changed as well. This object
         will also be changed to FALSE on reception of a BPDU."
    REFERENCE
        "IEEE 802.1t clause 14.8.2, 18.3.4"
    ::=3D { dot1dStpExtPortEntry 3 }

dot1dStpPortAdminPointToPoint OBJECT-TYPE
    SYNTAX      INTEGER {
                    forceTrue(0),
                    forceFalse(1),
                    auto(2)
                }
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "The administrative point-to-point status of the LAN segment
         attached to this port.  A value of forceTrue(0) indicates that
         this port should always be treated as if it is connected to
         a point-to-point link.  A value of forceFalse(1) indicates
         that this port should be treated as having a shared media
         connection.  A value of auto(2) indicates that this port is
         considered to have a point-to-point link if it is an Aggregator
         and all of its members are aggregatable, or if the MAC entity
         is configured for full duplex operation, either through
         auto-negotiation or by management means."





Ngai et. al               Expires October 2005                  [Page 8]
=0C
Internet Draft                  RSTP MIB                      April 2005


   REFERENCE
       "IEEE 802.1w clause 6.4.3, 6.5, 14.8.2"
   ::=3D { dot1dStpExtPortEntry 4 }

dot1dStpPortOperPointToPoint OBJECT-TYPE
    SYNTAX      TruthValue
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The operational point-to-point status of the LAN segment
         attached to this port.  It indicates whether a port is
         considered to have a point-to-point connection or not.
         The value is determined by management or by auto-detection,
         as described in the dot1dStpPortAdminPointToPoint object."
    REFERENCE
        "IEEE 802.1w clause 6.4.3, 6.5, 14.8.2"
    ::=3D { dot1dStpExtPortEntry 5 }

dot1dStpPortAdminPathCost OBJECT-TYPE
    SYNTAX      Integer32 (0..200000000)
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "The administratively assigned value for the contribution
         of this port to the path cost of paths towards the spanning
         tree root.

         Writing a value of '0' assigns the automatically calculated
         default Path Cost value to the port.  If the default Path
         Cost is being used, this object returns '0' when read.

         This complements the object dot1dStpPortPathCost or
         dot1dStpPortPathCost32, which returns the operational value
         of the path cost."
    REFERENCE
        "IEEE 802.1D-1998: Section 8.5.5.3"
    ::=3D { dot1dStpExtPortEntry 6 }

-- -------------------------------------------------------------
-- rstpMIB - Conformance Information
-- -------------------------------------------------------------

rstpGroups OBJECT IDENTIFIER ::=3D { rstpConformance 1 }                 =
  -

rstpCompliances OBJECT IDENTIFIER ::=3D { rstpConformance 2 }






Ngai et. al               Expires October 2005                  [Page 9]
=0C
Internet Draft                  RSTP MIB                      April 2005


-- -------------------------------------------------------------
-- Units of conformance
-- -------------------------------------------------------------

rstpBridgeGroup OBJECT-GROUP
    OBJECTS {
        dot1dStpVersion,
        dot1dStpTxHoldCount
    }
    STATUS      current
    DESCRIPTION
        "Rapid Spanning Tree information for the bridge."
    ::=3D { rstpGroups 1 }

rstpPortGroup OBJECT-GROUP                                               =
-
    OBJECTS {
        dot1dStpPortProtocolMigration,
        dot1dStpPortAdminEdgePort,
        dot1dStpPortOperEdgePort,
        dot1dStpPortAdminPointToPoint,
        dot1dStpPortOperPointToPoint,
        dot1dStpPortAdminPathCost
    }
    STATUS      current
    DESCRIPTION
        "Rapid Spanning Tree information for individual ports."
    ::=3D { rstpGroups 2 }                                               =
  |

-- -------------------------------------------------------------
-- Compliance statements
-- -------------------------------------------------------------

rstpCompliance MODULE-COMPLIANCE
    STATUS      current
    DESCRIPTION
        "The compliance statement for device support of Rapid            =
|
         Spanning Tree Protocol (RSTP) bridging services."               =
|
    MODULE
        MANDATORY-GROUPS {
            rstpBridgeGroup,
            rstpPortGroup
        }
    ::=3D { rstpCompliances 1 }                                          =
  -

END






Ngai et. al               Expires October 2005                 [Page 10]
=0C
Internet Draft                  RSTP MIB                      April 2005


6.  Acknowledgments                                                      =
+

   This document was produced on behalf of the Bridge MIB Working Group
   in the Operations and Management area of the Internet Engineering
   Task Force.

   The authors wish to thank the members of the Bridge MIB Working
   Group, especially Alex Ruzin, for their comments and suggestions
   which improved this effort.



7.  IANA Considerations                                                  =
+

   This document requires an OID assignment to be made by IANA:          =
+

            Descriptor        OBJECT IDENTIFIER value                    =
+
            ----------        -----------------------                    =
+
            rstpMIB           { mib-2 xxxx }                             =
+



8.  Security Considerations

   There are a number of management objects defined in this MIB that
   have a MAX-ACCESS clause of read-write and/or read-create.  Such
   objects may be considered sensitive or vulnerable in some network
   environments.  The support for SET operations in a non-secure
   environment without proper protection can have a negative effect on
   network operations.

   Writable objects that could be misused to cause network delays and    =
+
   spanning tree instabilities include dot1dStpVersion,                  =
+
   dot1dStpTxHoldCount, dot1dStpPortProtocolMigration,                   =
+
   dot1dStpPortAdminEdgePort, and dot1dStpPortAdminPathCost.             =
+

   The object dot1dStpVersion could be read by an attacker to identify   =
+
   environments containing applications or protocols which are           =
+
   potentially sensitive to RSTP mode.                                   =
+

   The object dot1dStpPortAdminPointToPoint could be used to mislead an  =
+
   access control protocol, such as 802.1x, to believe that only one     =
+
   other system is attached to a LAN segment and to enable network       =
+
   access based on that assumption.  This situation could permit         =
+
   potential man-in-the-middle attacks.                                  =
+






Ngai et. al               Expires October 2005                 [Page 11]
=0C
Internet Draft                  RSTP MIB                      April 2005


   SNMPv1 by itself is not a secure environment.  Even if the network
   itself is secure (for example by using IPSec), even then, there is no
   control as to who on the secure network is allowed to access and
   GET/SET (read/change/create/delete) the objects in this MIB.

   It is recommended that the implementers consider the security
   features as provided by the SNMPv3 framework.  Specifically, the use
   of the User-based Security Model [USM] and the View-based Access
   Control Model [VACM] is recommended.










































Ngai et. al               Expires October 2005                 [Page 12]
=0C
Internet Draft                  RSTP MIB                      April 2005


9.  Normative References

[RFC2578]    McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
             Rose, M., and S. Waldbusser, "Structure of Management
             Information Version 2 (SMIv2)", STD 58, RFC 2578, April
             1999.

[RFC2579]    McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
             Rose, M., and S. Waldbusser, "Textual Conventions for
             SMIv2", STD 58, RFC 2579, April 1999.

[RFC2580]    McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
             Rose, M., and S. Waldbusser, "Conformance Statements for
             SMIv2", STD 58, RFC 2580, April 1999.

[RFC2674]    Bell, E., Smith, A., Langille, P., Rijhsinghani, A. and
             McCloghrie, "Definitions of Managed Objects for Bridges
             with Traffic Classes, Multicast Filtering and Virtual LAN
             Extensions", RFC 2674, August 1999.

[802.1D-1998]     "Information technology - Telecommunications and       =
|
             information                                                 =
|
             exchange between systems - Local and metropolitan area
             networks - Common specifications - Part 3: Media Access
             Control (MAC) Bridges:  Revision.  This is a revision of
             ISO/IEC 10038: 1993, 802.1j-1992 and 802.6k-1992.  It
             incorporates P802.11c, P802.1p and P802.12e."  ISO/IEC
             15802-3: 1998.

[802.1D-2004]     IEEE Project 802 Local and Metropolitan  Area          =
+
             Networks, "IEEE Standard 802.1D-2004 MAC Bridges", 2004.    =
+

[RFC1493]  Decker, E., Langille, P., Rijsinghani, A. and K.  McCloghrie,
             "Definitions of Managed Objects for Bridges", RFC 1493,
             July 1993.

[RFC1493bis]  Bell, E. and Norseth, K., "Definitions of Managed Objects  =
+
             for Bridges", draft-ietf-bridge-bridgemib-smiv2-10.txt,     =
+
             February 2005.  NOTE TO RFC EDITOR:  Replace the above ID   =
+
             reference with the appropriate RFC.                         =
+

[802.1t]     IEEE 802.1t-2001, "(Amendment to IEEE Standard 802.1D) IEEE
             Standard for Information technology - Telecommunications
             and information exchange between systems - Local and
             metropolitan area networks - Common specifications - Part
             3: Media Access Control (MAC) Bridges: Technical and





Ngai et. al               Expires October 2005                 [Page 13]
=0C
Internet Draft                  RSTP MIB                      April 2005


             Editorial Corrections".

[802.1w]     IEEE 802.1w-2001, "(Amendment to IEEE Standard 802.1D) IEEE
             Standard for Information technology--Telecommunications and
             information exchange between systems--Local and
             metropolitan area networks--Common Specifications--Part 3:
             Media Access Control (MAC) Bridges: Rapid Reconfiguation".


10.  Informative References

[RFC3410]    Case, J., Mundy, R., Partain, D. and B. Stewart,            =
|
             "Introduction and Applicability Statements for Internet     =
|
             Standard                                                    =
|
             Management Framework", RFC 3410, December 2002.




































Ngai et. al               Expires October 2005                 [Page 14]
=0C
Internet Draft                  RSTP MIB                      April 2005


11.  Authors' Addresses

   Les Bell
   3Com Europe Limited
   eCom Centre, Boundary Way
   Hemel Hempstead
   Herts.  HP2 7YU
   UK

   Phone:  +44 1442 438025
   Email:  Les_Bell@3Com.com


   Vivian Ngai
   Enterasys Networks
   2691 South Decker Lake Lane
   Salt Lake City, UT 84119
   USA

   Phone: +1 801 556 5652
   Email: vivian_ngai@acm.org






























Ngai et. al               Expires October 2005                 [Page 15]
=0C
Internet Draft                  RSTP MIB                      April 2005


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Disclaimer of Validity

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Copyright Statement

   Copyright (C) The Internet Society (2004).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.










Ngai et. al               Expires October 2005                 [Page 16]
=0C

------=_NextPart_000_0061_01C53BC1.BE88CB10
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

------=_NextPart_000_0061_01C53BC1.BE88CB10--





From bridge-mib-bounces@ietf.org  Fri Apr  8 10:57:58 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28918;
	Fri, 8 Apr 2005 10:53:29 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJus0-0003Hr-QP; Fri, 08 Apr 2005 10:54:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJuOV-0001Nk-5s; Fri, 08 Apr 2005 10:23:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJuOQ-0001MD-Kq; Fri, 08 Apr 2005 10:23:30 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24913;
	Fri, 8 Apr 2005 10:23:29 -0400 (EDT)
Message-Id: <200504081423.KAA24913@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 08 Apr 2005 10:23:28 -0400
Cc: bridge-mib@ietf.org
Subject: [Bridge-mib] I-D ACTION:draft-ietf-bridge-rstpmib-06.txt
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
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>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Bridge MIB Working Group of the IETF.

	Title		: Definitions of Managed Objects for Bridges with Rapid 
			  Spanning Tree Protocol
	Author(s)	: E. Bell, V. Ngai
	Filename	: draft-ietf-bridge-rstpmib-06.txt
	Pages		: 16
	Date		: 2005-4-7
	
This memo defines an SMIv2 MIB module for managing the Rapid Spanning
   Tree capability defined by the IEEE P802.1t and P802.1w amendments to
   IEEE Std 802.1D-1998 for bridging between Local Area Network (LAN)
   segments.  The objects in this MIB are defined to apply both to
   transparent bridging and to bridges connected by subnetworks other
   than LAN segments.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-bridge-rstpmib-06.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-bridge-rstpmib-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-bridge-rstpmib-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-4-8105727.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-bridge-rstpmib-06.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-bridge-rstpmib-06.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-4-8105727.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--NextPart--





From bridge-mib-bounces@ietf.org  Fri Apr  8 11:44:27 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04633;
	Fri, 8 Apr 2005 11:44:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJvnZ-0004JT-75; Fri, 08 Apr 2005 11:53:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJvca-0002qf-89; Fri, 08 Apr 2005 11:42:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJvcZ-0002pz-6F
	for bridge-mib@megatron.ietf.org; Fri, 08 Apr 2005 11:42:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03938
	for <bridge-mib@ietf.org>; Fri, 8 Apr 2005 11:42:08 -0400 (EDT)
Message-Id: <200504081542.LAA03938@ietf.org>
Received: from sccrmhc14.comcast.net ([204.127.202.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJvkR-0003xv-66
	for bridge-mib@ietf.org; Fri, 08 Apr 2005 11:50:20 -0400
Received: from djyxpy41 (c-24-128-104-220.hsd1.nh.comcast.net[24.128.104.220])
	by comcast.net (sccrmhc14) with SMTP
	id <20050408154104014000ke9pe>; Fri, 8 Apr 2005 15:41:04 +0000
From: "David B Harrington" <dbharrington@comcast.net>
To: "'Bridge-Mib \(E-mail\)'" <bridge-mib@ietf.org>
Date: Fri, 8 Apr 2005 11:40:59 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcU8UVy9/V06QYuvRrSbxue3BmzDAA==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: 7bit
Subject: [Bridge-mib] draft-ietf-bridge-rstpmib-06.txt
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dbharrington@comcast.net
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
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>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit


FYI. draft-ietf-bridge-rstpmib-06.txt has been submitted to the IESG
for advancement to Proposed Standard.

David Harrington
dbharrington@comcast.net
co-chair, IETF Bridge WG
 



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


From bridge-mib-bounces@ietf.org Mon Apr 25 17:52:31 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQBVH-0004zN-CM; Mon, 25 Apr 2005 17:52:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQBVG-0004ys-NJ
	for bridge-mib@megatron.ietf.org; Mon, 25 Apr 2005 17:52:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02886
	for <bridge-mib@ietf.org>; Mon, 25 Apr 2005 17:52:27 -0400 (EDT)
Received: from ihemail2.lucent.com ([192.11.222.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQBhZ-0004cx-QE
	for bridge-mib@ietf.org; Mon, 25 Apr 2005 18:05:15 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id j3PLqHV8028841
	for <bridge-mib@ietf.org>; Mon, 25 Apr 2005 16:52:18 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <26JFSC3Y>; Mon, 25 Apr 2005 23:52:16 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15506AD7765@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Bridge-Mib (E-mail)" <bridge-mib@ietf.org>
Date: Mon, 25 Apr 2005 23:52:16 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Subject: [Bridge-mib] draft-ietf-bridge-bridgemib-smiv2-10.txt (Proposed
	Standard) 
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
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>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org

The IESG has approved this document.
Offical message will probably show up in a few days from
IESG secretariat.

Thanks to all who worked on this, specifically Juergen!

Bert

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



From bridge-mib-bounces@ietf.org Sun May 01 04:57:31 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DSAGR-0005HK-OW; Sun, 01 May 2005 04:57:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DRcnc-0006yV-10; Fri, 29 Apr 2005 17:13:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15144;
	Fri, 29 Apr 2005 17:13:21 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DRd0k-0004ao-Hs; Fri, 29 Apr 2005 17:26:58 -0400
Received: from apache by newodin.ietf.org with local (Exim 4.43)
	id 1DRcna-0003Qb-Lo; Fri, 29 Apr 2005 17:13:22 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1DRcna-0003Qb-Lo@newodin.ietf.org>
Date: Fri, 29 Apr 2005 17:13:22 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
X-Mailman-Approved-At: Sun, 01 May 2005 04:57:17 -0400
Cc: bridge chair <dromasca@avaya.com>,
	Internet Architecture Board <iab@iab.org>,
	bridge mailing list <bridge-mib@ietf.org>,
	RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Bridge-mib] Protocol Action: 'Definitions of Managed Objects for
 Bridges' to Proposed Standard 
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>,
	<mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
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>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org

The IESG has approved the following document:

- 'Definitions of Managed Objects for Bridges '
   <draft-ietf-bridge-bridgemib-smiv2-10.txt> as a Proposed Standard

This document is the product of the Bridge MIB Working Group. 

The IESG contact persons are Bert Wijnen and David Kessens.

Technical Summary

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in TCP/IP based internets.
   In particular it defines objects for managing MAC bridges based on
   the IEEE 802.1D-1998 standard between Local Area Network (LAN)
   segments.  Provisions are made for support of transparent bridging.
   Provisions are also made so that these objects apply to bridges
   connected by subnetworks other than LAN segments.

   The MIB module presented in this memo is a translation of the
   BRIDGE-MIB defined in RFC 1493 to the SMIv2 syntax, updated 
   slightly to accommodate higher speed links.

   This document obsoletes RFC 1493

Working Group Summary

   The Bridge MIB Working Group discussed this document and approved
   its content in a Working Group Last Call process. All issues raiseds
   during the WG Last Call have been resolved, maintained in the RT
   system, and a summary of the resolutions was published to the mailing
   list for comment. The WG recommends that this document be forwarded
   to the IESG for consideration as a Proposed Standard.

   It is the intention of the WG that subsequent mib module work for
   IEEE 802.1 technologies will be done by the IEEE 802.1 WG. There are
   some concerns about the quality of work likely to result from SNMP
   non-experts, but the IETF is providing MIB Doctor review of their 
   MIB module work during the transition.

Protocol Quality

   The document was reviewed in detail by John Flick, and discussed by
   several other MIB experts.  A number of IEEE 802.1 WG members, 
   including the vice chair, were involved in discussions. 
   The discussions and clarifications resulted in editorial changes in
   the document. 
   The MIB module proposed by this document is the SMIv2 version of
   RFC 1493, which is implemented by many vendors in the industry.
   Backwards compatibility has been maintained, and most of the protocol
   data is identical between versions. It is expected that at least some
   of these vendors will implement the new version incarnated by this
   document, and other may choose to implement it in the future, because
   of the growing acceptance of the IEEE 802.1 protocol in the industry.
   It is our belief that the document is at the appropriate quality
   for consideration as proposed standard. 


RFC Editor Note
 
   Please include Juergen Schoenwaelder (j.schoenwaelder@iu-bremen.de)
   in the AUTH48 review. Juergen did a lot of final editing of this
   document.

   The email address for Les Bell has changed to: elbell@ntlworld.com


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



