draft-ietf-bridge-rstpmib-09.txt   rfc4318.txt 
Internet Draft D.Levi Network Working Group D. Levi
Expires February 2006 Nortel Networks Request for Comments: 4318 Nortel Networks
draft-ietf-bridge-rstpmib-09.txt D.Harrington Category: Standards Track D. Harrington
Effective Software Effective Software
August 2005 December 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
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
aware will be disclosed, in accordance with Section 6 of BCP 79.
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 This document specifies an Internet standards track protocol for the
http://www.ietf.org/shadow.html. Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). All Rights Reserved. Copyright (C) The Internet Society (2005).
Abstract Abstract
This memo defines an SMIv2 MIB module for managing the Rapid Spanning 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 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) IEEE Std 802.1D-1998 for bridging between Local Area Network (LAN)
segments. The objects in this MIB are defined to apply both to segments. The objects in this MIB are defined to apply both to
transparent bridging and to bridges connected by subnetworks other transparent bridging and to bridges connected by subnetworks other
than LAN segments. than LAN segments.
Table of Contents Table of Contents
1 The Internet-Standard Management Framework ................... 3 1. The Internet-Standard Management Framework ......................2
2 Overview ..................................................... 3 2. Overview ........................................................2
3 Relationship to IEEE 802.1t and 802.1w amendments ............ 3 3. Relationship to IEEE 802.1t and 802.1w Amendments ...............2
4 Relation to the BRIDGE-MIB ................................... 4 4. Relation to the BRIDGE-MIB ......................................3
5 Definitions for RSTP-MIB ..................................... 5 5. Definitions for RSTP-MIB ........................................3
6 Acknowledgments .............................................. 12 6. Acknowledgements ...............................................10
7 IANA Considerations .......................................... 12 7. IANA Considerations ............................................10
8 Security Considerations ...................................... 12 8. Security Considerations ........................................10
9 Normative References ......................................... 14 9. Normative References ...........................................11
10 Informative References ...................................... 14 10. Informative References ........................................12
11 Authors' Addresses .......................................... 16
Intellectual Property Statement ............................... 17
Disclaimer of Validity ........................................ 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].
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).
skipping to change at page 3, line 29 skipping to change at page 2, line 29
2. Overview 2. Overview
This memo defines an SMIv2 MIB module for managing the Rapid Spanning This memo defines an SMIv2 MIB module for managing the Rapid Spanning
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 objects 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
There are concerns that there may be changes made in the 802.1D-2004 There are concerns that there may be changes made in the 802.1D-2004
edition that would lead to non-backwards compatible SMI changes for edition that would lead to non-backward-compatible SMI changes for
802.1t and 802.1w managed objects in the MIB modules. The Bridge MIB 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 working group decided to 'freeze' the technical content of the MIB
level that is compatible with the 802.1t and 802.1w versions, and modules at a level that is compatible with the 802.1t and 802.1w
leave to the IEEE 802.1 WG any updates beyond this. versions, and leave to the IEEE 802.1 working group any updates
beyond this.
For informational purposes only, these are the references for the For informational purposes only, these are the references for the
above objects in 802.1D-2004 [802.1D-2004]. 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 The objects in the RSTP-MIB supplement those defined in the Bridge
MIB [RFC1493bis]. MIB [RFC4188].
The Original BRIDGE-MIB [RFC1493] has been updated in an The Original BRIDGE-MIB [RFC1493] has been updated in an SMIv2-
SMIv2-compliant version [RFC1493bis]. Conformance statements have compliant version [RFC4188]. Conformance statements have been added
been added and some description and reference clauses have been and some description and reference clauses have been updated. The
updated. The interpretations of some objects were changed to interpretations of some objects were changed to accommodate IEEE
accommodate IEEE 802.1t and 802.1w amendments. 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 [RFC4188] for details.
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
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
dot1dStp, dot1dStpPortEntry dot1dStp, dot1dStpPortEntry
FROM BRIDGE-MIB; FROM BRIDGE-MIB;
rstpMIB MODULE-IDENTITY rstpMIB MODULE-IDENTITY
LAST-UPDATED "200507290000Z" LAST-UPDATED "200512070000Z"
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.
Copyright (C) The Internet Society (2005). This version of Copyright (C) The Internet Society (2005). This version of
this MIB module is part of RFC XXXX; See the RFC itself for this MIB module is part of RFC 4318; See the RFC itself for
full legal notices." full legal notices."
REVISION "200507290000Z" REVISION "200512070000Z"
DESCRIPTION DESCRIPTION
"The initial version of this MIB module as published in "The initial version of this MIB module as published in
RFC XXXX." RFC 4318."
::= { mib-2 134 }
::= { 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 7, line 10 skipping to change at page 5, line 39
The value of this object MUST be retained across The value of this object MUST be retained across
reinitializations of the management system." reinitializations of the management system."
REFERENCE REFERENCE
"IEEE 802.1w clause 17.16.6" "IEEE 802.1w clause 17.16.6"
DEFVAL { 3 } DEFVAL { 3 }
::= { dot1dStp 17 } ::= { dot1dStp 17 }
-- --
-- { dot1dStp 18 } was used to represent dot1dStpPathCostDefault -- { dot1dStp 18 } was used to represent dot1dStpPathCostDefault
-- in an earlier version of this MIB. It has since been
-- obsoleted, and should not be used. -- obsoleted, and should not be used.
-- --
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."
skipping to change at page 8, line 23 skipping to change at page 6, line 50
"IEEE 802.1w clause 14.8.2.4, 17.18.10, 17.26" "IEEE 802.1w clause 14.8.2.4, 17.18.10, 17.26"
::= { dot1dStpExtPortEntry 1 } ::= { dot1dStpExtPortEntry 1 }
dot1dStpPortAdminEdgePort OBJECT-TYPE dot1dStpPortAdminEdgePort OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The administrative value of the Edge Port parameter. A "The administrative value of the Edge Port parameter. A
value of true(1) indicates that this port should be value of true(1) indicates that this port should be
assumed as an edge-port and a value of false(2) indicates assumed as an edge-port, and a value of false(2) indicates
that this port should be assumed as a non-edge-port. that this port should be assumed as a non-edge-port.
Setting this object will also cause the corresponding Setting this object will also cause the corresponding
instance of dot1dStpPortOperEdgePort to change to the instance of dot1dStpPortOperEdgePort to change to the
same value. Note that even when this object's value same value. Note that even when this object's value
is true, the value of the corresponding instance of is true, the value of the corresponding instance of
dot1dStpPortOperEdgePort can be false if a BPDU has dot1dStpPortOperEdgePort can be false if a BPDU has
been received. been received.
The value of this object MUST be retained across The value of this object MUST be retained across
reinitializations of the management system." reinitializations of the management system."
skipping to change at page 9, line 20 skipping to change at page 7, line 47
forceTrue(0), forceTrue(0),
forceFalse(1), forceFalse(1),
auto(2) auto(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The administrative point-to-point status of the LAN segment "The administrative point-to-point status of the LAN segment
attached to this port, using the enumeration values of the attached to this port, using the enumeration values of the
IEEE 802.1w clause. A value of forceTrue(0) indicates IEEE 802.1w clause. A value of forceTrue(0) indicates
that this port should always be treated as if it is connected that this port should always be treated as if it is
to a point-to-point link. A value of forceFalse(1) indicates connected to a point-to-point link. A value of
that this port should be treated as having a shared media forceFalse(1) indicates that this port should be treated as
connection. A value of auto(2) indicates that this port is having a shared media connection. A value of auto(2)
considered to have a point-to-point link if it is an Aggregator indicates that this port is considered to have a
and all of its members are aggregatable, or if the MAC entity 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 is configured for full duplex operation, either through
auto-negotiation or by management means. Manipulating this auto-negotiation or by management means. Manipulating this
object changes the underlying adminPortToPortMAC. object changes the underlying adminPortToPortMAC.
The value of this object MUST be retained across The value of this object MUST be retained across
reinitializations of the management system." reinitializations of the management system."
REFERENCE REFERENCE
"IEEE 802.1w clause 6.4.3, 6.5, 14.8.2" "IEEE 802.1w clause 6.4.3, 6.5, 14.8.2"
::= { dot1dStpExtPortEntry 4 } ::= { dot1dStpExtPortEntry 4 }
dot1dStpPortOperPointToPoint OBJECT-TYPE dot1dStpPortOperPointToPoint OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The operational point-to-point status of the LAN segment "The operational point-to-point status of the LAN segment
attached to this port. It indicates whether a port is attached to this port. It indicates whether a port is
considered to have a point-to-point connection or not. considered to have a point-to-point connection.
If adminPointToPointMAC is set to auto(2), then the value If adminPointToPointMAC is set to auto(2), then the value
of operPointToPointMAC is determined in accordance with the of operPointToPointMAC is determined in accordance with the
specific procedures defined for the MAC entity concerned, specific procedures defined for the MAC entity concerned,
as defined in IEEE 802.1w clause 6.5. The value is as defined in IEEE 802.1w, clause 6.5. The value is
determined dynamically; i.e., it is re-evaluated whenever determined dynamically; that is, it is re-evaluated whenever
the value of adminPointToPointMAC changes, and whenever the value of adminPointToPointMAC changes, and whenever
the specific procedures defined for the MAC entity evaluate the specific procedures defined for the MAC entity evaluate
a change in its point-to-point status." a change in its point-to-point status."
REFERENCE REFERENCE
"IEEE 802.1w clause 6.4.3, 6.5, 14.8.2" "IEEE 802.1w clause 6.4.3, 6.5, 14.8.2"
::= { dot1dStpExtPortEntry 5 } ::= { dot1dStpExtPortEntry 5 }
dot1dStpPortAdminPathCost OBJECT-TYPE dot1dStpPortAdminPathCost OBJECT-TYPE
SYNTAX Integer32 (0..200000000) SYNTAX Integer32 (0..200000000)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The administratively assigned value for the contribution "The administratively assigned value for the contribution
of this port to the path cost of paths towards the spanning of this port to the path cost of paths toward the spanning
tree root. tree root.
Writing a value of '0' assigns the automatically calculated Writing a value of '0' assigns the automatically calculated
default Path Cost value to the port. If the default Path default Path Cost value to the port. If the default Path
Cost is being used, this object returns '0' when read. Cost is being used, this object returns '0' when read.
This complements the object dot1dStpPortPathCost or This complements the object dot1dStpPortPathCost or
dot1dStpPortPathCost32, which returns the operational value dot1dStpPortPathCost32, which returns the operational value
of the path cost. of the path cost.
skipping to change at page 12, line 5 skipping to change at page 10, line 16
Spanning Tree Protocol (RSTP) bridging services." Spanning Tree Protocol (RSTP) bridging services."
MODULE MODULE
MANDATORY-GROUPS { MANDATORY-GROUPS {
rstpBridgeGroup, rstpBridgeGroup,
rstpPortGroup rstpPortGroup
} }
::= { rstpCompliances 1 } ::= { rstpCompliances 1 }
END END
6. Acknowledgments 6. Acknowledgements
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 that
which improved this effort. improved this effort.
Vivian Ngai and Les Bell were the initial authors of this document, Vivian Ngai and Les Bell were the initial authors of this document,
and did the bulk of the development work for 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: The IANA has assigned the following OID:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
rstpMIB { mib-2 xxxx } rstpMIB { mib-2 134 }
8. Security Considerations 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 module
have a MAX-ACCESS clause of read-write and/or read-create. Such with 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. These are the tables and objects and their
sensitivity/vulnerability:
Writable objects that could be misused to cause network delays and Writable objects that could be misused to cause network delays and
spanning tree instabilities include dot1dStpVersion, spanning tree instabilities include dot1dStpVersion,
dot1dStpTxHoldCount, dot1dStpPortProtocolMigration, dot1dStpTxHoldCount, dot1dStpPortProtocolMigration,
dot1dStpPortAdminEdgePort, and dot1dStpPortAdminPathCost. dot1dStpPortAdminEdgePort, and dot1dStpPortAdminPathCost.
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
vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability:
dot1dStpVersion could be read by an attacker to identify environments dot1dStpVersion could be read by an attacker to identify environments
containing applications or protocols which are potentially sensitive containing applications or protocols that are potentially sensitive
to RSTP mode. to RSTP mode.
dot1dStpPortAdminPointToPoint could be used to mislead an access dot1dStpPortAdminPointToPoint could be used to mislead an access
control protocol, such as 802.1x, to believe that only one other control protocol, such as 802.1x, to believe that only one other
system is attached to a LAN segment and to enable network access system is attached to a LAN segment and to enable network access
based on that assumption. This situation could permit potential man- based on that assumption. This situation could permit potential
in-the-middle attacks. man-in-the-middle attacks.
SNMPv1 by itself is not a secure environment. Even if the network SNMP versions prior to SNMPv3 did not include adequate security.
itself is secure (for example by using IPSec), even then, there is no Even if the network itself is secure (for example by using IPsec),
control as to who on the secure network is allowed to access and even then, there is no control as to who on the secure network is
GET/SET (read/change/create/delete) the objects in this MIB. allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy), and user-based access control. authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
9. Normative References 9. Normative References
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Rose, M., and S. Waldbusser, "Structure of Management "Structure of Management Information Version 2
Information Version 2 (SMIv2)", STD 58, RFC 2578, April (SMIv2)", STD 58, RFC 2578, April 1999.
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Rose, M., and S. Waldbusser, "Textual Conventions for "Textual Conventions for SMIv2", STD 58, RFC 2579,
SMIv2", STD 58, RFC 2579, April 1999. April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Rose, M., and S. Waldbusser, "Conformance Statements for "Conformance Statements for SMIv2", STD 58, RFC 2580,
SMIv2", STD 58, RFC 2580, April 1999. 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 -
3: Media Access Control (MAC) Bridges: Revision. This is Part 3: Media Access Control (MAC) Bridges: Revision.
a revision of ISO/IEC 10038: 1993, 802.1j-1992 and This is a revision of ISO/IEC 10038: 1993, 802.1j-1992
802.6k-1992. It incorporates P802.11c, P802.1p and 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.
[RFC1493bis] Bell, E. and Norseth, K., "Definitions of Managed Objects [RFC4188] Norseth, K. and E. Bell, "Definitions of Managed
for Bridges", draft-ietf-bridge-bridgemib-smiv2-10.txt, Objects for Bridges", RFC 4188, September 2005.
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)
Standard for Information technology - Telecommunications IEEE Standard for Information technology -
and information exchange between systems - Local and Telecommunications and information exchange between
metropolitan area networks - Common specifications - Part systems - Local and metropolitan area networks - Common
3: Media Access Control (MAC) Bridges: Technical and specifications - Part 3: Media Access Control (MAC)
Editorial Corrections". Bridges: Technical and 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)
Standard for Information technology--Telecommunications and IEEE Standard for Information technology--
information exchange between systems--Local and Telecommunications and information exchange between
metropolitan area networks--Common Specifications--Part 3: systems--Local and metropolitan area networks--Common
Media Access Control (MAC) Bridges: Rapid Reconfiguation". Specifications--Part 3: 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
Standard Management Framework", RFC 3410, December 2002. Internet-Standard Management Framework", RFC 3410,
December 2002.
[802.1D-2004] IEEE Project 802 Local and Metropolitan Area [802.1D-2004] IEEE Project 802 Local and Metropolitan Area Networks,
Networks, "IEEE Standard 802.1D-2004 MAC Bridges", 2004. "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.
"Definitions of Managed Objects for Bridges", RFC 1493, McCloghrie, "Definitions of Managed Objects for
July 1993. Bridges", RFC 1493, July 1993.
11. Authors' Addresses Authors' Addresses
David Levi David Levi
Nortel Networks Nortel Networks
4655 Great America Parkway 4655 Great America Parkway
Santa Clara, CA 95054 Santa Clara, CA 95054
USA USA
Phone: +1 865 686 0432 Phone: +1 408 495 5138
Email: dlevi@nortel.com EMail: dlevi@nortel.com
David Harrington David Harrington
Effective Software Effective Software
50 Harding Rd. 50 Harding Rd.
Portsmouth, NH 03801 Portsmouth, NH 03801
USA USA
Phone: +1 603 436 8634 Phone: +1 603 436 8634
Email: ietfdbh@comcast.net EMail: ietfdbh@comcast.net
Les Bell Les Bell
Hemel Hempstead Hemel Hempstead
Herts. HP2 7YU Herts. HP2 7YU
UK UK
EMail: elbell@ntlworld.com EMail: elbell@ntlworld.com
Vivian Ngai Vivian Ngai
Salt lake City, UT Salt lake City, UT
USA USA
Email: vivian_ngai@acm.org EMail: vivian_ngai@acm.org
Intellectual Property Statement Full Copyright Statement
Copyright (C) The Internet Society (2005).
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.
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.
Intellectual Property
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
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an 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 attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at ietf-
ietf-ipr@ietf.org. 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 (2005). Acknowledgement
This document is subject to the rights, licenses and restrictions Funding for the RFC Editor function is currently provided by the
contained in BCP 78, and except as set forth therein, the authors Internet Society.
retain all their rights.
 End of changes. 54 change blocks. 
146 lines changed or deleted 149 lines changed or added

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