idnits 2.17.1 draft-ietf-bridge-rstpmib-04.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 (March 2004) is 7340 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 157, but not defined == Missing Reference: 'USM' is mentioned on line 559, but not defined == Missing Reference: 'VACM' is mentioned on line 560, but not defined == Unused Reference: 'RFC2674' is defined on line 625, 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 August 2004 Enterasys Networks 4 draft-ietf-bridge-rstpmib-04.txt E. Bell 5 3Com Corp. 6 March 2004 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 (2004). 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 Intellectual Property ........................................ 17 70 10 Full Copyright .............................................. 18 72 1. The SNMP Management Framework 74 The SNMP Management Framework presently consists of five major 75 components: 77 o An overall architecture, described in RFC 2571 [RFC2571]. 79 o Mechanisms for describing and naming objects and events for the 80 purpose of management. The first version of this Structure of 81 Management Information (SMI) is called SMIv1 and described in 82 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 83 1215 [RFC1215]. The second version, called SMIv2, is described 84 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 85 STD 58, RFC 2580 [RFC2580]. 87 o Message protocols for transferring management information. The 88 first version of the SNMP message protocol is called SNMPv1 and 89 described in STD 15, RFC 1157 [RFC1157]. A second version of 90 the SNMP message protocol, which is not an Internet standards 91 track protocol, is called SNMPv2c and described in RFC 1901 92 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 93 message protocol is called SNMPv3 and described in RFC 1906 94 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 96 o Protocol operations for accessing management information. The 97 first set of protocol operations and associated PDU formats is 98 described in STD 15, RFC 1157 [RFC1157]. A second set of 99 protocol operations and associated PDU formats is described in 100 RFC 1905 [RFC1905]. 102 o A set of fundamental applications described in RFC 2573 103 [RFC2573] and the view-based access control mechanism described 104 in RFC 2575 [RFC2575]. 106 A more detailed introduction to the current SNMP Management Framework 107 can be found in RFC 2570 [RFC2570]. 109 Managed objects are accessed via a virtual information store, termed 110 the Management Information Base or MIB. Objects in the MIB are 111 defined using the mechanisms defined in the SMI. 113 This memo specifies a MIB module that is compliant to the SMIv2. A 114 MIB conforming to the SMIv1 can be produced through the appropriate 115 translations. The resulting translated MIB must be semantically 116 equivalent, except where objects or events are omitted because no 117 translation is possible (use of Counter64). Some machine readable 118 information in SMIv2 will be converted into textual descriptions in 119 SMIv1 during the translation process. However, this loss of machine 120 readable information is not considered to change the semantics of the 121 MIB. 123 2. Overview 125 A common device present in many networks is the Bridge. This device 126 is used to connect Local Area Network segments below the network 127 layer. These devices are often known as 'layer 2 switches'. 129 There are two major modes defined for this bridging: Source-Route and 130 transparent. Source-Route bridging is described by IEEE 802.5 131 [802.5] and is not discussed further in this document. 133 The transparent method of bridging is defined by IEEE 802.1D-1998 134 [802.1D] Managed objects for that original specification of 135 transparent bridging were defined in RFC 1493 [BRIDGEMIB]. 137 2.1. Scope 139 This MIB includes a comprehensive set of managed objects which 140 attempts to match the set defined in IEEE P802.1t [802.1t] and 141 P802.1w [802.1w]. 143 3. Structure of MIBs 145 This document defines additional managed objects for Rapid Spanning 146 Tree Protocol defined by IEEE P802.1t and IEEE P802.1w, on top of 147 those existing in the original BRIDGE-MIB module defined in 148 [BRIDGEMIB]: that MIB module is to be maintained unchanged for 149 backwards compatibility. Section 3.4.1 of the present document 150 contains some recommendations regarding usage of objects in the 151 original bridge MIB by devices implementing the enhancements defined 152 here. 154 3.1. Structure of RSTP-MIB 156 Objects in this MIB are defined as an addition to the dot1dStp group 157 in the original bridge MIB [BRIDGE-MIB]. The overall structure is 158 shown below: 160 Bridge MIB Name IEEE 802.1 Reference 162 dot1dStp 163 dot1dStpVersion (w) 17.16.1 ForceVersion 164 dot1dStpTxHoldCount (w) 17.16.6 TxHoldCount 165 dot1dStpPathCostDefault 166 dot1dStpExtPortTable 167 dot1dStpPortProtocolMigration (w) 17.18.10 mcheck 168 dot1dStpPortAdminEdgePort (t) 18.3.3 adminEdgePort 169 dot1dStpPortOperEdgePort (t) 18.3.4 operEdgePort 170 dot1dStpPortAdminPointToPoint (w) 6.4.3 adminPointToPointMAC 171 dot1dStpPortOperPointToPoint (w) 6.4.3 operPointToPointMAC 172 dot1dStpPortAdminPathCost (D) 8.5.5.3 Path Cost 174 3.4. Relationship to Other MIBs 176 As described above, some IEEE 802.1D management objects have not been 177 included in this MIB because they overlap with objects in other MIBs 178 applicable to a bridge implementing this MIB. In particular, it is 179 assumed that a bridge implementing this MIB will implement the 180 original bridge MIB [BRIDGEMIB]. 182 3.4.1. Relation to Original Bridge MIB 184 This section defines how objects in the original bridge MIB module 185 [BRIDGEMIB] should be represented for devices which implement all the 186 MIB modules described in this memo. Some of the old objects are less 187 useful in such devices but must still be implemented for reasons of 188 backwards compatibility. 190 3.4.1.1. The dot1dBase Group 192 This mandatory group contains the objects which are applicable to all 193 types of bridges. Interpretation of this group is unchanged. 195 3.4.1.2. The dot1dStp Group 197 This group contains the objects that denote the bridge's state with 198 respect to the Spanning Tree Protocol. If a node does not implement 199 the Spanning Tree Protocol, this group will not be implemented. 201 In a device supporting the Spanning Tree Algorithm and Protocol 202 defined in IEEE 802.1D-1998 Clause 8, interpretation of this group is 203 unchanged. 205 In a device supporting the Rapid Spanning Tree Algorithm and Protocol 206 defined in IEEE 802.1w Clause 17, the interpretation of objects in 207 this group is unchanged except for those listed below: 209 dot1dStpPriority 210 Definition remains unchanged, but the permissible values are 211 changed to 0-61440, in steps of 4096. 213 dot1dStpPortPriority 214 Definition remains unchanged, but the permissible values are 215 changed to 0-240, in steps of 16. 217 dot1dStpTimeSinceTopologyChange 218 The time since the tcWhile timer for any port on this Bridge was 219 non-zero. 221 dot1dStpTopChanges 222 The number of times that there have been at least one non-zero 223 tcWhile timer on this Bridge. 225 In a device supporting the 32-bit default Path Costs defined in IEEE 226 802.1t Table 8-5, the interpretation of objects in this group is 227 unchanged except for the following: 229 dot1dStpPortPathCost 230 Definition remains unchanged, but the permissible values are 231 extended to 1-200,000,000. 233 3.4.1.3. The dot1dTp Group 235 This group contains objects that describe the entity's state with 236 respect to transparent bridging. Interpretation for this group is 237 unchanged. 239 3.4.1.4. The dot1dStatic Group 241 This group contains objects that describe the entity's state with 242 respect to destination-address filtering. Interpretation for this 243 group is unchanged. 245 4. Definitions for RSTP-MIB 247 RSTP-MIB DEFINITIONS ::= BEGIN 249 -- ------------------------------------------------------------- 250 -- MIB for IEEE 802.1w Rapid Spanning Tree Protocol 251 -- ------------------------------------------------------------- 253 IMPORTS 254 MODULE-IDENTITY, OBJECT-TYPE, Integer32 255 FROM SNMPv2-SMI 256 TruthValue 257 FROM SNMPv2-TC 258 MODULE-COMPLIANCE, OBJECT-GROUP 259 FROM SNMPv2-CONF 260 dot1dBridge, dot1dStp, dot1dStpPortEntry 261 FROM BRIDGE-MIB; 263 rstpMIB MODULE-IDENTITY 264 LAST-UPDATED "200403210000Z" 265 ORGANIZATION "IETF Bridge MIB Working Group" 266 CONTACT-INFO 267 "Email: Bridge-mib@ietf.org" 268 DESCRIPTION 269 "The Bridge MIB Extension module for managing devices 270 that support the Rapid Spanning Tree Protocol defined 271 by IEEE 802.1w." 272 REVISION "200403210000Z" 273 DESCRIPTION 274 "Draft 4" 275 ::= { dot1dBridge 11 } 277 -- ------------------------------------------------------------- 278 -- Addition to the dot1dStp group 279 -- ------------------------------------------------------------- 281 dot1dStpVersion OBJECT-TYPE 282 SYNTAX INTEGER { 283 stpCompatible(0), 284 rstp(2) 285 } 286 MAX-ACCESS read-write 287 STATUS current 288 DESCRIPTION 289 "The version of Spanning Tree Protocol the bridge is 290 currently running. The value 'stpCompatible(0)' 291 indicates the Spanning Tree Protocol specified in 292 IEEE 802.1D and 'rstp(2)' indicates the Rapid Spanning 293 Tree Protocol specified in IEEE 802.1w. New value may 294 be defined as future versions of the protocol become 295 available." 296 REFERENCE 297 "IEEE 802.1w clause 14.8.1, 17.12, 17.16.1" 298 DEFVAL { rstp } 299 ::= { dot1dStp 16 } 301 dot1dStpTxHoldCount OBJECT-TYPE 302 SYNTAX Integer32 (1..10) 303 MAX-ACCESS read-write 304 STATUS current 305 DESCRIPTION 306 "The value used by the Port Transmit state machine to limit 307 the maximum transmission rate." 308 REFERENCE 309 "IEEE 802.1w clause 17.16.6" 310 DEFVAL { 3 } 311 ::= { dot1dStp 17 } 313 dot1dStpPathCostDefault OBJECT-TYPE 314 SYNTAX INTEGER { 315 stp8021d1998(1), 316 stp8021t2001(2) 317 } 318 MAX-ACCESS read-write 319 STATUS current 320 DESCRIPTION 321 "The version of the Spanning Tree default Path Costs that 322 are to be used by this Bridge. A value of 8021d1998(1) 323 uses the 16-bit default Path Costs from IEEE Std. 802.1D-1998. 324 A value of stp8021t2001(2) uses the 32-bit default Path 325 Costs from IEEE Std. 802.1t." 326 REFERENCE 327 "IEEE 802.1D & 802.1t Table 8-5" 328 ::= { dot1dStp 18 } 330 dot1dStpExtPortTable OBJECT-TYPE 331 SYNTAX SEQUENCE OF Dot1dStpExtPortEntry 332 MAX-ACCESS not-accessible 333 STATUS current 334 DESCRIPTION 335 "A table that contains port-specific Rapid Spanning Tree 336 information." 337 ::= { dot1dStp 19 } 339 dot1dStpExtPortEntry OBJECT-TYPE 340 SYNTAX Dot1dStpExtPortEntry 341 MAX-ACCESS not-accessible 342 STATUS current 343 DESCRIPTION 344 "A list of Rapid Spanning Tree information maintained by 345 each port." 346 AUGMENTS { dot1dStpPortEntry } 347 ::= { dot1dStpExtPortTable 1 } 349 Dot1dStpExtPortEntry ::= 350 SEQUENCE { 351 dot1dStpPortProtocolMigration 352 TruthValue, 353 dot1dStpPortAdminEdgePort 354 TruthValue, 355 dot1dStpPortOperEdgePort 356 TruthValue, 357 dot1dStpPortAdminPointToPoint 358 INTEGER, 359 dot1dStpPortOperPointToPoint 360 TruthValue, 361 dot1dStpPortAdminPathCost 362 Integer32 363 } 365 dot1dStpPortProtocolMigration OBJECT-TYPE 366 SYNTAX TruthValue 367 MAX-ACCESS read-write 368 STATUS current 369 DESCRIPTION 370 "When operating in RSTP (version 2) mode, writing TRUE(1) 371 to this object forces this port to transmit RSTP BPDUs. 372 Any other operation on this object has no effect and 373 it always returns FALSE(2) when read." 374 REFERENCE 375 "IEEE 802.1w clause 14.8.2.4, 17.18.10, 17.26" 376 ::= { dot1dStpExtPortEntry 1 } 378 dot1dStpPortAdminEdgePort OBJECT-TYPE 379 SYNTAX TruthValue 380 MAX-ACCESS read-write 381 STATUS current 382 DESCRIPTION 383 "The administrative value of the Edge Port parameter. A 384 value of TRUE(1) indicates that this port should be 385 assumed as an edge-port and a value of FALSE(2) indicates 386 that this port should be assumed as a non-edge-port." 387 REFERENCE 388 "IEEE 802.1t clause 14.8.2, 18.3.3" 390 ::= { dot1dStpExtPortEntry 2 } 392 dot1dStpPortOperEdgePort OBJECT-TYPE 393 SYNTAX TruthValue 394 MAX-ACCESS read-only 395 STATUS current 396 DESCRIPTION 397 "The operational value of the Edge Port parameter. The 398 object is initialized to the value of 399 dot1dStpPortAdminEdgePort and is set FALSE on reception of 400 a BPDU." 401 REFERENCE 402 "IEEE 802.1t clause 14.8.2, 18.3.4" 403 ::= { dot1dStpExtPortEntry 3 } 405 dot1dStpPortAdminPointToPoint OBJECT-TYPE 406 SYNTAX INTEGER { 407 forceTrue(0), 408 forceFalse(1), 409 auto(2) 410 } 411 MAX-ACCESS read-write 412 STATUS current 413 DESCRIPTION 414 "The administrative point-to-point status of the LAN segment 415 attached to this port. A value of forceTrue(0) indicates that 416 this port should always be treated as if it is connected to 417 a point-to-point link. A value of forceFalse(1) indicates 418 that this port should be treated as having a shared media 419 connection. A value of auto(2) indicates that this port is 420 considered to have a point-to-point link if it is an Aggregator 421 and all of its members are aggregatable, or if the MAC entity 422 is configured for full duplex operation, either through 423 auto-negotiation or by management means." 424 REFERENCE 425 "IEEE 802.1w clause 6.4.3, 6.5, 14.8.2" 426 ::= { dot1dStpExtPortEntry 4 } 428 dot1dStpPortOperPointToPoint OBJECT-TYPE 429 SYNTAX TruthValue 430 MAX-ACCESS read-only 431 STATUS current 432 DESCRIPTION 433 "The operational point-to-point status of the LAN segment 434 attached to this port. It indicates whether a port is 435 considered to have a point-to-point connection or not. 436 The value is determined by management or by auto-detection, 437 as described in the dot1dStpPortAdminPointToPoint object." 439 REFERENCE 440 "IEEE 802.1w clause 6.4.3, 6.5, 14.8.2" 441 ::= { dot1dStpExtPortEntry 5 } 443 dot1dStpPortAdminPathCost OBJECT-TYPE 444 SYNTAX Integer32 (0..200000000) 445 MAX-ACCESS read-write 446 STATUS current 447 DESCRIPTION 448 "The administratively assigned value for the contribution 449 of this port to the path cost of paths towards the spanning 450 tree root. 452 Writing a value of '0' assigns the automatically calculated 453 default Path Cost value to the port. If the default Path 454 Cost is being used, this object returns '0' when read. 456 This complements the object dot1dStpPortPathCost or 457 dot1dStpPortPathCost32, which returns the operational value 458 of the path cost." 459 REFERENCE 460 "IEEE 802.1D-1998: Section 8.5.5.3" 461 ::= { dot1dStpExtPortEntry 6 } 463 -- ------------------------------------------------------------- 464 -- rstpMIB - Conformance Information 465 -- ------------------------------------------------------------- 467 rstpConformance OBJECT IDENTIFIER ::= { rstpMIB 1 } 469 rstpGroups OBJECT IDENTIFIER ::= { rstpConformance 1 } 471 rstpCompliances OBJECT IDENTIFIER ::= { rstpConformance 2 } 473 -- ------------------------------------------------------------- 474 -- Units of conformance 475 -- ------------------------------------------------------------- 477 rstpBridgeGroup OBJECT-GROUP 478 OBJECTS { 479 dot1dStpVersion, 480 dot1dStpTxHoldCount 481 } 482 STATUS current 483 DESCRIPTION 484 "Rapid Spanning Tree information for the bridge." 485 ::= { rstpGroups 1 } 487 rstpDefaultPathCostGroup OBJECT-GROUP 488 OBJECTS { 489 dot1dStpPathCostDefault 490 } 491 STATUS current 492 DESCRIPTION 493 "Default Spanning Tree path cost information." 494 ::= { rstpGroups 2 } 496 rstpPortGroup OBJECT-GROUP 497 OBJECTS { 498 dot1dStpPortProtocolMigration, 499 dot1dStpPortAdminEdgePort, 500 dot1dStpPortOperEdgePort, 501 dot1dStpPortAdminPointToPoint, 502 dot1dStpPortOperPointToPoint, 503 dot1dStpPortAdminPathCost 504 } 505 STATUS current 506 DESCRIPTION 507 "Rapid Spanning Tree information for individual ports." 508 ::= { rstpGroups 3 } 510 -- ------------------------------------------------------------- 511 -- Compliance statements 512 -- ------------------------------------------------------------- 514 rstpCompliance MODULE-COMPLIANCE 515 STATUS current 516 DESCRIPTION 517 "The compliance statement for device support of bridging 518 services." 520 MODULE 521 MANDATORY-GROUPS { 522 rstpBridgeGroup, 523 rstpPortGroup 524 } 526 GROUP rstpDefaultPathCostGroup 527 DESCRIPTION 528 "Support for this group is mandatory only if 529 both 16-bit and 32-bit Path Costs are supported." 530 ::= { rstpCompliances 1 } 532 END 533 5. Acknowledgments 535 This document was produced on behalf of the Bridge MIB Working Group 536 in the Operations and Management area of the Internet Engineering 537 Task Force. 539 The authors wish to thank the members of the Bridge MIB Working 540 Group, especially Alex Ruzin, for their comments and suggestions 541 which improved this effort. 543 6. Security Considerations 545 There are a number of management objects defined in this MIB that 546 have a MAX-ACCESS clause of read-write and/or read-create. Such 547 objects may be considered sensitive or vulnerable in some network 548 environments. The support for SET operations in a non-secure 549 environment without proper protection can have a negative effect on 550 network operations. 552 SNMPv1 by itself is not a secure environment. Even if the network 553 itself is secure (for example by using IPSec), even then, there is no 554 control as to who on the secure network is allowed to access and 555 GET/SET (read/change/create/delete) the objects in this MIB. 557 It is recommended that the implementers consider the security 558 features as provided by the SNMPv3 framework. Specifically, the use 559 of the User-based Security Model [USM] and the View-based Access 560 Control Model [VACM] is recommended. 562 7. References 564 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, An Architecture 565 for Describing SNMP Management Frameworks, RFC 2571, April 566 1999. 568 [RFC1155] Rose, M., and K. McCloghrie, Structure and Identification 569 of Management Information for TCP/IP-based Internets, STD 570 16, RFC 1155, May 1990. 572 [RFC1212] Rose, M., and K. McCloghrie, Concise MIB Definitions, STD 573 16, RFC 1212, March 1991. 575 [RFC1215] M. Rose, A Convention for Defining Traps for use with the 576 SNMP, RFC 1215, March 1991. 578 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 579 Rose, M., and S. Waldbusser, Structure of Management 580 Information Version 2 (SMIv2), STD 58, RFC 2578, April 581 1999. 583 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 584 Rose, M., and S. Waldbusser, Textual Conventions for SMIv2, 585 STD 58, RFC 2579, April 1999. 587 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 588 Rose, M., and S. Waldbusser, Conformance Statements for 589 SMIv2, STD 58, RFC 2580, April 1999. 591 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, Simple 592 Network Management Protocol, STD 15, RFC 1157, May 1990. 594 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 595 Introduction to Community-based SNMPv2, RFC 1901, January 596 1996. 598 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 599 Transport Mappings for Version 2 of the Simple Network 600 Management Protocol (SNMPv2), RFC 1906, January 1996. 602 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, Message 603 Processing and Dispatching for the Simple Network 604 Management Protocol (SNMP), RFC 2572, April 1999. 606 [RFC2574] Blumenthal, U., and B. Wijnen, User-based Security Model 607 (USM) for version 3 of the Simple Network Management 608 Protocol (SNMPv3), RFC 2574, April 1999. 610 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 611 Protocol Operations for Version 2 of the Simple Network 612 Management Protocol (SNMPv2), RFC 1905, January 1996. 614 [RFC2573] Levi, D., Meyer, P., and B. Stewart, SNMPv3 Applications, 615 RFC 2573, April 1999. 617 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, View-based 618 Access Control Model (VACM) for the Simple Network 619 Management Protocol (SNMP), RFC 2575, April 1999. 621 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 622 Introduction to Version 3 of the Internet-standard Network 623 Management Framework, RFC 2570, April 1999. 625 [RFC2674] Bell, E., Smith, A., Langille, P., Rijhsinghani, A. and 626 McCloghrie, "Definitions of Managed Objects for Bridges 627 with Traffic Classes, Multicast Filtering and Virtual LAN 628 Extensions", RFC 2674, August 1999. 630 [802.1D] "Information technology - Telecommunications and 631 information exchange between systems - Local and 632 metropolitan area networks - Common specifications - Part 633 3: Media Access Control (MAC) Bridges: Revision. This is 634 a revision of ISO/IEC 10038: 1993, 802.1j-1992 and 802.6k- 635 1992. It incorporates P802.11c, P802.1p and P802.12e." 636 ISO/IEC 15802-3: 1998. 638 [BRIDGEMIB] Decker, E., Langille, P., Rijsinghani, A. and K. 639 McCloghrie, "Definitions of Managed Objects for Bridges", 640 RFC 1493, July 1993. 642 [802.1t] IEEE 802.1t-2001, "(Amendment to IEEE Standard 802.1D) IEEE 643 Standard for Information technology - Telecommunications 644 and information exchange between systems - Local and 645 metropolitan area networks - Common specifications - Part 646 3: Media Access Control (MAC) Bridges: Technical and 647 Editorial Corrections". 649 [802.1w] IEEE 802.1w-2001, "(Amendment to IEEE Standard 802.1D) IEEE 650 Standard for Information technology--Telecommunications and 651 information exchange between systems--Local and 652 metropolitan area networks--Common Specifications--Part 3: 653 Media Access Control (MAC) Bridges: Rapid Reconfiguation". 655 9. Authors' Addresses 657 Les Bell 658 3Com Europe Limited 659 eCom Centre, Boundary Way 660 Hemel Hempstead 661 Herts. HP2 7YU 662 UK 664 Phone: +44 1442 438025 665 Email: Les_Bell@3Com.com 667 Vivian Ngai 668 Enterasys Networks 669 2691 South Decker Lake Lane 670 Salt Lake City, UT 84119 671 USA 673 Phone: +1 801 556 5652 674 Email: vivian_ngai@acm.org 676 9. Intellectual Property 678 The IETF takes no position regarding the validity or scope of any 679 intellectual property or other rights that might be claimed to 680 pertain to the implementation or use of the technology described in 681 this document or the extent to which any license under such rights 682 might or might not be available; neither does it represent that it 683 has made any effort to identify any such rights. Information on the 684 IETF's procedures with respect to rights in standards-track and 685 standards-related documentation can be found in BCP-11. Copies of 686 claims of rights made available for publication and any assurances of 687 licenses to be made available, or the result of an attempt made to 688 obtain a general license or permission for the use of such 689 proprietary rights by implementors or users of this specification can 690 be obtained from the IETF Secretariat. 692 The IETF invites any interested party to bring to its attention any 693 copyrights, patents or patent applications, or other proprietary 694 rights which may cover technology that may be required to practice 695 this standard. Please address the information to the IETF Executive 696 Director. 698 10. Full Copyright 700 Copyright (C) The Internet Society (2004). All Rights Reserved. 702 This document and translations of it may be copied and furnished 703 to others, and derivative works that comment on or otherwise 704 explain it or assist in its implementation may be prepared, copied, 705 published and distributed, in whole or in part, without 706 restriction of any kind, provided that the above copyright notice 707 and this paragraph are included on all such copies and derivative 708 works. However, this document itself may not be modified in any 709 way, such as by removing the copyright notice or references to the 710 Internet Society or other Internet organizations, except as needed 711 for the purpose of developing Internet standards in which case the 712 procedures for copyrights defined in the Internet Standards 713 process must be followed, or as required to translate it into 714 languages other than English. 716 The limited permissions granted above are perpetual and will not 717 be revoked by the Internet Society or its successors or assigns. 719 This document and the information contained herein is provided on 720 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 721 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 722 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 723 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 724 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.