idnits 2.17.1 draft-ietf-snmpv3-coex-06.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 == It seems as if not all pages are separated by form feeds - found 0 form feeds but 51 pages 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 11 instances of too long lines in the document, the longest one being 8 characters in excess of 72. ** The abstract seems to contain references ([13], [14]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. -- The abstract seems to indicate that this document obsoletes RFC1908, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 61 has weird spacing: '...ameters to S...' == Line 63 has weird spacing: '...ameters to S...' == Line 544 has weird spacing: '...rameter snmp...' == Line 1143 has weird spacing: '...ailable gen...' == Line 2011 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.) -- The document date (1 Dec 1999) is 8913 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) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '2') ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Informational RFC: RFC 1303 (ref. '5') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '6') ** Obsolete normative reference: RFC 1905 (ref. '10') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1906 (ref. '11') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 1907 (ref. '12') (Obsoleted by RFC 3418) ** Obsolete normative reference: RFC 1908 (ref. '13') (Obsoleted by RFC 2576) ** Obsolete normative reference: RFC 2089 (ref. '14') (Obsoleted by RFC 2576) ** Obsolete normative reference: RFC 2571 (ref. '16') (Obsoleted by RFC 3411) ** Obsolete normative reference: RFC 2572 (ref. '17') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2573 (ref. '18') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2574 (ref. '19') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 2575 (ref. '20') (Obsoleted by RFC 3415) Summary: 20 errors (**), 0 flaws (~~), 8 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT Rob Frye 2 CoSine Communications 3 David B. Levi 4 Nortel Networks 5 Shawn A. Routhier 6 Integrated Systems Inc. 7 Bert Wijnen 8 IBM T.J. Watson Research 9 1 Dec 1999 11 Coexistence between Version 1, Version 2, and Version 3 12 of the Internet-standard Network Management Framework 13 15 Status of this Memo 17 This document is an Internet-Draft and is in full conformance with 18 all provisions of Section 10 of RFC2026. Internet-Drafts are working 19 documents of the Internet Engineering Task Force (IETF), its areas, 20 and its working groups. Note that other groups may also distribute 21 working documents as Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html 34 Copyright Notice 36 Copyright (C) The Internet Society (1999). All Rights Reserved. 38 Abstract 40 The purpose of this document is to describe coexistence between 41 version 3 of the Internet-standard Network Management Framework, 42 (SNMPv3), version 2 of the Internet-standard Network Management 43 Framework (SNMPv2), and the original Internet-standard Network 44 Management Framework (SNMPv1). This document obsoletes RFC 1908 [13] 45 and RFC2089 [14]. 47 Table Of Contents 49 1 Overview ..................................................... 4 50 1.1 SNMPv1 ..................................................... 4 51 1.2 SNMPv2 ..................................................... 5 52 1.3 SNMPv3 ..................................................... 6 53 1.4 SNMPv1 and SNMPv2 Access to MIB Data ....................... 6 54 2 SMI and Management Information Mappings ...................... 8 55 2.1 MIB Modules ................................................ 8 56 2.1.1 Object Definitions ....................................... 8 57 2.1.2 Trap and Notification Definitions ........................ 11 58 2.2 Compliance Statements ...................................... 11 59 2.3 Capabilities Statements .................................... 12 60 3 Translating Notifications Parameters ......................... 13 61 3.1 Translating SNMPv1 Notification Parameters to SNMPv2 62 Notification Parameters ................................... 14 63 3.2 Translating SNMPv2 Notification Parameters to SNMPv1 64 Notification Parameters ................................... 15 65 4 Approaches to Coexistence in a Multi-lingual Network ......... 18 66 4.1 Multi-lingual implementations .............................. 18 67 4.1.1 Command Generator ........................................ 18 68 4.1.2 Command Responder ........................................ 19 69 4.1.2.1 Handling Counter64 ..................................... 19 70 4.1.2.2 Mapping SNMPv2 Exceptions .............................. 20 71 4.1.2.2.1 Mapping noSuchObject and noSuchInstance .............. 21 72 4.1.2.2.2 Mapping endOfMibView ................................. 21 73 4.1.2.3 Processing An SNMPv1 GetRequest ........................ 21 74 4.1.2.4 Processing An SNMPv1 GetNextRequest .................... 22 75 4.1.2.5 Processing An SNMPv1 SetRequest ........................ 24 76 4.1.2.6 Translation of authorizationError ...................... 24 77 4.1.3 Notification Originator .................................. 24 78 4.1.4 Notification Receiver .................................... 25 79 4.2 Proxy Implementations ...................................... 25 80 4.2.1 Upstream Version Greater Than Downstream Version ......... 26 81 4.2.2 Upstream Version Less Than Downstream Version ............ 27 82 4.3 Error Status Mappings ...................................... 28 83 5 Message Processing Models and Security Models ................ 30 84 5.1 Mappings ................................................... 30 85 5.2 The SNMPv1 MP Model and SNMPv1 Community-based Security 86 Model ..................................................... 30 87 5.2.1 Processing An Incoming Request ........................... 31 88 5.2.2 Generating An Outgoing Response .......................... 33 89 5.2.3 Generating An Outgoing Notification ...................... 33 90 5.3 The SNMP Community MIB Module .............................. 34 91 6 Intellectual Property ........................................ 45 92 7 Acknowledgments .............................................. 46 93 8 Security Considerations ...................................... 47 94 9 References ................................................... 48 95 10 Editor's Address ............................................ 50 96 A. Full Copyright Statement .................................... 51 98 1. Overview 100 The purpose of this document is to describe coexistence between 101 version 3 of the Internet-standard Network Management Framework, 102 termed the SNMP version 3 framework (SNMPv3), version 2 of the 103 Internet-standard Network Management Framework, termed the SNMP 104 version 2 framework (SNMPv2), and the original Internet-standard 105 Network Management Framework (SNMPv1). 107 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 108 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 109 document are to be interpreted as described in RFC2119 [15]. 111 There are four general aspects of coexistence described in this 112 document. Each of these is described in a separate section: 114 - Conversion of MIB documents between SMIv1 and SMIv2 formats is 115 documented in section 2. 117 - Mapping of notification parameters is documented in section 3. 119 - Approaches to coexistence between entities which support the 120 various versions of SNMP in a multi-lingual network is 121 documented in section 4. This section addresses the 122 processing of protocol operations in multi-lingual 123 implementations, as well as behaviour of proxy 124 implementations. 126 - The SNMPv1 Message Processing Model and Community-Based 127 Security Model, which provides mechanisms for adapting SNMPv1 128 into the View-Based Access Control Model (VACM) [20], is 129 documented in section 5 (this section also addresses the 130 SNMPv2c Message Processing Model and Community-Based Security 131 Model). 133 1.1. SNMPv1 135 SNMPv1 is defined by these documents: 137 - STD 15, RFC 1157 [2] which defines the Simple Network 138 Management Protocol (SNMPv1), the protocol used for network 139 access to managed objects. 141 - STD 16, RFC 1155 [1] which defines the Structure of Management 142 Information (SMIv1), the mechanisms used for describing and 143 naming objects for the purpose of management. 145 - STD 16, RFC 1212 [3] which defines a more concise description 146 mechanism, which is wholly consistent with the SMIv1. 148 - RFC 1215 [4] which defines a convention for defining Traps for 149 use with the SMIv1. 151 Note that throughout this document, the term 'SMIv1' is used. This 152 term generally refers to the information presented in RFC 1155, RFC 153 1212, and RFC 1215. 155 1.2. SNMPv2 157 SNMPv2 is defined by these documents: 159 - STD 58, RFC 2578 which defines Version 2 of the Structure of 160 Management Information (SMIv2) [7]. 162 - STD 58, RFC 2579 which defines common MIB "Textual 163 Conventions" [8]. 165 - STD 58, RFC 2580 which defines Conformance Statements and 166 requirements for defining agent and manager capabilities [9]. 168 - RFC 1905 which defines the Protocol Operations used in 169 processing [10]. 171 - RFC 1906 which defines the Transport Mappings used "on the 172 wire" [11]. 174 - RFC 1907 which defines the basic Management Information Base 175 for monitoring and controlling some basic common functions of 176 SNMP entities [12]. 178 Note that SMIv2 as used throughout this document refers to the first 179 three documents listed above (RFCs 2578, 2579, and 2580). 181 The following document augments the definition of SNMPv2: 183 - RFC 1901 [6] is an Experimental definition for using SNMPv2 184 PDUs within a community-based message wrapper. This is 185 referred to throughout this document as SNMPv2c. 187 1.3. SNMPv3 189 SNMPv3 is defined by these documents: 191 - RFC 2571 which defines an Architecture for Describing SNMP 192 Management Frameworks [16]. 194 - RFC 2572 which defines Message Processing and Dispatching 195 [17]. 197 - RFC 2573 which defines various SNMP Applications [18]. 199 - RFC 2574 which defines the User-based Security Model (USM), 200 providing for both Authenticated and Private (encrypted) SNMP 201 messages [19]. 203 - RFC 2575 which defines the View-based Access Control Model 204 (VACM), providing the ability to limit access to different MIB 205 objects on a per-user basis [20]. 207 SNMPv3 also uses the SNMPv2 definitions of RFCs 1905 through 1907 and 208 the SMIv2 definitions of 2578 through 2580 described above. 210 1.4. SNMPv1 and SNMPv2 Access to MIB Data 212 In several places, this document refers to 'SNMPv1 Access to MIB 213 Data' and 'SNMPv2 Access to MIB Data'. These terms refer to the part 214 of an SNMP agent which actually accesses instances of MIB objects, 215 and which actually initiates generation of notifications. 216 Differences between the two types of access to MIB data are: 218 - Error-status values generated. 220 - Generation of exception codes. 222 - Use of the Counter64 data type. 224 - The format of parameters provided when a notification is 225 generated. 227 SNMPv1 access to MIB data may generate SNMPv1 error-status values, 228 will never generate exception codes nor use the Counter64 data type, 229 and will provide SNMPv1 format parameters for generating 230 notifications. Note also that SNMPv1 access to MIB data will 231 actually never generate a readOnly error (a noSuchName error would 232 always occur in the situation where one would expect a readOnly 233 error). 235 SNMPv2 access to MIB data may generate SNMPv2 error-status values, 236 may generate exception codes, may use the Counter64 data type, and 237 will provide SNMPv2 format parameters for generating notifications. 238 Note that SNMPv2 access to MIB data will never generate readOnly, 239 noSuchName, or badValue errors. 241 Note that a particular multi-lingual implementation may choose to 242 implement all access to MIB data as SNMPv2 access to MIB data, and 243 perform the translations described herein for SNMPv1-based 244 transactions. 246 2. SMI and Management Information Mappings 248 The SMIv2 approach towards describing collections of managed objects 249 is nearly a proper superset of the approach defined in the SMIv1. 250 For example, both approaches use an adapted subset of ASN.1 (1988) 251 [11] as the basis for a formal descriptive notation. Indeed, one 252 might note that the SMIv2 approach largely codifies the existing 253 practice for defining MIB modules, based on extensive experience with 254 the SMIv1. 256 The following sections consider the three areas: MIB modules, 257 compliance statements, and capabilities statements. 259 2.1. MIB Modules 261 MIB modules defined using the SMIv1 may continue to be used with 262 protocol versions which use SNMPv2 PDUs. However, for the MIB 263 modules to conform to the SMIv2, the following changes SHALL be made: 265 2.1.1. Object Definitions 267 In general, conversion of a MIB module does not require the 268 deprecation of the objects contained therein. If the definition of 269 an object is truly inadequate for its intended purpose, the object 270 SHALL be deprecated or obsoleted, otherwise deprecation is not 271 required. 273 (1) The IMPORTS statement MUST reference SNMPv2-SMI, instead of 274 RFC1155-SMI and RFC-1212. 276 (2) The MODULE-IDENTITY macro MUST be invoked immediately after any 277 IMPORTs statement. 279 (3) For any object with an integer-valued SYNTAX clause, in which the 280 corresponding INTEGER does not have a range restriction (i.e., the 281 INTEGER has neither a defined set of named-number enumerations nor 282 an assignment of lower- and upper-bounds on its value), the object 283 MUST have the value of its SYNTAX clause changed to Integer32, or 284 have an appropriate range specified. 286 (4) For any object with a SYNTAX clause value of Counter, the object 287 MUST have the value of its SYNTAX clause changed to Counter32. 289 (5) For any object with a SYNTAX clause value of Gauge, the object MUST 290 have the value of its SYNTAX clause changed to Gauge32, or 291 Unsigned32 where appropriate. 293 (6) For all objects, the ACCESS clause MUST be replaced by a MAX-ACCESS 294 clause. The value of the MAX-ACCESS clause SHALL be the same as 295 that of the ACCESS clause unless some other value makes "protocol 296 sense" as the maximal level of access for the object. In 297 particular, object types for which instances can be explicitly 298 created by a protocol set operation, SHALL have a MAX-ACCESS clause 299 of "read-create". If the value of the ACCESS clause is "write- 300 only", then the value of the MAX-ACCESS clause MUST be "read- 301 write", and the DESCRIPTION clause SHALL note that reading this 302 object will result in implementation-specific results. Note that 303 in SMIv1, the ACCESS clause specifies the minimal required access, 304 while in SMIv2, the MAX-ACCESS clause specifies the maximum allowed 305 access. This should be considered when converting an ACCESS clause 306 to a MAX-ACCESS clause. 308 (7) For all objects, if the value of the STATUS clause is "mandatory" 309 or "optional", the value MUST be replaced with "current", 310 "deprecated", or "obsolete" depending on the current usage of such 311 objects. 313 (8) For any object not containing a DESCRIPTION clause, the object MUST 314 have a DESCRIPTION clause defined. 316 (9) For any object corresponding to a conceptual row which does not 317 have an INDEX clause, the object MUST have either an INDEX clause 318 or an AUGMENTS clause defined. 320 (10) If any INDEX clause contains a reference to an object with a syntax 321 of NetworkAddress, then a new object MUST be created and placed in 322 this INDEX clause immediately preceding the object whose syntax is 323 NetworkAddress. This new object MUST have a syntax of INTEGER, it 324 MUST be not-accessible, and its value MUST always be 1. 326 (11) For any object with a SYNTAX of NetworkAddress, the SYNTAX MUST be 327 changed to IpAddress. Note that the use of NetworkAddress in new 328 MIB documents is strongly discouraged (in fact, new MIB documents 329 should be written using SMIv2, which does not define 330 NetworkAddress). 332 (12) For any object containing a DEFVAL clause with an OBJECT IDENTIFIER 333 value which is expressed as a collection of sub-identifiers, the 334 value MUST be changed to reference a single ASN.1 identifier. This 335 may require defining a series of new administrative assignments 336 (OBJECT IDENTIFIERS) in order to define the single ASN.1 337 identifier. 339 (13) One or more OBJECT-GROUPS MUST be defined, and related objects 340 SHOULD be collected into appropriate groups. Note that SMIv2 341 requires all OBJECT-TYPEs to be a member of at least one OBJECT- 342 GROUP. 344 Other changes are desirable, but not necessary: 346 (1) Creation and deletion of conceptual rows is inconsistent using the 347 SMIv1. The SMIv2 corrects this. As such, if the MIB module 348 undergoes review early in its lifetime, and it contains conceptual 349 tables which allow creation and deletion of conceptual rows, then 350 the objects relating to those tables MAY be deprecated and replaced 351 with objects defined using the new approach. The approach based on 352 SMIv2 can be found in section 7 of RFC2578 [7], and the RowStatus 353 and StorageType TEXTUAL-CONVENTIONs are described in section 2 of 354 RFC2579 [8]. 356 (2) For any object with a string-valued SYNTAX clause, in which the 357 corresponding OCTET STRING does not have a size restriction (i.e., 358 the OCTET STRING has no assignment of lower- and upper-bounds on 359 its length), the bounds for the size of the object SHOULD be 360 defined. 362 (3) All textual conventions informally defined in the MIB module SHOULD 363 be redefined using the TEXTUAL-CONVENTION macro. Such a change 364 would not necessitate deprecating objects previously defined using 365 an informal textual convention. 367 (4) For any object which represents a measurement in some kind of 368 units, a UNITS clause SHOULD be added to the definition of that 369 object. 371 (5) For any conceptual row which is an extension of another conceptual 372 row, i.e., for which subordinate columnar objects both exist and 373 are identified via the same semantics as the other conceptual row, 374 an AUGMENTS clause SHOULD be used in place of the INDEX clause for 375 the object corresponding to the conceptual row which is an 376 extension. 378 Finally, to avoid common errors in SMIv1 MIB modules: 380 (1) For any non-columnar object that is instanced as if it were 381 immediately subordinate to a conceptual row, the value of the 382 STATUS clause of that object MUST be changed to "obsolete". 384 (2) For any conceptual row object that is not contained immediately 385 subordinate to a conceptual table, the value of the STATUS clause 386 of that object (and all subordinate objects) MUST be changed to 387 "obsolete". 389 2.1.2. Trap and Notification Definitions 391 If a MIB module is changed to conform to the SMIv2, then each 392 occurrence of the TRAP-TYPE macro MUST be changed to a corresponding 393 invocation of the NOTIFICATION-TYPE macro: 395 (1) The IMPORTS statement MUST NOT reference RFC-1215 [4], and MUST 396 reference SNMPv2-SMI instead. 398 (2) The ENTERPRISE clause MUST be removed. 400 (3) The VARIABLES clause MUST be renamed to the OBJECTS clause. 402 (4) A STATUS clause MUST be added, with an appropriate value. Normally 403 the value should be 'current,' although 'deprecated' or 'obsolete' 404 may be used as needed. 406 (5) The value of an invocation of the NOTIFICATION-TYPE macro is an 407 OBJECT IDENTIFIER, not an INTEGER, and MUST be changed accordingly. 408 Specifically, if the value of the ENTERPRISE clause is not 'snmp' 409 then the value of the invocation SHALL be the value of the 410 ENTERPRISE clause extended with two sub-identifiers, the first of 411 which has the value 0, and the second has the value of the 412 invocation of the TRAP-TYPE. If the value of the ENTERPRISE clause 413 is 'snmp', then the value of the invocation of the NOTIFICATION- 414 TYPE macro SHALL be mapped in the same manner as described in 415 section 3.1 in this document. 417 (6) A DESCRIPTION clause MUST be added, if not already present. 419 (7) One or more NOTIFICATION-GROUPs MUST be defined, and related 420 notifications MUST be collected into those groups. Note that SMIv2 421 requires that all NOTIFICATION-TYPEs be a member of at least one 422 NOTIFICATION-GROUP. 424 2.2. Compliance Statements 426 For those information modules which are "standards track", a 427 corresponding invocation of the MODULE-COMPLIANCE macro and related 428 OBJECT-GROUP and/or NOTIFICATION-GROUP macros MUST be included within 429 the information module (or in a companion information module), and 430 any commentary text in the information module which relates to 431 compliance SHOULD be removed. Typically this editing can occur when 432 the information module undergoes review. 434 Note that a MODULE-COMPLIANCE statement is not required for a MIB 435 document that is not on the standards track (for example, an 436 enterprise MIB), though it may be useful in some circumstances to 437 define a MODULE-COMPLIANCE statement for such a MIB document. 439 2.3. Capabilities Statements 441 RFC1303 [5] uses the MODULE-CONFORMANCE macro to describe an agent's 442 capabilities with respect to one or more MIB modules. Converting 443 such a description for use with the SMIv2 requires these changes: 445 (1) The macro name AGENT-CAPABILITIES SHOULD be used instead of MODULE- 446 CONFORMANCE. 448 (2) The STATUS clause SHOULD be added, with a value of 'current'. 450 (3) All occurrences of the CREATION-REQUIRES clause MUST either be 451 omitted if appropriate, or be changed such that the semantics are 452 consistent with RFC2580 [9]. 454 In order to ease coexistence, object groups defined in an SMIv1 455 compliant MIB module may be referenced by the INCLUDES clause of an 456 invocation of the AGENT-CAPABILITIES macro: upon encountering a 457 reference to an OBJECT IDENTIFIER subtree defined in an SMIv1 MIB 458 module, all leaf objects which are subordinate to the subtree and 459 have a STATUS clause value of mandatory are deemed to be INCLUDEd. 460 (Note that this method is ambiguous when different revisions of an 461 SMIv1 MIB have different sets of mandatory objects under the same 462 subtree; in such cases, the only solution is to rewrite the MIB using 463 the SMIv2 in order to define the object groups unambiguously.) 465 3. Translating Notifications Parameters 467 This section describes how parameters used for generating 468 notifications are translated between the format used for SNMPv1 469 notification protocol operations and the format used for SNMPv2 470 notification protocol operations. The parameters used to generate a 471 notification are called 'notification parameters.' The format of 472 parameters used for SNMPv1 notification protocol operations is 473 refered to in this document as 'SNMPv1 notification parameters.' The 474 format of parameters used for SNMPv2 notification protocol operations 475 is refered to in this document as 'SNMPv2 notification parameters.' 477 The situations where notification parameters MUST be translated are: 479 - When an entity generates a set of notification parameters in a 480 particular format, and the configuration of the entity 481 indicates that the notification must be sent using an SNMP 482 message version that requires the other format for 483 notification parameters. 485 - When a proxy receives a notification that was sent using an 486 SNMP message version that requires one format of notification 487 parameters, and must forward the notification using an SNMP 488 message version that requires the other format of notification 489 parameters. 491 In addition, it MAY be desirable to translate notification parameters 492 in a notification receiver application in order to present 493 notifications to the end user in a consistent format. 495 Note that for the purposes of this section, the set of notification 496 parameters is independent of whether the notification is to be sent 497 as a trap or an inform. 499 SNMPv1 notification parameters consist of: 501 - An enterprise parameter (OBJECT IDENTIFIER). 503 - An agent-addr parameter (NetworkAddress). 505 - A generic-trap parameter (INTEGER). 507 - A specific-trap parameter (INTEGER). 509 - A time-stamp parameter (TimeTicks). 511 - A list of variable-bindings (VarBindList). 513 SNMPv2 notification parameters consist of: 515 - A sysUpTime parameter (TimeTicks). This appears in the first 516 variable-binding in an SNMPv2-Trap-PDU or InformRequest-PDU. 518 - An snmpTrapOID parameter (OBJECT IDENTIFIER). This appears in 519 the second variable-binding in an SNMPv2-Trap-PDU or 520 InformRequest-PDU. 522 - A list of variable-bindings (VarBindList). This refers to all 523 but the first two variable-bindings in an SNMPv2-Trap-PDU or 524 InformRequest-PDU. 526 3.1. Translating SNMPv1 Notification Parameters to SNMPv2 Notification 527 Parameters 529 The following procedure describes how to translate SNMPv1 530 notification parameters into SNMPv2 notification parameters: 532 (1) The SNMPv2 sysUpTime parameter SHALL be taken directly from the 533 SNMPv1 time-stamp parameter. 535 (2) If the SNMPv1 generic-trap parameter is 'enterpriseSpecific(6)', 536 the SNMPv2 snmpTrapOID parameter SHALL be the concatentation of the 537 SNMPv1 enterprise parameter and two additional sub-identifiers, 538 '0', and the SNMPv1 specific-trap parameter. 540 (3) If the SNMPv1 generic-trap parameter is not 541 'enterpriseSpecific(6)', the SNMPv2 snmpTrapOID parameter SHALL be 542 the corresponding trap as defined in section 2 of RFC1907 [12]: 544 generic-trap parameter snmpTrapOID.0 545 ====================== ============= 546 0 1.3.6.1.6.3.1.1.5.1 (coldStart) 547 1 1.3.6.1.6.3.1.1.5.2 (warmStart) 548 2 1.3.6.1.6.3.1.1.5.3 (linkDown) 549 3 1.3.6.1.6.3.1.1.5.4 (linkUp) 550 4 1.3.6.1.6.3.1.1.5.5 (authenticationFailure) 551 5 1.3.6.1.6.3.1.1.5.6 (egpNeighborLoss) 553 (4) The SNMPv2 variable-bindings SHALL be the SNMPv1 variable-bindings. 554 In addition, if the translation is being performed by a proxy in 555 order to forward a received trap, three additional variable- 556 bindings will be appended, if these three additional variable- 557 bindings do not already exist in the SNMPv1 variable-bindings. The 558 name portion of the first additional variable binding SHALL contain 559 snmpTrapAddress.0, and the value SHALL contain the SNMPv1 agent- 560 addr parameter. The name portion of the second additional variable 561 binding SHALL contain snmpTrapCommunity.0, and the value SHALL 562 contain the value of the community-string field from the received 563 SNMPv1 message which contained the SNMPv1 Trap-PDU. The name 564 portion of the third additional variable binding SHALL contain 565 snmpTrapEnterprise.0 [12], and the value SHALL be the SNMPv1 566 enterprise parameter. 568 3.2. Translating SNMPv2 Notification Parameters to SNMPv1 Notification 569 Parameters 571 The following procedure describes how to translate SNMPv2 572 notification parameters into SNMPv1 notification parameters: 574 (1) The SNMPv1 enterprise parameter SHALL be determined as follows: 576 - If the SNMPv2 snmpTrapOID parameter is one of the standard 577 traps as defined in RFC1907 [12], then the SNMPv1 enterprise 578 parameter SHALL be set to the value of the variable-binding in 579 the SNMPv2 variable-bindings whose name is 580 snmpTrapEnterprise.0 if that variable-binding exists. If it 581 does not exist, the SNMPv1 enterprise parameter SHALL be set 582 to the value 'snmpTraps' as defined in RFC1907 [12]. 584 - If the SNMPv2 snmpTrapOID parameter is not one of the standard 585 traps as defined in RFC1907 [12], then the SNMPv1 enterprise 586 parameter SHALL be determined from the SNMPv2 snmpTrapOID 587 parameter as follows: 589 - If the next-to-last sub-identifier of the snmpTrapOID is 590 zero, then the SMIv1 enterprise SHALL be the SNMPv2 591 snmpTrapOID with the last 2 sub-identifiers removed, 592 otherwise 594 - If the next-to-last sub-identifier of the snmpTrapOID is 595 non-zero, then the SMIv1 enterprise SHALL be the SNMPv2 596 snmpTrapOID with the last sub-identifier removed. 598 (2) The SNMPv1 agent-addr parameter SHALL be determined based on the 599 situation in which the translation occurs. 601 - If the translation occurs within a notification originator 602 application, and the notification is to be sent over IP, the 603 SNMPv1 agent-addr parameter SHALL be set to the IP address of 604 the SNMP entity in which the notification originator resides. 605 If the notification is to be sent over some other transport, 606 the SNMPv1 agent-addr parameter SHALL be set to 0.0.0.0. 608 - If the translation occurs within a proxy application, the 609 proxy must attempt to extract the original source of the 610 notification from the variable-bindings. If the SNMPv2 611 variable-bindings contains a variable binding whose name is 612 snmpTrapAddress.0, the agent-addr parameter SHALL be set to 613 the value of that variable binding. Otherwise, the SNMPv1 614 agent-addr parameter SHALL be set to 0.0.0.0. 616 (3) If the SNMPv2 snmpTrapOID parameter is one of the standard traps as 617 defined in RFC1907 [12], the SNMPv1 generic-trap parameter SHALL be 618 set as follows: 620 snmpTrapOID.0 parameter generic-trap 621 =============================== ============ 622 1.3.6.1.6.3.1.1.5.1 (coldStart) 0 623 1.3.6.1.6.3.1.1.5.2 (warmStart) 1 624 1.3.6.1.6.3.1.1.5.3 (linkDown) 2 625 1.3.6.1.6.3.1.1.5.4 (linkUp) 3 626 1.3.6.1.6.3.1.1.5.5 (authenticationFailure) 4 627 1.3.6.1.6.3.1.1.5.6 (egpNeighborLoss) 5 629 Otherwise, the SNMPv1 generic-trap parameter SHALL be set to 6. 631 (4) If the SNMPv2 snmpTrapOID parameter is one of the standard traps as 632 defined in RFC1907 [12], the SNMPv1 specific-trap parameter SHALL 633 be set to zero. Otherwise, the SNMPv1 specific-trap parameter 634 SHALL be set to the last sub-identifier of the SNMPv2 snmpTrapOID 635 parameter. 637 (5) The SNMPv1 time-stamp parameter SHALL be taken directly from the 638 SNMPv2 sysUpTime parameter. 640 (6) The SNMPv1 variable-bindings SHALL be the SNMPv2 variable-bindings. 641 Note, however, that if the SNMPv2 variable-bindings contain any 642 objects whose type is Counter64, the translation to SNMPv1 643 notification parameters cannot be performed. In this case, the 644 notification cannot be encoded in an SNMPv1 packet (and so the 645 notification cannot be sent using SNMPv1, see section 4.1.3 and 646 section 4.2). 648 4. Approaches to Coexistence in a Multi-lingual Network 650 There are two basic approaches to coexistence in a multi-lingual 651 network, multi-lingual implementations and proxy implementations. 652 Multi-lingual implementations allow elements in a network to 653 communicate with each other using an SNMP version which both elements 654 support. This allows a multi-lingual implementation to communicate 655 with any mono-lingual implementation, regardless of the SNMP version 656 supported by the mono-lingual implementation. 658 Proxy implementations provide a mechanism for translating between 659 SNMP versions using a third party network element. This allows 660 network elements which support only a single, but different, SNMP 661 version to communicate with each other. Proxy implementations are 662 also useful for securing communications over an insecure link between 663 two locally secure networks. 665 4.1. Multi-lingual implementations 667 This approach requires an entity to support multiple SNMP message 668 versions. Typically this means supporting SNMPv1, SNMPv2c, and 669 SNMPv3 message versions. The behaviour of various types of SNMP 670 applications which support multiple message versions is described in 671 the following sections. This approach allows entities which support 672 multiple SNMP message versions to coexist with and communicate with 673 entities which support only a single SNMP message version. 675 4.1.1. Command Generator 677 A command generator must select an appropriate message version when 678 sending requests to another entity. One way to achieve this is to 679 consult a local database to select the appropriate message version. 681 In addition, a command generator MUST 'downgrade' GetBulk requests to 682 GetNext requests when selecting SNMPv1 as the message version for an 683 outgoing request. This is done by simply changing the operation type 684 to GetNext, ignoring any non-repeaters and max-repetitions values, 685 and setting error-status and error-index to zero. 687 4.1.2. Command Responder 689 A command responder must be able to deal with both SNMPv1 and SNMPv2 690 access to MIB data. There are three aspects to dealing with this. A 691 command responder must: 693 - Deal correctly with SNMPv2 access to MIB data that returns a 694 Counter64 value while processing an SNMPv1 message, 696 - Deal correctly with SNMPv2 access to MIB data that returns one 697 of the three exception values while processing an SNMPv1 698 message, and 700 - Map SNMPv2 error codes returned from SNMPv2 access to MIB data 701 into SNMPv1 error codes when processing an SNMPv1 message. 703 Note that SNMPv1 error codes SHOULD NOT be used without any change 704 when processing SNMPv2c or SNMPv3 messages, except in the case of 705 proxy forwarding. In the case of proxy forwarding, for backwards 706 compatibility, SNMPv1 error codes may be used without any change in a 707 forwarded SNMPv2c or SNMPv3 message. 709 The following sections describe the behaviour of a command responder 710 application which supports multiple SNMP message versions, and which 711 uses some combination of SNMPv1 and SNMPv2 access to MIB data. 713 4.1.2.1. Handling Counter64 715 The SMIv2 [7] defines one new syntax that is incompatible with SMIv1. 716 This syntax is Counter64. All other syntaxes defined by SMIv2 are 717 compatible with SMIv1. 719 The impact on multi-lingual command responders is that they MUST NOT 720 ever return a variable binding containing a Counter64 value in a 721 response to a request that was received using the SNMPv1 message 722 version. 724 Multi-lingual command responders SHALL take the approach that object 725 instances whose type is Counter64 are implicitly excluded from view 726 when processing an SNMPv1 message. So: 728 - On receipt of an SNMPv1 GetRequest-PDU containing a variable 729 binding whose name field points to an object instance of type 730 Counter64, a GetResponsePDU SHALL be returned, with an error- 731 status of noSuchName and the error-index set to the variable 732 binding that caused this error. 734 - On an SNMPv1 GetNextRequest-PDU, any object instance which 735 contains a syntax of Counter64 SHALL be skipped, and the next 736 accessible object instance that does not have the syntax of 737 Counter64 SHALL be retrieved. If no such object instance 738 exists, then an error-status of noSuchName SHALL be returned, 739 and the error-index SHALL be set to the variable binding that 740 caused this error. 742 - Any SNMPv1 request which contains a variable binding with a 743 Counter64 value is ill-formed, so the foregoing rules do not 744 apply. If that error is detected, a response SHALL NOT be 745 returned, since it would contain a copy of the ill-formed 746 variable binding. Instead, the offending PDU SHALL be 747 discarded and the counter snmpInASNParseErrs SHALL be 748 incremented. 750 4.1.2.2. Mapping SNMPv2 Exceptions 752 SNMPv2 provides a feature called exceptions, which allow an SNMPv2 753 Response PDU to return as much management information as possible, 754 even when an error occurs. However, SNMPv1 does not support 755 exceptions, and so an SNMPv1 Response PDU cannot return any 756 management information, and can only return an error-status and 757 error-index value. 759 When an SNMPv1 request is received, a command responder MUST check 760 any variable bindings returned using SNMPv2 access to MIB data for 761 exception values, and convert these exception values into SNMPv1 762 error codes. 764 The type of exception that can be returned when accessing MIB data 765 and the action taken depends on the type of SNMP request. 767 - For a GetRequest, a noSuchObject or noSuchInstance exception 768 may be returned. 770 - For a GetNextRequest, an endOfMibView exception may be 771 returned. 773 - No exceptions will be returned for a SetRequest, and a 774 GetBulkRequest should only be received in an SNMPv2c or SNMPv3 775 message, so these request types may be ignored when mapping 776 exceptions. 778 Note that when a response contains multiple exceptions, it is an 779 implementation choice as to which variable binding the error-index 780 should reference. 782 4.1.2.2.1. Mapping noSuchObject and noSuchInstance 784 A noSuchObject or noSuchInstance exception generated by an SNMPv2 785 access to MIB data indicates that the requested object instance can 786 not be returned. The SNMPv1 error code for this condition is 787 noSuchName, and so the error-status field of the response PDU SHALL 788 be set to noSuchName. Also, the error-index field SHALL be set to 789 the index of the variable binding for which an exception occurred 790 (there may be more than one and it is an implementation decision as 791 to which is used), and the variable binding list from the original 792 request SHALL be returned with the response PDU. 794 4.1.2.2.2. Mapping endOfMibView 796 When an SNMPv2 access to MIB data returns a variable binding 797 containing an endOfMibView exception, it indicates that there are no 798 object instances available which lexicographically follow the object 799 in the request. In an SNMPv1 agent, this condition normally results 800 in a noSuchName error, and so the error-status field of the response 801 PDU SHALL be set to noSuchName. Also, the error-index field SHALL be 802 set to the index of the variable binding for which an exception 803 occurred (there may be more than one and it is an implementation 804 decision as to which is used), and the variable binding list from the 805 original request SHALL be returned with the response PDU. 807 4.1.2.3. Processing An SNMPv1 GetRequest 809 When processing an SNMPv1 GetRequest, the following procedures MUST 810 be followed when using an SNMPv2 access to MIB data. 812 When such an access to MIB data returns response data using SNMPv2 813 syntax and error-status values, then: 815 (1) If the error-status is anything other than noError, 817 - The error status SHALL be translated to an SNMPv1 error-status 818 using the table in section 4.3, "Error Status Mappings". 820 - The error-index SHALL be set to the position (in the original 821 request) of the variable binding that caused the error-status. 823 - The variable binding list of the response PDU SHALL be made 824 exactly the same as the variable binding list that was 825 received in the original request. 827 (2) If the error-status is noError, the variable bindings SHALL be 828 checked for any SNMPv2 exception (noSuchObject or noSuchInstance) 829 or an SNMPv2 syntax that is unknown to SNMPv1 (Counter64). If 830 there are any such variable bindings, one of those variable 831 bindings SHALL be selected (it is an implementation choice as to 832 which is selected), and: 834 - The error-status SHALL be set to noSuchName, 836 - The error-index SHALL be set to the position (in the variable 837 binding list of the original request) of the selected variable 838 binding, and 840 - The variable binding list of the response PDU SHALL be exactly 841 the same as the variable binding list that was received in the 842 original request. 844 (3) If there are no such variable bindings, then: 846 - The error-status SHALL be set to noError, 848 - The error-index SHALL be set to zero, and 850 - The variable binding list of the response SHALL be composed 851 from the data as it is returned by the access to MIB data. 853 4.1.2.4. Processing An SNMPv1 GetNextRequest 855 When processing an SNMPv1 GetNextRequest, the following procedures 856 MUST be followed when an SNMPv2 access to MIB data is called as part 857 of processing the request. There may be repetitive accesses to MIB 858 data to try to find the first object which lexicographically follows 859 each of the objects in the request. This is implementation specific. 860 These procedures are followed only for data returned when using 861 SNMPv2 access to MIB data. Data returned using SNMPv1 access to MIB 862 data may be treated in the normal manner for an SNMPv1 request. 864 First, if the access to MIB data returns an error-status of anything 865 other than noError: 867 (1) The error status SHALL be translated to an SNMPv1 error-status 868 using the table in section 4.3, "Error Status Mappings". 870 (2) The error-index SHALL be set to the position (in the original 871 request) of the variable binding that caused the error-status. 873 (3) The variable binding list of the response PDU SHALL be exactly the 874 same as the variable binding list that was received in the original 875 request. 877 Otherwise, if the access to MIB data returns an error-status of 878 noError: 880 (1) Any variable bindings containing an SNMPv2 syntax of Counter64 881 SHALL be considered to be not in view, and MIB data SHALL be 882 accessed as many times as is required until either a value other 883 than Counter64 is returned, or an error occurs. 885 (2) If there is any variable binding that contains an SNMPv2 exception 886 endOfMibView (there may be more than one, it is an implementation 887 decision as to which is chosen): 889 - The error-status SHALL be set to noSuchName, 891 - The error-index SHALL be set to the position (in the variable 892 binding list of the original request) of the variable binding 893 that returned such an SNMPv2 exception, and 895 - The variable binding list of the response PDU SHALL be exactly 896 the same as the variable binding list that was received in the 897 original request. 899 (3) If there are no such variable bindings, then: 901 - The error-status SHALL be set to noError, 903 - The error-index SHALL be set to zero, and 905 - The variable binding list of the response SHALL be composed 906 from the data as it is returned by the access to MIB data. 908 4.1.2.5. Processing An SNMPv1 SetRequest 910 When processing an SNMPv1 SetRequest, the following procedures MUST 911 be followed when calling SNMPv2 MIB access routines. 913 When such MIB access routines return response data using SNMPv2 914 syntax and error-status values, and the error-status is anything 915 other than noError, then: 917 - The error status SHALL be translated to an SNMPv1 error-status 918 using the table in section 4.3, "Error Status Mappings". 920 - The error-index SHALL be set to the position (in the original 921 request) of the variable binding that caused the error-status. 923 - The variable binding list of the response PDU SHALL be made 924 exactly the same as the variable binding list that was 925 received in the original request. 927 4.1.2.6. Translation of authorizationError 929 Whenever the SNMPv2 error-status value of authorizationError is 930 translated to an SNMPv1 error-status value of noSuchName, the value 931 of snmpInBadCommunityUses MUST be incremented. 933 4.1.3. Notification Originator 935 A notification originator must be able to translate between SNMPv1 936 notifications parameters and SNMPv2 notification parameters in order 937 to send a notification using a particular SNMP message version. If a 938 notification is generated using SNMPv1 notification parameters, and 939 configuration information specifies that notifications be sent using 940 SNMPv2c or SNMPv3, the notification parameters must be translated to 941 SNMPv2 notification parameters. Likewise, if a notification is 942 generated using SNMPv2 notification parameters, and configuration 943 information specifies that notifications be sent using SNMPv1, the 944 notification parameters must be translated to SNMPv1 notification 945 parameters. In this case, if the notification cannot be translated 946 (due to the presence of a Counter64 type), it will not be sent using 947 SNMPv1. 949 When a notification originator generates a notification, using 950 parameters obtained from the SNMP-TARGET-MIB and SNMP-NOTIFICATION- 951 MIB, if the SNMP version used to generate the notification is SNMPv1, 952 the PDU type used will always be a TrapPDU, regardless of whether the 953 value of snmpNotifyType is trap(1) or inform(2). 955 Note also that access control and notification filtering are 956 performed in the usual manner for notifications, regardless of the 957 SNMP message version to be used when sending a notification. The 958 parameters for performing access control are found in the usual 959 manner (i.e., from inspecting the SNMP-TARGET-MIB and SNMP- 960 NOTIFICATION-MIB). In particular, when generating an SNMPv1 Trap, in 961 order to perform the access check specified in [18], section 3.3, 962 bullet (3), the notification originator may need to generate a value 963 for snmpTrapOID.0 as described in section 3.1, bullets (2) and (3) of 964 this document. If the SNMPv1 notification parameters being used were 965 previously translated from a set of SNMPv2 notification parameters, 966 this value may already be known, in which case it need not be 967 generated. 969 4.1.4. Notification Receiver 971 There are no special requirements of a notification receiver. 972 However, an implementation may find it useful to allow a higher level 973 application to request whether notifications should be delivered to a 974 higher level application using SNMPv1 notification parameter or 975 SNMPv2 notification parameters. The notification receiver would then 976 translate notification parameters when required in order to present a 977 notification using the desired set of parameters. 979 4.2. Proxy Implementations 981 A proxy implementation may be used to enable communication between 982 entities which support different SNMP message versions. This is 983 accomplished in a proxy forwarder application by performing 984 translations on PDUs. These translations depend on the PDU type, the 985 SNMP version of the packet containing a received PDU, and the SNMP 986 version to be used to forward a received PDU. The following sections 987 describe these translations. In all cases other than those described 988 below, the proxy SHALL forward a received PDU without change, subject 989 to size contraints as defined in section 5.3 (Community MIB) of this 990 document. Note that in the following sections, the 'Upstream 991 Version' refers to the version used between the command generator and 992 the proxy, and the 'Downstream Version' refers to the version used 993 between the proxy and the command responder. 995 4.2.1. Upstream Version Greater Than Downstream Version 997 - If a GetBulkRequest-PDU is received and must be forwarded 998 using the SNMPv1 message version, the proxy forwarder SHALL 999 set the non-repeaters and max-repetitions fields to 0, and 1000 SHALL set the tag of the PDU to GetNextRequest-PDU. 1002 - If a GetResponse-PDU is received whose error-status field has 1003 a value of 'tooBig', the message will be forwarded using the 1004 SNMPv2c or SNMPv3 message version, and the original request 1005 received by the proxy was not a GetBulkRequest-PDU, the proxy 1006 forwarder SHALL remove the contents of the variable-bindings 1007 field before forwarding the response. 1009 - If a GetResponse-PDU is received whose error-status field has 1010 a value of 'tooBig,' and the message will be forwarded using 1011 the SNMPv2c or SNMPv3 message version, and the original 1012 request received by the proxy was a GetBulkRequest-PDU, the 1013 proxy forwarder SHALL re-send the forwarded request (which 1014 would have been altered to be a GetNextRequest-PDU) with all 1015 but the first variable-binding removed. The proxy forwarder 1016 SHALL only re-send such a request a single time. If the 1017 resulting GetResponse-PDU also contains an error-status field 1018 with a value of 'tooBig,' then the proxy forwarder SHALL 1019 remove the contents of the variable-bindings field, and change 1020 the error-status field to 'noError' before forwarding the 1021 response. Note that if the original request only contained a 1022 single variable-binding, the proxy may skip re-sending the 1023 request and simply remove the variable-bindings and change the 1024 error-status to 'noError.' 1026 - If a Trap-PDU is received, and will be forwarded using the 1027 SNMPv2c or SNMPv3 message version, the proxy SHALL apply the 1028 translation rules described in section 3, and SHALL forward 1029 the notification as an SNMPv2-Trap-PDU. 1031 Note that when an SNMPv1 agent generates a message containing 1032 a Trap-PDU which is subsequently forwarded by one or more 1033 proxy forwarders using SNMP versions other than SNMPv1, the 1034 community string and agent-addr fields from the original 1035 message generated by the SNMPv1 agent will be preserved 1036 through the use of the snmpTrapAddress and snmpTrapCommunity 1037 objects. 1039 4.2.2. Upstream Version Less Than Downstream Version 1041 - If a GetResponse-PDU is received in response to a GetRequest- 1042 PDU (previously generated by the proxy) which contains 1043 variable-bindings of type Counter64 or which contain an SNMPv2 1044 exception code, and the message would be forwarded using the 1045 SNMPv1 message version, the proxy MUST generate an alternate 1046 response PDU consisting of the request-id and variable 1047 bindings from the original SNMPv1 request, containing a 1048 noSuchName error-status value, and containing an error-index 1049 value indicating the position of the variable-binding 1050 containing the Counter64 type or exception code. 1052 - If a GetResponse-PDU is received in response to a 1053 GetNextRequest-PDU (previously generated by the proxy) which 1054 contains variable-bindings that contain an SNMPv2 exception 1055 code, and the message would be forwarded using the SNMPv1 1056 message version, the proxy MUST generate an alternate response 1057 PDU consisting of the request-id and variable bindings from 1058 the original SNMPv1 request, containing a noSuchName error- 1059 status value, and containing an error-index value indicating 1060 the position of the variable-binding containing the exception 1061 code. 1063 - If a GetResponse-PDU is received in response to a 1064 GetNextRequest-PDU (previously generated by the proxy) which 1065 contains variable-bindings of type Counter64, the proxy MUST 1066 re-send the entire GetNextRequest-PDU, with the following 1067 modifications. For any variable bindings in the received 1068 GetResponse which contained Counter64 types, the proxy 1069 substitutes the object names of these variable bindings for 1070 the corresponding object names in the previously-sent 1071 GetNextRequest. The proxy MUST repeat this process until no 1072 Counter64 objects are returned. Note that an implementation 1073 may attempt to optimize this process of skipping Counter64 1074 objects. One approach to such an optimization would be to 1075 replace the last sub-identifier of the object names of 1076 varbinds containing a Counter64 type with 65535 if that sub- 1077 identifier is less than 65535, or with 4294967295 if that 1078 sub-identifier is greater than 65535. This approach should 1079 skip multiple instances of the same Counter64 object, while 1080 maintaining compatibility with some broken agent 1081 implementations (which only use 16-bit integers for sub- 1082 identifiers). 1084 Deployment Hint: The process of repeated GetNext requests 1085 used by a proxy when Counter64 types are returned can be 1086 expensive. When deploying a proxy, this can be avoided by 1087 configuring the target agents to which the proxy forwards 1088 requests in a manner such that any objects of type Counter64 1089 are in fact not-in-view for the principal that the proxy is 1090 using when communicating with these agents. 1092 - If a GetResponse-PDU is received which contains an SNMPv2 1093 error-status value of wrongValue, wrongEncoding, wrongType, 1094 wrongLength, inconsistentValue, noAccess, notWritable, 1095 noCreation, inconsistentName, resourceUnavailable, 1096 commitFailed, undoFailed, or authorizationError, the error- 1097 status value is modified using the mappings in section 4.3. 1099 - If an SNMPv2-Trap-PDU is received, and will be forwarded using 1100 the SNMPv1 message version, the proxy SHALL apply the 1101 translation rules described in section 3, and SHALL forward 1102 the notification as a Trap-PDU. Note that if the translation 1103 fails due to the existence of a Counter64 data-type in the 1104 received SNMPv2-Trap-PDU, the trap cannot be forwarded using 1105 SNMPv1. 1107 - If an InformRequest-PDU is received, any configuration 1108 information indicating that it would be forwarded using the 1109 SNMPv1 message version SHALL be ignored. An InformRequest-PDU 1110 can only be forwarded using the SNMPv2c or SNMPv3 message 1111 version. The InformRequest-PDU may still be forwarded if 1112 there is other configuration information indicating that it 1113 should be forwarded using SNMPv2c or SNMPv3. 1115 4.3. Error Status Mappings 1117 The following tables shows the mappings of SNMPv1 error-status values 1118 into SNMPv2 error-status values, and the mappings of SNMPv2 error- 1119 status values into SNMPv1 error-status values. 1121 SNMPv1 error-status SNMPv2 error-status 1122 =================== =================== 1123 noError noError 1124 tooBig tooBig 1125 noSuchName noSuchName 1126 badValue badValue 1127 genErr genErr 1129 SNMPv2 error-status SNMPv1 error-status 1130 =================== =================== 1131 noError noError 1132 tooBig tooBig 1133 genErr genErr 1134 wrongValue badValue 1135 wrongEncoding badValue 1136 wrongType badValue 1137 wrongLength badValue 1138 inconsistentValue badValue 1139 noAccess noSuchName 1140 notWritable noSuchName 1141 noCreation noSuchName 1142 inconsistentName noSuchName 1143 resourceUnavailable genErr 1144 commitFailed genErr 1145 undoFailed genErr 1146 authorizationError noSuchName 1148 5. Message Processing Models and Security Models 1150 In order to adapt SNMPv1 (and SNMPv2c) into the SNMP architecture, 1151 the following models are defined in this document: 1153 - The SNMPv1 Message Processing Model 1155 - The SNMPv1 Community-Based Security Model 1157 The following models are also described in this document: 1159 - The SNMPv2c Message Processing Model 1161 - The SNMPv2c Community-Based Security Model 1163 In most respects, the SNMPv1 Message Processing Model and the 1164 SNMPv2c Message Processing Model are identical, and so these 1165 are not discussed independently in this document. Differences 1166 between the two models are described as required. 1168 Similarly, the SNMPv1 Community-Based Security Model and the 1169 SNMPv2c Community-Based Security Model are nearly identical, 1170 and so are not discussed independently. Differences between 1171 these two models are also described as required. 1173 5.1. Mappings 1175 The SNMPv1 (and SNMPv2c) Message Processing Model and Security Model 1176 require mappings between parameters used in SNMPv1 (and SNMPv2c) 1177 messages, and the version independent parameters used in the SNMP 1178 architecture [16]. The parameters which MUST be mapped consist of the 1179 SNMPv1 (and SNMPv2c) community name, and the SNMP securityName and 1180 contextEngineID/contextName pair. A MIB module (the SNMP-COMMUNITY-MIB) 1181 is provided in this document in order to perform these mappings. This 1182 MIB provides mappings in both directions, that is, a community name may 1183 be mapped to a securityName, contextEngineID, and contextName, or the 1184 combination of securityName, contextEngineID, and contextName may be 1185 mapped to a community name. 1187 5.2. The SNMPv1 MP Model and SNMPv1 Community-based Security Model 1189 The SNMPv1 Message Processing Model handles processing of SNMPv1 1190 messages. The processing of messages is handled generally in the 1191 same manner as described in RFC1157 [2], with differences and 1192 clarifications as described in the following sections. The 1193 SnmpMessageProcessingModel value for SNMPv1 is 0 (the value for 1194 SNMPv2c is 1). 1196 5.2.1. Processing An Incoming Request 1198 In RFC1157 [2], section 4.1, item (3) for an entity which receives a 1199 message, states that various parameters are passed to the 'desired 1200 authentication scheme.' The desired authentication scheme in this 1201 case is the SNMPv1 Community-Based Security Model, which will be 1202 called using the processIncomingMsg ASI. The parameters passed to 1203 this ASI are: 1205 - The messageProcessingModel, which will be 0 (or 1 for 1206 SNMPv2c). 1208 - The maxMessageSize, which should be the maximum size of a 1209 message that the receiving entity can generate (since there is 1210 no such value in the received message). 1212 - The securityParameters, which consist of the community string 1213 and the message's source and destination transport domains and 1214 addresses. 1216 - The securityModel, which will be 1 (or 2 for SNMPv2c). 1218 - The securityLevel, which will be noAuthNoPriv. 1220 - The wholeMsg and wholeMsgLength. 1222 The Community-Based Security Model will attempt to select a row in 1223 the snmpCommunityTable. This is done by performing a search through 1224 the snmpCommunityTable in lexicographic order. The first entry for 1225 which the following matching criteria are satisfied will be selected: 1227 - The community string is equal to the snmpCommunityName value. 1229 - If the snmpCommunityTransportTag is an empty string, it is 1230 ignored for the purpose of matching. If the 1231 snmpCommunityTransportTag is not an empty string, the 1232 transportDomain and transportAddress from which the message 1233 was received must match one of the entries in the 1234 snmpTargetAddrTable selected by the snmpCommunityTransportTag 1235 value. The snmpTargetAddrTMask object is used as described in 1236 section 5.3 when checking whether the transportDomain and 1237 transportAddress matches a entry in the snmpTargetAddrTable. 1239 If no such entry can be found, an authentication failure occurs as 1240 described in RFC1157 [2], and the snmpInBadCommunityNames counter is 1241 incremented. 1243 The parameters returned from the Community-Based Security Model are: 1245 - The securityEngineID, which will always be the local value of 1246 snmpEngineID.0. 1248 - The securityName. 1250 - The scopedPDU. Note that this parameter will actually consist 1251 of three values, the contextSnmpEngineID, the contextName, and 1252 the PDU. These must be separate values, since the first two 1253 do not actually appear in the message. 1255 - The maxSizeResponseScopedPDU. 1257 - The securityStateReference. 1259 The appropriate SNMP application will then be called (depending on 1260 the value of the contextEngineID and the request type in the PDU) 1261 using the processPdu ASI. The parameters passed to this ASI are: 1263 - The messageProcessingModel, which will be 0 (or 1 for 1264 SNMPv2c). 1266 - The securityModel, which will be 1 (or 2 for SNMPv2c). 1268 - The securityName, which was returned from the call to 1269 processIncomingMsg. 1271 - The securityLevel, which is noAuthNoPriv. 1273 - The contextEngineID, which was returned as part of the 1274 ScopedPDU from the call to processIncomingMsg. 1276 - The contextName, which was returned as part of the ScopedPDU 1277 from the call to processIncomingMsg. 1279 - The pduVersion, which should indicate an SNMPv1 version PDU 1280 (if the message version was SNMPv2c, this would be an SNMPv2 1281 version PDU). 1283 - The PDU, which was returned as part of the ScopedPDU from the 1284 call to processIncomingMsg. 1286 - The maxSizeResponseScopedPDU which was returned from the call 1287 to processIncomingMsg. 1289 - The stateReference which was returned from the call to 1290 processIncomingMsg. 1292 The SNMP application should process the request as described 1293 previously in this document. Note that access control is applied by 1294 an SNMPv3 command responder application as usual. The parameters as 1295 passed to the processPdu ASI will be used in calls to the 1296 isAccessAllowed ASI. 1298 5.2.2. Generating An Outgoing Response 1300 There is no special processing required for generating an outgoing 1301 response. However, the community string used in an outgoing response 1302 must be the same as the community string from the original request. 1303 The original community string MUST be present in the stateReference 1304 information of the original request. 1306 5.2.3. Generating An Outgoing Notification 1308 In a multi-lingual SNMP entity, the parameters used for generating 1309 notifications will be obtained by examining the SNMP-TARGET-MIB and 1310 SNMP-NOTIFICATION-MIB. These parameters will be passed to the SNMPv1 1311 Message Processing Model using the sendPdu ASI. The SNMPv1 Message 1312 Processing Model will attempt to locate an appropriate community 1313 string in the snmpCommunityTable based on the parameters passed to 1314 the sendPdu ASI. This is done by performing a search through the 1315 snmpCommunityTable in lexicographic order. The first entry for which 1316 the following matching criteria are satisfied will be selected: 1318 - The securityName must be equal to the 1319 snmpCommunitySecurityName value. 1321 - The contextEngineID must be equal to the 1322 snmpCommunityContextEngineID value. 1324 - The contextName must be equal to the snmpCommunityContextName 1325 value. 1327 - If the snmpCommunityTransportTag is an empty string, it is 1328 ignored for the purpose of matching. If the 1329 snmpCommunityTransportTag is not an empty string, the 1330 transportDomain and transportAddress must match one of the 1331 entries in the snmpTargetAddrTable selected by the 1332 snmpCommunityTransportTag value. 1334 If no such entry can be found, the notification is not sent. 1335 Otherwise, the community string used in the outgoing notification 1336 will be the value of the snmpCommunityName column of the selected 1337 row. 1339 5.3. The SNMP Community MIB Module 1341 The SNMP-COMMUNITY-MIB contains objects for mapping between community 1342 strings and version-independent SNMP message parameters. In 1343 addition, this MIB provides a mechanism for performing source address 1344 validation on incoming requests, and for selecting community strings 1345 based on target addresses for outgoing notifications. These two 1346 features are accomplished by providing a tag in the 1347 snmpCommunityTable which selects sets of entries in the 1348 snmpTargetAddrTable [18]. In addition, the SNMP-COMMUNITY-MIB 1349 augments the snmpTargetAddrTable with a transport address mask value 1350 and a maximum message size value. These values are used only where 1351 explicitly stated. In cases where the snmpTargetAddrTable is used 1352 without mention of these augmenting values, the augmenting values 1353 should be ignored. 1355 The mask value, snmpTargetAddrTMask, allows selected entries in the 1356 snmpTargetAddrTable to specify multiple addresses (rather than just a 1357 single address per entry). This would typically be used to specify a 1358 subnet in an snmpTargetAddrTable rather than just a single address. 1359 The mask value is used to select which bits of a transport address 1360 must match bits of the corresponding instance of 1361 snmpTargetAddrTAddress, in order for the transport address to match a 1362 particular entry in the snmpTargetAddrTable. The value of an 1363 instance of snmpTargetAddrTMask must always be an OCTET STRING whose 1364 length is either zero or the same as that of the corresponding 1365 instance of snmpTargetAddrTAddress. 1367 Note that the snmpTargetAddrTMask object is only used where 1368 explicitly stated. In particular, it is not used when generating 1369 notifications (i.e., when generating notifications, entries in the 1370 snmpTargetAddrTable only specify individual addresses). 1372 When checking whether a transport address matches an entry in the 1373 snmpTargetAddrTable, if the value of snmpTargetAddrTMask is a zero- 1374 length OCTET STRING, the mask value is ignored, and the value of 1375 snmpTargetAddrTAddress must exactly match a transport address. 1376 Otherwise, each bit of each octet in the snmpTargetAddrTMask value 1377 corresponds to the same bit of the same octet in the 1378 snmpTargetAddrTAddress value. For bits that are set in the 1379 snmpTargetAddrTMask value (i.e., bits equal to 1), the corresponding 1380 bits in the snmpTargetAddrTAddress value must match the bits in a 1381 transport address. If all such bits match, the transport address is 1382 matched by that snmpTargetAddrTable entry. Otherwise, the transport 1383 address is not matched. 1385 The maximum message size value, snmpTargetAddrMMS, is used to 1386 determine the maximum message size acceptable to another SNMP entity 1387 when the value cannot be determined from the protocol. 1389 SNMP-COMMUNITY-MIB DEFINITIONS ::= BEGIN 1391 IMPORTS 1392 IpAddress, 1393 MODULE-IDENTITY, 1394 OBJECT-TYPE, 1395 Integer32, 1396 snmpModules 1397 FROM SNMPv2-SMI 1398 RowStatus, 1399 StorageType 1400 FROM SNMPv2-TC 1401 SnmpAdminString, 1402 SnmpEngineID 1403 FROM SNMP-FRAMEWORK-MIB 1404 SnmpTagValue, 1405 snmpTargetAddrEntry 1406 FROM SNMP-TARGET-MIB 1407 MODULE-COMPLIANCE, 1408 OBJECT-GROUP 1409 FROM SNMPv2-CONF; 1411 snmpCommunityMIB MODULE-IDENTITY 1412 LAST-UPDATED "199910050000Z" -- 5 Oct 1999, midnight 1413 ORGANIZATION "SNMPv3 Working Group" 1414 CONTACT-INFO "WG-email: snmpv3@lists.tislabs.com 1415 Subscribe: majordomo@lists.tislabs.com 1416 In msg body: subscribe snmpv3 1418 Chair: Russ Mundy 1419 TIS Labs at Network Associates 1421 Postal: 3060 Washington Rd 1422 Glenwood MD 21738 1423 USA 1424 Email: mundy@tislabs.com 1425 Phone: +1-301-854-6889 1427 Co-editor: Rob Frye 1428 CoSine Communications 1429 Postal: 1200 Bridge Parkway 1430 Redwood City, CA 94065 1431 USA 1432 E-mail: rfrye@cosinecom.com 1433 Phone: +1 650 637 4777 1435 Co-editor: David B. Levi 1436 Nortel Networks 1437 Postal: 3505 Kesterwood Drive 1438 Knoxville, TN 37918 1439 E-mail: dlevi@nortelnetworks.com 1440 Phone: +1 423 686 0432 1442 Co-editor: Shawn A. Routhier 1443 Integrated Systems Inc. 1444 Postal: 333 North Ave 4th Floor 1445 Wakefield, MA 01880 1446 E-mail: sar@epilogue.com 1447 Phone: +1 781 245 0804 1449 Co-editor: Bert Wijnen 1450 IBM T. J. Watson Research 1451 Postal: Schagen 33 1452 3461 GL Linschoten 1453 Netherlands 1454 Email: wijnen@vnet.ibm.com 1455 Phone: +31-348-432-794 1456 " 1458 DESCRIPTION 1459 "This MIB module defines objects to help support coexistence 1460 between SNMPv1, SNMPv2c, and SNMPv3." 1461 REVISION "199905130000Z" -- 13 May 1999 1462 DESCRIPTION "The Initial Revision" 1463 REVISION "199910050000Z" -- 5 Oct 1999 (same as LAST-UPDATED) 1464 DESCRIPTION "This version published as RFC xxxx" 1465 -- RFC-editor assigns xxxx 1466 ::= { snmpModules 18 } 1468 -- Administrative assignments **************************************** 1470 snmpCommunityMIBObjects OBJECT IDENTIFIER ::= { snmpCommunityMIB 1 } 1471 snmpCommunityMIBConformance OBJECT IDENTIFIER ::= { snmpCommunityMIB 2 } 1473 -- 1474 -- The snmpCommunityTable contains a database of community strings. 1475 -- This table provides mappings between community strings, and the 1476 -- parameters required for View-based Access Control. 1477 -- 1479 snmpCommunityTable OBJECT-TYPE 1480 SYNTAX SEQUENCE OF SnmpCommunityEntry 1481 MAX-ACCESS not-accessible 1482 STATUS current 1483 DESCRIPTION 1484 "The table of community strings configured in the SNMP 1485 engine's Local Configuration Datastore (LCD)." 1486 ::= { snmpCommunityMIBObjects 1 } 1488 snmpCommunityEntry OBJECT-TYPE 1489 SYNTAX SnmpCommunityEntry 1490 MAX-ACCESS not-accessible 1491 STATUS current 1492 DESCRIPTION 1493 "Information about a particular community string." 1494 INDEX { IMPLIED snmpCommunityIndex } 1495 ::= { snmpCommunityTable 1 } 1497 SnmpCommunityEntry ::= SEQUENCE { 1498 snmpCommunityIndex SnmpAdminString, 1499 snmpCommunityName OCTET STRING, 1500 snmpCommunitySecurityName SnmpAdminString, 1501 snmpCommunityContextEngineID SnmpEngineID, 1502 snmpCommunityContextName SnmpAdminString, 1503 snmpCommunityTransportTag SnmpTagValue, 1504 snmpCommunityStorageType StorageType, 1505 snmpCommunityStatus RowStatus 1506 } 1508 snmpCommunityIndex OBJECT-TYPE 1509 SYNTAX SnmpAdminString (SIZE(1..32)) 1510 MAX-ACCESS not-accessible 1511 STATUS current 1512 DESCRIPTION 1513 "The unique index value of a row in this table." 1514 ::= { snmpCommunityEntry 1 } 1516 snmpCommunityName OBJECT-TYPE 1517 SYNTAX OCTET STRING 1518 MAX-ACCESS read-create 1519 STATUS current 1520 DESCRIPTION 1521 "The community string for which a row in this table 1522 represents a configuration." 1523 ::= { snmpCommunityEntry 2 } 1525 snmpCommunitySecurityName OBJECT-TYPE 1526 SYNTAX SnmpAdminString (SIZE(1..32)) 1527 MAX-ACCESS read-create 1528 STATUS current 1529 DESCRIPTION 1530 "A human readable string representing the corresponding 1531 value of snmpCommunityName in a Security Model 1532 independent format." 1533 ::= { snmpCommunityEntry 3 } 1535 snmpCommunityContextEngineID OBJECT-TYPE 1536 SYNTAX SnmpEngineID 1537 MAX-ACCESS read-create 1538 STATUS current 1539 DESCRIPTION 1540 "The contextEngineID indicating the location of the 1541 context in which management information is accessed 1542 when using the community string specified by the 1543 corresponding instance of snmpCommunityName. 1545 The default value is the snmpEngineID of the entity in 1546 which this object is instantiated." 1547 ::= { snmpCommunityEntry 4 } 1549 snmpCommunityContextName OBJECT-TYPE 1550 SYNTAX SnmpAdminString (SIZE(0..32)) 1551 MAX-ACCESS read-create 1552 STATUS current 1553 DESCRIPTION 1554 "The context in which management information is accessed 1555 when using the community string specified by the corresponding 1556 instance of snmpCommunityName." 1557 DEFVAL { ''H } -- the empty string 1558 ::= { snmpCommunityEntry 5 } 1560 snmpCommunityTransportTag OBJECT-TYPE 1561 SYNTAX SnmpTagValue 1562 MAX-ACCESS read-create 1563 STATUS current 1564 DESCRIPTION 1565 "This object specifies a set of transport endpoints 1566 from which a command responder application will accept 1567 management requests. If a management request containing 1568 this community is received on a transport endpoint other 1569 than the transport endpoints identified by this object, 1570 the request is deemed unauthentic. 1572 The transports identified by this object are specified 1573 in the snmpTargetAddrTable. Entries in that table 1574 whose snmpTargetAddrTagList contains this tag value 1575 are identified. 1577 If the value of this object has zero-length, transport 1578 endpoints are not checked when authenticating messages 1579 containing this community string." 1580 DEFVAL { ''H } -- the empty string 1581 ::= { snmpCommunityEntry 6 } 1583 snmpCommunityStorageType OBJECT-TYPE 1584 SYNTAX StorageType 1585 MAX-ACCESS read-create 1586 STATUS current 1587 DESCRIPTION 1588 "The storage type for this conceptual row in the 1589 snmpCommunityTable. Conceptual rows having the value 1590 'permanent' need not allow write-access to any 1591 columnar object in the row." 1592 ::= { snmpCommunityEntry 7 } 1594 snmpCommunityStatus OBJECT-TYPE 1595 SYNTAX RowStatus 1596 MAX-ACCESS read-create 1597 STATUS current 1598 DESCRIPTION 1599 "The status of this conceptual row in the snmpCommunityTable. 1601 An entry in this table is not qualified for activation 1602 until instances of all corresponding columns have been 1603 initialized, either through default values, or through 1604 Set operations. The snmpCommunityName and 1605 snmpCommunitySecurityName objects must be explicitly set. 1607 There is no restriction on setting columns in this table 1608 when the value of snmpCommunityStatus is active(1)." 1609 ::= { snmpCommunityEntry 8 } 1611 -- 1612 -- The snmpTargetAddrExtTable 1613 -- 1615 snmpTargetAddrExtTable OBJECT-TYPE 1616 SYNTAX SEQUENCE OF SnmpTargetAddrExtEntry 1617 MAX-ACCESS not-accessible 1618 STATUS current 1619 DESCRIPTION 1620 "The table of mask and mms values associated with the 1621 snmpTargetAddrTable. 1623 The snmpTargetAddrExtTable augments the 1624 snmpTargetAddrTable with a transport address mask value 1625 and a maximum message size value. The transport address 1626 mask allows entries in the snmpTargetAddrTable to define 1627 a set of addresses instead of just a single address. 1628 The maximum message size value allows the maximum 1629 message size of another SNMP entity to be configured for 1630 use in SNMPv1 (and SNMPv2c) transactions, where the 1631 message format does not specify a maximum message size." 1632 ::= { snmpCommunityMIBObjects 2 } 1634 snmpTargetAddrExtEntry OBJECT-TYPE 1635 SYNTAX SnmpTargetAddrExtEntry 1636 MAX-ACCESS not-accessible 1637 STATUS current 1638 DESCRIPTION 1639 "Information about a particular mask and mms value." 1640 AUGMENTS { snmpTargetAddrEntry } 1641 ::= { snmpTargetAddrExtTable 1 } 1643 SnmpTargetAddrExtEntry ::= SEQUENCE { 1644 snmpTargetAddrTMask OCTET STRING, 1645 snmpTargetAddrMMS Integer32 1646 } 1648 snmpTargetAddrTMask OBJECT-TYPE 1649 SYNTAX OCTET STRING (SIZE (0..255)) 1650 MAX-ACCESS read-create 1651 STATUS current 1652 DESCRIPTION 1653 "The mask value associated with an entry in the 1654 snmpTargetAddrTable. The value of this object must 1655 have the same length as the corresponding instance of 1656 snmpTargetAddrTAddress, or must have length 0. An 1657 attempt to set it to any other value will result in 1658 an inconsistentValue error. 1660 The value of this object allows an entry in the 1661 snmpTargetAddrTable to specify multiple addresses. 1662 The mask value is used to select which bits of 1663 a transport address must match bits of the corresponding 1664 instance of snmpTargetAddrTAddress, in order for the 1665 transport address to match a particular entry in the 1666 snmpTargetAddrTable. Bits which are 1 in the mask 1667 value indicate bits in the transport address which 1668 must match bits in the snmpTargetAddrTAddress value. 1669 Bits which are 0 in the mask indicate bits in the 1670 transport address which need not match. If the 1671 length of the mask is 0, the mask should be treated 1672 as if all its bits were 1 and its length were equal 1673 to the length of the corresponding value of 1674 snmpTargetAddrTable. 1676 This object may not be modified while the value of the 1677 corresponding instance of snmpTargetAddrRowStatus is 1678 active(1). An attempt to set this object in this case 1679 will result in an inconsistentValue error." 1680 DEFVAL { ''H } 1681 ::= { snmpTargetAddrExtEntry 1 } 1683 snmpTargetAddrMMS OBJECT-TYPE 1684 SYNTAX Integer32 (0|484..2147483647) 1685 MAX-ACCESS read-create 1686 STATUS current 1687 DESCRIPTION 1688 "The maximum message size value associated with an entry 1689 in the snmpTargetAddrTable." 1690 DEFVAL { 484 } 1691 ::= { snmpTargetAddrExtEntry 2 } 1693 -- 1694 -- The snmpTrapAddress and snmpTrapCommunity objects are included 1695 -- in notifications that are forwarded by a proxy, which were 1696 -- originally received as SNMPv1 Trap messages. 1697 -- 1699 snmpTrapAddress OBJECT-TYPE 1700 SYNTAX IpAddress 1701 MAX-ACCESS accessible-for-notify 1702 STATUS current 1703 DESCRIPTION 1704 "The value of the agent-addr field of a Trap PDU which 1705 is forwarded by a proxy forwarder application using 1706 an SNMP version other than SNMPv1. The value of this 1707 object SHOULD contain the value of the agent-addr field 1708 from the original Trap PDU as generated by an SNMPv1 1709 agent." 1710 ::= { snmpCommunityMIBObjects 3 } 1712 snmpTrapCommunity OBJECT-TYPE 1713 SYNTAX OCTET STRING 1714 MAX-ACCESS accessible-for-notify 1715 STATUS current 1716 DESCRIPTION 1717 "The value of the community string field of an SNMPv1 1718 message containing a Trap PDU which is forwarded by a 1719 a proxy forwarder application using an SNMP version 1720 other than SNMPv1. The value of this object SHOULD 1721 contain the value of the community string field from 1722 the original SNMPv1 message containing a Trap PDU as 1723 generated by an SNMPv1 agent." 1724 ::= { snmpCommunityMIBObjects 4 } 1726 -- Conformance Information ******************************************* 1728 snmpCommunityMIBCompliances OBJECT IDENTIFIER 1729 ::= { snmpCommunityMIBConformance 1 } 1730 snmpCommunityMIBGroups OBJECT IDENTIFIER 1731 ::= { snmpCommunityMIBConformance 2 } 1733 -- Compliance statements 1735 snmpCommunityMIBCompliance MODULE-COMPLIANCE 1736 STATUS current 1737 DESCRIPTION 1738 "The compliance statement for SNMP engines which 1739 implement the SNMP-COMMUNITY-MIB." 1741 MODULE -- this module 1742 MANDATORY-GROUPS { snmpCommunityGroup } 1744 OBJECT snmpCommunityName 1745 MIN-ACCESS read-only 1746 DESCRIPTION "Write access is not required." 1748 OBJECT snmpCommunitySecurityName 1749 MIN-ACCESS read-only 1750 DESCRIPTION "Write access is not required." 1751 OBJECT snmpCommunityContextEngineID 1752 MIN-ACCESS read-only 1753 DESCRIPTION "Write access is not required." 1755 OBJECT snmpCommunityContextName 1756 MIN-ACCESS read-only 1757 DESCRIPTION "Write access is not required." 1759 OBJECT snmpCommunityTransportTag 1760 MIN-ACCESS read-only 1761 DESCRIPTION "Write access is not required." 1763 OBJECT snmpCommunityStorageType 1764 MIN-ACCESS read-only 1765 DESCRIPTION "Write access is not required." 1767 OBJECT snmpCommunityStatus 1768 MIN-ACCESS read-only 1769 DESCRIPTION "Write access is not required." 1771 ::= { snmpCommunityMIBCompliances 1 } 1773 snmpProxyTrapForwardCompliance MODULE-COMPLIANCE 1774 STATUS current 1775 DESCRIPTION 1776 "The compliance statement for SNMP engines which 1777 contain a proxy forwarding application which is 1778 capable of forwarding SNMPv1 traps using SNMPv2c 1779 or SNMPv3." 1780 MODULE -- this module 1781 MANDATORY-GROUPS { snmpProxyTrapForwardGroup } 1782 ::= { snmpCommunityMIBCompliances 2 } 1784 snmpCommunityGroup OBJECT-GROUP 1785 OBJECTS { 1786 snmpCommunityName, 1787 snmpCommunitySecurityName, 1788 snmpCommunityContextEngineID, 1789 snmpCommunityContextName, 1790 snmpCommunityTransportTag, 1791 snmpCommunityStorageType, 1792 snmpCommunityStatus, 1793 snmpTargetAddrTMask, 1794 snmpTargetAddrMMS 1795 } 1796 STATUS current 1797 DESCRIPTION 1798 "A collection of objects providing for configuration 1799 of community strings for SNMPv1 (and SNMPv2c) usage." 1800 ::= { snmpCommunityMIBGroups 1 } 1802 snmpProxyTrapForwardGroup OBJECT-GROUP 1803 OBJECTS { 1804 snmpTrapAddress, 1805 snmpTrapCommunity 1806 } 1807 STATUS current 1808 DESCRIPTION 1809 "Objects which are used by proxy forwarding applications 1810 when translating traps between SNMP versions. These are 1811 used to preserve SNMPv1-specific information when 1812 translating to SNMPv2c or SNMPv3." 1813 ::= { snmpCommunityMIBGroups 3 } 1815 END 1817 6. Intellectual Property 1819 The IETF takes no position regarding the validity or scope of any 1820 intellectual property or other rights that might be claimed to 1821 pertain to the implementation or use of the technology described in 1822 this document or the extent to which any license under such rights 1823 might or might not be available; neither does it represent that it 1824 has made any effort to identify any such rights. Information on the 1825 IETF's procedures with respect to rights in standards-track and 1826 standards-related documentation can be found in BCP-11. Copies of 1827 claims of rights made available for publication and any assurances of 1828 licenses to be made available, or the result of an attempt made to 1829 obtain a general license or permission for the use of such 1830 proprietary rights by implementors or users of this specification can 1831 be obtained from the IETF Secretariat. 1833 The IETF invites any interested party to bring to its attention any 1834 copyrights, patents or patent applications, or other proprietary 1835 rights which may cover technology that may be required to practice 1836 this standard. Please address the information to the IETF Executive 1837 Director. 1839 7. Acknowledgments 1841 This document is the result of the efforts of the SNMPv3 Working 1842 Group. The design of the SNMP-COMMUNITY-MIB incorporates work done 1843 by the authors of SNMPv2*: 1845 Jeff Case (SNMP Research, Inc.) 1846 David Harrington (Cabletron Systems Inc.) 1847 David Levi (SNMP Research, Inc.) 1848 Brian O'Keefe (Hewlett Packard) 1849 Jon Saperia (IronBridge Networks, Inc.) 1850 Steve Waldbusser (International Network Services) 1852 8. Security Considerations 1854 Although SNMPv1 and SNMPv2 do not provide any security, allowing 1855 community names to be mapped into securityName/contextName provides 1856 the ability to use view-based access control to limit the access of 1857 unsecured SNMPv1 and SNMPv2 operations. In fact, it is important for 1858 network administrators to make use of this capability in order to 1859 avoid unauthorized access to MIB data that would otherwise be secure. 1861 Further, the SNMP-COMMUNITY-MIB has the potential to expose community 1862 strings which provide access to more information than that which is 1863 available using the usual 'public' community string. For this 1864 reason, a security administrator may wish to limit accessibility to 1865 the SNMP-COMMUNITY-MIB, and in particular, to make it inaccessible 1866 when using the 'public' community string. 1868 When a proxy implementation translates messages between SNMPv1 (or 1869 SNMPv2c) and SNMPv3, there may be a loss of security. For example, 1870 an SNMPv3 message received using authentication and privacy which is 1871 subsequently forwarded using SNMPv1 will lose the security benefits 1872 of using authentication and privacy. Careful configuration of 1873 proxies is required to address such situations. One approach to deal 1874 with such situations might be to use an encrypted tunnel. 1876 9. References 1878 [1] Rose, M. and K. McCloghrie, "Structure and Identification of 1879 Management Information for TCP/IP-based internets"", STD16, RFC 1880 1155, May 1990. 1882 [2] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1883 Management Protocol", STD15, RFC 1157, SNMP Research, Performance 1884 Systems International, Performance Systems International, MIT 1885 Laboratory for Computer Science, May 1990. 1887 [3] McCloghrie, K., and M. Rose, Editors, "Concise MIB Definitions", 1888 STD 16, RFC 1212, Hughes LAN Systems, Performance Systems 1889 International, March 1991. 1891 [4] Rose, M. T., "A Convention for Defining Traps for use with the 1892 SNMP", RFC 1215, March 1991. 1894 [5] McCloghrie, K., and M. Rose, "A Convention for Describing SNMP- 1895 based Agents", RFC 1303, Hughes LAN Systems, Dover Beach 1896 Consulting, Inc., February 1992. 1898 [6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1899 Waldbusser, "Introduction to Community-based SNMPv2", RFC1901, SNMP 1900 Research,Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1901 International Network Services, January 1996. 1903 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1904 and S. Waldbusser, "Structure of Management Information Version 2 1905 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 1906 Braunschweig, SNMP Research, First Virtual Holdings, International 1907 Network Services, April 1999. 1909 [8] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1910 and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 1911 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 1912 Virtual Holdings, International Network Services, April 1999. 1914 [9] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1915 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, 1916 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 1917 First Virtual Holdings, International Network Services, April 1999. 1919 [10] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1920 Waldbusser, "Protocol Operations for Version 2 of the Simple 1921 Network Management Protocol (SNMPv2)", RFC1905, SNMP Research,Inc., 1922 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1923 Network Services, January 1996. 1925 [11] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport 1926 Mappings for Version 2 of the Simple Network Management Protocol 1927 (SNMPv2)", RFC 1906, January 1996. 1929 [12] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1930 Waldbusser, "Management Information Base for Version 2 of the 1931 Simple Network Management Protocol (SNMPv2)", RFC1907, SNMP 1932 Research,Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1933 International Network Services, January 1996. 1935 [13] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1936 Waldbusser, "Coexistence between Version 1 and Version 2 of the 1937 Internet-standard Network Management Framework", RFC1908, SNMP 1938 Research,Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1939 International Network Services, January 1996. 1941 [14] Levi, D., Wijnen, B., "Mapping SNMPv2 onto SNMPv1 within a bi- 1942 lingual SNMP agent", RFC2089, SNMP Research, Inc., IBM, January 1943 1997. 1945 [15] Bradner, S., "Key words for use in RFCs to Indicate Requirement 1946 Levels", BCP 14, RFC 2119, March 1997. 1948 [16] The SNMPv3 Working Group, Harrington, D., Wijnen, B., "An 1949 Architecture for Describing SNMP Management Frameworks", RFC 2571, 1950 May 1999. 1952 [17] The SNMPv3 Working Group, Case, J., Harrington, D., Wijnen, B., 1953 "Message Processing and Dispatching for the Simple Network 1954 Management Protocol (SNMP)", RFC 2572, May 1999. 1956 [18] The SNMPv3 Working Group, Levi, D., Meyer, P., Stewart, B., "SNMP 1957 Applications", RFC2573, May 1999. 1959 [19] The SNMPv3 Working Group, Blumenthal, U., Wijnen, B., "The User- 1960 Based Security Model for Version 3 of the Simple Network Management 1961 Protocol (SNMP)", RFC 2574, May 1999. 1963 [20] The SNMPv3 Working Group, Wijnen, B., Presuhn, R., McCloghrie, K., 1964 "View-based Access Control Model for the Simple Network Management 1965 Protocol (SNMP)", RFC 2575, May 1999. 1967 10. Editor's Address 1969 Rob Frye 1970 MCI WorldCom 1971 2100 Reston Parkway, Suite 600 1972 Reston, VA 20191 1973 U.S.A. 1974 Phone: +1 703 715 7225 1975 EMail: Rob.Frye@wcom.com 1977 David B. Levi 1978 Nortel Networks 1979 3505 Kesterwood Drive 1980 Knoxville, TN 37918 1981 U.S.A. 1982 Phone: +1 423 686 0432 1983 EMail: dlevi@nortelnetworks.com 1985 Shawn A. Routhier 1986 Integrated Systems Inc. 1987 333 North Ave 4th Floor 1988 Wakefield MA 01880 1989 U.S.A. 1990 Phone: + 1 781 245 0804 1991 EMail: sar@epilogue.com 1993 Bert Wijnen 1994 IBM T. J. Watson Research 1995 Schagen 33 1996 3461 GL Linschoten 1997 Netherlands 1998 Phone: +31 348 432 794 1999 EMail: wijnen@vnet.ibm.com 2001 A. Full Copyright Statement 2003 This document and translations of it may be copied and furnished to 2004 others, and derivative works that comment on or otherwise explain it 2005 or assist in its implementation may be prepared, copied, published 2006 and distributed, in whole or in part, without restriction of any 2007 kind, provided that the above copyright notice and this paragraph are 2008 included on all such copies and derivative works. However, this 2009 document itself may not be modified in any way, such as by removing 2010 the copyright notice or references to the Internet Society or other 2011 Internet organizations, except as needed for the purpose of 2012 developing Internet standards in which case the procedures for 2013 copyrights defined in the Internet Standards process must be 2014 followed, or as required to translate it into languages other than 2015 English. 2017 The limited permissions granted above are perpetual and will not be 2018 revoked by the Internet Society or its successors or assigns. 2020 This document and the information contained herein is provided on an 2021 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2022 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2023 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2024 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2025 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.