idnits 2.17.1 draft-ietf-bridge-rstpmib-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 18. -- Found old boilerplate from RFC 3978, Section 5.5 on line 615. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 591. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 598. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 604. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 38), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 38. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 213: '...e of this object MUST be retained acro...' RFC 2119 keyword, line 228: '...e of this object MUST be retained acro...' RFC 2119 keyword, line 307: '...e of this object MUST be retained acro...' RFC 2119 keyword, line 351: '...e of this object MUST be retained acro...' RFC 2119 keyword, line 395: '...e of this object MUST be retained acro...' (1 more instance...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 2005) is 6829 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 1493 (Obsoleted by RFC 4188) Summary: 6 errors (**), 0 flaws (~~), 3 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft RSTP MIB August 2005 4 Internet Draft V. Ngai 5 Expires February 2006 Enterasys Networks 6 draft-ietf-bridge-rstpmib-08.txt E. Bell 7 3Com Corp. 8 August 2005 10 Definitions of Managed Objects for Bridges 11 with Rapid Spanning Tree Protocol 13 Status of this Memo 15 By submitting this Internet-Draft, each author represents that any 16 applicable patent or other IPR claims of which he or she is aware 17 have been or will be disclosed, and any of which he or she becomes 18 aware will be disclosed, in accordance with Section 6 of BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 Copyright Notice 38 Copyright (C) The Internet Society (2005). All Rights Reserved. 40 Abstract 42 This memo defines an SMIv2 MIB module for managing the Rapid Spanning 43 Tree capability defined by the IEEE P802.1t and P802.1w amendments to 44 IEEE Std 802.1D-1998 for bridging between Local Area Network (LAN) 45 segments. The objects in this MIB are defined to apply both to 46 transparent bridging and to bridges connected by subnetworks other 47 than LAN segments. 49 Table of Contents 51 1 The Internet-Standard Management Framework ................... 3 52 2 Overview ..................................................... 3 53 3 Relationship to IEEE 802.1t and 802.1w amendments ............ 3 54 4 Relation to the BRIDGE-MIB ................................... 4 55 5 Definitions for RSTP-MIB ..................................... 5 56 6 Acknowledgments .............................................. 12 57 7 IANA Considerations .......................................... 12 58 8 Security Considerations ...................................... 12 59 9 Normative References ......................................... 14 60 10 Informative References ...................................... 15 61 11 Authors' Addresses .......................................... 16 62 Intellectual Property Statement ............................... 17 63 Disclaimer of Validity ........................................ 17 64 Copyright Statement ........................................... 17 66 1. The Internet-Standard Management Framework 68 For a detailed overview of the documents that describe the current 69 Internet-Standard Management Framework, please refer to section 7 of 70 RFC 3410 [RFC3410]. 72 Managed objects are accessed via a virtual information store, termed 73 the Management Information Base or MIB. MIB objects are generally 74 accessed through the Simple Network Management Protocol (SNMP). 75 Objects in the MIB are defined using the mechanisms defined in the 76 Structure of Management Information (SMI). This memo specifies a MIB 77 module that is compliant to the SMIv2, which is described in STD 58, 78 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 79 [RFC2580]. 81 2. Overview 83 This memo defines an SMIv2 MIB module for managing the Rapid Spanning 84 Tree (RSTP) capability defined by the IEEE P802.1t [802.1t] and 85 P802.1w [802.1w] amendments to IEEE Std 802.1D-1998 [802.1D-1998] for 86 bridging between Local Area Network (LAN) segments. The objects in 87 this MIB are defined to apply both to transparent bridging and to 88 bridges connected by subnetworks other than LAN segments. 90 3. Relationship to IEEE 802.1t and 802.1w amendments 92 This document defines managed object for the Rapid Spanning Tree 93 Protocol defined by the IEEE P802.1t and IEEE P802.1w amendments to 94 802.1d-1998. 96 RSTP-MIB Name IEEE 802.1 Reference 98 dot1dStp 99 dot1dStpVersion (w) 17.16.1 ForceVersion 100 dot1dStpTxHoldCount (w) 17.16.6 TxHoldCount 101 dot1dStpExtPortTable 102 dot1dStpPortProtocolMigration (w) 17.18.10 mcheck 103 dot1dStpPortAdminEdgePort (t) 18.3.3 adminEdgePort 104 dot1dStpPortOperEdgePort (t) 18.3.4 operEdgePort 105 dot1dStpPortAdminPointToPoint (w) 6.4.3 adminPointToPointMAC 106 dot1dStpPortOperPointToPoint (w) 6.4.3 operPointToPointMAC 107 dot1dStpPortAdminPathCost (D) 8.5.5.3 Path Cost 109 Following are the references for the above objects in 802.1D-2004 111 [802.1D-2004]. 113 RSTP-MIB Name IEEE 802.1D-2004 Reference 115 dot1dStp 116 dot1dStpVersion 17.13.4 ForceVersion 117 dot1dStpTxHoldCount 17.13.12 TxHoldCount 118 dot1dStpExtPortTable 119 dot1dStpPortProtocolMigration 17.19.13 mcheck 120 dot1dStpPortAdminEdgePort 17.13.1 adminEdgePort 121 dot1dStpPortOperEdgePort 17.19.17 operEdgePort 122 dot1dStpPortAdminPointToPoint 6.4.3 adminPointToPointMAC 123 dot1dStpPortOperPointToPoint 6.4.3 operPointToPointMAC 124 dot1dStpPortAdminPathCost 17.13.11 Path Cost 126 4. Relation to the BRIDGE-MIB 128 The Original BRIDGE-MIB [RFC1493] has been updated in an 129 SMIv2-compliant version [RFC1493bis]. Conformance statements have 130 been added and some description and reference clauses have been 131 updated. The interpretations of some objects were changed to 132 accommodate IEEE 802.1t and 802.1w amendments. 134 The object dot1dStpPortPathCost32 was added to support IEEE 802.1t, 135 and the permissible values of dot1dStpPriority and 136 dot1dStpPortPriority have been clarified for bridges supporting IEEE 137 802.1t or IEEE 802.1w. The interpretation of 138 dot1dStpTimeSinceTopologyChange has been clarified for bridges 139 supporting the RSTP. 141 See the updated BRIDGE-MIB [RFC1493bis] for details. 143 The objects in the RSTP-MIB supplement those defined in the Bridge 144 MIB [RFC1493bis]. 146 5. Definitions for RSTP-MIB 148 RSTP-MIB DEFINITIONS ::= BEGIN 150 -- ------------------------------------------------------------- 151 -- MIB for IEEE 802.1w Rapid Spanning Tree Protocol 152 -- ------------------------------------------------------------- 154 IMPORTS 155 MODULE-IDENTITY, OBJECT-TYPE, Integer32, mib-2 156 FROM SNMPv2-SMI 157 TruthValue 158 FROM SNMPv2-TC 159 MODULE-COMPLIANCE, OBJECT-GROUP 160 FROM SNMPv2-CONF 161 dot1dStp, dot1dStpPortEntry 162 FROM BRIDGE-MIB; 164 rstpMIB MODULE-IDENTITY 165 LAST-UPDATED "200507290000Z" 166 ORGANIZATION "IETF Bridge MIB Working Group" 167 CONTACT-INFO 168 "Email: Bridge-mib@ietf.org" 169 DESCRIPTION 170 "The Bridge MIB Extension module for managing devices 171 that support the Rapid Spanning Tree Protocol defined 172 by IEEE 802.1w." 173 REVISION "200507290000Z" 174 -- RFC Ed.: replace XXXX with RFC number and remove this note 175 DESCRIPTION 176 "Copyright (C) The Internet Society (2005). The initial 177 version of this MIB module was published in RFC XXXX; for full 178 legal notices see the RFC itself. Supplementary information 179 may be available at: 180 http://www.ietf.org/copyrights/ianamib.html." 181 -- RFC Ed.: replace xxxx with IANA-assigned number and 182 -- remove this note 183 ::= { mib-2 xxxx } 185 -- ---------------------------------------------------------- -- 186 -- subtrees in the RSTP-MIB 187 -- ---------------------------------------------------------- -- 189 rstpNotifications OBJECT IDENTIFIER ::= { rstpMIB 0 } 190 rstpObjects OBJECT IDENTIFIER ::= { rstpMIB 1 } 191 rstpConformance OBJECT IDENTIFIER ::= { rstpMIB 2 } 192 -- ------------------------------------------------------------- 193 -- Addition to the dot1dStp group 194 -- ------------------------------------------------------------- 196 dot1dStpVersion OBJECT-TYPE 197 SYNTAX INTEGER { 198 stpCompatible(0), 199 rstp(2) 200 } 201 MAX-ACCESS read-write 202 STATUS current 203 DESCRIPTION 204 "The version of Spanning Tree Protocol the bridge is 205 currently running. The value 'stpCompatible(0)' 206 indicates the Spanning Tree Protocol specified in 207 IEEE 802.1D-1998 and 'rstp(2)' indicates the Rapid 208 Spanning Tree Protocol specified in IEEE 802.1w and 209 clause 17 of 802.1D-2004. The values are directly from 210 the IEEE standard. New values may be defined as future 211 versions of the protocol become available. 213 The value of this object MUST be retained across 214 reinitializations of the management system." 215 REFERENCE 216 "IEEE 802.1w clause 14.8.1, 17.12, 17.16.1" 217 DEFVAL { rstp } 218 ::= { dot1dStp 16 } 220 dot1dStpTxHoldCount OBJECT-TYPE 221 SYNTAX Integer32 (1..10) 222 MAX-ACCESS read-write 223 STATUS current 224 DESCRIPTION 225 "The value used by the Port Transmit state machine to limit 226 the maximum transmission rate. 228 The value of this object MUST be retained across 229 reinitializations of the management system." 231 REFERENCE 232 "IEEE 802.1w clause 17.16.6" 233 DEFVAL { 3 } 234 ::= { dot1dStp 17 } 236 -- 237 -- { dot1dStp 18 } was used to represent dot1dStpPathCostDefault 238 -- in an internet-draft version of this MIB. It has since been 239 -- obsoleted, and should not be used. 240 -- 242 dot1dStpExtPortTable OBJECT-TYPE 243 SYNTAX SEQUENCE OF Dot1dStpExtPortEntry 244 MAX-ACCESS not-accessible 245 STATUS current 246 DESCRIPTION 247 "A table that contains port-specific Rapid Spanning Tree 248 information." 249 ::= { dot1dStp 19 } 251 dot1dStpExtPortEntry OBJECT-TYPE 252 SYNTAX Dot1dStpExtPortEntry 253 MAX-ACCESS not-accessible 254 STATUS current 255 DESCRIPTION 256 "A list of Rapid Spanning Tree information maintained by 257 each port." 258 AUGMENTS { dot1dStpPortEntry } 259 ::= { dot1dStpExtPortTable 1 } 261 Dot1dStpExtPortEntry ::= 262 SEQUENCE { 263 dot1dStpPortProtocolMigration 264 TruthValue, 265 dot1dStpPortAdminEdgePort 266 TruthValue, 267 dot1dStpPortOperEdgePort 268 TruthValue, 269 dot1dStpPortAdminPointToPoint 270 INTEGER, 271 dot1dStpPortOperPointToPoint 272 TruthValue, 273 dot1dStpPortAdminPathCost 274 Integer32 275 } 277 dot1dStpPortProtocolMigration OBJECT-TYPE 278 SYNTAX TruthValue 279 MAX-ACCESS read-write 280 STATUS current 281 DESCRIPTION 282 "When operating in RSTP (version 2) mode, writing true(1) 283 to this object forces this port to transmit RSTP BPDUs. 285 Any other operation on this object has no effect and 286 it always returns false(2) when read." 287 REFERENCE 288 "IEEE 802.1w clause 14.8.2.4, 17.18.10, 17.26" 289 ::= { dot1dStpExtPortEntry 1 } 291 dot1dStpPortAdminEdgePort OBJECT-TYPE 292 SYNTAX TruthValue 293 MAX-ACCESS read-write 294 STATUS current 295 DESCRIPTION 296 "The administrative value of the Edge Port parameter. A 297 value of true(1) indicates that this port should be 298 assumed as an edge-port and a value of false(2) indicates 299 that this port should be assumed as a non-edge-port. 300 Setting this object will also cause the corresponding 301 instance of dot1dStpPortOperEdgePort to change to the 302 same value. Note that even when this object's value 303 is true, the value of the corresponding instance of 304 dot1dStpPortOperEdgePort can be false if a BPDU has 305 been received. 307 The value of this object MUST be retained across 308 reinitializations of the management system." 310 REFERENCE 311 "IEEE 802.1t clause 14.8.2, 18.3.3" 312 ::= { dot1dStpExtPortEntry 2 } 314 dot1dStpPortOperEdgePort OBJECT-TYPE 315 SYNTAX TruthValue 316 MAX-ACCESS read-only 317 STATUS current 318 DESCRIPTION 319 "The operational value of the Edge Port parameter. The 320 object is initialized to the value of the corresponding 321 instance of dot1dStpPortAdminEdgePort. When the 322 corresponding instance of dot1dStpPortAdminEdgePort is 323 set, this object will be changed as well. This object 324 will also be changed to false on reception of a BPDU." 325 REFERENCE 326 "IEEE 802.1t clause 14.8.2, 18.3.4" 327 ::= { dot1dStpExtPortEntry 3 } 329 dot1dStpPortAdminPointToPoint OBJECT-TYPE 330 SYNTAX INTEGER { 331 forceTrue(0), 332 forceFalse(1), 333 auto(2) 334 } 335 MAX-ACCESS read-write 336 STATUS current 337 DESCRIPTION 338 "The administrative point-to-point status of the LAN segment 339 attached to this port, using the enumeration values of the 340 IEEE 802.1w clause. A value of forceTrue(0) indicates 341 that this port should always be treated as if it is connected 342 to a point-to-point link. A value of forceFalse(1) indicates 343 that this port should be treated as having a shared media 344 connection. A value of auto(2) indicates that this port is 345 considered to have a point-to-point link if it is an Aggregator 346 and all of its members are aggregatable, or if the MAC entity 347 is configured for full duplex operation, either through 348 auto-negotiation or by management means. Manipulating this 349 object changes the underlying adminPortToPortMAC. 351 The value of this object MUST be retained across 352 reinitializations of the management system." 354 REFERENCE 355 "IEEE 802.1w clause 6.4.3, 6.5, 14.8.2" 356 ::= { dot1dStpExtPortEntry 4 } 358 dot1dStpPortOperPointToPoint OBJECT-TYPE 359 SYNTAX TruthValue 360 MAX-ACCESS read-only 361 STATUS current 362 DESCRIPTION 363 "The operational point-to-point status of the LAN segment 364 attached to this port. It indicates whether a port is 365 considered to have a point-to-point connection or not. 366 If adminPointToPointMAC is set to auto(2), then the value 367 of operPointToPointMAC is determined in accordance with the 368 specific procedures defined for the MAC entity concerned, 369 as defined in IEEE 802.1w clause 6.5. The value is 370 determined dynamically; i.e., it is re-evaluated whenever 371 the value of adminPointToPointMAC changes, and whenever 372 the specific procedures defined for the MAC entity evaluate 373 a change in its point-to-point status." 374 REFERENCE 375 "IEEE 802.1w clause 6.4.3, 6.5, 14.8.2" 376 ::= { dot1dStpExtPortEntry 5 } 378 dot1dStpPortAdminPathCost OBJECT-TYPE 379 SYNTAX Integer32 (0..200000000) 380 MAX-ACCESS read-write 381 STATUS current 382 DESCRIPTION 383 "The administratively assigned value for the contribution 384 of this port to the path cost of paths towards the spanning 385 tree root. 387 Writing a value of '0' assigns the automatically calculated 388 default Path Cost value to the port. If the default Path 389 Cost is being used, this object returns '0' when read. 391 This complements the object dot1dStpPortPathCost or 392 dot1dStpPortPathCost32, which returns the operational value 393 of the path cost. 395 The value of this object MUST be retained across 396 reinitializations of the management system." 397 REFERENCE 398 "IEEE 802.1D-1998: Section 8.5.5.3" 399 ::= { dot1dStpExtPortEntry 6 } 401 -- ------------------------------------------------------------- 402 -- rstpMIB - Conformance Information 403 -- ------------------------------------------------------------- 405 rstpGroups OBJECT IDENTIFIER ::= { rstpConformance 1 } 407 rstpCompliances OBJECT IDENTIFIER ::= { rstpConformance 2 } 409 -- ------------------------------------------------------------- 410 -- Units of conformance 411 -- ------------------------------------------------------------- 413 rstpBridgeGroup OBJECT-GROUP 414 OBJECTS { 415 dot1dStpVersion, 416 dot1dStpTxHoldCount 417 } 418 STATUS current 419 DESCRIPTION 420 "Rapid Spanning Tree information for the bridge." 421 ::= { rstpGroups 1 } 423 rstpPortGroup OBJECT-GROUP 424 OBJECTS { 425 dot1dStpPortProtocolMigration, 426 dot1dStpPortAdminEdgePort, 427 dot1dStpPortOperEdgePort, 428 dot1dStpPortAdminPointToPoint, 429 dot1dStpPortOperPointToPoint, 430 dot1dStpPortAdminPathCost 431 } 432 STATUS current 433 DESCRIPTION 434 "Rapid Spanning Tree information for individual ports." 435 ::= { rstpGroups 2 } 437 -- ------------------------------------------------------------- 438 -- Compliance statements 439 -- ------------------------------------------------------------- 441 rstpCompliance MODULE-COMPLIANCE 442 STATUS current 443 DESCRIPTION 444 "The compliance statement for device support of Rapid 445 Spanning Tree Protocol (RSTP) bridging services." 446 MODULE 447 MANDATORY-GROUPS { 448 rstpBridgeGroup, 449 rstpPortGroup 450 } 451 ::= { rstpCompliances 1 } 453 END 454 6. Acknowledgments 456 This document was produced on behalf of the Bridge MIB Working Group 457 in the Operations and Management area of the Internet Engineering 458 Task Force. 460 The authors wish to thank the members of the Bridge MIB Working 461 Group, especially Alex Ruzin, for their comments and suggestions 462 which improved this effort. 464 7. IANA Considerations 466 This document requires an OID assignment to be made by IANA: 468 Descriptor OBJECT IDENTIFIER value 469 ---------- ----------------------- 470 rstpMIB { mib-2 xxxx } 472 8. Security Considerations 474 There are a number of management objects defined in this MIB that 475 have a MAX-ACCESS clause of read-write and/or read-create. Such 476 objects may be considered sensitive or vulnerable in some network 477 environments. The support for SET operations in a non-secure 478 environment without proper protection can have a negative effect on 479 network operations. 481 Writable objects that could be misused to cause network delays and 482 spanning tree instabilities include dot1dStpVersion, 483 dot1dStpTxHoldCount, dot1dStpPortProtocolMigration, 484 dot1dStpPortAdminEdgePort, and dot1dStpPortAdminPathCost. 486 dot1dStpVersion could be read by an attacker to identify environments 487 containing applications or protocols which are potentially sensitive 488 to RSTP mode. 490 dot1dStpPortAdminPointToPoint could be used to mislead an access 491 control protocol, such as 802.1x, to believe that only one other 492 system is attached to a LAN segment and to enable network access 493 based on that assumption. This situation could permit potential man- 494 in-the-middle attacks. 496 SNMPv1 by itself is not a secure environment. Even if the network 497 itself is secure (for example by using IPSec), even then, there is no 498 control as to who on the secure network is allowed to access and 499 GET/SET (read/change/create/delete) the objects in this MIB. 501 It is RECOMMENDED that implementers consider the security features as 502 provided by the SNMPv3 framework (see [RFC3410], section 8), 503 including full support for the SNMPv3 cryptographic mechanisms (for 504 authentication and privacy), and user-based access control. 506 9. Normative References 508 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 509 Rose, M., and S. Waldbusser, "Structure of Management 510 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 511 1999. 513 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 514 Rose, M., and S. Waldbusser, "Textual Conventions for 515 SMIv2", STD 58, RFC 2579, April 1999. 517 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 518 Rose, M., and S. Waldbusser, "Conformance Statements for 519 SMIv2", STD 58, RFC 2580, April 1999. 521 [802.1D-1998] "Information technology - Telecommunications and 522 information exchange between systems - Local and 523 metropolitan area networks - Common specifications - Part 524 3: Media Access Control (MAC) Bridges: Revision. This is 525 a revision of ISO/IEC 10038: 1993, 802.1j-1992 and 526 802.6k-1992. It incorporates P802.11c, P802.1p and 527 P802.12e." ISO/IEC 15802-3: 1998. 529 [802.1D-2004] IEEE Project 802 Local and Metropolitan Area 530 Networks, "IEEE Standard 802.1D-2004 MAC Bridges", 2004. 532 [RFC1493] Decker, E., Langille, P., Rijsinghani, A. and K. McCloghrie, 533 "Definitions of Managed Objects for Bridges", RFC 1493, 534 July 1993. 536 [RFC1493bis] Bell, E. and Norseth, K., "Definitions of Managed Objects 537 for Bridges", draft-ietf-bridge-bridgemib-smiv2-10.txt, 538 February 2005. NOTE TO RFC EDITOR: Replace the above ID 539 reference with the appropriate RFC. 541 [802.1t] IEEE 802.1t-2001, "(Amendment to IEEE Standard 802.1D) IEEE 542 Standard for Information technology - Telecommunications 543 and information exchange between systems - Local and 544 metropolitan area networks - Common specifications - Part 545 3: Media Access Control (MAC) Bridges: Technical and 546 Editorial Corrections". 548 [802.1w] IEEE 802.1w-2001, "(Amendment to IEEE Standard 802.1D) IEEE 549 Standard for Information technology--Telecommunications and 550 information exchange between systems--Local and 551 metropolitan area networks--Common Specifications--Part 3: 553 Media Access Control (MAC) Bridges: Rapid Reconfiguation". 555 10. Informative References 557 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 558 "Introduction and Applicability Statements for Internet 559 Standard Management Framework", RFC 3410, December 2002. 561 11. Authors' Addresses 563 Les Bell 564 3Com Europe Limited 565 eCom Centre, Boundary Way 566 Hemel Hempstead 567 Herts. HP2 7YU 568 UK 570 Phone: +44 1442 438025 571 Email: Les_Bell@3Com.com 573 Vivian Ngai 574 Enterasys Networks 575 2691 South Decker Lake Lane 576 Salt Lake City, UT 84119 577 USA 579 Phone: +1 801 556 5652 580 Email: vivian_ngai@acm.org 582 Intellectual Property Statement 584 The IETF takes no position regarding the validity or scope of any 585 Intellectual Property Rights or other rights that might be claimed to 586 pertain to the implementation or use of the technology described in 587 this document or the extent to which any license under such rights 588 might or might not be available; nor does it represent that it has 589 made any independent effort to identify any such rights. Information 590 on the procedures with respect to rights in RFC documents can be 591 found in BCP 78 and BCP 79. 593 Copies of IPR disclosures made to the IETF Secretariat and any 594 assurances of licenses to be made available, or the result of an 595 attempt made to obtain a general license or permission for the use of 596 such proprietary rights by implementers or users of this 597 specification can be obtained from the IETF on-line IPR repository at 598 http://www.ietf.org/ipr. 600 The IETF invites any interested party to bring to its attention any 601 copyrights, patents or patent applications, or other proprietary 602 rights that may cover technology that may be required to implement 603 this standard. Please address the information to the IETF at 604 ietf-ipr@ietf.org. 606 Disclaimer of Validity 608 This document and the information contained herein are provided 609 on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 610 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND 611 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, 612 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT 613 THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 614 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 615 PARTICULAR PURPOSE. 617 Copyright Statement 619 Copyright (C) The Internet Society (2005). 621 This document is subject to the rights, licenses and restrictions 622 contained in BCP 78, and except as set forth therein, the authors 623 retain all their rights.