idnits 2.17.1 draft-ietf-atommib-atmacct-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There is 1 instance of too long lines in the document, the longest one being 3 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (4 October 1998) is 9334 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) == Unused Reference: '17' is defined on line 603, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2271 (ref. '1') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Obsolete normative reference: RFC 1902 (ref. '5') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '6') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '7') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2272 (ref. '11') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2274 (ref. '12') (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. '14') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2275 (ref. '15') (Obsoleted by RFC 2575) == Outdated reference: A later version (-09) exists of draft-ietf-atommib-atm2TC-08 Summary: 23 errors (**), 0 flaws (~~), 4 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force Keith McCloghrie 2 INTERNET DRAFT Cisco Systems, Inc. 3 Expires April 1999 Juha Heinanen 4 Telia Finland, Inc. 5 Wedge Greene 6 MCI Telecommunications Corp. 7 Anil Prasad 8 Cisco Systems, Inc. 9 4 October 1998 11 Accounting Information for ATM Networks 13 draft-ietf-atommib-atmacct-03.txt 15 Status of this Memo 17 This document is an Internet-Draft. Internet-Drafts are working 18 documents of the Internet Engineering Task Force (IETF), its areas, and 19 its working groups. Note that other groups may also distribute working 20 documents as Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet- Drafts as reference material 25 or to cite them other than as ``work in progress.'' 27 To learn the current status of any Internet-Draft, please check the 28 ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow 29 Directories on ftp.ietf.org (US East Coast), nic.nordu.net (Europe), 30 ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 32 Copyright Notice 34 Copyright (C) The Internet Society (1998). All Rights Reserved. 36 1. Introduction 38 This memo defines a portion of the Management Information Base (MIB) for 39 use with network management protocols in the Internet community. A 40 separate memo [16] defines managed objects, in a manner independent of 41 the type of network, for controlling the selection, collection and 42 storage of accounting information into files for later retrieval via a 43 file transfer protocol. This memo defines a set of ATM-specific 44 accounting information which can be collected for connections on ATM 45 networks. 47 2. The SNMP Network Management Framework 49 The SNMP Management Framework presently consists of five major 50 components: 52 o An overall architecture, described in RFC 2271 [1]. 54 o Mechanisms for describing and naming objects and events for the 55 purpose of management. The first version of this Structure of 56 Management Information (SMI) is called SMIv1 and described in RFC 57 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 58 called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 59 1904 [7]. 61 o Message protocols for transferring management information. The 62 first version of the SNMP message protocol is called SNMPv1 and 63 described in RFC 1157 [8]. A second version of the SNMP message 64 protocol, which is not an Internet standards track protocol, is 65 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 66 The third version of the message protocol is called SNMPv3 and 67 described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. 69 o Protocol operations for accessing management information. The 70 first set of protocol operations and associated PDU formats is 71 described in RFC 1157 [8]. A second set of protocol operations and 72 associated PDU formats is described in RFC 1905 [13]. 74 o A set of fundamental applications described in RFC 2273 [14] and 75 the view-based access control mechanism described in RFC 2275 [15]. 77 Managed objects are accessed via a virtual information store, termed the 78 Management Information Base or MIB. Objects in the MIB are defined 79 using the mechanisms defined in the SMI. 81 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 82 conforming to the SMIv1 can be produced through the appropriate 83 translations. The resulting translated MIB must be semantically 84 equivalent, except where objects or events are omitted because no 85 translation is possible (e.g., use of Counter64). Some machine readable 86 information in SMIv2 will be converted into textual descriptions in 87 SMIv1 during the translation process. However, this loss of machine 88 readable information is not considered to change the semantics of the 89 MIB. 91 3. Overview 93 In [16], the items of accounting data to be collected are specified as a 94 set of objects. Which objects are contained in such a set is selectable 95 by an administrator through the specification of one or more (subtree, 96 list) tuples, where the set of objects to be collected is the union of 97 the subsets specified by each tuple: 99 'subtree' specifies a OBJECT IDENTIFIER value such that every object 100 in the subset is named by the subtree's value appended with a 101 single additional sub-identifier. 103 'list' specifies an OCTET STRING value, such that if the N-th bit of 104 the string's value is set then the the subset contains the 105 object named by appending N as a single additional sub- 106 identifier to the subtree. 108 This memo specifies such a subtree containing a set of objects defining 109 items of accounting information which are applicable to ATM connections. 111 Note that all of the objects defined here have a MAX-ACCESS clause of 112 not-accessible, since their purpose is not to be read/written by SNMP, 113 but rather, to be the syntax and semantics of the set of information 114 which can be represented within a single (subtree, list) tuple. 116 4. Definitions 118 ATM-ACCOUNTING-INFORMATION-MIB DEFINITIONS ::= BEGIN 120 IMPORTS 121 MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, 122 mib-2, Integer32, Counter64 FROM SNMPv2-SMI 123 DisplayString, DateAndTime FROM SNMPv2-TC 124 AtmAddr FROM ATM-TC-MIB; 126 atmAccountingInformationMIB MODULE-IDENTITY 127 LAST-UPDATED "9611052000Z" 128 ORGANIZATION "IETF AToM MIB Working Group" 129 CONTACT-INFO " 130 Keith McCloghrie 131 Cisco Systems, Inc. 132 170 West Tasman Drive, 133 San Jose CA 95134-1706. 134 Phone: +1 408 526 5260 135 Email: kzm@cisco.com" 136 DESCRIPTION 137 "The MIB module for identifying items of accounting 138 information which are applicable to ATM connections." 139 ::= { mib-2 xx } -- to be filled in by IANA 141 atmAcctngMIBObjects OBJECT IDENTIFIER ::= { atmAccountingInformationMIB 1 } 143 -- Definitions of objects for use in specifying ATM accounting 144 -- data to be collected 146 atmAcctngDataObjects OBJECT-IDENTITY 147 STATUS current 148 DESCRIPTION 149 "This identifier defines a subtree under which various 150 objects are defined such that a set of objects to be 151 collected as ATM accounting data can be specified as a 152 (subtree, list) tuple using this identifier as the subtree." 153 ::= { atmAcctngMIBObjects 1 } 155 -- Objects defined under the atmAcctngDataObjects subtree 156 -- 157 -- In each case the semantics of the object are interpreted with 158 -- respect to the creation/storage of an accounting record for a 159 -- particular connection on a particular interface. 161 atmAcctngConnectionType OBJECT-TYPE 162 SYNTAX INTEGER { pvc(1), 163 pvp(2), 164 svcIncoming(3), 165 svcOutgoing(4), 166 svpIncoming(5), 167 svpOutgoing(6), 168 spvcInitiator(7), 169 spvcTarget(8), 170 spvpInitiator(9), 171 spvpTarget(10) } 172 MAX-ACCESS not-accessible 173 STATUS current 174 DESCRIPTION 175 "The type of connection." 176 ::= { atmAcctngDataObjects 1 } 178 atmAcctngCastType OBJECT-TYPE 179 SYNTAX INTEGER { p2p(1), p2mp(2) } 180 MAX-ACCESS not-accessible 181 STATUS current 182 DESCRIPTION 183 "An indication of whether the connection is point-to-point 184 or point-to-multipoint." 185 ::= { atmAcctngDataObjects 2 } 187 atmAcctngIfName OBJECT-TYPE 188 SYNTAX DisplayString 189 MAX-ACCESS not-accessible 190 STATUS current 191 DESCRIPTION 192 "A textual name for the interface on which the data for the 193 connection was collected. If the local SNMP agent supports 194 the object ifName, the value of this object must be 195 identical to that of ifName in the conceptual row of the 196 ifTable corresponding to this interface." 197 ::= { atmAcctngDataObjects 3 } 199 atmAcctngIfAlias OBJECT-TYPE 200 SYNTAX DisplayString 201 MAX-ACCESS not-accessible 202 STATUS current 203 DESCRIPTION 204 "The 'alias' name for the interface as specified by a 205 network manager, e.g., via a management set operation to 206 modify the relevant instance of the ifAlias object. Note 207 that in contrast to ifIndex, ifAlias provides a non-volatile 208 'handle' for the interface, the value of which is retained 209 across agent reboots." 210 ::= { atmAcctngDataObjects 4 } 212 atmAcctngVpi OBJECT-TYPE 213 SYNTAX INTEGER (0..4095) 214 MAX-ACCESS not-accessible 215 STATUS current 216 DESCRIPTION 217 "The VPI used for the connection." 218 ::= { atmAcctngDataObjects 5 } 220 atmAcctngVci OBJECT-TYPE 221 SYNTAX INTEGER (0..65535) 222 MAX-ACCESS not-accessible 223 STATUS current 224 DESCRIPTION 225 "The VCI used for the connection." 226 ::= { atmAcctngDataObjects 6 } 228 atmAcctngCallingParty OBJECT-TYPE 229 SYNTAX AtmAddr 230 MAX-ACCESS not-accessible 231 STATUS current 232 DESCRIPTION 233 "The connection's calling party. If unknown (e.g., for a 234 PVC), then the value of this object is the zero-length 235 string." 236 ::= { atmAcctngDataObjects 7 } 238 atmAcctngCalledParty OBJECT-TYPE 239 SYNTAX AtmAddr 240 MAX-ACCESS not-accessible 241 STATUS current 242 DESCRIPTION 243 "The connection's called party. If unknown (e.g., for a 244 PVC), then the value of this object is the zero-length 245 string." 246 ::= { atmAcctngDataObjects 8 } 248 atmAcctngCallReference OBJECT-TYPE 249 SYNTAX OCTET STRING (SIZE(0..3)) 250 MAX-ACCESS not-accessible 251 STATUS current 252 DESCRIPTION 253 "The connection's call reference value (e.g., from Q.2931). 254 If unknown (e.g., for a PVC), then the value of this object 255 is the zero-length string." 256 ::= { atmAcctngDataObjects 9 } 258 atmAcctngStartTime OBJECT-TYPE 259 SYNTAX DateAndTime 260 MAX-ACCESS not-accessible 261 STATUS current 262 DESCRIPTION 263 "The time when the connection was established." 264 ::= { atmAcctngDataObjects 10 } 266 atmAcctngCollectionTime OBJECT-TYPE 267 SYNTAX DateAndTime 268 MAX-ACCESS not-accessible 269 STATUS current 270 DESCRIPTION 271 "The time at which the data in this record was collected." 272 ::= { atmAcctngDataObjects 11 } 274 atmAcctngCollectMode OBJECT-TYPE 275 SYNTAX INTEGER { onRelease(1), 276 periodically(2), 277 onCommand(3) } 278 MAX-ACCESS not-accessible 279 STATUS current 280 DESCRIPTION 281 "The reason why this connection data was collected." 282 ::= { atmAcctngDataObjects 12 } 284 atmAcctngReleaseCause OBJECT-TYPE 285 SYNTAX Integer32 286 MAX-ACCESS not-accessible 287 STATUS current 288 DESCRIPTION 289 "If the connection data was collected because of the release 290 of an SVC, then this is the cause code in the Release 291 message for the connection; otherwise, this object has the 292 value zero." 293 ::= { atmAcctngDataObjects 13 } 295 atmAcctngServiceCategory OBJECT-TYPE 296 SYNTAX INTEGER { other(1), cbr(2), vbrRt(3), vbrNrt(4), 297 abr(5), ubr(6), unknown(7) } 298 MAX-ACCESS not-accessible 299 STATUS current 300 DESCRIPTION 301 "The connection's service category." 302 ::= { atmAcctngDataObjects 14 } 304 atmAcctngTransmittedCells OBJECT-TYPE 305 SYNTAX Counter64 306 MAX-ACCESS not-accessible 307 STATUS current 308 DESCRIPTION 309 "The number of cells, including OAM cells, transmitted by 310 this switch on this connection." 311 ::= { atmAcctngDataObjects 15 } 313 atmAcctngTransmittedClp0Cells OBJECT-TYPE 314 SYNTAX Counter64 315 MAX-ACCESS not-accessible 316 STATUS current 317 DESCRIPTION 318 "The number of cells with CLP=0, including OAM cells, 319 transmitted by this switch on this connection." 320 ::= { atmAcctngDataObjects 16 } 322 atmAcctngReceivedCells OBJECT-TYPE 323 SYNTAX Counter64 324 MAX-ACCESS not-accessible 325 STATUS current 326 DESCRIPTION 327 "The number of cells, including OAM cells, received by this 328 switch on this connection." 329 ::= { atmAcctngDataObjects 17 } 331 atmAcctngReceivedClp0Cells OBJECT-TYPE 332 SYNTAX Counter64 333 MAX-ACCESS not-accessible 334 STATUS current 335 DESCRIPTION 336 "The number of cells with CLP=0, including OAM cells, 337 received by this switch on this connection." 338 ::= { atmAcctngDataObjects 18 } 340 atmAcctngTransmitTrafficDescriptorType OBJECT-TYPE 341 SYNTAX OBJECT IDENTIFIER 342 MAX-ACCESS not-accessible 343 STATUS current 344 DESCRIPTION 345 "The traffic descriptor type (as defined in RFC 1695 and its 346 successors) in the direction in which the switch transmits 347 cells on the connection." 348 REFERENCE 349 "See atmTrafficDescriptorTypes in ATM-MIB.my in RFC 1695 and 350 its successors." 351 ::= { atmAcctngDataObjects 19 } 353 atmAcctngTransmitTrafficDescriptorParam1 OBJECT-TYPE 354 SYNTAX INTEGER (0..2147483647) 355 MAX-ACCESS not-accessible 356 STATUS current 357 DESCRIPTION 358 "The first traffic descriptor parameter in the direction in 359 which this switch transmits cells on this connection. 360 Interpretation of this parameter is dependent on the value 361 of atmAcctngTransmitTrafficDescriptorType." 362 ::= { atmAcctngDataObjects 20 } 364 atmAcctngTransmitTrafficDescriptorParam2 OBJECT-TYPE 365 SYNTAX INTEGER (0..2147483647) 366 MAX-ACCESS not-accessible 367 STATUS current 368 DESCRIPTION 369 "The second traffic descriptor parameter in the direction in 370 which this switch transmits cells on this connection. 371 Interpretation of this parameter is dependent on the value 372 of atmAcctngTransmitTrafficDescriptorType." 373 ::= { atmAcctngDataObjects 21 } 375 atmAcctngTransmitTrafficDescriptorParam3 OBJECT-TYPE 376 SYNTAX INTEGER (0..2147483647) 377 MAX-ACCESS not-accessible 378 STATUS current 379 DESCRIPTION 380 "The third traffic descriptor parameter in the direction in 381 which this switch transmits cells on this connection. 382 Interpretation of this parameter is dependent on the value 383 of atmAcctngTransmitTrafficDescriptorType." 384 ::= { atmAcctngDataObjects 22 } 386 atmAcctngTransmitTrafficDescriptorParam4 OBJECT-TYPE 387 SYNTAX INTEGER (0..2147483647) 388 MAX-ACCESS not-accessible 389 STATUS current 390 DESCRIPTION 391 "The fourth traffic descriptor parameter in the direction in 392 which this switch transmits cells on this connection. 393 Interpretation of this parameter is dependent on the value 394 of atmAcctngTransmitTrafficDescriptorType." 395 ::= { atmAcctngDataObjects 23 } 397 atmAcctngTransmitTrafficDescriptorParam5 OBJECT-TYPE 398 SYNTAX INTEGER (0..2147483647) 399 MAX-ACCESS not-accessible 400 STATUS current 401 DESCRIPTION 402 "The fifth traffic descriptor parameter in the direction in 403 which this switch transmits cells on this connection. 404 Interpretation of this parameter is dependent on the value 405 of atmAcctngTransmitTrafficDescriptorType." 406 ::= { atmAcctngDataObjects 24 } 408 atmAcctngReceiveTrafficDescriptorType OBJECT-TYPE 409 SYNTAX OBJECT IDENTIFIER 410 MAX-ACCESS not-accessible 411 STATUS current 412 DESCRIPTION 413 "The traffic descriptor type (as defined in RFC 1695 and its 414 successors) in the direction in which this switch receives 415 cells on this connection." 416 REFERENCE 417 "See atmTrafficDescriptorTypes in ATM-MIB.my in RFC 1695 and 418 its successors." 419 ::= { atmAcctngDataObjects 25 } 421 atmAcctngReceiveTrafficDescriptorParam1 OBJECT-TYPE 422 SYNTAX INTEGER (0..2147483647) 423 MAX-ACCESS not-accessible 424 STATUS current 425 DESCRIPTION 426 "The first traffic descriptor parameter in the direction in 427 which this switch receives cells on this connection. 428 Interpretation of this parameter is dependent on the value 429 of atmAcctngReceiveTrafficDescriptorType." 430 ::= { atmAcctngDataObjects 26 } 432 atmAcctngReceiveTrafficDescriptorParam2 OBJECT-TYPE 433 SYNTAX INTEGER (0..2147483647) 434 MAX-ACCESS not-accessible 435 STATUS current 436 DESCRIPTION 437 "The second traffic descriptor parameter in the direction in 438 which this switch receives cells on this connection. 439 Interpretation of this parameter is dependent on the value 440 of atmAcctngReceiveTrafficDescriptorType." 441 ::= { atmAcctngDataObjects 27 } 443 atmAcctngReceiveTrafficDescriptorParam3 OBJECT-TYPE 444 SYNTAX INTEGER (0..2147483647) 445 MAX-ACCESS not-accessible 446 STATUS current 447 DESCRIPTION 448 "The third traffic descriptor parameter in the direction in 449 which this switch receives cells on this connection. 450 Interpretation of this parameter is dependent on the value 451 of atmAcctngReceiveTrafficDescriptorType." 452 ::= { atmAcctngDataObjects 28 } 454 atmAcctngReceiveTrafficDescriptorParam4 OBJECT-TYPE 455 SYNTAX INTEGER (0..2147483647) 456 MAX-ACCESS not-accessible 457 STATUS current 458 DESCRIPTION 459 "The fourth traffic descriptor parameter in the direction in 460 which this switch receives cells on this connection. 461 Interpretation of this parameter is dependent on the value 462 of atmAcctngReceiveTrafficDescriptorType." 463 ::= { atmAcctngDataObjects 29 } 465 atmAcctngReceiveTrafficDescriptorParam5 OBJECT-TYPE 466 SYNTAX INTEGER (0..2147483647) 467 MAX-ACCESS not-accessible 468 STATUS current 469 DESCRIPTION 470 "The fifth traffic descriptor parameter in the direction in 471 which this switch receives cells on this connection. 472 Interpretation of this parameter is dependent on the value 473 of atmAcctngReceiveTrafficDescriptorType." 474 ::= { atmAcctngDataObjects 30 } 476 atmAcctngCallingPartySubAddress OBJECT-TYPE 477 SYNTAX AtmAddr 478 MAX-ACCESS not-accessible 479 STATUS current 480 DESCRIPTION 481 "The connection's calling party sub-address. If the 482 connection has no calling party sub-address, or it's value 483 is unknown, then the value of this object is the zero-length 484 string." 485 ::= { atmAcctngDataObjects 31 } 487 atmAcctngCalledPartySubAddress OBJECT-TYPE 488 SYNTAX AtmAddr 489 MAX-ACCESS not-accessible 490 STATUS current 491 DESCRIPTION 492 "The connection's called party sub-address. If the 493 connection has no called party sub-address, or it's value is 494 unknown, then the value of this object is the zero-length 495 string." 496 ::= { atmAcctngDataObjects 32 } 498 atmAcctngRecordCrc16 OBJECT-TYPE 499 SYNTAX OCTET STRING (SIZE(2)) 500 MAX-ACCESS not-accessible 501 STATUS current 502 DESCRIPTION 503 "The value of the CRC-16 checksum (as defined by ISO 3309 504 (HDLC) and/or ITU X.25) calculated over the accounting 505 record containing this object. 507 While the mechanism for calculating/encoding the checksum 508 value is specific to the method of encoding the accounting 509 record, an accounting record containing this object is 510 typically generated by initializing the value of this object 511 to the all-zeros string ('0000'H), with the location of 512 these zeros being saved. After generating the record, the 513 checksum is calculated over the whole connection record and 514 then the all-zeros value is overwritten (at the saved 515 location) by the calculated value of the checksum." 516 ::= { atmAcctngDataObjects 33 } 518 END 519 5. Acknowledgements 521 The comments of the IETF's AToM MIB Working Group are acknowledged. 523 6. References 525 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 526 Describing SNMP Management Frameworks", RFC 2271, Cabletron 527 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 528 January 1998 530 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 531 Management Information for TCP/IP-based Internets", RFC 1155, 532 Performance Systems International, Hughes LAN Systems, May 1990 534 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 535 Performance Systems International, Hughes LAN Systems, March 1991 537 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 538 RFC 1215, Performance Systems International, March 1991 540 [5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 541 Waldbusser, "Structure of Management Information for Version 2 of 542 the Simple Network Management Protocol (SNMPv2)", RFC 1902, SNMP 543 Research,Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 544 International Network Services, January 1996. 546 [6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 547 Waldbusser, "Textual Conventions for Version 2 of the Simple 548 Network Management Protocol (SNMPv2)", RFC 1903, SNMP Research, 549 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 550 International Network Services, January 1996. 552 [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 553 Waldbusser, "Conformance Statements for Version 2 of the Simple 554 Network Management Protocol (SNMPv2)", RFC 1904, SNMP Research, 555 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 556 International Network Services, January 1996. 558 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 559 Management Protocol", RFC 1157, SNMP Research, Performance Systems 560 International, Performance Systems International, MIT Laboratory 561 for Computer Science, May 1990. 563 [9] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 564 Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, 565 SNMP Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, 566 Inc., International Network Services, January 1996. 568 [10] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 569 Waldbusser, "Transport Mappings for Version 2 of the Simple Network 570 Management Protocol (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco 571 Systems, Inc., Dover Beach Consulting, Inc., International Network 572 Services, January 1996. 574 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 575 Processing and Dispatching for the Simple Network Management 576 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, 577 Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998. 579 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 580 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 581 2274, IBM T. J. Watson Research, January 1998. 583 [13] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 584 Waldbusser, "Protocol Operations for Version 2 of the Simple 585 Network Management Protocol (SNMPv2)", RFC 1905, SNMP Research, 586 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 587 International Network Services, January 1996. 589 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 590 2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 591 Systems, January 1998. 593 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 594 Control Model (VACM) for the Simple Network Management Protocol 595 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., 596 Cisco Systems, Inc., January 1998. 598 [16] McCloghrie, K., Heinanen, J., Greene, W., and A. Prasad, "Managed 599 Objects for Controlling the Collection and Storage of Accounting 600 Information for Connection-Oriented Networks" Internet Draft, 601 draft-ietf-atommib-acct-06.txt, October 1998. 603 [17] Noto, M., Spiegel, E., and K. Tesink, "Definitions of Textual 604 Conventions and OBJECT-IDENTITIES for ATM Management", Internet 605 Draft, draft-ietf-atommib-atm2TC-08.txt, August 1998. 607 7. Security Considerations 609 This MIB module defines data items for potential use as accounting 610 information. Each of these data items is only accessible through a 611 collected accounting file. After being collected, the accounting data 612 should be protected against modification or unauthorized deletion. 614 8. IANA Considerations 616 Prior to publication of this memo as an RFC, IANA is requested to make a 617 suitable OBJECT IDENTIFIER assignment and update the following line in 618 the MIB: 620 ::= { mib-2 xx } -- to be filled in by IANA 622 9. Authors' Addresses 624 Keith McCloghrie 625 Cisco Systems, Inc. 626 170 West Tasman Drive, 627 San Jose CA 95134 628 Phone: +1 408 526 5260 629 Email: kzm@cisco.com 631 Juha Heinanen 632 Telia Finland, Inc. 633 Myyrmaentie 2 634 01600 VANTAA 635 Finland 636 Phone +358 303 944 808 637 Email: jh@telia.fi 639 Wedge Greene 640 MCI Telecommunications Corporation 641 901 International Parkway 642 Richardson, Texas 75081 643 Phone: 214-498-1232 or 972-729-1232 644 Email: wedge.greene@mci.com 646 Anil Prasad 647 Cisco Systems, Inc. 648 170 West Tasman Drive, 649 San Jose CA 95134 650 Phone: +1 408 525-7209 651 E-mail: aprasad@cisco.com 653 10. Full Copyright Statement 655 Copyright (C) The Internet Society (1998). All Rights Reserved. 657 This document and translations of it may be copied and furnished to 658 others, and derivative works that comment on or otherwise explain it or 659 assist in its implmentation may be prepared, copied, published and 660 distributed, in whole or in part, without restriction of any kind, 661 provided that the above copyright notice and this paragraph are included 662 on all such copies and derivative works. However, this document itself 663 may not be modified in any way, such as by removing the copyright notice 664 or references to the Internet Society or other Internet organizations, 665 except as needed for the purpose of developing Internet standards in 666 which case the procedures for copyrights defined in the Internet 667 Standards process must be followed, or as required to translate it into 668 languages other than English. 670 The limited permissions granted above are perpetual and will not be 671 revoked by the Internet Society or its successors or assigns. 673 This document and the information contained herein is provided on an "AS 674 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 675 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 676 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 677 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 678 FITNESS FOR A PARTICULAR PURPOSE." 679 Table of Contents 681 1 Introduction .................................................... 2 682 2 The SNMP Network Management Framework ........................... 2 683 3 Overview ........................................................ 3 684 4 Definitions ..................................................... 4 685 5 Acknowledgements ................................................ 14 686 6 References ...................................................... 14 687 7 Security Considerations ......................................... 16 688 8 IANA Considerations ............................................. 16 689 9 Authors' Addresses .............................................. 16 690 10 Full Copyright Statement ....................................... 17