draft-ietf-bridge-rstpmib-08.txt   draft-ietf-bridge-rstpmib-09.txt 
Internet Draft V. Ngai Internet Draft D.Levi
Expires February 2006 Enterasys Networks Expires February 2006 Nortel Networks
draft-ietf-bridge-rstpmib-08.txt E. Bell draft-ietf-bridge-rstpmib-09.txt D.Harrington
3Com Corp. Effective Software
August 2005 August 2005
Definitions of Managed Objects for Bridges Definitions of Managed Objects for Bridges
with Rapid Spanning Tree Protocol with Rapid Spanning Tree Protocol
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
skipping to change at page 2, line 16 skipping to change at page 2, line 16
1 The Internet-Standard Management Framework ................... 3 1 The Internet-Standard Management Framework ................... 3
2 Overview ..................................................... 3 2 Overview ..................................................... 3
3 Relationship to IEEE 802.1t and 802.1w amendments ............ 3 3 Relationship to IEEE 802.1t and 802.1w amendments ............ 3
4 Relation to the BRIDGE-MIB ................................... 4 4 Relation to the BRIDGE-MIB ................................... 4
5 Definitions for RSTP-MIB ..................................... 5 5 Definitions for RSTP-MIB ..................................... 5
6 Acknowledgments .............................................. 12 6 Acknowledgments .............................................. 12
7 IANA Considerations .......................................... 12 7 IANA Considerations .......................................... 12
8 Security Considerations ...................................... 12 8 Security Considerations ...................................... 12
9 Normative References ......................................... 14 9 Normative References ......................................... 14
10 Informative References ...................................... 15 10 Informative References ...................................... 14
11 Authors' Addresses .......................................... 16 11 Authors' Addresses .......................................... 16
Intellectual Property Statement ............................... 17 Intellectual Property Statement ............................... 17
Disclaimer of Validity ........................................ 17 Disclaimer of Validity ........................................ 17
Copyright Statement ........................................... 17 Copyright Statement ........................................... 17
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
skipping to change at page 3, line 33 skipping to change at page 3, line 33
Tree (RSTP) capability defined by the IEEE P802.1t [802.1t] and 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 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 bridging between Local Area Network (LAN) segments. The objects in
this MIB are defined to apply both to transparent bridging and to this MIB are defined to apply both to transparent bridging and to
bridges connected by subnetworks other than LAN segments. bridges connected by subnetworks other than LAN segments.
3. Relationship to IEEE 802.1t and 802.1w amendments 3. Relationship to IEEE 802.1t and 802.1w amendments
This document defines managed object for the Rapid Spanning Tree This document defines managed object for the Rapid Spanning Tree
Protocol defined by the IEEE P802.1t and IEEE P802.1w amendments to Protocol defined by the IEEE P802.1t and IEEE P802.1w amendments to
802.1d-1998. 802.1D-1998.
RSTP-MIB Name IEEE 802.1 Reference RSTP-MIB Name IEEE 802.1 Reference
dot1dStp dot1dStp
dot1dStpVersion (w) 17.16.1 ForceVersion dot1dStpVersion (w) 17.16.1 ForceVersion
dot1dStpTxHoldCount (w) 17.16.6 TxHoldCount dot1dStpTxHoldCount (w) 17.16.6 TxHoldCount
dot1dStpExtPortTable dot1dStpExtPortTable
dot1dStpPortProtocolMigration (w) 17.18.10 mcheck dot1dStpPortProtocolMigration (w) 17.18.10 mcheck
dot1dStpPortAdminEdgePort (t) 18.3.3 adminEdgePort dot1dStpPortAdminEdgePort (t) 18.3.3 adminEdgePort
dot1dStpPortOperEdgePort (t) 18.3.4 operEdgePort dot1dStpPortOperEdgePort (t) 18.3.4 operEdgePort
dot1dStpPortAdminPointToPoint (w) 6.4.3 adminPointToPointMAC dot1dStpPortAdminPointToPoint (w) 6.4.3 adminPointToPointMAC
dot1dStpPortOperPointToPoint (w) 6.4.3 operPointToPointMAC dot1dStpPortOperPointToPoint (w) 6.4.3 operPointToPointMAC
dot1dStpPortAdminPathCost (D) 8.5.5.3 Path Cost dot1dStpPortAdminPathCost (D) 8.5.5.3 Path Cost
Following are the references for the above objects in 802.1D-2004 There are concerns that there may be changes made in the 802.1D-2004
[802.1D-2004]. edition that would lead to non-backwards compatible SMI changes for
802.1t and 802.1w managed objects in the MIB modules. The Bridge MIB
WG decided to 'freeze' the technical content of the MIB modules at a
level that is compatible with the 802.1t and 802.1w versions, and
leave to the IEEE 802.1 WG any updates beyond this.
For informational purposes only, these are the references for the
above objects in 802.1D-2004 [802.1D-2004].
RSTP-MIB Name IEEE 802.1D-2004 Reference RSTP-MIB Name IEEE 802.1D-2004 Reference
dot1dStp dot1dStp
dot1dStpVersion 17.13.4 ForceVersion dot1dStpVersion 17.13.4 ForceVersion
dot1dStpTxHoldCount 17.13.12 TxHoldCount dot1dStpTxHoldCount 17.13.12 TxHoldCount
dot1dStpExtPortTable dot1dStpExtPortTable
dot1dStpPortProtocolMigration 17.19.13 mcheck dot1dStpPortProtocolMigration 17.19.13 mcheck
dot1dStpPortAdminEdgePort 17.13.1 adminEdgePort dot1dStpPortAdminEdgePort 17.13.1 adminEdgePort
dot1dStpPortOperEdgePort 17.19.17 operEdgePort dot1dStpPortOperEdgePort 17.19.17 operEdgePort
dot1dStpPortAdminPointToPoint 6.4.3 adminPointToPointMAC dot1dStpPortAdminPointToPoint 6.4.3 adminPointToPointMAC
dot1dStpPortOperPointToPoint 6.4.3 operPointToPointMAC dot1dStpPortOperPointToPoint 6.4.3 operPointToPointMAC
dot1dStpPortAdminPathCost 17.13.11 Path Cost dot1dStpPortAdminPathCost 17.13.11 Path Cost
4. Relation to the BRIDGE-MIB 4. Relation to the BRIDGE-MIB
The objects in the RSTP-MIB supplement those defined in the Bridge
MIB [RFC1493bis].
The Original BRIDGE-MIB [RFC1493] has been updated in an The Original BRIDGE-MIB [RFC1493] has been updated in an
SMIv2-compliant version [RFC1493bis]. Conformance statements have SMIv2-compliant version [RFC1493bis]. Conformance statements have
been added and some description and reference clauses have been been added and some description and reference clauses have been
updated. The interpretations of some objects were changed to updated. The interpretations of some objects were changed to
accommodate IEEE 802.1t and 802.1w amendments. accommodate IEEE 802.1t and 802.1w amendments.
The object dot1dStpPortPathCost32 was added to support IEEE 802.1t, The object dot1dStpPortPathCost32 was added to support IEEE 802.1t,
and the permissible values of dot1dStpPriority and and the permissible values of dot1dStpPriority and
dot1dStpPortPriority have been clarified for bridges supporting IEEE dot1dStpPortPriority have been clarified for bridges supporting IEEE
802.1t or IEEE 802.1w. The interpretation of 802.1t or IEEE 802.1w. The interpretation of
dot1dStpTimeSinceTopologyChange has been clarified for bridges dot1dStpTimeSinceTopologyChange has been clarified for bridges
supporting the RSTP. supporting the RSTP.
See the updated BRIDGE-MIB [RFC1493bis] for details. See the updated BRIDGE-MIB [RFC1493bis] for details.
The objects in the RSTP-MIB supplement those defined in the Bridge
MIB [RFC1493bis].
5. Definitions for RSTP-MIB 5. Definitions for RSTP-MIB
RSTP-MIB DEFINITIONS ::= BEGIN RSTP-MIB DEFINITIONS ::= BEGIN
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- MIB for IEEE 802.1w Rapid Spanning Tree Protocol -- MIB for IEEE 802.1w Rapid Spanning Tree Protocol
-- ------------------------------------------------------------- -- -------------------------------------------------------------
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Integer32, mib-2 MODULE-IDENTITY, OBJECT-TYPE, Integer32, mib-2
skipping to change at page 5, line 31 skipping to change at page 5, line 31
FROM BRIDGE-MIB; FROM BRIDGE-MIB;
rstpMIB MODULE-IDENTITY rstpMIB MODULE-IDENTITY
LAST-UPDATED "200507290000Z" LAST-UPDATED "200507290000Z"
ORGANIZATION "IETF Bridge MIB Working Group" ORGANIZATION "IETF Bridge MIB Working Group"
CONTACT-INFO CONTACT-INFO
"Email: Bridge-mib@ietf.org" "Email: Bridge-mib@ietf.org"
DESCRIPTION DESCRIPTION
"The Bridge MIB Extension module for managing devices "The Bridge MIB Extension module for managing devices
that support the Rapid Spanning Tree Protocol defined that support the Rapid Spanning Tree Protocol defined
by IEEE 802.1w." by IEEE 802.1w.
REVISION "200507290000Z"
Copyright (C) The Internet Society (2005). This version of
this MIB module is part of RFC XXXX; See the RFC itself for
full legal notices."
-- RFC Ed.: replace XXXX with RFC number and remove this note -- RFC Ed.: replace XXXX with RFC number and remove this note
REVISION "200507290000Z"
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2005). The initial "The initial version of this MIB module as published in
version of this MIB module was published in RFC XXXX; for full RFC XXXX."
legal notices see the RFC itself. Supplementary information -- RFC Ed.: replace XXXX with RFC number and remove this note
may be available at:
http://www.ietf.org/copyrights/ianamib.html." ::= { mib-2 xxxx }
-- RFC Ed.: replace xxxx with IANA-assigned number and -- RFC Ed.: replace xxxx with IANA-assigned number and
-- remove this note -- remove this note
::= { mib-2 xxxx }
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
-- subtrees in the RSTP-MIB -- subtrees in the RSTP-MIB
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
rstpNotifications OBJECT IDENTIFIER ::= { rstpMIB 0 } rstpNotifications OBJECT IDENTIFIER ::= { rstpMIB 0 }
rstpObjects OBJECT IDENTIFIER ::= { rstpMIB 1 } rstpObjects OBJECT IDENTIFIER ::= { rstpMIB 1 }
rstpConformance OBJECT IDENTIFIER ::= { rstpMIB 2 } rstpConformance OBJECT IDENTIFIER ::= { rstpMIB 2 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Addition to the dot1dStp group -- Addition to the dot1dStp group
-- ------------------------------------------------------------- -- -------------------------------------------------------------
skipping to change at page 12, line 15 skipping to change at page 12, line 15
6. Acknowledgments 6. Acknowledgments
This document was produced on behalf of the Bridge MIB Working Group This document was produced on behalf of the Bridge MIB Working Group
in the Operations and Management area of the Internet Engineering in the Operations and Management area of the Internet Engineering
Task Force. Task Force.
The authors wish to thank the members of the Bridge MIB Working The authors wish to thank the members of the Bridge MIB Working
Group, especially Alex Ruzin, for their comments and suggestions Group, especially Alex Ruzin, for their comments and suggestions
which improved this effort. which improved this effort.
Vivian Ngai and Les Bell were the initial authors of this document,
and did the bulk of the development work for this document.
7. IANA Considerations 7. IANA Considerations
This document requires an OID assignment to be made by IANA: This document requires an OID assignment to be made by IANA:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
rstpMIB { mib-2 xxxx } rstpMIB { mib-2 xxxx }
8. Security Considerations 8. Security Considerations
skipping to change at page 14, line 28 skipping to change at page 14, line 28
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[802.1D-1998] "Information technology - Telecommunications and [802.1D-1998] "Information technology - Telecommunications and
information exchange between systems - Local and information exchange between systems - Local and
metropolitan area networks - Common specifications - Part metropolitan area networks - Common specifications - Part
3: Media Access Control (MAC) Bridges: Revision. This is 3: Media Access Control (MAC) Bridges: Revision. This is
a revision of ISO/IEC 10038: 1993, 802.1j-1992 and a revision of ISO/IEC 10038: 1993, 802.1j-1992 and
802.6k-1992. It incorporates P802.11c, P802.1p and 802.6k-1992. It incorporates P802.11c, P802.1p and
P802.12e." ISO/IEC 15802-3: 1998. 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 [RFC1493bis] Bell, E. and Norseth, K., "Definitions of Managed Objects
for Bridges", draft-ietf-bridge-bridgemib-smiv2-10.txt, for Bridges", draft-ietf-bridge-bridgemib-smiv2-10.txt,
February 2005. NOTE TO RFC EDITOR: Replace the above ID February 2005. NOTE TO RFC EDITOR: Replace the above ID
reference with the appropriate RFC. reference with the appropriate RFC.
[802.1t] IEEE 802.1t-2001, "(Amendment to IEEE Standard 802.1D) IEEE [802.1t] IEEE 802.1t-2001, "(Amendment to IEEE Standard 802.1D) IEEE
Standard for Information technology - Telecommunications Standard for Information technology - Telecommunications
and information exchange between systems - Local and and information exchange between systems - Local and
metropolitan area networks - Common specifications - Part metropolitan area networks - Common specifications - Part
3: Media Access Control (MAC) Bridges: Technical and 3: Media Access Control (MAC) Bridges: Technical and
skipping to change at page 15, line 4 skipping to change at page 14, line 44
Standard for Information technology - Telecommunications Standard for Information technology - Telecommunications
and information exchange between systems - Local and and information exchange between systems - Local and
metropolitan area networks - Common specifications - Part metropolitan area networks - Common specifications - Part
3: Media Access Control (MAC) Bridges: Technical and 3: Media Access Control (MAC) Bridges: Technical and
Editorial Corrections". Editorial Corrections".
[802.1w] IEEE 802.1w-2001, "(Amendment to IEEE Standard 802.1D) IEEE [802.1w] IEEE 802.1w-2001, "(Amendment to IEEE Standard 802.1D) IEEE
Standard for Information technology--Telecommunications and Standard for Information technology--Telecommunications and
information exchange between systems--Local and information exchange between systems--Local and
metropolitan area networks--Common Specifications--Part 3: metropolitan area networks--Common Specifications--Part 3:
Media Access Control (MAC) Bridges: Rapid Reconfiguation". Media Access Control (MAC) Bridges: Rapid Reconfiguation".
10. Informative References 10. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet "Introduction and Applicability Statements for Internet
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[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.
11. Authors' Addresses 11. Authors' Addresses
David Levi
Nortel Networks
4655 Great America Parkway
Santa Clara, CA 95054
USA
Phone: +1 865 686 0432
Email: dlevi@nortel.com
David Harrington
Effective Software
50 Harding Rd.
Portsmouth, NH 03801
USA
Phone: +1 603 436 8634
Email: ietfdbh@comcast.net
Les Bell Les Bell
3Com Europe Limited
eCom Centre, Boundary Way
Hemel Hempstead Hemel Hempstead
Herts. HP2 7YU Herts. HP2 7YU
UK UK
Phone: +44 1442 438025 EMail: elbell@ntlworld.com
Email: Les_Bell@3Com.com
Vivian Ngai Vivian Ngai
Enterasys Networks Salt lake City, UT
2691 South Decker Lake Lane
Salt Lake City, UT 84119
USA USA
Phone: +1 801 556 5652
Email: vivian_ngai@acm.org Email: vivian_ngai@acm.org
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights 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 might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/