idnits 2.17.1 draft-ietf-bridge-rstpmib-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 3 instances of too long lines in the document, the longest one being 2 characters in excess of 72. ** The abstract seems to contain references ([RFC2578], [Q-BRIDGE-MIB], [BRIDGEMIB]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. 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 (June 2002) is 7976 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) == Missing Reference: 'Q-BRIDGE-MIB' is mentioned on line 48, but not defined == Missing Reference: 'BRIDGE-MIB' is mentioned on line 156, but not defined == Missing Reference: 'USM' is mentioned on line 557, but not defined == Missing Reference: 'VACM' is mentioned on line 558, but not defined == Unused Reference: 'RFC2674' is defined on line 623, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2674 (Obsoleted by RFC 4363) ** Obsolete normative reference: RFC 1493 (ref. 'BRIDGEMIB') (Obsoleted by RFC 4188) Summary: 19 errors (**), 0 flaws (~~), 8 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft V. Ngai 3 Expires November 2002 Enterasys Networks 4 draft-ietf-bridge-rstpmib-03.txt E. Bell 5 3Com Corp. 6 June 2002 8 Definitions of Managed Objects for Bridges 9 with Rapid Spanning Tree Protocol 11 Status of this Memo 13 This document is an Internet-Draft and is subject to all provisions 14 of Section 10 of RFC2026. Internet-Drafts are working documents of 15 the Internet Engineering Task Force (IETF), its areas, and its 16 working groups. Note that other groups may also distribute working 17 documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference 22 material or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/1id-abstracts.html 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html 30 Copyright Notice 32 Copyright (C) The Internet Society (2001). All Rights Reserved. 34 Abstract 36 This memo defines a portion of the Management Information Base (MIB) 37 for use with network management protocols in TCP/IP based internets. 38 In particular, it defines a MIB module for managing the Rapid 39 Spanning Tree capability defined by the IEEE P802.1t [802.1t] and 40 P802.1w [802.1w] amendments to IEEE Std 802.1D-1998 for bridging 41 between Local Area Network (LAN) segments. 43 Provisions are made for support of transparent bridging. Provisions 44 are also made so that these objects apply to bridges connected by 45 subnetworks other than LAN segments. This memo also includes a MIB 46 module in a manner that is compliant to SMIv2 [RFC2578]. 48 This memo supplements RFC 1493 [BRIDGEMIB] and RFC 2674 [Q-BRIDGE- 49 MIB]. 51 Table of Contents 53 1 The SNMP Management Framework ................................ 3 54 2 Overview ..................................................... 4 55 2.1 Scope ...................................................... 4 56 3 Structure of MIBs ............................................ 4 57 3.1 Structure of RSTP-MIB ...................................... 4 58 3.4 Relationship to Other MIBs ................................. 5 59 3.4.1 Relationship to Original Bridge MIB ...................... 5 60 3.4.1.1 The dot1dBase Group .................................... 5 61 3.4.1.2 The dot1dStp Group ..................................... 5 62 3.4.1.3 The dot1dTp Group ...................................... 6 63 3.4.1.4 The dot1dStatic Group .................................. 6 64 4 Definition for RSTP-MIB ...................................... 7 65 5 Acknowledgments .............................................. 13 66 6 Security consideration ....................................... 13 67 7 References ................................................... 14 68 8 Authors' Addresses ........................................... 16 69 9 Full Copyright ............................................... 17 71 1. The SNMP Management Framework 73 The SNMP Management Framework presently consists of five major 74 components: 76 o An overall architecture, described in RFC 2571 [RFC2571]. 78 o Mechanisms for describing and naming objects and events for the 79 purpose of management. The first version of this Structure of 80 Management Information (SMI) is called SMIv1 and described in 81 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 82 1215 [RFC1215]. The second version, called SMIv2, is described 83 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 84 STD 58, RFC 2580 [RFC2580]. 86 o Message protocols for transferring management information. The 87 first version of the SNMP message protocol is called SNMPv1 and 88 described in STD 15, RFC 1157 [RFC1157]. A second version of 89 the SNMP message protocol, which is not an Internet standards 90 track protocol, is called SNMPv2c and described in RFC 1901 91 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 92 message protocol is called SNMPv3 and described in RFC 1906 93 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 95 o Protocol operations for accessing management information. The 96 first set of protocol operations and associated PDU formats is 97 described in STD 15, RFC 1157 [RFC1157]. A second set of 98 protocol operations and associated PDU formats is described in 99 RFC 1905 [RFC1905]. 101 o A set of fundamental applications described in RFC 2573 102 [RFC2573] and the view-based access control mechanism described 103 in RFC 2575 [RFC2575]. 105 A more detailed introduction to the current SNMP Management Framework 106 can be found in RFC 2570 [RFC2570]. 108 Managed objects are accessed via a virtual information store, termed 109 the Management Information Base or MIB. Objects in the MIB are 110 defined using the mechanisms defined in the SMI. 112 This memo specifies a MIB module that is compliant to the SMIv2. A 113 MIB conforming to the SMIv1 can be produced through the appropriate 114 translations. The resulting translated MIB must be semantically 115 equivalent, except where objects or events are omitted because no 116 translation is possible (use of Counter64). Some machine readable 117 information in SMIv2 will be converted into textual descriptions in 118 SMIv1 during the translation process. However, this loss of machine 119 readable information is not considered to change the semantics of the 120 MIB. 122 2. Overview 124 A common device present in many networks is the Bridge. This device 125 is used to connect Local Area Network segments below the network 126 layer. These devices are often known as 'layer 2 switches'. 128 There are two major modes defined for this bridging: Source-Route and 129 transparent. Source-Route bridging is described by IEEE 802.5 130 [802.5] and is not discussed further in this document. 132 The transparent method of bridging is defined by IEEE 802.1D-1998 133 [802.1D] Managed objects for that original specification of 134 transparent bridging were defined in RFC 1493 [BRIDGEMIB]. 136 2.1. Scope 138 This MIB includes a comprehensive set of managed objects which 139 attempts to match the set defined in IEEE P802.1t [802.1t] and 140 P802.1w [802.1w]. 142 3. Structure of MIBs 144 This document defines additional managed objects for Rapid Spanning 145 Tree Protocol defined by IEEE P802.1t and IEEE P802.1w, on top of 146 those existing in the original BRIDGE-MIB module defined in 147 [BRIDGEMIB]: that MIB module is to be maintained unchanged for 148 backwards compatibility. Section 3.4.1 of the present document 149 contains some recommendations regarding usage of objects in the 150 original bridge MIB by devices implementing the enhancements defined 151 here. 153 3.1. Structure of RSTP-MIB 155 Objects in this MIB are defined as an addition to the dot1dStp group 156 in the original bridge MIB [BRIDGE-MIB]. The overall structure is 157 shown below: 159 Bridge MIB Name IEEE 802.1 Reference 161 dot1dStp 162 dot1dStpVersion (w) 17.16.1 ForceVersion 163 dot1dStpTxHoldCount (w) 17.16.6 TxHoldCount 164 dot1dStpPathCostDefault 165 dot1dStpExtPortTable 166 dot1dStpPortProtocolMigration (w) 17.18.10 mcheck 167 dot1dStpPortAdminEdgePort (t) 18.3.3 adminEdgePort 168 dot1dStpPortOperEdgePort (t) 18.3.4 operEdgePort 169 dot1dStpPortAdminPointToPoint (w) 6.4.3 adminPointToPointMAC 170 dot1dStpPortOperPointToPoint (w) 6.4.3 operPointToPointMAC 171 dot1dStpPortAdminPathCost (D) 8.5.5.3 Path Cost 173 3.4. Relationship to Other MIBs 175 As described above, some IEEE 802.1D management objects have not been 176 included in this MIB because they overlap with objects in other MIBs 177 applicable to a bridge implementing this MIB. In particular, it is 178 assumed that a bridge implementing this MIB will implement the 179 original bridge MIB [BRIDGEMIB]. 181 3.4.1. Relation to Original Bridge MIB 183 This section defines how objects in the original bridge MIB module 184 [BRIDGEMIB] should be represented for devices which implement all the 185 MIB modules described in this memo. Some of the old objects are less 186 useful in such devices but must still be implemented for reasons of 187 backwards compatibility. 189 3.4.1.1. The dot1dBase Group 191 This mandatory group contains the objects which are applicable to all 192 types of bridges. Interpretation of this group is unchanged. 194 3.4.1.2. The dot1dStp Group 196 This group contains the objects that denote the bridge's state with 197 respect to the Spanning Tree Protocol. If a node does not implement 198 the Spanning Tree Protocol, this group will not be implemented. 200 In a device supporting the Spanning Tree Algorithm and Protocol 201 defined in IEEE 802.1D-1998 Clause 8, interpretation of this group is 202 unchanged. 204 In a device supporting the Rapid Spanning Tree Algorithm and Protocol 205 defined in IEEE 802.1w Clause 17, the interpretation of objects in 206 this group is unchanged except for those listed below: 208 dot1dStpPriority 209 Definition remains unchanged, but the permissible values are 210 changed to 0-61440, in steps of 4096. 212 dot1dStpPortPriority 213 Definition remains unchanged, but the permissible values are 214 changed to 0-240, in steps of 16. 216 dot1dStpTimeSinceTopologyChange 217 The time since the tcWhile timer for any port on this Bridge was 218 non-zero. 220 dot1dStpTopChanges 221 The number of times that there have been at least one non-zero 222 tcWhile timer on this Bridge. 224 In a device supporting the 32-bit default Path Costs defined in IEEE 225 802.1t Table 8-5, the interpretation of objects in this group is 226 unchanged except for the following: 228 dot1dStpPortPathCost 229 Definition remains unchanged, but the permissible values are 230 extended to 1-200,000,000. 232 3.4.1.3. The dot1dTp Group 234 This group contains objects that describe the entity's state with 235 respect to transparent bridging. Interpretation for this group is 236 unchanged. 238 3.4.1.4. The dot1dStatic Group 240 This group contains objects that describe the entity's state with 241 respect to destination-address filtering. Interpretation for this 242 group is unchanged. 244 4. Definitions for RSTP-MIB 246 RSTP-MIB DEFINITIONS ::= BEGIN 248 -- ------------------------------------------------------------- 249 -- MIB for IEEE 802.1w Rapid Spanning Tree Protocol 250 -- ------------------------------------------------------------- 252 IMPORTS 253 MODULE-IDENTITY, OBJECT-TYPE 254 FROM SNMPv2-SMI 255 TruthValue 256 FROM SNMPv2-TC 257 MODULE-COMPLIANCE, OBJECT-GROUP 258 FROM SNMPv2-CONF 259 dot1dBridge, dot1dStp, dot1dStpPortEntry 260 FROM BRIDGE-MIB; 262 rstpMIB MODULE-IDENTITY 263 LAST-UPDATED "200206170000Z" 264 ORGANIZATION "IETF Bridge MIB Working Group" 265 CONTACT-INFO 266 "Email: Bridge-mib@ietf.org" 267 DESCRIPTION 268 "The Bridge MIB Extension module for managing devices 269 that support the Rapid Spanning Tree Protocol defined 270 by IEEE 802.1w." 271 REVISION "200206170000Z" 272 DESCRIPTION 273 "Draft 1" 274 ::= { dot1dBridge 11 } 276 -- ------------------------------------------------------------- 277 -- Addition to the dot1dStp group 278 -- ------------------------------------------------------------- 280 dot1dStpVersion OBJECT-TYPE 281 SYNTAX INTEGER { 282 stpCompatible(0), 283 rstp(2) 284 } 285 MAX-ACCESS read-write 286 STATUS current 287 DESCRIPTION 288 "The version of Spanning Tree Protocol the bridge is 289 currently running. The value 'stpCompatible(0)' 290 indicates the Spanning Tree Protocol specified in 291 IEEE 802.1D and 'rstp(2)' indicates the Rapid Spanning 292 Tree Protocol specified in IEEE 802.1w. New value may 293 be defined as future versions of the protocol become 294 available." 295 REFERENCE 296 "IEEE 802.1w clause 14.8.1, 17.12, 17.16.1" 297 DEFVAL { rstp } 298 ::= { dot1dStp 16 } 300 dot1dStpTxHoldCount OBJECT-TYPE 301 SYNTAX INTEGER (1..10) 302 MAX-ACCESS read-write 303 STATUS current 304 DESCRIPTION 305 "The value used by the Port Transmit state machine to limit 306 the maximum transmission rate." 307 REFERENCE 308 "IEEE 802.1w clause 17.16.6" 309 DEFVAL { 3 } 310 ::= { dot1dStp 17 } 312 dot1dStpPathCostDefault OBJECT-TYPE 313 SYNTAX INTEGER { 314 stp8021d1998(1), 315 stp8021t2001(2) 316 } 317 MAX-ACCESS read-write 318 STATUS current 319 DESCRIPTION 320 "The version of the Spanning Tree default Path Costs that 321 are to be used by this Bridge. A value of 8021d1998(1) 322 uses the 16-bit default Path Costs from IEEE Std. 802.1D-1998. 323 A value of stp8021t2001(2) uses the 32-bit default Path 324 Costs from IEEE Std. 802.1t." 325 REFERENCE 326 "IEEE 802.1D & 802.1t Table 8-5" 327 ::= { dot1dStp 18 } 329 dot1dStpExtPortTable OBJECT-TYPE 330 SYNTAX SEQUENCE OF Dot1dStpExtPortEntry 331 MAX-ACCESS not-accessible 332 STATUS current 333 DESCRIPTION 334 "A table that contains port-specific Rapid Spanning Tree 335 information." 336 ::= { dot1dStp 19 } 338 dot1dStpExtPortEntry OBJECT-TYPE 339 SYNTAX Dot1dStpExtPortEntry 340 MAX-ACCESS not-accessible 341 STATUS current 342 DESCRIPTION 343 "A list of Rapid Spanning Tree information maintained by 344 each port." 345 AUGMENTS { dot1dStpPortEntry } 346 ::= { dot1dStpExtPortTable 1 } 348 Dot1dStpExtPortEntry ::= 349 SEQUENCE { 350 dot1dStpPortProtocolMigration 351 TruthValue, 352 dot1dStpPortAdminEdgePort 353 TruthValue, 354 dot1dStpPortOperEdgePort 355 TruthValue, 356 dot1dStpPortAdminPointToPoint 357 INTEGER, 358 dot1dStpPortOperPointToPoint 359 TruthValue, 360 dot1dStpPortAdminPathCost 361 INTEGER 362 } 364 dot1dStpPortProtocolMigration OBJECT-TYPE 365 SYNTAX TruthValue 366 MAX-ACCESS read-write 367 STATUS current 368 DESCRIPTION 369 "When operating in RSTP (version 2) mode, writing TRUE(1) 370 to this object forces this port to transmit RSTP BPDUs. 371 Any other operation on this object has no effect and 372 it always returns FALSE(2) when read." 373 REFERENCE 374 "IEEE 802.1w clause 14.8.2.4, 17.18.10, 17.26" 375 ::= { dot1dStpExtPortEntry 1 } 377 dot1dStpPortAdminEdgePort OBJECT-TYPE 378 SYNTAX TruthValue 379 MAX-ACCESS read-write 380 STATUS current 381 DESCRIPTION 382 "The administrative value of the Edge Port parameter. A 383 value of TRUE(1) indicates that this port should be 384 assumed as an edge-port and a value of FALSE(2) indicates 385 that this port should be assumed as a non-edge-port." 386 REFERENCE 387 "IEEE 802.1t clause 14.8.2, 18.3.3" 389 ::= { dot1dStpExtPortEntry 2 } 391 dot1dStpPortOperEdgePort OBJECT-TYPE 392 SYNTAX TruthValue 393 MAX-ACCESS read-only 394 STATUS current 395 DESCRIPTION 396 "The operational value of the Edge Port parameter. The 397 object is initialized to the value of 398 dot1dStpPortAdminEdgePort and is set FALSE on reception of 399 a BPDU." 400 REFERENCE 401 "IEEE 802.1t clause 14.8.2, 18.3.4" 402 ::= { dot1dStpExtPortEntry 3 } 404 dot1dStpPortAdminPointToPoint OBJECT-TYPE 405 SYNTAX INTEGER { 406 forceTrue(0), 407 forceFalse(1), 408 auto(2) 409 } 410 MAX-ACCESS read-write 411 STATUS current 412 DESCRIPTION 413 "The administrative point-to-point status of the LAN segment 414 attached to this port. A value of forceTrue(0) indicates that 415 this port should always be treated as if it is connected to 416 a point-to-point link. A value of forceFalse(1) indicates 417 that this port should be treated as having a shared media 418 connection. A value of auto(2) indicates that this port is 419 considered to have a point-to-point link if it is an Aggregator 420 and all of its members are aggregatable, or if the MAC entity 421 is configured for full duplex operation, either through 422 auto-negotiation or by management means." 423 REFERENCE 424 "IEEE 802.1w clause 6.4.3, 6.5, 14.8.2" 425 ::= { dot1dStpExtPortEntry 4 } 427 dot1dStpPortOperPointToPoint OBJECT-TYPE 428 SYNTAX TruthValue 429 MAX-ACCESS read-only 430 STATUS current 431 DESCRIPTION 432 "The operational point-to-point status of the LAN segment 433 attached to this port. It indicates whether a port is 434 considered to have a point-to-point connection or not. 435 The value is determined by management or by auto-detection, 436 as described in the dot1dStpPortAdminPointToPoint object." 438 REFERENCE 439 "IEEE 802.1w clause 6.4.3, 6.5, 14.8.2" 440 ::= { dot1dStpExtPortEntry 5 } 442 dot1dStpPortAdminPathCost OBJECT-TYPE 443 SYNTAX INTEGER (0..65535) 444 MAX-ACCESS read-write 445 STATUS current 446 DESCRIPTION 447 "The administratively assigned value for the contribution 448 of this port to the path cost of paths towards the spanning 449 tree root. 451 Writing a value of '0' assigns the automatically calculated 452 default Path Cost value to the port. If the default Path 453 Cost is being used, this object returns '0' when read. 455 This complements the object dot1dStpPortPathCost, which 456 returns the operational value of the path cost." 457 REFERENCE 458 "IEEE 802.1D-1998: Section 8.5.5.3" 459 ::= { dot1dStpExtPortEntry 6 } 461 -- ------------------------------------------------------------- 462 -- rstpMIB - Conformance Information 463 -- ------------------------------------------------------------- 465 rstpConformance OBJECT IDENTIFIER ::= { rstpMIB 1 } 467 rstpGroups OBJECT IDENTIFIER ::= { rstpConformance 1 } 469 rstpCompliances OBJECT IDENTIFIER ::= { rstpConformance 2 } 471 -- ------------------------------------------------------------- 472 -- Units of conformance 473 -- ------------------------------------------------------------- 475 rstpBridgeGroup OBJECT-GROUP 476 OBJECTS { 477 dot1dStpVersion, 478 dot1dStpTxHoldCount 479 } 480 STATUS current 481 DESCRIPTION 482 "Rapid Spanning Tree information for the bridge." 483 ::= { rstpGroups 1 } 485 rstpDefaultPathCostGroup OBJECT-GROUP 486 OBJECTS { 487 dot1dStpPathCostDefault 488 } 489 STATUS current 490 DESCRIPTION 491 "Default Spanning Tree path cost information." 492 ::= { rstpGroups 2 } 494 rstpPortGroup OBJECT-GROUP 495 OBJECTS { 496 dot1dStpPortProtocolMigration, 497 dot1dStpPortAdminEdgePort, 498 dot1dStpPortOperEdgePort, 499 dot1dStpPortAdminPointToPoint, 500 dot1dStpPortOperPointToPoint, 501 dot1dStpPortAdminPathCost 502 } 503 STATUS current 504 DESCRIPTION 505 "Rapid Spanning Tree information for individual ports." 506 ::= { rstpGroups 3 } 508 -- ------------------------------------------------------------- 509 -- Compliance statements 510 -- ------------------------------------------------------------- 512 rstpCompliance MODULE-COMPLIANCE 513 STATUS current 514 DESCRIPTION 515 "The compliance statement for device support of bridging 516 services." 518 MODULE 519 MANDATORY-GROUPS { 520 rstpBridgeGroup, 521 rstpPortGroup 522 } 524 GROUP rstpDefaultPathCostGroup 525 DESCRIPTION 526 "Support for this group is mandatory only if 527 both 16-bit and 32-bit Path Costs are supported." 528 ::= { rstpCompliances 1 } 530 END 531 5. Acknowledgments 533 This document was produced on behalf of the Bridge MIB Working Group 534 in the Operations and Management area of the Internet Engineering 535 Task Force. 537 The authors wish to thank the members of the Bridge MIB Working 538 Group, especially Alex Ruzin, for their comments and suggestions 539 which improved this effort. 541 6. Security Considerations 543 There are a number of management objects defined in this MIB that 544 have a MAX-ACCESS clause of read-write and/or read-create. Such 545 objects may be considered sensitive or vulnerable in some network 546 environments. The support for SET operations in a non-secure 547 environment without proper protection can have a negative effect on 548 network operations. 550 SNMPv1 by itself is not a secure environment. Even if the network 551 itself is secure (for example by using IPSec), even then, there is no 552 control as to who on the secure network is allowed to access and 553 GET/SET (read/change/create/delete) the objects in this MIB. 555 It is recommended that the implementers consider the security 556 features as provided by the SNMPv3 framework. Specifically, the use 557 of the User-based Security Model [USM] and the View-based Access 558 Control Model [VACM] is recommended. 560 7. References 562 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, An Architecture 563 for Describing SNMP Management Frameworks, RFC 2571, April 564 1999. 566 [RFC1155] Rose, M., and K. McCloghrie, Structure and Identification 567 of Management Information for TCP/IP-based Internets, STD 568 16, RFC 1155, May 1990. 570 [RFC1212] Rose, M., and K. McCloghrie, Concise MIB Definitions, STD 571 16, RFC 1212, March 1991. 573 [RFC1215] M. Rose, A Convention for Defining Traps for use with the 574 SNMP, RFC 1215, March 1991. 576 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 577 Rose, M., and S. Waldbusser, Structure of Management 578 Information Version 2 (SMIv2), STD 58, RFC 2578, April 579 1999. 581 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 582 Rose, M., and S. Waldbusser, Textual Conventions for SMIv2, 583 STD 58, RFC 2579, April 1999. 585 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 586 Rose, M., and S. Waldbusser, Conformance Statements for 587 SMIv2, STD 58, RFC 2580, April 1999. 589 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, Simple 590 Network Management Protocol, STD 15, RFC 1157, May 1990. 592 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 593 Introduction to Community-based SNMPv2, RFC 1901, January 594 1996. 596 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 597 Transport Mappings for Version 2 of the Simple Network 598 Management Protocol (SNMPv2), RFC 1906, January 1996. 600 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, Message 601 Processing and Dispatching for the Simple Network 602 Management Protocol (SNMP), RFC 2572, April 1999. 604 [RFC2574] Blumenthal, U., and B. Wijnen, User-based Security Model 605 (USM) for version 3 of the Simple Network Management 606 Protocol (SNMPv3), RFC 2574, April 1999. 608 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 609 Protocol Operations for Version 2 of the Simple Network 610 Management Protocol (SNMPv2), RFC 1905, January 1996. 612 [RFC2573] Levi, D., Meyer, P., and B. Stewart, SNMPv3 Applications, 613 RFC 2573, April 1999. 615 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, View-based 616 Access Control Model (VACM) for the Simple Network 617 Management Protocol (SNMP), RFC 2575, April 1999. 619 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 620 Introduction to Version 3 of the Internet-standard Network 621 Management Framework, RFC 2570, April 1999. 623 [RFC2674] Bell, E., Smith, A., Langille, P., Rijhsinghani, A. and 624 McCloghrie, "Definitions of Managed Objects for Bridges 625 with Traffic Classes, Multicast Filtering and Virtual LAN 626 Extensions", RFC 2674, August 1999. 628 [802.1D] "Information technology - Telecommunications and 629 information exchange between systems - Local and 630 metropolitan area networks - Common specifications - Part 631 3: Media Access Control (MAC) Bridges: Revision. This is 632 a revision of ISO/IEC 10038: 1993, 802.1j-1992 and 802.6k- 633 1992. It incorporates P802.11c, P802.1p and P802.12e." 634 ISO/IEC 15802-3: 1998. 636 [BRIDGEMIB] Decker, E., Langille, P., Rijsinghani, A. and K. 637 McCloghrie, "Definitions of Managed Objects for Bridges", 638 RFC 1493, July 1993. 640 [802.1t] IEEE 802.1t-2001, "(Amendment to IEEE Standard 802.1D) IEEE 641 Standard for Information technology - Telecommunications 642 and information exchange between systems - Local and 643 metropolitan area networks - Common specifications - Part 644 3: Media Access Control (MAC) Bridges: Technical and 645 Editorial Corrections". 647 [802.1w] IEEE 802.1w-2001, "(Amendment to IEEE Standard 802.1D) IEEE 648 Standard for Information technology--Telecommunications and 649 information exchange between systems--Local and 650 metropolitan area networks--Common Specifications--Part 3: 651 Media Access Control (MAC) Bridges: Rapid Reconfiguation". 653 9. Authors' Addresses 655 Les Bell 656 3Com Europe Limited 657 eCom Centre, Boundary Way 658 Hemel Hempstead 659 Herts. HP2 7YU 660 UK 662 Phone: +44 1442 438025 663 Email: Les_Bell@3Com.com 665 Vivian Ngai 666 Enterasys Networks 667 2691 South Decker Lake Lane 668 Salt Lake City, UT 84119 669 USA 671 Phone: +1 801-887-9802 672 Fax: +1 801-972-5789 673 Email: vngai@enterasys.com 675 9. Full Copyright 677 Copyright (C) The Internet Society (date). All Rights Reserved. 679 This document and translations of it may be copied and furnished 680 to others, and derivative works that comment on or otherwise 681 explain it or assist in its implementation may be prepared, copied, 682 published and distributed, in whole or in part, without 683 restriction of any kind, provided that the above copyright notice 684 and this paragraph are included on all such copies and derivative 685 works. However, this document itself may not be modified in any 686 way, such as by removing the copyright notice or references to the 687 Internet Society or other Internet organizations, except as needed 688 for the purpose of developing Internet standards in which case the 689 procedures for copyrights defined in the Internet Standards 690 process must be followed, or as required to translate it into 691 languages other than English. 693 The limited permissions granted above are perpetual and will not 694 be revoked by the Internet Society or its successors or assigns. 696 This document and the information contained herein is provided on 697 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 698 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 699 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 700 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 701 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.