draft-ietf-bridge-bridgemib-smiv2-08.txt   draft-ietf-bridge-bridgemib-smiv2-09.txt 
Network Working Group K. Norseth, Ed. Network Working Group K. Norseth, Ed.
Internet-Draft L-3 Communications Internet-Draft L-3 Communications
Obsoletes: 1493 (if approved) E. Bell, Ed. Obsoletes: 1493 (if approved) E. Bell, Ed.
Expires: June 29, 2005 3Com Europe Limited Expires: July 13, 2005 3Com Europe Limited
December 29, 2004 January 12, 2005
Definitions of Managed Objects for Bridges Definitions of Managed Objects for Bridges
draft-ietf-bridge-bridgemib-smiv2-08.txt draft-ietf-bridge-bridgemib-smiv2-09.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions This document is an Internet-Draft and is subject to all provisions
of section 3 of RFC 3667. By submitting this Internet-Draft, each of section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of author represents that any 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 is aware have been or will be disclosed, and any of
which he or she become aware will be disclosed, in accordance with which he or she become aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on June 29, 2005. This Internet-Draft will expire on July 13, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). Copyright (C) The Internet Society (2005).
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP based internets. for use with network management protocols in TCP/IP based internets.
In particular it defines objects for managing MAC bridges based on In particular it defines objects for managing MAC bridges based on
the IEEE 802.1D-1998 standard between Local Area Network (LAN) the IEEE 802.1D-1998 standard between Local Area Network (LAN)
segments. Provisions are made for support of transparent bridging. segments. Provisions are made for support of transparent bridging.
Provisions are also made so that these objects apply to bridges Provisions are also made so that these objects apply to bridges
connected by subnetworks other than LAN segments. connected by subnetworks other than LAN segments.
skipping to change at page 2, line 26 skipping to change at page 2, line 26
3.1 Structure of the MIB Module . . . . . . . . . . . . . . . 4 3.1 Structure of the MIB Module . . . . . . . . . . . . . . . 4
3.1.1 The dot1dBase Subtree . . . . . . . . . . . . . . . . 6 3.1.1 The dot1dBase Subtree . . . . . . . . . . . . . . . . 6
3.1.2 The dot1dStp Subtree . . . . . . . . . . . . . . . . . 6 3.1.2 The dot1dStp Subtree . . . . . . . . . . . . . . . . . 6
3.1.3 The dot1dSr Subtree . . . . . . . . . . . . . . . . . 6 3.1.3 The dot1dSr Subtree . . . . . . . . . . . . . . . . . 6
3.1.4 The dot1dTp Subtree . . . . . . . . . . . . . . . . . 7 3.1.4 The dot1dTp Subtree . . . . . . . . . . . . . . . . . 7
3.1.5 The dot1dStatic Subtree . . . . . . . . . . . . . . . 7 3.1.5 The dot1dStatic Subtree . . . . . . . . . . . . . . . 7
3.2 Relationship to Other MIB Modules . . . . . . . . . . . . 7 3.2 Relationship to Other MIB Modules . . . . . . . . . . . . 7
3.2.1 Relationship to the SNMPv2-MIB . . . . . . . . . . . . 7 3.2.1 Relationship to the SNMPv2-MIB . . . . . . . . . . . . 7
3.2.2 Relationship to the IF-MIB . . . . . . . . . . . . . . 7 3.2.2 Relationship to the IF-MIB . . . . . . . . . . . . . . 7
4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 39 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 39
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 40 6. Security Considerations . . . . . . . . . . . . . . . . . . . 39
7. Contact Information . . . . . . . . . . . . . . . . . . . . . 41 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 40
8. Changes from RFC 1493 . . . . . . . . . . . . . . . . . . . . 41 8. Contact Information . . . . . . . . . . . . . . . . . . . . . 41
9. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . 42 9. Changes from RFC 1493 . . . . . . . . . . . . . . . . . . . . 42
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 42 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 42
10.1 Normative References . . . . . . . . . . . . . . . . . . . . 42 10.1 Normative References . . . . . . . . . . . . . . . . . . . . 42
10.2 Informative References . . . . . . . . . . . . . . . . . . . 43 10.2 Informative References . . . . . . . . . . . . . . . . . . . 43
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 43 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 43
Intellectual Property and Copyright Statements . . . . . . . . 45 Intellectual Property and Copyright Statements . . . . . . . . 44
1. Conventions 1. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL", when they appear in this document, are to be interpreted "OPTIONAL", when they appear in this document, are to be interpreted
as described in BCP 14, RFC 2119 [RFC2119]. as described in BCP 14, RFC 2119 [RFC2119].
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
skipping to change at page 7, line 5 skipping to change at page 7, line 5
respect to the Spanning Tree Protocol. If a node does not respect to the Spanning Tree Protocol. If a node does not
implemented the Spanning Tree Protocol, this subtree will not be implemented the Spanning Tree Protocol, this subtree will not be
implemented. implemented.
3.1.3 The dot1dSr Subtree 3.1.3 The dot1dSr Subtree
This subtree contains the objects that describe the entity's state This subtree contains the objects that describe the entity's state
with respect to source route bridging. If source routing is not with respect to source route bridging. If source routing is not
supported this subtree will not be implemented. This subtree is supported this subtree will not be implemented. This subtree is
applicable to source route only, and SRT bridges. This subtree applicable to source route only, and SRT bridges. This subtree
described in RFC 1513 [RFC1513] is applicable only to source route described in RFC 1525 [RFC1525] is applicable only to source route
bridging. bridging.
3.1.4 The dot1dTp Subtree 3.1.4 The dot1dTp Subtree
This subtree contains objects that describe the entity's state with This subtree contains objects that describe the entity's state with
respect to transparent bridging. If transparent bridging is not respect to transparent bridging. If transparent bridging is not
supported this subtree will not be implemented. This subtree is supported this subtree will not be implemented. This subtree is
applicable to transparent only and SRT bridges. applicable to transparent only and SRT bridges.
3.1.5 The dot1dStatic Subtree 3.1.5 The dot1dStatic Subtree
skipping to change at page 9, line 4 skipping to change at page 9, line 4
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Counter32, Integer32, TimeTicks, mib-2 Counter32, Integer32, TimeTicks, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, MacAddress TEXTUAL-CONVENTION, MacAddress
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
InterfaceIndex FROM IF-MIB InterfaceIndex FROM IF-MIB
; ;
bridgeMIB MODULE-IDENTITY dot1dBridge MODULE-IDENTITY
LAST-UPDATED "200412290000Z" LAST-UPDATED "200501120000Z"
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
K.C. Norseth (Editor) K.C. Norseth (Editor)
L-3 Communications L-3 Communications
Tel: +1 801-594-2809 Tel: +1 801-594-2809
Email: kenyon.c.norseth@L-3com.com Email: kenyon.c.norseth@L-3com.com
Postal: 640 N. 2200 West. Postal: 640 N. 2200 West.
Salt Lake City, Utah 84116-0850 Salt Lake City, Utah 84116-0850
skipping to change at page 9, line 34 skipping to change at page 9, line 34
UK UK
Send comments to <bridge-mib@ietf.org>" Send comments to <bridge-mib@ietf.org>"
DESCRIPTION DESCRIPTION
"The Bridge MIB module for managing devices that support "The Bridge MIB module for managing devices that support
IEEE 802.1D. IEEE 802.1D.
Copyright (C) The Internet Society (2004). This version of Copyright (C) The Internet Society (2004). This version of
this MIB module is part of RFC XXXX; see the RFC itself for this MIB module is part of RFC XXXX; see the RFC itself for
full legal notices." full legal notices."
REVISION "200412290000Z" REVISION "200501120000Z"
-- RFC Ed.: replace XXXX with actual RFC number and remove this note -- RFC Ed.: replace XXXX with RFC number and remove this note
DESCRIPTION DESCRIPTION
"Third revision, published as part of RFC XXXX. "Third revision, published as part of RFC XXXX.
The MIB module has been converted to SMIv2 format. The MIB module has been converted to SMIv2 format.
Conformance statements have been added and some Conformance statements have been added and some
description and reference clauses have been updated. description and reference clauses have been updated.
The object dot1dStpPortPathCost32 was added to The object dot1dStpPortPathCost32 was added to
support IEEE 802.1t and the permissible values of support IEEE 802.1t and the permissible values of
dot1dStpPriority and dot1dStpPortPriority have been dot1dStpPriority and dot1dStpPortPriority have been
skipping to change at page 10, line 10 skipping to change at page 10, line 10
The interpretation of dot1dStpTimeSinceTopologyChange The interpretation of dot1dStpTimeSinceTopologyChange
has been clarified for bridges supporting the rapid has been clarified for bridges supporting the rapid
spanning tree protocol (RSTP)." spanning tree protocol (RSTP)."
REVISION "199307310000Z" REVISION "199307310000Z"
DESCRIPTION DESCRIPTION
"Second revision, published as part of RFC 1493." "Second revision, published as part of RFC 1493."
REVISION "199112310000Z" REVISION "199112310000Z"
DESCRIPTION DESCRIPTION
"Initial revision, published as part of RFC 1286." "Initial revision, published as part of RFC 1286."
::= { mib-2 dot1dBridge(17) 8 } ::= { mib-2 17 }
dot1dNotification OBJECT IDENTIFIER ::= { dot1dBridge 0 }
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
-- Textual Conventions -- Textual Conventions
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
BridgeId ::= TEXTUAL-CONVENTION BridgeId ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Bridge-Identifier as used in the Spanning Tree "The Bridge-Identifier as used in the Spanning Tree
Protocol to uniquely identify a bridge. Its first two Protocol to uniquely identify a bridge. Its first two
skipping to change at page 11, line 29 skipping to change at page 11, line 26
n is the value in 1/100 second units n is the value in 1/100 second units
b is the value in 1/256 second units b is the value in 1/256 second units
Note: it is important that the arithmetic operations are Note: it is important that the arithmetic operations are
done in the order specified (i.e., multiply first, done in the order specified (i.e., multiply first,
divide second)." divide second)."
SYNTAX Integer32 SYNTAX Integer32
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
dot1dBridge OBJECT IDENTIFIER ::= { mib-2 17 }
-- ---------------------------------------------------------- --
-- subtrees in the Bridge MIB -- subtrees in the Bridge MIB
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
dot1dNotifications OBJECT IDENTIFIER ::= { dot1dBridge 0 }
dot1dBase OBJECT IDENTIFIER ::= { dot1dBridge 1 } dot1dBase OBJECT IDENTIFIER ::= { dot1dBridge 1 }
dot1dStp OBJECT IDENTIFIER ::= { dot1dBridge 2 } dot1dStp OBJECT IDENTIFIER ::= { dot1dBridge 2 }
dot1dSr OBJECT IDENTIFIER ::= { dot1dBridge 3 } dot1dSr OBJECT IDENTIFIER ::= { dot1dBridge 3 }
-- documented in RFC 1513 -- documented in RFC 1525
dot1dTp OBJECT IDENTIFIER ::= { dot1dBridge 4 } dot1dTp OBJECT IDENTIFIER ::= { dot1dBridge 4 }
dot1dStatic OBJECT IDENTIFIER ::= { dot1dBridge 5 } dot1dStatic OBJECT IDENTIFIER ::= { dot1dBridge 5 }
-- Subtrees defined in the Bridge MIB Extensions: -- Subtrees used by Bridge MIB Extensions:
-- pBridgeMIB MODULE-IDENTITY ::= { dot1dBridge 6 } -- pBridgeMIB MODULE-IDENTITY ::= { dot1dBridge 6 }
-- qBridgeMIB MODULE-IDENTITY ::= { dot1dBridge 7 } -- qBridgeMIB MODULE-IDENTITY ::= { dot1dBridge 7 }
-- Note that the practice of registering related MIB modules
-- below dot1dBridge has been discouraged since there is no
-- robust mechanism to track such registrations.
-- The MODULE-IDENTITY for this MIB has been defined above as: dot1dConformance OBJECT IDENTIFIER ::= { dot1dBridge 8 }
-- bridgeMIB MODULE-IDENTITY ::= { dot1dBridge 8 }
-- The MODULE-IDENTITY for the Source Routing MIB has been
-- defined in that MIB as:
-- srMIB MODULE-IDENTITY ::= { dot1dBridge 9 }
-- Subtrees defined in the Source Routing MIB:
-- dot1dPortPair OBJECT IDENTIFIER ::= { dot1dBridge 10 }
-- Subtrees defined in the Rapid Spanning Tree MIB:
-- rstpMIB MODULE-IDENTITY ::= { dot1dBridge 11 }
dot1dConformance OBJECT IDENTIFIER ::= { bridgeMIB 1 }
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
-- the dot1dBase subtree -- the dot1dBase subtree
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
-- Implementation of the dot1dBase subtree is mandatory for all -- Implementation of the dot1dBase subtree is mandatory for all
-- bridges. -- bridges.
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
dot1dBaseBridgeAddress OBJECT-TYPE dot1dBaseBridgeAddress OBJECT-TYPE
skipping to change at page 24, line 15 skipping to change at page 23, line 50
SYNTAX Integer32 (1..200000000) SYNTAX Integer32 (1..200000000)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The contribution of this port to the path cost of "The contribution of this port to the path cost of
paths towards the spanning tree root which include paths towards the spanning tree root which include
this port. 802.1D-1998 recommends that the default this port. 802.1D-1998 recommends that the default
value of this parameter be in inverse proportion to value of this parameter be in inverse proportion to
the speed of the attached LAN. the speed of the attached LAN.
Replacement for deprecated object dot1dStpPortPathCost." This object replaces dot1dStpPortPathCost to support
IEEE 802.1t."
REFERENCE REFERENCE
"IEEE 802.1t clause 8.10.2, Table 8-5." "IEEE 802.1t clause 8.10.2, Table 8-5."
::= { dot1dStpPortEntry 11 } ::= { dot1dStpPortEntry 11 }
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
-- the dot1dTp subtree -- the dot1dTp subtree
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
-- Implementation of the dot1dTp subtree is optional. It is -- Implementation of the dot1dTp subtree is optional. It is
-- implemented by those bridges that support the transparent -- implemented by those bridges that support the transparent
-- bridging mode. A transparent or SRT bridge will implement -- bridging mode. A transparent or SRT bridge will implement
skipping to change at page 32, line 36 skipping to change at page 32, line 23
newRoot NOTIFICATION-TYPE newRoot NOTIFICATION-TYPE
-- OBJECTS { } -- OBJECTS { }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The newRoot trap indicates that the sending agent has "The newRoot trap indicates that the sending agent has
become the new root of the Spanning Tree; the trap is become the new root of the Spanning Tree; the trap is
sent by a bridge soon after its election as the new sent by a bridge soon after its election as the new
root, e.g., upon expiration of the Topology Change Timer root, e.g., upon expiration of the Topology Change Timer
immediately subsequent to its election. Implementation immediately subsequent to its election. Implementation
of this trap is optional." of this trap is optional."
::= { dot1dNotification 1 } ::= { dot1dNotifications 1 }
topologyChange NOTIFICATION-TYPE topologyChange NOTIFICATION-TYPE
-- OBJECTS { } -- OBJECTS { }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A topologyChange trap is sent by a bridge when any of "A topologyChange trap is sent by a bridge when any of
its configured ports transitions from the Learning state its configured ports transitions from the Learning state
to the Forwarding state, or from the Forwarding state to to the Forwarding state, or from the Forwarding state to
the Blocking state. The trap is not sent if a newRoot the Blocking state. The trap is not sent if a newRoot
trap is sent for the same transition. Implementation of trap is sent for the same transition. Implementation of
this trap is optional." this trap is optional."
::= { dot1dNotification 2 } ::= { dot1dNotifications 2 }
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
-- IEEE 802.1D MIB - Conformance Information -- IEEE 802.1D MIB - Conformance Information
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
dot1dGroups OBJECT IDENTIFIER ::= { dot1dConformance 1 } dot1dGroups OBJECT IDENTIFIER ::= { dot1dConformance 1 }
dot1dCompliances OBJECT IDENTIFIER ::= { dot1dConformance 2 } dot1dCompliances OBJECT IDENTIFIER ::= { dot1dConformance 2 }
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
-- units of conformance -- units of conformance
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
-- the dot1dBase group -- the dot1dBase group
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
skipping to change at page 34, line 30 skipping to change at page 34, line 19
dot1dStpPortPriority, dot1dStpPortPriority,
dot1dStpPortState, dot1dStpPortState,
dot1dStpPortEnable, dot1dStpPortEnable,
dot1dStpPortPathCost, dot1dStpPortPathCost,
dot1dStpPortDesignatedRoot, dot1dStpPortDesignatedRoot,
dot1dStpPortDesignatedCost, dot1dStpPortDesignatedCost,
dot1dStpPortDesignatedBridge, dot1dStpPortDesignatedBridge,
dot1dStpPortDesignatedPort, dot1dStpPortDesignatedPort,
dot1dStpPortForwardTransitions dot1dStpPortForwardTransitions
} }
STATUS deprecated STATUS current
DESCRIPTION DESCRIPTION
"Spanning Tree data for each port on this device." "Spanning Tree data for each port on this device."
::= { dot1dGroups 4 } ::= { dot1dGroups 4 }
dot1dStpPortGroup2 OBJECT-GROUP dot1dStpPortGroup2 OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dStpPort, dot1dStpPort,
dot1dStpPortPriority, dot1dStpPortPriority,
dot1dStpPortState, dot1dStpPortState,
dot1dStpPortEnable, dot1dStpPortEnable,
skipping to change at page 37, line 42 skipping to change at page 37, line 32
GROUP dot1dStaticGroup GROUP dot1dStaticGroup
DESCRIPTION DESCRIPTION
"Implementation of this group is optional." "Implementation of this group is optional."
GROUP dot1dNotificationGroup GROUP dot1dNotificationGroup
DESCRIPTION DESCRIPTION
"Implementation of this group is optional." "Implementation of this group is optional."
::= { dot1dCompliances 1 } ::= { dot1dCompliances 1 }
bridgeComplianceXXXX MODULE-COMPLIANCE bridgeComplianceXXXX MODULE-COMPLIANCE
-- RFC Ed.: replace XXXX with actual RFC number and remove this note -- RFC Ed.: replace XXXX with RFC number and remove this note
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for device support of bridging "The compliance statement for device support of bridging
services. This supports 32-bit Path Cost values and the services. This supports 32-bit Path Cost values and the
more restricted bridge and port priorities, as per IEEE more restricted bridge and port priorities, as per IEEE
802.1t." 802.1t."
MODULE MODULE
MANDATORY-GROUPS { MANDATORY-GROUPS {
dot1dBaseBridgeGroup, dot1dBaseBridgeGroup,
skipping to change at page 39, line 14 skipping to change at page 39, line 4
GROUP dot1dTpGroup GROUP dot1dTpGroup
DESCRIPTION DESCRIPTION
"Implementation of this group is mandatory for "Implementation of this group is mandatory for
bridges that support the transparent bridging bridges that support the transparent bridging
mode. A transparent or SRT bridge will implement mode. A transparent or SRT bridge will implement
this group." this group."
GROUP dot1dStaticGroup GROUP dot1dStaticGroup
DESCRIPTION DESCRIPTION
"Implementation of this group is optional." "Implementation of this group is optional."
GROUP dot1dNotificationGroup GROUP dot1dNotificationGroup
DESCRIPTION DESCRIPTION
"Implementation of this group is optional." "Implementation of this group is optional."
::= { dot1dCompliances 2 } ::= { dot1dCompliances 2 }
END END
5. Security Considerations 5. IANA Considerations
The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
dot1dBridge { mib-2 17 }
Editor's Note (to be removed prior to publication): this draft makes
no additional requests of the IANA. (XXX)
6. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
that have a MAX-ACCESS clause of read-write and/or read-create. Such that have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. network operations.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
skipping to change at page 40, line 44 skipping to change at page 40, line 44
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
6. Acknowledgments 7. Acknowledgments
The MIB module presented in this memo is a translation of the The MIB module presented in this memo is a translation of the
BRIDGE-MIB defined in [RFC1493] to the SMIv2 syntax. The original BRIDGE-MIB defined in [RFC1493] to the SMIv2 syntax. The original
authors of the SMIv1 module were E. Decker, P. Langille, A authors of the SMIv1 module were E. Decker, P. Langille, A
Rijsinghani and K. McCloghrie. Further acknowledgement is given to Rijsinghani and K. McCloghrie. Further acknowledgement is given to
the members of the original Bridge Working Group in [RFC1493]. the members of the original Bridge Working Group in [RFC1493].
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. The editors wish to thank the members of the Bridge MIB Task Force. The editors wish to thank the members of the Bridge MIB
Working Group, especially Mike MacFadden, John Flick, and Bert Working Group, especially Mike MacFadden, John Flick, and Bert
Visscher for their many comments and suggestions which improved this Visscher for their many comments and suggestions which improved this
effort. Juergen Schoenwaelder helped in finalizing the draft for effort. Juergen Schoenwaelder helped in finalizing the draft for
publication. publication.
7. Contact Information 8. Contact Information
The original version of this document was the result of significant The original version of this document was the result of significant
work by four major contributors: work by four major contributors:
E. Decker E. Decker
xxx details missing here xxx xxx details missing here xxx
P. Langille P. Langille
xxx details missing here xxx xxx details missing here xxx
skipping to change at page 41, line 49 skipping to change at page 42, line 5
640 N. 2200 West 640 N. 2200 West
Salt Lake City, Utah 84116-0850 Salt Lake City, Utah 84116-0850
USA USA
E. Bell E. Bell
3Com Europe Limited 3Com Europe Limited
3Com Centre, Boundary Way 3Com Centre, Boundary Way
Hemel Hempstead Herts. HP2 7YU Hemel Hempstead Herts. HP2 7YU
UK UK
8. Changes from RFC 1493 9. Changes from RFC 1493
The following changes have been made from RFC 1493. The following changes have been made from RFC 1493.
1. Translated the MIB definitions to use SMIv2. This includes the 1. Translated the MIB definitions to use SMIv2. This includes the
introduction of conformance statements. ASN.1 type definitions introduction of conformance statements. ASN.1 type definitions
have been converted into textual-conventions and several units have been converted into textual-conventions and several units
clauses were added. clauses were added.
2. The object dot1dStpPortPathCost32 was added to support IEEE 2. The object dot1dStpPortPathCost32 was added to support IEEE
802.1t. 802.1t.
3. Permissible values for dot1dStpPriority and dot1dStpPortPriority 3. Permissible values for dot1dStpPriority and dot1dStpPortPriority
skipping to change at page 42, line 23 skipping to change at page 42, line 27
802.1w. 802.1w.
4. Interpretation of dot1dStpTimeSinceTopologyChange has been 4. Interpretation of dot1dStpTimeSinceTopologyChange has been
clarified for bridges supporting the rapid spanning tree protocol clarified for bridges supporting the rapid spanning tree protocol
(RSTP). (RSTP).
5. Updated the introductionary boilerplate text, the security 5. Updated the introductionary boilerplate text, the security
considerations section and the references to comply with the considerations section and the references to comply with the
current IETF standards and guidelines. current IETF standards and guidelines.
6. Updated references to point to newer IEEE 802.1d documents. 6. Updated references to point to newer IEEE 802.1d documents.
7. Additions and clarifications in various description clauses. 7. Additions and clarifications in various description clauses.
9. Open Issues
This list of open issues should be cleared and removed before this
document hits the IESG.
1. Shall we define a special value for dot1dStpPortPathCost in case
dot1dStpPortPathCost32 is supported and goes out of the
dot1dStpPortPathCost range? Yes. John Flick to provide text
based on 802.1t Table 8.5 and the following Note 2 to explain
this issue.
2. Someone (John?) should check whether the BridgeId description is
still consistent with 802.1t.
3. There is a comment for the module registration of the rstpMIB
currently in draft-ietf-bridge-rstpmib-05.txt. What is the
future of this document - is it safe to leave this in?
4. Complete the contributor's contact information.
10. References 10. References
10.1 Normative References 10.1 Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D. and J. Schoenwaelder, [RFC2578] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
"Structure of Management Information Version 2 (SMIv2)", "Structure of Management Information Version 2 (SMIv2)",
STD 58, RFC 2578, April 1999. STD 58, RFC 2578, April 1999.
skipping to change at page 43, line 31 skipping to change at page 43, line 18
[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 "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
[RFC1493] Decker, E., Langille, P., Rijsinghani, A. and K. [RFC1493] Decker, E., Langille, P., Rijsinghani, A. and K.
McCloghrie, "Definitions of Managed Objects for Bridges", McCloghrie, "Definitions of Managed Objects for Bridges",
RFC 1493, July 1993. RFC 1493, July 1993.
[RFC1513] Waldbusser, S., "Token Ring Extensions to the Remote [RFC1525] Decker, E., McCloghrie, K., Langille, P. and A.
Network Monitoring MIB", RFC 1513, September 1993. Rijsinghani, "Definitions of Managed Objects for Source
Routing Bridges", RFC 1525, September 1993.
Authors' Addresses Authors' Addresses
Kenyon C. Norseth (editor) Kenyon C. Norseth (editor)
L-3 Communications L-3 Communications
640 N. 2200 West 640 N. 2200 West
Salt Lake City, Utah 84116-0850 Salt Lake City, Utah 84116-0850
USA USA
Phone: +1 801-594-2809 Phone: +1 801-594-2809
skipping to change at page 45, line 41 skipping to change at page 44, line 41
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

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