draft-ietf-bridge-rstpmib-05.txt   draft-ietf-bridge-rstpmib-06.txt 
Internet Draft V. Ngai Internet Draft V. Ngai
Expires March 2005 Enterasys Networks Expires October 2005 Enterasys Networks
draft-ietf-bridge-rstpmib-05.txt E. Bell draft-ietf-bridge-rstpmib-06.txt E. Bell
3Com Corp. 3Com Corp.
September 2004 April 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, I certify that any applicable By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed, 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 or will be disclosed, and any of which I become aware will be
disclosed, in accordance with RFC 3668. disclosed, in accordance with RFC 3668.
skipping to change at page 1, line 43 skipping to change at page 1, line 43
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 21, 2005. This Internet-Draft will expire on January 21, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines an SMIv2 MIB module for managing the Rapid Spanning
for use with network management protocols in TCP/IP based internets. Tree capability defined by the IEEE P802.1t and P802.1w amendments to
In particular, it defines a MIB module for managing the Rapid IEEE Std 802.1D-1998 for bridging between Local Area Network (LAN)
Spanning Tree capability defined by the IEEE P802.1t [802.1t] and segments. The objects in this MIB are defined to apply both to
P802.1w [802.1w] amendments to IEEE Std 802.1D-1998 for bridging transparent bridging and to bridges connected by subnetworks other
between Local Area Network (LAN) segments. than 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. This memo also includes a MIB
module in a manner that is compliant to SMIv2 [RFC2578].
This memo supplements RFC 1493 [RFC1493] and RFC 2674 [RFC2674].
Table of Contents Table of Contents
1 The Internet-Standard Management Framework ................... 4 1 The Internet-Standard Management Framework ................... 3
2 Overview ..................................................... 4 2 Overview ..................................................... 3
2.1 Scope ...................................................... 4 3 Relationship to IEEE 802.1t and 802.1w amendments ............ 3
3 Structure of MIBs ............................................ 4 4 Relation to the BRIDGE-MIB ................................... 4
3.1 Structure of RSTP-MIB ...................................... 5 5 Definitions for RSTP-MIB ..................................... 5
3.2 Relationship to Other MIBs ................................. 5 6 Acknowledgments .............................................. 11
3.2.1 Relation to Original Bridge MIB .......................... 5 7 IANA Considerations .......................................... 11
3.2.1.1 The dot1dBase Group .................................... 6 8 Security Considerations ...................................... 11
3.2.1.2 The dot1dStp Group ..................................... 6 9 Normative References ......................................... 13
3.2.1.3 The dot1dTp Group ...................................... 7 10 Informative References ...................................... 14
3.2.1.4 The dot1dStatic Group .................................. 7 11 Authors' Addresses .......................................... 15
4 Definitions for RSTP-MIB ..................................... 8 Intellectual Property Statement ............................... 16
5 Acknowledgments .............................................. 15 Disclaimer of Validity ........................................ 16
6 Security Considerations ...................................... 15 Copyright Statement ........................................... 16
7 Normative References ......................................... 16
8 Informative References ....................................... 17
9 Authors' Addresses ........................................... 18
Intellectual Property Statement ............................... 19
Disclaimer of Validity ........................................ 19
Copyright Statement ........................................... 19
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].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, 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 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
2. Overview 2. Overview
A common device present in many networks is the Bridge. This device This memo defines an SMIv2 MIB module for managing the Rapid Spanning
is used to connect Local Area Network segments below the network Tree (RSTP) capability defined by the IEEE P802.1t [802.1t] and
layer. These devices are often known as 'layer 2 switches'. 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
There are two major modes defined for this bridging: Source-Route and this MIB are defined to apply both to transparent bridging and to
transparent. Source-Route bridging is described by IEEE 802.5 bridges connected by subnetworks other than LAN segments.
[802.5] and is not discussed further in this document.
The transparent method of bridging is defined by IEEE 802.1D-1998
[802.1D] Managed objects for that original specification of
transparent bridging were defined in RFC 1493 [RFC1493].
2.1. Scope
This MIB includes a comprehensive set of managed objects which
attempts to match the set defined in IEEE P802.1t [802.1t] and
P802.1w [802.1w].
3. Structure of MIBs
This document defines additional managed objects for Rapid Spanning
Tree Protocol defined by IEEE P802.1t and IEEE P802.1w, on top of
those existing in the original BRIDGE-MIB module defined in
[RFC1493]: that MIB module is to be maintained unchanged for
backwards compatibility. Section 3.4.1 of the present document
contains some recommendations regarding usage of objects in the
original bridge MIB by devices implementing the enhancements defined
here.
3.1. Structure of RSTP-MIB 3. Relationship to IEEE 802.1t and 802.1w amendments
Objects in this MIB are defined as an addition to the dot1dStp group This document defines managed object for the Rapid Spanning Tree
in the original bridge MIB [RFC1493]. The overall structure is Protocol defined by the IEEE P802.1t and IEEE P802.1w amendments to
shown below: 802.1d-1998.
Bridge 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
dot1dStpPathCostDefault
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
3.2. Relationship to Other MIBs Following are the references for the above objects in 802.1D-2004.
As described above, some IEEE 802.1D management objects have not been
included in this MIB because they overlap with objects in other MIBs
applicable to a bridge implementing this MIB. In particular, it is
assumed that a bridge implementing this MIB will implement the
original bridge MIB [RFC1493].
3.2.1. Relation to Original Bridge MIB
This section defines how objects in the original bridge MIB module
[RFC1493] should be represented for devices which implement all the
MIB modules described in this memo. Some of the old objects are less
useful in such devices but must still be implemented for reasons of
backwards compatibility.
3.2.1.1. The dot1dBase Group
This mandatory group contains the objects which are applicable to all
types of bridges. Interpretation of this group is unchanged.
3.2.1.2. The dot1dStp Group
This group contains the objects that denote the bridge's state with
respect to the Spanning Tree Protocol. If a node does not implement
the Spanning Tree Protocol, this group will not be implemented.
In a device supporting the Spanning Tree Algorithm and Protocol
defined in IEEE 802.1D-1998 Clause 8, interpretation of this group is
unchanged.
In a device supporting the Rapid Spanning Tree Algorithm and Protocol
defined in IEEE 802.1w Clause 17, the interpretation of objects in
this group is unchanged except for those listed below:
dot1dStpPriority
Definition remains unchanged, but the permissible values are
changed to 0-61440, in steps of 4096.
dot1dStpPortPriority
Definition remains unchanged, but the permissible values are
changed to 0-240, in steps of 16.
dot1dStpTimeSinceTopologyChange RSTP-MIB Name IEEE 802.1D-2004 Reference
The time since the tcWhile timer for any port on this Bridge was
non-zero.
dot1dStpTopChanges dot1dStp
The number of times that there have been at least one non-zero dot1dStpVersion 17.13.4 ForceVersion
tcWhile timer on this Bridge. 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
In a device supporting the 32-bit default Path Costs defined in IEEE 4. Relation to the BRIDGE-MIB
802.1t Table 8-5, the object dot1dStpPortPathCost32 [RFC1493] should
be used rather than the older object dot1dStpPortPathCost. The newer
object supports the expanded range of 1-200,000,000.
3.2.1.3. The dot1dTp Group 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.
This group contains objects that describe the entity's state with The object dot1dStpPortPathCost32 was added to support IEEE 802.1t,
respect to transparent bridging. Interpretation for this group is and the permissible values of dot1dStpPriority and
unchanged. 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.
3.2.1.4. The dot1dStatic Group See the updated BRIDGE-MIB [RFC1493bis] for details.
This group contains objects that describe the entity's state with The objects in the RSTP-MIB supplement those defined in the Bridge
respect to destination-address filtering. Interpretation for this MIB [RFC1493bis].
group is unchanged.
4. 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 MODULE-IDENTITY, OBJECT-TYPE, Integer32
FROM SNMPv2-SMI FROM SNMPv2-SMI
TruthValue TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
dot1dBridge, dot1dStp, dot1dStpPortEntry dot1dBridge, dot1dStp, dot1dStpPortEntry
FROM BRIDGE-MIB; FROM BRIDGE-MIB;
rstpMIB MODULE-IDENTITY rstpMIB MODULE-IDENTITY
LAST-UPDATED "200403210000Z" LAST-UPDATED "200503190000Z"
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 "200403210000Z" REVISION "200503190000Z"
-- RFC Ed.: replace XXXX with RFC number and remove this note
DESCRIPTION DESCRIPTION
"Draft 4" "Initial revision, published as part of RFC XXXX"
::= { dot1dBridge 11 } -- RFC Ed.: replace xxxx with IANA-assigned number and
-- remove this note
::= { mib-2 xxxx }
-- ---------------------------------------------------------- --
-- subtrees in the RSTP-MIB
-- ---------------------------------------------------------- --
rstpNotifications OBJECT IDENTIFIER ::= { rstpMIB 0 }
rstpObjects OBJECT IDENTIFIER ::= { rstpMIB 1 }
rstpConformance OBJECT IDENTIFIER ::= { rstpMIB 2 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Addition to the dot1dStp group -- Addition to the dot1dStp group
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1dStpVersion OBJECT-TYPE dot1dStpVersion OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
stpCompatible(0), stpCompatible(0),
rstp(2) rstp(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The version of Spanning Tree Protocol the bridge is "The version of Spanning Tree Protocol the bridge is
currently running. The value 'stpCompatible(0)' currently running. The value 'stpCompatible(0)'
indicates the Spanning Tree Protocol specified in indicates the Spanning Tree Protocol specified in
IEEE 802.1D and 'rstp(2)' indicates the Rapid Spanning IEEE 802.1D-1998 and 'rstp(2)' indicates the Rapid
Tree Protocol specified in IEEE 802.1w. New value may Spanning Tree Protocol specified in IEEE 802.1w and
be defined as future versions of the protocol become clause 17 of 802.1D-2004. New values may be defined
available." as future versions of the protocol become available."
REFERENCE REFERENCE
"IEEE 802.1w clause 14.8.1, 17.12, 17.16.1" "IEEE 802.1w clause 14.8.1, 17.12, 17.16.1"
DEFVAL { rstp } DEFVAL { rstp }
::= { dot1dStp 16 } ::= { dot1dStp 16 }
dot1dStpTxHoldCount OBJECT-TYPE dot1dStpTxHoldCount OBJECT-TYPE
SYNTAX Integer32 (1..10) SYNTAX Integer32 (1..10)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value used by the Port Transmit state machine to limit "The value used by the Port Transmit state machine to limit
the maximum transmission rate." the maximum transmission rate."
REFERENCE REFERENCE
"IEEE 802.1w clause 17.16.6" "IEEE 802.1w clause 17.16.6"
DEFVAL { 3 } DEFVAL { 3 }
::= { dot1dStp 17 } ::= { dot1dStp 17 }
dot1dStpPathCostDefault OBJECT-TYPE --
SYNTAX INTEGER { -- { dot1dStp 18 } was used to represent dot1dStpPathCostDefault
stp8021d1998(1), -- in an internet-draft version of this MIB. It has since been
stp8021t2001(2) -- obsoleted, and should not be used.
} --
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The version of the Spanning Tree default Path Costs that
are to be used by this Bridge. A value of 8021d1998(1)
means the bridge is using the 16-bit default Path Costs from
IEEE Std. 802.1D-1998. A value of stp8021t2001(2) means
the bridge is using the 32-bit default Path Costs from IEEE
Std. 802.1t."
REFERENCE
"IEEE 802.1D & 802.1t Table 8-5"
::= { dot1dStp 18 }
dot1dStpExtPortTable OBJECT-TYPE dot1dStpExtPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dStpExtPortEntry SYNTAX SEQUENCE OF Dot1dStpExtPortEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table that contains port-specific Rapid Spanning Tree "A table that contains port-specific Rapid Spanning Tree
information." information."
::= { dot1dStp 19 } ::= { dot1dStp 19 }
skipping to change at page 12, line 49 skipping to change at page 9, line 46
dot1dStpPortPathCost32, which returns the operational value dot1dStpPortPathCost32, which returns the operational value
of the path cost." of the path cost."
REFERENCE REFERENCE
"IEEE 802.1D-1998: Section 8.5.5.3" "IEEE 802.1D-1998: Section 8.5.5.3"
::= { dot1dStpExtPortEntry 6 } ::= { dot1dStpExtPortEntry 6 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- rstpMIB - Conformance Information -- rstpMIB - Conformance Information
-- ------------------------------------------------------------- -- -------------------------------------------------------------
rstpConformance OBJECT IDENTIFIER ::= { rstpMIB 1 }
rstpGroups OBJECT IDENTIFIER ::= { rstpConformance 1 } rstpGroups OBJECT IDENTIFIER ::= { rstpConformance 1 }
rstpCompliances OBJECT IDENTIFIER ::= { rstpConformance 2 } rstpCompliances OBJECT IDENTIFIER ::= { rstpConformance 2 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Units of conformance -- Units of conformance
-- ------------------------------------------------------------- -- -------------------------------------------------------------
rstpBridgeGroup OBJECT-GROUP rstpBridgeGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dStpVersion, dot1dStpVersion,
dot1dStpTxHoldCount dot1dStpTxHoldCount
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Rapid Spanning Tree information for the bridge." "Rapid Spanning Tree information for the bridge."
::= { rstpGroups 1 } ::= { rstpGroups 1 }
rstpDefaultPathCostGroup OBJECT-GROUP
OBJECTS {
dot1dStpPathCostDefault
}
STATUS current
DESCRIPTION
"Default Spanning Tree path cost information."
::= { rstpGroups 2 }
rstpPortGroup OBJECT-GROUP rstpPortGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dStpPortProtocolMigration, dot1dStpPortProtocolMigration,
dot1dStpPortAdminEdgePort, dot1dStpPortAdminEdgePort,
dot1dStpPortOperEdgePort, dot1dStpPortOperEdgePort,
dot1dStpPortAdminPointToPoint, dot1dStpPortAdminPointToPoint,
dot1dStpPortOperPointToPoint, dot1dStpPortOperPointToPoint,
dot1dStpPortAdminPathCost dot1dStpPortAdminPathCost
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Rapid Spanning Tree information for individual ports." "Rapid Spanning Tree information for individual ports."
::= { rstpGroups 3 } ::= { rstpGroups 2 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Compliance statements -- Compliance statements
-- ------------------------------------------------------------- -- -------------------------------------------------------------
rstpCompliance MODULE-COMPLIANCE rstpCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for device support of bridging "The compliance statement for device support of Rapid
services." Spanning Tree Protocol (RSTP) bridging services."
MODULE MODULE
MANDATORY-GROUPS { MANDATORY-GROUPS {
rstpBridgeGroup, rstpBridgeGroup,
rstpPortGroup rstpPortGroup
} }
GROUP rstpDefaultPathCostGroup
DESCRIPTION
"Support for this group is mandatory only if
both 16-bit and 32-bit Path Costs are supported."
::= { rstpCompliances 1 } ::= { rstpCompliances 1 }
END END
5. 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.
6. Security Considerations 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 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 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.
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.
SNMPv1 by itself is not a secure environment. Even if the network 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 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 control as to who on the secure network is allowed to access and
GET/SET (read/change/create/delete) the objects in this MIB. GET/SET (read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model [USM] and the View-based Access of the User-based Security Model [USM] and the View-based Access
Control Model [VACM] is recommended. Control Model [VACM] is recommended.
7. Normative References 9. Normative References
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Structure of Management Rose, M., and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Textual Conventions for Rose, M., and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for Rose, M., and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC2674] Bell, E., Smith, A., Langille, P., Rijhsinghani, A. and [RFC2674] Bell, E., Smith, A., Langille, P., Rijhsinghani, A. and
McCloghrie, "Definitions of Managed Objects for Bridges McCloghrie, "Definitions of Managed Objects for Bridges
with Traffic Classes, Multicast Filtering and Virtual LAN with Traffic Classes, Multicast Filtering and Virtual LAN
Extensions", RFC 2674, August 1999. Extensions", RFC 2674, August 1999.
[802.1D] "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 802.6k- a revision of ISO/IEC 10038: 1993, 802.1j-1992 and
1992. It incorporates P802.11c, P802.1p and P802.12e." 802.6k-1992. It incorporates P802.11c, P802.1p and
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, [RFC1493] Decker, E., Langille, P., Rijsinghani, A. and K. McCloghrie,
"Definitions of Managed Objects for Bridges", RFC 1493, "Definitions of Managed Objects for Bridges", RFC 1493,
July 1993. 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 [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
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".
8. 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.
9. Authors' Addresses 11. Authors' Addresses
Les Bell Les Bell
3Com Europe Limited 3Com Europe Limited
eCom Centre, Boundary Way eCom Centre, Boundary Way
Hemel Hempstead Hemel Hempstead
Herts. HP2 7YU Herts. HP2 7YU
UK UK
Phone: +44 1442 438025 Phone: +44 1442 438025
Email: Les_Bell@3Com.com Email: Les_Bell@3Com.com
 End of changes. 

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