idnits 2.17.1 draft-ietf-eos-snmpxproto-mib-00.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: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 110 has weird spacing: '...cted to imple...' == Line 424 has weird spacing: '...for the purpo...' -- 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.) -- Couldn't find a document date in the document -- date freshness check skipped. 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: 'RFC 2571' is mentioned on line 110, but not defined ** Obsolete undefined reference: RFC 2571 (Obsoleted by RFC 3411) == Missing Reference: 'RFC2262' is mentioned on line 156, but not defined ** Obsolete undefined reference: RFC 2262 (Obsoleted by RFC 2272) == Unused Reference: 'RFC2021' is defined on line 394, but no explicit reference was found in the text == Unused Reference: 'RFC2274' is defined on line 398, but no explicit reference was found in the text == Unused Reference: 'RFC2275' is defined on line 402, but no explicit reference was found in the text == Unused Reference: 'RFC2119' is defined on line 406, but no explicit reference was found in the text == Unused Reference: 'RFC3014' is defined on line 409, 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 2021 (Obsoleted by RFC 4502) ** Obsolete normative reference: RFC 2274 (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 2275 (Obsoleted by RFC 2575) Summary: 18 errors (**), 0 flaws (~~), 10 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 EOS Working Group S. Chisholm 2 Internet Draft Nortel Networks 3 Document: draft-ietf-eos-snmpxproto-mib-00.txt 4 Category: Standards Track 5 Expiration Date: October 2001 April 18 2001 7 SNMP Extended Protocol MIB 9 Status of this Memo 11 This document is an Internet-Draft and is in full conformance 12 with all provisions of Section 10 of RFC2026. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that 16 other groups may also distribute working documents as 17 Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six 20 months and may be updated, replaced, or obsoleted by other 21 documents at any time. It is inappropriate to use Internet- 22 Drafts as reference material or to cite them other than as 23 "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 Abstract 33 This memo defines a portion of the Management Information Base (MIB) 34 for use with network management protocols in the Internet community. 35 In particular, it describes SNMP protocol extensions supported by 36 an SNMP entity. 38 Table of Contents 40 1. The SNMP Management Framework 41 2. Introduction 42 3. Extended Protocol Management 43 3.1. Standard Extensions 44 3.2. Vendor Extensions 45 3.3. Interoperability 46 3.4. Relation to Agent Capabilities 47 4. MIB Overview 48 5. Definitions 49 6. IANA Considerations 50 7. Security Considerations 51 8. Author's Address 52 9. Acknowledgements 53 10. References 54 11. Full Copyright Statement 55 1. The SNMP Management Framework 57 The SNMP Management Framework presently consists of five major 58 components: 60 o An overall architecture, described in RFC 2571 [RFC2571]. 62 o Mechanisms for describing and naming objects and events for the 63 purpose of management. The first version of this Structure of 64 Management Information (SMI) is called SMIv1 and described in 65 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 66 1215 [RFC1215]. The second version, called SMIv2, is described 67 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 68 STD 58, RFC 2580 [RFC2580]. 70 o Message protocols for transferring management information. The 71 first version of the SNMP message protocol is called SNMPv1 and 72 described in STD 15, RFC 1157 [RFC1157]. A second version of 73 the SNMP message protocol, which is not an Internet standards 74 track protocol, is called SNMPv2c and described in RFC 1901 75 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 76 message protocol is called SNMPv3 and described in RFC 1906 77 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 79 o Protocol operations for accessing management information. The 80 first set of protocol operations and associated PDU formats is 81 described in STD 15, RFC 1157 [RFC1157]. A second set of 82 protocol operations and associated PDU formats is described in 83 RFC 1905 [RFC1905]. 85 o A set of fundamental applications described in RFC 2573 86 [RFC2573] and the view-based access control mechanism described 87 in RFC 2575 [RFC2575]. 89 A more detailed introduction to the current SNMP Management Framework 90 can be found in RFC 2570 [RFC2570]. 92 Managed objects are accessed via a virtual information store, termed 93 the Management Information Base or MIB. Objects in the MIB are 94 defined using the mechanisms defined in the SMI. 96 This memo specifies a MIB module that is ;'ant to the SMIv2. A 97 MIB conforming to the SMIv1 can be produced through the appropriate 98 translations. The resulting translated MIB must be semantically 99 equivalent, except where objects or events are omitted because no 100 translation is possible (use of Counter64). Some machine readable 101 information in SMIv2 will be converted into textual descriptions in 102 SMIv1 during the translation process. However, this loss of machine 103 readable information is not considered to change the semantics of the 104 MIB. 106 2. Introduction 108 Traditionally, features have been added to SNMP by developing a new 109 version of the protocol that supports these new features. Currently, 110 SNMP entities that conform to [RFC 2571] are expected to implement 111 all the protocol functionality defined by the standards. 113 The idea, moving forward, is to add features to SNMP in a more 114 modular fashion and without necessarily increasing the version 115 number. Since the protocol version number is no longer sufficient 116 information to determine which protocol features an SNMP entity 117 supports, another method is required. This memo defines a MIB to be 118 used to determine the SNMP capabilities of an SNMP entity, above and 119 beyond the base features of its protocol version. 121 Requirements of this feature are: 122 o It must be easy to determine the features that an SNMP entity 123 supports; 124 o It MUST be extensible so that vendor defined features may appear 125 in the capabilities list. 127 This feature is not required to: 129 o List base features of the SNMPv3 protocol. 131 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 132 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 133 document are to be interpreted as described in RFC 2119. 135 3. Extended Protocol Management 137 3.1 Standard Extensions 139 Standard protocol extensions are those extensions that are developed 140 within the IETF and published in standards track RFCs. 142 3.2 Vendor Extensions 144 Vendor Extensions are proprietary protocol extensions developed by a 145 particular vendor. They are not part of standard SNMP, and should 146 not be positioned as such. 148 3.3 Interoperability 150 An SNMP entity MUST only issue a response using an extended protocol 151 feature if it received the request using the extended protocol 152 feature. 154 If an SNMP entity receives an extended protocol feature it does not 155 understand, it MUST follow the unknown PDU response mechanism as 156 defined in [RFC2262] section 4.2.2.1 158 3.4 Relation to Agent Capabilities 160 Agent capability statements are used when describing capabilities of 161 agents with respect to object definitions. The extended protocol 162 MIB is used when describing the capabilities of agents with respect 163 to protocol operations. 165 4. MIB Overview 167 The SNMP Extended Protocol MIB consists of snmpXProtoStandard to 168 indicate which standard PDU extensions are supported and 169 snmpXProtoVendorTable to indicate which vendor extensions are 170 supported. 172 5. Definitions 173 SNMP-EXTENDED-PROTOCOL-MIB DEFINITIONS ::= BEGIN 175 IMPORTS 176 MODULE-IDENTITY, OBJECT-TYPE, 177 Unsigned32, mib-2 FROM SNMPv2-SMI 178 DisplayString FROM SNMPv2-TC 179 IANASnmpExtendedProtocol FROM SNMP-X-PROTOCOL-TC 180 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 182 snmpXProtoMIB MODULE-IDENTITY 183 LAST-UPDATED "200104180000Z" 184 ORGANIZATION "IETF Evolution of SNMP Working Group" 185 CONTACT-INFO 186 " Sharon Chisholm 187 Nortel Networks 188 PO Box 3511 Station C 189 Ottawa, Ont. K1Y 4H7 190 Canada 191 schishol@nortelnetworks.com" 192 DESCRIPTION 193 "The MIB module describes the SNMP protocol 194 extensions supported by this SNMP entity." 195 REVISION "200104180000Z" 196 DESCRIPTION 197 "Initial version, published as RFC XXXX." 199 ::= { mib-2 xx } 201 snmpXProtoObjects OBJECT IDENTIFIER ::= { snmpXProtoMIB 1 } 203 snmpXProtoConformance OBJECT IDENTIFIER ::= { snmpXProtoMIB 3 } 205 snmpXProtoCompliances OBJECT IDENTIFIER 206 ::= { snmpXProtoConformance 1 } 208 snmpXProtoStandard OBJECT-TYPE 209 SYNTAX IANASnmpExtendedProtocol 210 MAX-ACCESS read-only 211 STATUS current 212 DESCRIPTION 213 "The standard SNMP protocol operations supported 214 by this system above and beyond basic protocol 215 support." 216 ::= { snmpXProtoObjects 1 } 218 snmpXProtoVendorTable OBJECT-TYPE 219 SYNTAX SEQUENCE OF SnmpXProtoVendorEntry 220 MAX-ACCESS not-accessible 221 STATUS current 222 DESCRIPTION "A table of vendor protocol extensions to SNMP 223 supported by SNMP entity." 224 ::= { snmpXProtoObjects 2 } 226 snmpXProtoVendorEntry OBJECT-TYPE 227 SYNTAX SnmpXProtoVendorEntry 228 MAX-ACCESS not-accessible 229 STATUS current 230 DESCRIPTION "A vendor protocol extensions to SNMP 231 supported by SNMP entity." 232 INDEX { snmpXProtoVendorIndex } 233 ::= { snmpXProtoVendorTable 1 } 235 SnmpXProtoVendorEntry ::= SEQUENCE { 236 snmpXProtoVendorIndex Unsigned32, 237 snmpXProtoVendorFeature OBJECT IDENTIFIER, 238 snmpXProtoVendorDocument DisplayString 239 } 241 snmpXProtoVendorIndex OBJECT-TYPE 242 SYNTAX Unsigned32(1..4294967295) 243 MAX-ACCESS not-accessible 244 STATUS current 245 DESCRIPTION "An arbitrary index into this table." 246 ::= { snmpXProtoVendorEntry 1 } 248 snmpXProtoVendorFeature OBJECT-TYPE 249 SYNTAX OBJECT IDENTIFIER 250 MAX-ACCESS not-accessible 251 STATUS current 252 DESCRIPTION "The OID of the object within the vendor tree 253 which identifies this vendor feature." 254 ::= { snmpXProtoVendorEntry 2 } 256 snmpXProtoVendorDocument OBJECT-TYPE 257 SYNTAX DisplayString 258 MAX-ACCESS not-accessible 259 STATUS current 260 DESCRIPTION "The vendor specific document identifier which 261 unambiguously points to the user documentation which defines 262 this protocol feature." 263 ::= { snmpXProtoVendorEntry 3 } 265 snmpXProtoCompliance MODULE-COMPLIANCE 266 STATUS current 267 DESCRIPTION 268 "The compliance statement for systems supporting 269 the snmpXProto MIB." 270 MODULE -- this module 271 MANDATORY-GROUPS { 272 snmpXProtoGroup 273 } 274 ::= { snmpXProtoCompliances 1 } 276 snmpXProtoGroups OBJECT IDENTIFIER ::= { snmpXProtoConformance 2 } 278 snmpXProtoGroup OBJECT-GROUP 279 OBJECTS { 280 snmpXProtoStandard 281 } 282 STATUS current 283 DESCRIPTION 284 "Standard snmpXProto group." 285 ::= { snmpXProtoGroups 1} 287 snmpXProtoVendorGroup OBJECT-GROUP 288 OBJECTS { 289 snmpXProtoVendorIndex, 290 snmpXProtoVendorFeature, 291 snmpXProtoVendorDocument 292 } 293 STATUS current 294 DESCRIPTION 295 "Vendor snmpXProto group." 296 ::= { snmpXProtoGroups 2} 298 END 300 6 IANA Considerations 302 IANASnmpExtendedProtocol is a bitmap which indicates which standard 303 extensions to SNMP an SNMP entity supports. It may be given out for 304 SNMP protocol extensions published as standards track RFCs. 306 7. Security Considerations 308 There are no management objects defined in this MIB that have a 309 MAX-ACCESS clause of read-write and/or read-create. So, if this MIB 310 is implemented correctly, then there is no risk that an intruder can 311 alter or create any management objects of this MIB via direct SNMP 312 SET operations. 314 8. Author's Address 316 Sharon Chisholm 317 Nortel Networks 318 PO Box 3511, Station C 319 Ottawa, Ontario, K1Y 4H7 320 Canada 321 Email: schishol@nortelnetworks.com 323 9. Acknowledgments 325 This document is a product of the Evolution of SNMP Working Group. 326 ... 328 11. References 330 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 331 Architecture for Describing SNMP Management Frameworks", 332 RFC 2571, April 41999. 334 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 335 of Management Information for TCP/IP-based Internets", STD 336 16, RFC 1155, May 1990. 338 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 339 STD 16, RFC 1212, March 1991. 341 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 342 SNMP", RFC 1215, March 1991. 344 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 345 Rose, M., and S. Waldbusser, "Structure of Management 346 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 347 1999. 349 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 350 Rose, M., and S. Waldbusser, "Textual Conventions for 351 SMIv2", STD 58, RFC 2579, April 1999. 353 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 354 Rose, M., and S. Waldbusser, "Conformance Statements for 355 SMIv2", STD 58, RFC 2580, April 1999. 357 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 358 "Simple Network Management Protocol", STD 15, RFC 1157, 359 May 1990. 361 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 362 "Introduction to Community-based SNMPv2", RFC 1901, 363 January 364 1996. 366 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 367 "Transport Mappings for Version 2 of the Simple Network 368 Management Protocol (SNMPv2)", RFC 1906, January 1996. 370 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 371 "Message Processing and Dispatching for the Simple 372 Network Management Protocol (SNMP)", RFC 2572, April 373 1999. 375 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 376 (USM) for version 3 of the Simple Network Management 377 Protocol (SNMPv3)", RFC 2574, April 1999. 379 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 380 "Protocol Operations for Version 2 of the Simple Network 381 Management Protocol (SNMPv2)", RFC 1905, January 1996. 383 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 384 Applications", RFC 2573, April 1999. 386 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 387 Access Control Model (VACM) for the Simple Network 388 Management Protocol (SNMP)", RFC 2575, April 1999. 390 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 391 "Introduction to Version 3 of the Internet-standard 392 Network Management Framework", RFC 2570, April 1999. 394 [RFC2021] Waldbusser, S. "Remote Network Monitoring Management 395 Information Base Version 2 using SMIv2", RFC 2021, 396 January 1997 398 [RFC2274] Blumenthal, U. and B. Wijnen, "User-based Security 399 Model (USM) for version 3 of the Simple Network Management 400 Protocol (SNMPv3)", RFC 2274, January 1998. 402 [RFC2275] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 403 Access Control Model (VACM) for the Simple Network 404 Management Protocol (SNMP)", RFC 2275, January 1998. 406 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 407 Requirement Levels", BCP 14, RFC 2119, March 1997. 409 [RFC3014] Stewart, B., Kavasseri, R., "Notification Log MIB, 410 RFC 3014, November 2000 412 10. Full Copyright Statement 414 Copyright (C) The Internet Society (2001). All Rights Reserved. 416 This document and translations of it may be copied and furnished to 417 others, and derivative works that comment on or otherwise explain it 418 or assist in its implementation may be prepared, copied, published 419 and distributed, in whole or in part, without restriction of any kind, 420 provided that the above copyright notice and this paragraph are 421 included on all such copies and derivative works. However, this 422 document itself may not be modified in any way, such as by removing 423 the copyright notice or references to the Internet Society or other 424 Internet organizations, except as needed for the purpose of 425 developing Internet standards in which case the procedures for 426 copyrights defined in the Internet Standards process must be followed, 427 or as required to translate it into languages other than English. 429 The limited permissions granted above are perpetual and will not be 430 revoked by the Internet Society or its successors or assigns. 432 This document and the information contained herein is provided on an 433 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 434 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 435 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN 436 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 437 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.