Draft-ietf-bridge-rstpmib-09.txt
"David B Harrington" <[email protected]> Wed, 24 Aug 2005 19:49:51 -0400
| Newsgroups | gmane.ietf.bridge |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. ------=_NextPart_000_007A_01C5A8E4.FE320CF0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Please publish this update. This update is in response to IESG Evaluation::Revised ID Needed David Harrington [email protected] ------=_NextPart_000_007A_01C5A8E4.FE320CF0 Content-Type: text/plain; name="draft-ietf-bridge-rstpmib-09.txt" Content-Disposition: attachment; filename="draft-ietf-bridge-rstpmib-09.txt" Content-Transfer-Encoding: quoted-printable =0A= =0A= =0A= =0A= Internet Draft RSTP MIB August 2005=0A= =0A= =0A= Internet Draft D.Levi=0A= Expires February 2006 Nortel Networks=0A= draft-ietf-bridge-rstpmib-09.txt D.Harrington=0A= Effective Software=0A= August 2005=0A= =0A= Definitions of Managed Objects for Bridges=0A= with Rapid Spanning Tree Protocol=0A= =0A= Status of this Memo=0A= =0A= By submitting this Internet-Draft, each author represents that any=0A= applicable patent or other IPR claims of which he or she is aware=0A= have been or will be disclosed, and any of which he or she becomes=0A= aware will be disclosed, in accordance with Section 6 of BCP 79.=0A= =0A= =0A= Internet-Drafts are working documents of the Internet Engineering=0A= Task Force (IETF), its areas, and its working groups. Note that=0A= other groups may also distribute working documents as Internet-=0A= Drafts.=0A= =0A= Internet-Drafts are draft documents valid for a maximum of six months=0A= and may be updated, replaced, or obsoleted by other documents at any=0A= time. It is inappropriate to use Internet-Drafts as reference=0A= material or to cite them other than as "work in progress."=0A= =0A= The list of current Internet-Drafts can be accessed at=0A= http://www.ietf.org/ietf/1id-abstracts.txt.=0A= =0A= The list of Internet-Draft Shadow Directories can be accessed at=0A= http://www.ietf.org/shadow.html.=0A= =0A= Copyright Notice=0A= =0A= Copyright (C) The Internet Society (2005). All Rights Reserved.=0A= =0A= Abstract=0A= =0A= This memo defines an SMIv2 MIB module for managing the Rapid Spanning=0A= Tree capability defined by the IEEE P802.1t and P802.1w amendments to=0A= IEEE Std 802.1D-1998 for bridging between Local Area Network (LAN)=0A= segments. The objects in this MIB are defined to apply both to=0A= transparent bridging and to bridges connected by subnetworks other=0A= than LAN segments.=0A= =0A= =0A= =0A= =0A= =0A= =0A= Levi et. al Expires February 2006 [Page 1]=0A= =0C=0A= Internet Draft RSTP MIB August 2005=0A= =0A= =0A= Table of Contents=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Levi et. al Expires February 2006 [Page 2]=0A= =0C=0A= Internet Draft RSTP MIB August 2005=0A= =0A= =0A= 1. The Internet-Standard Management Framework=0A= =0A= For a detailed overview of the documents that describe the current=0A= Internet-Standard Management Framework, please refer to section 7 of=0A= RFC 3410 [RFC3410].=0A= =0A= Managed objects are accessed via a virtual information store, termed=0A= the Management Information Base or MIB. MIB objects are generally=0A= accessed through the Simple Network Management Protocol (SNMP).=0A= Objects in the MIB are defined using the mechanisms defined in the=0A= Structure of Management Information (SMI). This memo specifies a MIB=0A= module that is compliant to the SMIv2, which is described in STD 58,=0A= RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580=0A= [RFC2580].=0A= =0A= =0A= 2. Overview=0A= =0A= This memo defines an SMIv2 MIB module for managing the Rapid Spanning=0A= Tree (RSTP) capability defined by the IEEE P802.1t [802.1t] and=0A= P802.1w [802.1w] amendments to IEEE Std 802.1D-1998 [802.1D-1998] for=0A= bridging between Local Area Network (LAN) segments. The objects in=0A= this MIB are defined to apply both to transparent bridging and to=0A= bridges connected by subnetworks other than LAN segments.=0A= =0A= =0A= 3. Relationship to IEEE 802.1t and 802.1w amendments=0A= =0A= This document defines managed object for the Rapid Spanning Tree=0A= Protocol defined by the IEEE P802.1t and IEEE P802.1w amendments to=0A= 802.1D-1998.=0A= =0A= RSTP-MIB Name IEEE 802.1 Reference=0A= =0A= dot1dStp=0A= dot1dStpVersion (w) 17.16.1 ForceVersion=0A= dot1dStpTxHoldCount (w) 17.16.6 TxHoldCount=0A= dot1dStpExtPortTable=0A= dot1dStpPortProtocolMigration (w) 17.18.10 mcheck=0A= dot1dStpPortAdminEdgePort (t) 18.3.3 adminEdgePort=0A= dot1dStpPortOperEdgePort (t) 18.3.4 operEdgePort=0A= dot1dStpPortAdminPointToPoint (w) 6.4.3 adminPointToPointMAC=0A= dot1dStpPortOperPointToPoint (w) 6.4.3 operPointToPointMAC=0A= dot1dStpPortAdminPathCost (D) 8.5.5.3 Path Cost=0A= =0A= There are concerns that there may be changes made in the 802.1D-2004=0A= =0A= =0A= =0A= =0A= =0A= Levi et. al Expires February 2006 [Page 3]=0A= =0C=0A= Internet Draft RSTP MIB August 2005=0A= =0A= =0A= edition that would lead to non-backwards compatible SMI changes for=0A= 802.1t and 802.1w managed objects in the MIB modules. The Bridge MIB=0A= WG decided to 'freeze' the technical content of the MIB modules at a=0A= level that is compatible with the 802.1t and 802.1w versions, and=0A= leave to the IEEE 802.1 WG any updates beyond this.=0A= =0A= For informational purposes only, these are the references for the=0A= above objects in 802.1D-2004 [802.1D-2004].=0A= =0A= RSTP-MIB Name IEEE 802.1D-2004 Reference=0A= =0A= dot1dStp=0A= dot1dStpVersion 17.13.4 ForceVersion=0A= dot1dStpTxHoldCount 17.13.12 TxHoldCount=0A= dot1dStpExtPortTable=0A= dot1dStpPortProtocolMigration 17.19.13 mcheck=0A= dot1dStpPortAdminEdgePort 17.13.1 adminEdgePort=0A= dot1dStpPortOperEdgePort 17.19.17 operEdgePort=0A= dot1dStpPortAdminPointToPoint 6.4.3 adminPointToPointMAC=0A= dot1dStpPortOperPointToPoint 6.4.3 operPointToPointMAC=0A= dot1dStpPortAdminPathCost 17.13.11 Path Cost=0A= =0A= =0A= =0A= 4. Relation to the BRIDGE-MIB=0A= =0A= The objects in the RSTP-MIB supplement those defined in the Bridge=0A= MIB [RFC1493bis].=0A= =0A= The Original BRIDGE-MIB [RFC1493] has been updated in an=0A= SMIv2-compliant version [RFC1493bis]. Conformance statements have=0A= been added and some description and reference clauses have been=0A= updated. The interpretations of some objects were changed to=0A= accommodate IEEE 802.1t and 802.1w amendments.=0A= =0A= The object dot1dStpPortPathCost32 was added to support IEEE 802.1t,=0A= and the permissible values of dot1dStpPriority and=0A= dot1dStpPortPriority have been clarified for bridges supporting IEEE=0A= 802.1t or IEEE 802.1w. The interpretation of=0A= dot1dStpTimeSinceTopologyChange has been clarified for bridges=0A= supporting the RSTP.=0A= =0A= See the updated BRIDGE-MIB [RFC1493bis] for details.=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Levi et. al Expires February 2006 [Page 4]=0A= =0C=0A= Internet Draft RSTP MIB August 2005=0A= =0A= =0A= 5. Definitions for RSTP-MIB=0A= =0A= RSTP-MIB DEFINITIONS ::=3D BEGIN=0A= =0A= -- -------------------------------------------------------------=0A= -- MIB for IEEE 802.1w Rapid Spanning Tree Protocol=0A= -- -------------------------------------------------------------=0A= =0A= IMPORTS=0A= MODULE-IDENTITY, OBJECT-TYPE, Integer32, mib-2=0A= FROM SNMPv2-SMI=0A= TruthValue=0A= FROM SNMPv2-TC=0A= MODULE-COMPLIANCE, OBJECT-GROUP=0A= FROM SNMPv2-CONF=0A= dot1dStp, dot1dStpPortEntry=0A= FROM BRIDGE-MIB;=0A= =0A= rstpMIB MODULE-IDENTITY=0A= LAST-UPDATED "200507290000Z"=0A= ORGANIZATION "IETF Bridge MIB Working Group"=0A= CONTACT-INFO=0A= "Email: [email protected]"=0A= DESCRIPTION=0A= "The Bridge MIB Extension module for managing devices=0A= that support the Rapid Spanning Tree Protocol defined=0A= by IEEE 802.1w.=0A= =0A= Copyright (C) The Internet Society (2005). This version of=0A= this MIB module is part of RFC XXXX; See the RFC itself for=0A= full legal notices."=0A= -- RFC Ed.: replace XXXX with RFC number and remove this note=0A= =0A= REVISION "200507290000Z"=0A= DESCRIPTION=0A= "The initial version of this MIB module as published in=0A= RFC XXXX."=0A= -- RFC Ed.: replace XXXX with RFC number and remove this note=0A= =0A= =0A= ::=3D { mib-2 xxxx }=0A= -- RFC Ed.: replace xxxx with IANA-assigned number and=0A= -- remove this note=0A= =0A= -- ---------------------------------------------------------- --=0A= -- subtrees in the RSTP-MIB=0A= =0A= =0A= =0A= =0A= =0A= Levi et. al Expires February 2006 [Page 5]=0A= =0C=0A= Internet Draft RSTP MIB August 2005=0A= =0A= =0A= -- ---------------------------------------------------------- --=0A= =0A= rstpNotifications OBJECT IDENTIFIER ::=3D { rstpMIB 0 }=0A= rstpObjects OBJECT IDENTIFIER ::=3D { rstpMIB 1 }=0A= rstpConformance OBJECT IDENTIFIER ::=3D { rstpMIB 2 }=0A= =0A= -- -------------------------------------------------------------=0A= -- Addition to the dot1dStp group=0A= -- -------------------------------------------------------------=0A= =0A= dot1dStpVersion OBJECT-TYPE=0A= SYNTAX INTEGER {=0A= stpCompatible(0),=0A= rstp(2)=0A= }=0A= MAX-ACCESS read-write=0A= STATUS current=0A= DESCRIPTION=0A= "The version of Spanning Tree Protocol the bridge is=0A= currently running. The value 'stpCompatible(0)'=0A= indicates the Spanning Tree Protocol specified in=0A= IEEE 802.1D-1998 and 'rstp(2)' indicates the Rapid=0A= Spanning Tree Protocol specified in IEEE 802.1w and=0A= clause 17 of 802.1D-2004. The values are directly from=0A= the IEEE standard. New values may be defined as future=0A= versions of the protocol become available.=0A= =0A= The value of this object MUST be retained across=0A= reinitializations of the management system."=0A= REFERENCE=0A= "IEEE 802.1w clause 14.8.1, 17.12, 17.16.1"=0A= DEFVAL { rstp }=0A= ::=3D { dot1dStp 16 }=0A= =0A= dot1dStpTxHoldCount OBJECT-TYPE=0A= SYNTAX Integer32 (1..10)=0A= MAX-ACCESS read-write=0A= STATUS current=0A= DESCRIPTION=0A= "The value used by the Port Transmit state machine to limit=0A= the maximum transmission rate.=0A= =0A= The value of this object MUST be retained across=0A= reinitializations of the management system."=0A= =0A= REFERENCE=0A= =0A= =0A= =0A= =0A= =0A= Levi et. al Expires February 2006 [Page 6]=0A= =0C=0A= Internet Draft RSTP MIB August 2005=0A= =0A= =0A= "IEEE 802.1w clause 17.16.6"=0A= DEFVAL { 3 }=0A= ::=3D { dot1dStp 17 }=0A= =0A= --=0A= -- { dot1dStp 18 } was used to represent dot1dStpPathCostDefault=0A= -- in an internet-draft version of this MIB. It has since been=0A= -- obsoleted, and should not be used.=0A= --=0A= =0A= dot1dStpExtPortTable OBJECT-TYPE=0A= SYNTAX SEQUENCE OF Dot1dStpExtPortEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION=0A= "A table that contains port-specific Rapid Spanning Tree=0A= information."=0A= ::=3D { dot1dStp 19 }=0A= =0A= dot1dStpExtPortEntry OBJECT-TYPE=0A= SYNTAX Dot1dStpExtPortEntry=0A= MAX-ACCESS not-accessible=0A= STATUS current=0A= DESCRIPTION=0A= "A list of Rapid Spanning Tree information maintained by=0A= each port."=0A= AUGMENTS { dot1dStpPortEntry }=0A= ::=3D { dot1dStpExtPortTable 1 }=0A= =0A= Dot1dStpExtPortEntry ::=3D=0A= SEQUENCE {=0A= dot1dStpPortProtocolMigration=0A= TruthValue,=0A= dot1dStpPortAdminEdgePort=0A= TruthValue,=0A= dot1dStpPortOperEdgePort=0A= TruthValue,=0A= dot1dStpPortAdminPointToPoint=0A= INTEGER,=0A= dot1dStpPortOperPointToPoint=0A= TruthValue,=0A= dot1dStpPortAdminPathCost=0A= Integer32=0A= }=0A= =0A= dot1dStpPortProtocolMigration OBJECT-TYPE=0A= =0A= =0A= =0A= =0A= =0A= Levi et. al Expires February 2006 [Page 7]=0A= =0C=0A= Internet Draft RSTP MIB August 2005=0A= =0A= =0A= SYNTAX TruthValue=0A= MAX-ACCESS read-write=0A= STATUS current=0A= DESCRIPTION=0A= "When operating in RSTP (version 2) mode, writing true(1)=0A= to this object forces this port to transmit RSTP BPDUs.=0A= Any other operation on this object has no effect and=0A= it always returns false(2) when read."=0A= REFERENCE=0A= "IEEE 802.1w clause 14.8.2.4, 17.18.10, 17.26"=0A= ::=3D { dot1dStpExtPortEntry 1 }=0A= =0A= dot1dStpPortAdminEdgePort OBJECT-TYPE=0A= SYNTAX TruthValue=0A= MAX-ACCESS read-write=0A= STATUS current=0A= DESCRIPTION=0A= "The administrative value of the Edge Port parameter. A=0A= value of true(1) indicates that this port should be=0A= assumed as an edge-port and a value of false(2) indicates=0A= that this port should be assumed as a non-edge-port.=0A= Setting this object will also cause the corresponding=0A= instance of dot1dStpPortOperEdgePort to change to the=0A= same value. Note that even when this object's value=0A= is true, the value of the corresponding instance of=0A= dot1dStpPortOperEdgePort can be false if a BPDU has=0A= been received.=0A= =0A= The value of this object MUST be retained across=0A= reinitializations of the management system."=0A= =0A= REFERENCE=0A= "IEEE 802.1t clause 14.8.2, 18.3.3"=0A= ::=3D { dot1dStpExtPortEntry 2 }=0A= =0A= dot1dStpPortOperEdgePort OBJECT-TYPE=0A= SYNTAX TruthValue=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION=0A= "The operational value of the Edge Port parameter. The=0A= object is initialized to the value of the corresponding=0A= instance of dot1dStpPortAdminEdgePort. When the=0A= corresponding instance of dot1dStpPortAdminEdgePort is=0A= set, this object will be changed as well. This object=0A= will also be changed to false on reception of a BPDU."=0A= =0A= =0A= =0A= =0A= =0A= Levi et. al Expires February 2006 [Page 8]=0A= =0C=0A= Internet Draft RSTP MIB August 2005=0A= =0A= =0A= REFERENCE=0A= "IEEE 802.1t clause 14.8.2, 18.3.4"=0A= ::=3D { dot1dStpExtPortEntry 3 }=0A= =0A= dot1dStpPortAdminPointToPoint OBJECT-TYPE=0A= SYNTAX INTEGER {=0A= forceTrue(0),=0A= forceFalse(1),=0A= auto(2)=0A= }=0A= MAX-ACCESS read-write=0A= STATUS current=0A= DESCRIPTION=0A= "The administrative point-to-point status of the LAN segment=0A= attached to this port, using the enumeration values of the=0A= IEEE 802.1w clause. A value of forceTrue(0) indicates=0A= that this port should always be treated as if it is connected=0A= to a point-to-point link. A value of forceFalse(1) indicates=0A= that this port should be treated as having a shared media=0A= connection. A value of auto(2) indicates that this port is=0A= considered to have a point-to-point link if it is an Aggregator=0A= and all of its members are aggregatable, or if the MAC entity=0A= is configured for full duplex operation, either through=0A= auto-negotiation or by management means. Manipulating this=0A= object changes the underlying adminPortToPortMAC.=0A= =0A= The value of this object MUST be retained across=0A= reinitializations of the management system."=0A= =0A= REFERENCE=0A= "IEEE 802.1w clause 6.4.3, 6.5, 14.8.2"=0A= ::=3D { dot1dStpExtPortEntry 4 }=0A= =0A= dot1dStpPortOperPointToPoint OBJECT-TYPE=0A= SYNTAX TruthValue=0A= MAX-ACCESS read-only=0A= STATUS current=0A= DESCRIPTION=0A= "The operational point-to-point status of the LAN segment=0A= attached to this port. It indicates whether a port is=0A= considered to have a point-to-point connection or not.=0A= If adminPointToPointMAC is set to auto(2), then the value=0A= of operPointToPointMAC is determined in accordance with the=0A= specific procedures defined for the MAC entity concerned,=0A= as defined in IEEE 802.1w clause 6.5. The value is=0A= determined dynamically; i.e., it is re-evaluated whenever=0A= =0A= =0A= =0A= =0A= =0A= Levi et. al Expires February 2006 [Page 9]=0A= =0C=0A= Internet Draft RSTP MIB August 2005=0A= =0A= =0A= the value of adminPointToPointMAC changes, and whenever=0A= the specific procedures defined for the MAC entity evaluate=0A= a change in its point-to-point status."=0A= REFERENCE=0A= "IEEE 802.1w clause 6.4.3, 6.5, 14.8.2"=0A= ::=3D { dot1dStpExtPortEntry 5 }=0A= =0A= dot1dStpPortAdminPathCost OBJECT-TYPE=0A= SYNTAX Integer32 (0..200000000)=0A= MAX-ACCESS read-write=0A= STATUS current=0A= DESCRIPTION=0A= "The administratively assigned value for the contribution=0A= of this port to the path cost of paths towards the spanning=0A= tree root.=0A= =0A= Writing a value of '0' assigns the automatically calculated=0A= default Path Cost value to the port. If the default Path=0A= Cost is being used, this object returns '0' when read.=0A= =0A= This complements the object dot1dStpPortPathCost or=0A= dot1dStpPortPathCost32, which returns the operational value=0A= of the path cost.=0A= =0A= The value of this object MUST be retained across=0A= reinitializations of the management system."=0A= REFERENCE=0A= "IEEE 802.1D-1998: Section 8.5.5.3"=0A= ::=3D { dot1dStpExtPortEntry 6 }=0A= =0A= -- -------------------------------------------------------------=0A= -- rstpMIB - Conformance Information=0A= -- -------------------------------------------------------------=0A= =0A= rstpGroups OBJECT IDENTIFIER ::=3D { rstpConformance 1 }=0A= =0A= rstpCompliances OBJECT IDENTIFIER ::=3D { rstpConformance 2 }=0A= =0A= -- -------------------------------------------------------------=0A= -- Units of conformance=0A= -- -------------------------------------------------------------=0A= =0A= rstpBridgeGroup OBJECT-GROUP=0A= OBJECTS {=0A= dot1dStpVersion,=0A= dot1dStpTxHoldCount=0A= =0A= =0A= =0A= =0A= =0A= Levi et. al Expires February 2006 [Page 10]=0A= =0C=0A= Internet Draft RSTP MIB August 2005=0A= =0A= =0A= }=0A= STATUS current=0A= DESCRIPTION=0A= "Rapid Spanning Tree information for the bridge."=0A= ::=3D { rstpGroups 1 }=0A= =0A= rstpPortGroup OBJECT-GROUP=0A= OBJECTS {=0A= dot1dStpPortProtocolMigration,=0A= dot1dStpPortAdminEdgePort,=0A= dot1dStpPortOperEdgePort,=0A= dot1dStpPortAdminPointToPoint,=0A= dot1dStpPortOperPointToPoint,=0A= dot1dStpPortAdminPathCost=0A= }=0A= STATUS current=0A= DESCRIPTION=0A= "Rapid Spanning Tree information for individual ports."=0A= ::=3D { rstpGroups 2 }=0A= =0A= -- -------------------------------------------------------------=0A= -- Compliance statements=0A= -- -------------------------------------------------------------=0A= =0A= rstpCompliance MODULE-COMPLIANCE=0A= STATUS current=0A= DESCRIPTION=0A= "The compliance statement for device support of Rapid=0A= Spanning Tree Protocol (RSTP) bridging services."=0A= MODULE=0A= MANDATORY-GROUPS {=0A= rstpBridgeGroup,=0A= rstpPortGroup=0A= }=0A= ::=3D { rstpCompliances 1 }=0A= =0A= END=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Levi et. al Expires February 2006 [Page 11]=0A= =0C=0A= Internet Draft RSTP MIB August 2005=0A= =0A= =0A= 6. Acknowledgments=0A= =0A= This document was produced on behalf of the Bridge MIB Working Group=0A= in the Operations and Management area of the Internet Engineering=0A= Task Force.=0A= =0A= The authors wish to thank the members of the Bridge MIB Working=0A= Group, especially Alex Ruzin, for their comments and suggestions=0A= which improved this effort.=0A= =0A= Vivian Ngai and Les Bell were the initial authors of this document,=0A= and did the bulk of the development work for this document.=0A= =0A= =0A= 7. IANA Considerations=0A= =0A= This document requires an OID assignment to be made by IANA:=0A= =0A= Descriptor OBJECT IDENTIFIER value=0A= ---------- -----------------------=0A= rstpMIB { mib-2 xxxx }=0A= =0A= =0A= =0A= 8. Security Considerations=0A= =0A= There are a number of management objects defined in this MIB that=0A= have a MAX-ACCESS clause of read-write and/or read-create. Such=0A= objects may be considered sensitive or vulnerable in some network=0A= environments. The support for SET operations in a non-secure=0A= environment without proper protection can have a negative effect on=0A= network operations.=0A= =0A= Writable objects that could be misused to cause network delays and=0A= spanning tree instabilities include dot1dStpVersion,=0A= dot1dStpTxHoldCount, dot1dStpPortProtocolMigration,=0A= dot1dStpPortAdminEdgePort, and dot1dStpPortAdminPathCost.=0A= =0A= dot1dStpVersion could be read by an attacker to identify environments=0A= containing applications or protocols which are potentially sensitive=0A= to RSTP mode.=0A= =0A= dot1dStpPortAdminPointToPoint could be used to mislead an access=0A= control protocol, such as 802.1x, to believe that only one other=0A= system is attached to a LAN segment and to enable network access=0A= based on that assumption. This situation could permit potential man-=0A= =0A= =0A= =0A= =0A= =0A= Levi et. al Expires February 2006 [Page 12]=0A= =0C=0A= Internet Draft RSTP MIB August 2005=0A= =0A= =0A= in-the-middle attacks.=0A= =0A= SNMPv1 by itself is not a secure environment. Even if the network=0A= itself is secure (for example by using IPSec), even then, there is no=0A= control as to who on the secure network is allowed to access and=0A= GET/SET (read/change/create/delete) the objects in this MIB.=0A= =0A= It is RECOMMENDED that implementers consider the security features as=0A= provided by the SNMPv3 framework (see [RFC3410], section 8),=0A= including full support for the SNMPv3 cryptographic mechanisms (for=0A= authentication and privacy), and user-based access control.=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Levi et. al Expires February 2006 [Page 13]=0A= =0C=0A= Internet Draft RSTP MIB August 2005=0A= =0A= =0A= 9. Normative References=0A= =0A= [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,=0A= Rose, M., and S. Waldbusser, "Structure of Management=0A= Information Version 2 (SMIv2)", STD 58, RFC 2578, April=0A= 1999.=0A= =0A= [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,=0A= Rose, M., and S. Waldbusser, "Textual Conventions for=0A= SMIv2", STD 58, RFC 2579, April 1999.=0A= =0A= [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,=0A= Rose, M., and S. Waldbusser, "Conformance Statements for=0A= SMIv2", STD 58, RFC 2580, April 1999.=0A= =0A= [802.1D-1998] "Information technology - Telecommunications and=0A= information exchange between systems - Local and=0A= metropolitan area networks - Common specifications - Part=0A= 3: Media Access Control (MAC) Bridges: Revision. This is=0A= a revision of ISO/IEC 10038: 1993, 802.1j-1992 and=0A= 802.6k-1992. It incorporates P802.11c, P802.1p and=0A= P802.12e." ISO/IEC 15802-3: 1998.=0A= =0A= [RFC1493bis] Bell, E. and Norseth, K., "Definitions of Managed Objects=0A= for Bridges", draft-ietf-bridge-bridgemib-smiv2-10.txt,=0A= February 2005. NOTE TO RFC EDITOR: Replace the above ID=0A= reference with the appropriate RFC.=0A= =0A= [802.1t] IEEE 802.1t-2001, "(Amendment to IEEE Standard 802.1D) IEEE=0A= Standard for Information technology - Telecommunications=0A= and information exchange between systems - Local and=0A= metropolitan area networks - Common specifications - Part=0A= 3: Media Access Control (MAC) Bridges: Technical and=0A= Editorial Corrections".=0A= =0A= [802.1w] IEEE 802.1w-2001, "(Amendment to IEEE Standard 802.1D) IEEE=0A= Standard for Information technology--Telecommunications and=0A= information exchange between systems--Local and=0A= metropolitan area networks--Common Specifications--Part 3:=0A= Media Access Control (MAC) Bridges: Rapid Reconfiguation".=0A= =0A= =0A= 10. Informative References=0A= =0A= [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,=0A= "Introduction and Applicability Statements for Internet=0A= =0A= =0A= =0A= =0A= =0A= Levi et. al Expires February 2006 [Page 14]=0A= =0C=0A= Internet Draft RSTP MIB August 2005=0A= =0A= =0A= Standard Management Framework", RFC 3410, December 2002.=0A= =0A= [802.1D-2004] IEEE Project 802 Local and Metropolitan Area=0A= Networks, "IEEE Standard 802.1D-2004 MAC Bridges", 2004.=0A= =0A= [RFC1493] Decker, E., Langille, P., Rijsinghani, A. and K. McCloghrie,=0A= "Definitions of Managed Objects for Bridges", RFC 1493,=0A= July 1993.=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Levi et. al Expires February 2006 [Page 15]=0A= =0C=0A= Internet Draft RSTP MIB August 2005=0A= =0A= =0A= 11. Authors' Addresses=0A= =0A= David Levi=0A= Nortel Networks=0A= 4655 Great America Parkway=0A= Santa Clara, CA 95054=0A= USA=0A= =0A= Phone: +1 865 686 0432=0A= Email: [email protected]=0A= =0A= =0A= David Harrington=0A= Effective Software=0A= 50 Harding Rd.=0A= Portsmouth, NH 03801=0A= USA=0A= =0A= Phone: +1 603 436 8634=0A= Email: [email protected]=0A= =0A= =0A= =0A= Les Bell=0A= Hemel Hempstead=0A= Herts. HP2 7YU=0A= UK=0A= =0A= EMail: [email protected]=0A= =0A= =0A= Vivian Ngai=0A= Salt lake City, UT=0A= USA=0A= =0A= Email: [email protected]=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Levi et. al Expires February 2006 [Page 16]=0A= =0C=0A= Internet Draft RSTP MIB August 2005=0A= =0A= =0A= Intellectual Property Statement=0A= =0A= The IETF takes no position regarding the validity or scope of any=0A= Intellectual Property Rights or other rights that might be claimed to=0A= pertain to the implementation or use of the technology described in=0A= this document or the extent to which any license under such rights=0A= might or might not be available; nor does it represent that it has=0A= made any independent effort to identify any such rights. Information=0A= on the procedures with respect to rights in RFC documents can be=0A= found in BCP 78 and BCP 79.=0A= =0A= Copies of IPR disclosures made to the IETF Secretariat and any=0A= assurances of licenses to be made available, or the result of an=0A= attempt made to obtain a general license or permission for the use of=0A= such proprietary rights by implementers or users of this=0A= specification can be obtained from the IETF on-line IPR repository at=0A= http://www.ietf.org/ipr.=0A= =0A= The IETF invites any interested party to bring to its attention any=0A= copyrights, patents or patent applications, or other proprietary=0A= rights that may cover technology that may be required to implement=0A= this standard. Please address the information to the IETF at=0A= [email protected].=0A= =0A= =0A= Disclaimer of Validity=0A= =0A= This document and the information contained herein are provided=0A= on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE=0A= REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND=0A= THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,=0A= EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT=0A= THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR=0A= ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A=0A= PARTICULAR PURPOSE.=0A= =0A= =0A= Copyright Statement=0A= =0A= Copyright (C) The Internet Society (2005).=0A= =0A= This document is subject to the rights, licenses and restrictions=0A= contained in BCP 78, and except as set forth therein, the authors=0A= retain all their rights.=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Levi et. al Expires February 2006 [Page 17]=0A= =0C=0A= Internet Draft RSTP MIB August 2005=0A= =0A= =0A= Table of Contents=0A= =0A= =0A= 1 The Internet-Standard Management Framework ................... 3=0A= 2 Overview ..................................................... 3=0A= 3 Relationship to IEEE 802.1t and 802.1w amendments ............ 3=0A= 4 Relation to the BRIDGE-MIB ................................... 4=0A= 5 Definitions for RSTP-MIB ..................................... 5=0A= 6 Acknowledgments .............................................. 12=0A= 7 IANA Considerations .......................................... 12=0A= 8 Security Considerations ...................................... 12=0A= 9 Normative References ......................................... 14=0A= 10 Informative References ...................................... 14=0A= 11 Authors' Addresses .......................................... 16=0A= Intellectual Property Statement ............................... 17=0A= Disclaimer of Validity ........................................ 17=0A= Copyright Statement ........................................... 17=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Levi et. al Expires February 2006 [Page 18]=0A= =0C=0A= ------=_NextPart_000_007A_01C5A8E4.FE320CF0 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Bridge-mib mailing list [email protected] https://www1.ietf.org/mailman/listinfo/bridge-mib ------=_NextPart_000_007A_01C5A8E4.FE320CF0--