idnits 2.17.1 draft-ietf-atommib-test-06.txt: ** The Abstract section seems to be numbered 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 document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 36 longer pages, the longest (page 2) being 111 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 37 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. (A line matching the expected section header was found, but with an unexpected indentation: ' 2. Abstract' ) ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 6. Security Considerations' ) ** 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 an Authors' Addresses Section. ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. ** The abstract seems to contain references ([RFC2233], [RFC2573], [RFC1906], [RFC1155], [RFC2574], [RFC2575], [RFC1157], [RFC2580], [RFC2578], [RFC1212], [RFC1213], [RFC2579], [RFC1901], [RFC1215], [TestMIB], [RFC2570], [RFC2571], [RFC2515], [RFC1905], [RFC2572]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. 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 (November 28, 1999) is 8915 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? 'RFC2515' on line 1228 looks like a reference -- Missing reference section? 'RFC2571' on line 1157 looks like a reference -- Missing reference section? 'RFC1155' on line 1161 looks like a reference -- Missing reference section? 'RFC1212' on line 1166 looks like a reference -- Missing reference section? 'RFC1215' on line 1169 looks like a reference -- Missing reference section? 'RFC2578' on line 1172 looks like a reference -- Missing reference section? 'RFC2579' on line 1177 looks like a reference -- Missing reference section? 'RFC2580' on line 1182 looks like a reference -- Missing reference section? 'RFC1157' on line 1187 looks like a reference -- Missing reference section? 'RFC1901' on line 1191 looks like a reference -- Missing reference section? 'RFC1906' on line 1195 looks like a reference -- Missing reference section? 'RFC2572' on line 1200 looks like a reference -- Missing reference section? 'RFC2574' on line 1205 looks like a reference -- Missing reference section? 'RFC1905' on line 1210 looks like a reference -- Missing reference section? 'RFC2573' on line 1215 looks like a reference -- Missing reference section? 'RFC2575' on line 1218 looks like a reference -- Missing reference section? 'RFC2570' on line 1223 looks like a reference -- Missing reference section? 'TestMIB' on line 1253 looks like a reference -- Missing reference section? 'RFC1213' on line 1232 looks like a reference -- Missing reference section? 'RFC2233' on line 1238 looks like a reference Summary: 11 errors (**), 0 flaws (~~), 4 warnings (==), 22 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Definitions of Tests 2 for ATM Management 4 November 28, 1999 6 Internet-Draft 8 Michael Noto (editor) 9 3Com Corporation 10 mike_noto@3com.com 12 Kaj Tesink (editor) 13 Telcordia Technologies 14 kaj@research.telcordia.com 16 1. Status of this Memo 18 This document is an Internet-Draft and is in full conformance 19 with all provisions of Section 10 of RFC2026. 21 Internet-Drafts are working documents of the Internet 22 Engineering Task Force (IETF), its areas, and its working 23 groups. Note that other groups may also distribute working 24 documents as Internet-Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six 27 months and may be updated, replaced, or obsoleted by other 28 documents at any time. It is inappropriate to use Internet- 29 Drafts as reference material or to cite them other than as 30 "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt 35 The list of Internet-Draft Shadow Directories can be accessed 36 at http://www.ietf.org/shadow.html. 38 Copyright Notice 40 Copyright (C) The Internet Society (1999). All Rights 41 Reserved. 43 2. Abstract 45 This memo defines a portion of the Management Information Base 46 (MIB) for use with network management protocols in the 47 Internet community. In particular, it describes objects used 48 for managing ATM-based interfaces, devices, networks and 49 services in addition to those defined in the ATM MIB 50 [RFC2515], to provide support for the management of on-demand 51 ATM Loopback Tests. 53 3. The SNMP Network Management Framework 55 The SNMP Management Framework presently consists of five major 56 components: 58 o An overall architecture, described in RFC 2571 59 [RFC2571]. 61 o Mechanisms for describing and naming objects and 62 events for the purpose of management. The first 63 version of this Structure of Management Information 64 (SMI) is called SMIv1 and described in STD 16, RFC 65 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 66 1215 [RFC1215]. The second version, called SMIv2, is 67 described in STD 58, RFC 2578 [RFC2578], RFC 2579 68 [RFC2579] and RFC 2580 [RFC2580]. 70 o Message protocols for transferring management 71 information. The first version of the SNMP message 72 protocol is called SNMPv1 and described in STD 15, RFC 73 1157 [RFC1157]. A second version of the SNMP message 74 protocol, which is not an Internet standards track 75 protocol, is called SNMPv2c and described in RFC 1901 76 [RFC1901] and RFC 1906 [RFC1906]. The third version of 77 the message protocol is called SNMPv3 and described in 78 RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 79 [RFC2574]. 81 o Protocol operations for accessing management 82 information. The first set of protocol operations and 83 associated PDU formats is described in STD 15, RFC 84 1157 [RFC1157]. A second set of protocol operations 85 and associated PDU formats is described in RFC 1905 86 [RFC1905]. 88 o A set of fundamental applications described in RFC 89 2573 [RFC2573] and the view-based access control 90 mechanism described in RFC 2575 [RFC2575]. 92 A more detailed introduction to the current SNMP 93 Management Framework can be found in RFC 2570 94 [RFC2570]. 96 Managed objects are accessed via a virtual information 97 store, termed the Management Information Base or MIB. 98 Objects in the MIB are defined using the mechanisms 99 defined in the SMI. 101 This memo specifies a MIB module that is compliant to 102 the SMIv2. A MIB conforming to the SMIv1 can be 103 produced through the appropriate translations. The 104 resulting translated MIB must be semantically 105 equivalent, except where objects or events are omitted 106 because no translation is possible (use of Counter64). 107 Some machine readable information in SMIv2 will be 108 converted into textual descriptions in SMIv1 during 109 the translation process. However, this loss of machine 110 readable information is not considered to change the 111 semantics of the MIB. 113 4. Overview 115 The purpose of this memo is to provide additional 116 capabilities, not found in the ATM MIB [RFC2515], which are 117 needed to manage ATM interfaces. This memo addresses ATM 118 Testing Support and must be used in conjunction with the 119 System/Interface Test MIB [TestMIB]. 121 4.1. Background 123 In addition to the MIB module defined in this memo, other MIB 124 modules are necessary to manage ATM interfaces, links and 125 cross-connects. Examples include MIB II for general system 126 [RFC1213] and interface management [RFC2233], the DS3 or 127 SONET/SDH MIBs for management of SONET/SDH and DS3 physical 128 interfaces, and, as appropriate, MIB modules for applications 129 that make use of ATM, such as SMDS and LAN Emulation. These 130 MIB modules are outside the scope of this specification. 132 This MIB module requires the use of the ATM MIB module defined 133 in [RFC2515] and the System/Interface Test MIB module 134 [TestMIB]. 136 This memo defines extensions to the ATM MIB in order to 137 support ATM Loopback Tests. An ATM Loopback Test provides the 138 ability to send out a loopback OAM (Operations and 139 Maintenance) cell to verify the existence of connectivity for 140 a particular connection. 142 4.2. Terminology 144 The following terms are defined here and used throughout this 145 MIB: 146 - Virtual Path Link (VPL) 147 - Virtual Path Connection (VPC) 148 - Virtual Path Segment (VP Segment) 149 - Virtual Channel Link (VCL) 150 - Virtual Channel Connection (VCC) 151 - Virtual Channel Segment (VC Segment). 153 _____ _______ _______ _______ _____ 154 | |____| |____| |____| |____| | 155 |Host1| |SwitchA| |SwitchB| |SwitchC| |Host2| 156 | |____| |____| |____| |____| | 157 |_____| |_______| |_______| |_______| |_____| 159 |<----->| Virtual |<----->| Virtual 160 Path Link Path Link 162 |<------------Virtual Path Connection---------->| 163 (between Host1 and Host2) 165 |<--------------->| Virtual Path 166 Segment (between 167 SwitchA and SwitchC) 169 Figure 1: Examples of Virtual Path Links, Virtual Path 170 Connection, and Virtual Path Segment 172 _____ _______ _______ _______ _____ 173 | |____| |____| |____| |____| | 174 |Host1|----|SwitchA|----|SwitchB|----|SwitchC|----|Host2| 175 | |____| |____| |____| |____| | 176 |_____| |_______| |_______| |_______| |_____| 178 |<----->| Virtual |<----->| Virtual 179 Channel Link Channel Link 181 |<----------Virtual Channel Connection--------->| 182 (between Host1 and Host2) 184 |<--------------->| Virtual Channel 185 Segment (between 186 SwitchA and SwitchC) 188 Figure 2: Examples of Virtual Channel Links, Virtual 189 Channel Connection, and Virtual Channel Segment 191 4.3. Supported Functions 193 The managed ATM objects are organized as follows: 195 (1) ATM Loopback Testing 196 (2) ATM End-Point Tables 198 4.3.1. ATM Loopback Testing 200 The loopback test provides the ability to send out a loopback 201 OAM cell to verify the existence of connectivity for a 202 particular connection. Loopback tests can be performed on 203 either an entire connection (i.e., an end-to-end test), a 204 segment of the connection (i.e., a segment test), a portion of 205 a segment (i.e., a loopback location identifier test), or the 206 network portion of a connection (i.e., a service internal 207 test). 209 The loopback test makes use of the Test Table defined in 210 [TestMIB]. For a given interface, a loopback test can be 211 invoked by obtaining ownership of a test and then by setting 212 the value of testType equal to one of the ATM Loopback Test 213 Types defined in Section 5. See procedures in [TestMIB] for 214 using the Test Table. After invoking a loopback test, the 215 object testResult can be read to determine the outcome of the 216 loopback test (e.g., 'success(2)' if the loopback cell made it 217 back to the originator of the test or 'failed(7)' if the 218 loopback cell did not make it back). 220 The following types of loopback tests are defined: 222 - End-to-end Loopback Test 223 - Segment Loopback Test 224 - Loopback Test Using Loopback Location Identifier 225 - Network Loopback Test. 227 1) End-to-end Loopback Test 229 The end-to-end loopback (LB) is self-explanatory. For a VP 230 test, the cell is sent on the given VP, via VCI=4 specified in 231 [UNI3.1]. For a VC test, the LB cell is sent on the VC under 232 test, with the PTI (Payload Type Indicator) set to 5 as 233 specified in [UNI3.1]. Figure 3 illustrates the end-to-end 234 loopback test. 236 ____ _______ _______ _______ ____ 237 |Host| | | | | | | |Host| 238 |____|----|SwitchA|----|SwitchB|----|SwitchC|----|____| 239 |_______| |_______| |_______| 241 |<--------------------------------------------->| Test 242 Path 244 Figure 3: End-to-end Loopback Test 246 See Section 5 for more details on how to use the End-to-end 247 Loopback Test. 249 2) Segment Loopback Test 251 The segment LB test is explained in ITU-T I.610[I.610]. For a 252 VP segment test, the LB cell is sent on the VP under test via 253 VCI=3 as specified in [UNI3.1], and the Loopback Location ID 254 field is set to all 1's. For a VC segment test, the LB cell 255 is sent on the VC under test, with the PTI set to 4 as 256 specified in [UNI3.1], and the Loopback Location ID field is 257 set to all 1's. 259 This test involves a LB cell being inserted at a pre-defined 260 segment end-point, and looped back at the corresponding 261 segment end-point encountered. The pair of segment end-points 262 define a segment (which is used for the segment loopback 263 test). A VP/VC connection can have multiple segments, but 264 multiple segments cannot overlap. 266 A UNI interface is by definition defined as a segment end- 267 point (hence a UNI would be considered a segment). A segment 268 can also define: 269 - a B-ICI 270 - a public carrier's 'piece' of the connection 271 - a private network's 'piece' of the connection. 273 In order to support this functionality, the VP/VC link 274 termination needs to be able to be defined as a segment. This 275 can be done using either the atmVplSegmentEndPoint or 276 atmVclSegmentEndPoint object depending on whether it is for a 277 VPC or VCC. A segment loopback test is illustrated in Figure 278 4. 280 ____ _______ _______ _______ ____ 281 |Host| | | | | | | |Host| 282 |____|----|SwitchA|----|SwitchB|----|SwitchC|----|____| 283 |_______| |_______| |_______| 285 |<----------------------->| Segment 287 Figure 4: Segment Loopback Test 289 Section 5 describes the use of the ATM Segment Loopback Tests. 291 3) Loopback Test Using Loopback Location Identifier 293 This loopback test is a special type of 2) where the Loopback 294 Location ID field is set to a value that corresponds to a 295 specific node in a given network (Note that the format of this 296 field is not standardized, that is, the value is significant 297 only within an administrative domain). In this case, the 298 device initiating the LB test inserts the appropriate Loop 299 Back Location ID. When the LB cell reaches the corresponding 300 device, that device recognizes the Loopback Location ID as its 301 own, and loops it back. This test is useful for performing 302 fault sectionalization without having to provision segment 303 end-points. An additional object, the atmIfLogicalLoopbackId, 304 is defined to determine the loopback point. Figure 5 shows a 305 loopback test using a location identifier. Note that the 306 loopback test using location identifier can be used to perform 307 a loopback test over a portion of a defined segment. See 308 Figure 5. 310 ____ _______ _______ _______ ____ 311 |Host| | | | | | | |Host| 312 |____|----|SwitchA|----|SwitchB|----|SwitchC|----|____| 313 |_______| |_______| |_______| 315 |<---------->| Portion of Segment that 316 Loopback test is 317 performed on 319 |<----------------------->| Segment 321 Figure 5: Loopback Test Using Location Identifier 323 See Section 5 for more details. 325 4) Network Loopback Test 327 This is a loopback test that the manager requests an agent in 328 a network to perform over the internal portion of a designated 329 connection. The Network then initiates the internal network 330 loopback test by inserting an OAM loopback cell at one of the 331 end-points of the internal network portion of the connection. 332 When the loopback cell reaches the other end-point of the 333 internal Network , the cell is looped back. This test is 334 useful for verifying connectivity through a particular 335 network. Figure 6 illustrates the Network loopback test. 337 ____ _______ _______ _______ ____ 338 |Host| |Netwk 1| |Netwk 1| |Netwk 1| |Host| 339 |____|----|SwitchA|----|SwitchB|----|SwitchC|----|____| 340 |_______| |_______| |_______| 342 |<----------------------->| LB Test Path 343 thru Network 1 345 Figure 6: Network Loopback Test 347 See Section 5 for more details. 349 4.3.2. ATM End-Point Tables 351 There are two ATM End-point tables: the ATM VP End-point Table 352 and the ATM VC End-point Table. The ATM VP End-point Table 353 augments the atmVplTable and defines the 354 atmVplEndptSegmentEndPoint object to represent whether or not 355 a specified VPL is a segment end-point. Similarly for Virtual 356 Channels, the ATM VC End-point Table and the 357 atmVclEndptSegmentEndPoint object are used to represent 358 whether or not a specified VCL is a segment end-point. 360 5. Definitions 362 ATMTEST-MIB DEFINITIONS ::= BEGIN 364 IMPORTS 365 MODULE-IDENTITY, OBJECT-IDENTITY, 366 OBJECT-TYPE, mib-2 367 FROM SNMPv2-SMI 368 MODULE-COMPLIANCE, OBJECT-GROUP 369 FROM SNMPv2-CONF 370 atmVplEntry, atmVclEntry, atmInterfaceConfEntry 371 FROM ATM-MIB; 373 atmTESTMIB MODULE-IDENTITY 374 LAST-UPDATED "9911281200Z" 375 ORGANIZATION "IETF AToMMIB Working Group" 376 CONTACT-INFO 377 " Michael Noto 378 Postal: 3Com Corporation 379 5400 Bayfront Plaza 380 Santa Clara, CA 95052 381 USA 382 Tel: +1 408 326 2218 383 E-mail: mike_noto@3com.com 385 Kaj Tesink 386 Postal: Telcordia Technologies 387 331 Newman Springs Road 388 Red Bank, NJ 07701 389 USA 390 Tel: +1 732 758 5254 391 Fax: +1 732 758 2269 392 E-mail: kaj@research.telcordia.com" 393 DESCRIPTION 394 "This MIB Module provides 395 ATM Loopback Tests and supporting objects 396 that must be supported by ATM devices 397 providing ATM Loopback Tests." 398 REVISION "9911281200Z" 399 DESCRIPTION 400 "Initial version, published as RFCxxxx" 401 ::= { mib-2 XX } 403 -- ******** NOTE TO THE RFC EDITOR / IANA *********** 404 -- * Before this module is put on the standards track 405 -- * fill out RFCxxxx with the RFC number of this document 406 -- * assign XX by IANA. 407 -- * remove this notice from the MIB 409 atmTESTMIBObjects OBJECT IDENTIFIER ::= {atmTESTMIB 1} 411 -- This ATMTEST-MIB Module consists of the following: 412 -- (1) ATM Loopback Testing 413 -- (2) ATM End-Point Tables 414 -- ************************************************ 415 -- (1) ATM Loopback Testing 417 -- This concerns information for interfaces 418 -- supporting ATM Loopback Tests and includes: 419 -- 1. ATM Loopback Objects 420 -- 2. List of ATM Loopback Test Types 422 atmLoopbackTestGroup OBJECT IDENTIFIER ::= { 423 atmTESTMIBObjects 1} 425 -- 1. ATM Loopback Objects 426 -- The following objects are defined for use in 427 -- performing ATM Loopback Tests. 429 atmInterfaceLLIDTable OBJECT-TYPE 430 SYNTAX SEQUENCE OF AtmInterfaceLLIDEntry 431 MAX-ACCESS not-accessible 432 STATUS current 433 DESCRIPTION 434 "A table of Logical Loopback Identifiers (LLID) 435 for ATM interfaces" 436 ::= { atmLoopbackTestGroup 1 } 438 atmInterfaceLLIDEntry OBJECT-TYPE 439 SYNTAX AtmInterfaceLLIDEntry 440 MAX-ACCESS not-accessible 441 STATUS current 442 DESCRIPTION 443 "A conceptual row in the atmInterfaceLLIDTable." 444 AUGMENTS { atmInterfaceConfEntry } 445 ::= { atmInterfaceLLIDTable 1 } 447 AtmInterfaceLLIDEntry ::= SEQUENCE { 448 atmIfLogicalLoopbackId OCTET STRING 449 } 451 atmIfLogicalLoopbackId OBJECT-TYPE 452 SYNTAX OCTET STRING (SIZE (0|16)) 453 MAX-ACCESS read-write 454 STATUS current 455 DESCRIPTION 456 "This identifier is used to identify this local ATM 457 interface for loopback.The value of this object can 458 be used by other ATM devices to identify this local 459 ATM interface as the interface that is being 460 requested to loopback OAM Loopback cells. The 461 default for this field is the zero length string 462 which signifies that loopback at this interface is 463 disabled. To enable loopback set the value to a 16 464 byte fixed length octet string. Non-zero length 465 identifiers of less than 16 octets signify that 466 loopback checking is enabled and are left justified, 467 and padded with all 0's." 468 DEFVAL {''H } 469 REFERENCE 470 "ITU-T Recommendation I.610, Broadband Integrated 471 Service Digital Network (B-ISDN) Operation and 472 Maintenance Principles and Functions, July 1995" 473 ::= { atmInterfaceLLIDEntry 1 } 475 -- 2. List of ATM Loopback Test Types 476 -- The following loopback test types are defined: 477 -- atmLoopbackVpE2e 478 -- atmLoopbackVcE2e 479 -- atmLoopbackVpSegment 480 -- atmLoopbackVcSegment 481 -- atmLoopbackVpLocationID 482 -- atmLoopbackVcLocationID 483 -- atmLoopbackVpServiceInternal 484 -- atmLoopbackVcServiceInternal 486 atmLoopbackTestTypes OBJECT IDENTIFIER ::= { 487 atmLoopbackTestGroup 4 } 489 atmLoopbackVpE2e OBJECT-IDENTITY 490 STATUS current 491 DESCRIPTION 492 "This is an end-to-end loopback test performed on a 493 designated VP (Virtual Path). To perform this test an 494 end-to-end loopback OAM cell is inserted at one of the 495 end-points of the designated VP connection (e.g., at a 496 host) via VCI=4 (the VCI value for VP OAM end-to-end 497 cells), travels to the other end-point of the VP 498 connection, and then loops back to the originating 499 end-point on the designated VP. Success is achieved 500 if the loopback OAM cell returns to the originating 501 end-point within 5 seconds, otherwise, the test fails. 503 The manager-station performs a loopback test by making 504 use of the testTable defined in [TestMIB]. In order 505 to run this test the object testType in the testTable 506 shall be set to atmLoopbackVpE2e, and the object 507 testTarget points to the row in the atmVplTable in 508 [TestMIB] corresponding to the VP designated for the 509 test. 511 Before starting a test, a manager-station must first 512 obtain 'ownership' of the entry in the testTable for 513 the interface to be tested (follow procedure defined 514 in [TestMIB]). Once the manager-station obtains 515 ownership, a loopback test for a given interface can 516 be invoked by first setting up parameters necessary 517 for the loopback test (e.g., set the testTarget), and 518 then setting the value of testType in the testTable 519 equal to 'atmLoopbackVpE2e'. The testRowStatus is used 520 to invoke the atmLoopbackVpE2e test on the VP with the 521 VPI corresponding to the testTarget. 523 After invoking a loopback test, wait for the test 524 completion by polling for the object testResult. A 525 value of 'inProgress(3)' will result if the test is 526 still in progress. Once the test is completed, the 527 object testResult will have a value of 'success(2)' if 528 the loopback OAM cell returned to the originator of 529 the test within 5 seconds, if not, a value of 530 'failed(7)' will result. If the ATM system does not 531 support this type of loopback test, then a value of 532 'notSupported(4)' will be provided. Other possible 533 values for the testResult object are 'unAbleToRun(5)' 534 and 'aborted(6)'." 535 ::= { atmLoopbackTestTypes 1 } 537 atmLoopbackVcE2e OBJECT-IDENTITY 538 STATUS current 539 DESCRIPTION 540 "This is an end-to-end loopback test performed on a 541 designated VC (Virtual Channel). To perform this test 542 an end-to-end loopback OAM cell is inserted at one of 543 the end-points of the designated VC connection (e.g., 544 at a host) via PTI=5 (the PTI value used for VC OAM 545 end-to-end cells), travels to the other end-point of 546 the VC connection, and then loops back to the 547 originating end-point on the designated VC. Success is 548 achieved if the loopback OAM cell returns to the 549 originating end-point within 5 seconds, otherwise, the 550 test fails. 552 The manager-station performs a loopback test by making 553 use of the testTable defined in [TestMIB]. In order to 554 run this test the object testType in the testTable 555 shall be set to atmLoopbackVcE2e, and the object 556 testTarget points to the row in the atmVclTable in 557 [RFC2515] corresponding to the VC designated for the 558 test. 560 Before starting a test, a manager-station must first 561 obtain 'ownership' of the entry in the testTable for 562 the interface to be tested (follow procedure defined in 563 [TestMIB]). Once the manager-station obtains 564 ownership, a loopback test for a given interface can be 565 invoked by first setting up parameters necessary for 566 the loopback test (e.g., set the testTarget), and then 567 setting the value of testType in the testTable equal to 568 'atmLoopbackVcE2e'. The testRowStatus is used to invoke 569 the atmLoopbackVcE2e test on the VC with the VPI/VCI 570 corresponding to the testTarget. 572 After invoking a loopback test, wait for the test 573 completion by polling for the object testResult. A 574 value of 'inProgress(3)' will result if the test is 575 still in progress. Once the test is completed, the 576 object testResult will have a value of 'success(2)' if 577 the loopback OAM cell returned to the originator of the 578 test within 5 seconds, if not, a value of 'failed(7)' 579 will result. If the ATM system does not support this 580 type of loopback test, then a value of 581 'notSupported(4)' will be provided. Other possible 582 values for the testResult object are 'unAbleToRun(5)' 583 and 'aborted(6)'." 584 ::= { atmLoopbackTestTypes 2 } 586 atmLoopbackVpSegment OBJECT-IDENTITY 587 STATUS current 588 DESCRIPTION 589 "This is a loopback test performed on a designated 590 segment of a VP (Virtual Path). To perform this test a 591 segment OAM cell is inserted at one of the segment 592 end-points of the designated VP connection (e.g., at a 593 host) via VCI=3 (the VCI used for VP OAM segment 594 cells), travels across the segment on the designated VP 595 to the device pre-configured as the corresponding 596 segment end-point, and then loops back to the 597 originating segment end-point on the designated VP. 598 Success is achieved if the loopback OAM cell returns to 599 the originating end-point within 5 seconds, otherwise, 600 the test fails. 602 In order to use the atmLoopbackVpSegment test, a 603 segment must be defined by setting up segment end- 604 points using the atmVplEndptSegmentEndPoint object from 605 the atmVplEndptTable. The atmVplEndptSegmentEndPoint 606 is set to 'isaVpSegmentEndPoint(1)' for each segment 607 end-point. Note that this object is by default set to 608 'isaVpSegmentEndPoint(1)' if the atmVplTable supports 609 one end of a UNI. In such a case, a UNI VP loopback 610 test would be achieved when the atmLoopbackVpSegment 611 test was initiated over the UNI. 613 The manager-station performs a loopback test by making 614 use of the testTable defined in [TestMIB]. In order to 615 run this test the object testType in the testTable 616 shall be set to atmLoopbackVpE2e, and the object 617 testTarget points to the row in the atmVplTable in 618 [RFC2515] corresponding to the VP designated for the 619 test. 621 Before starting a test, a manager-station must first 622 obtain 'ownership' of the entry in the testTable for 623 the interface to be tested (follow procedure defined in 624 [TestMIB]). Once the manager-station obtains 625 ownership, a loopback test for a given interface can be 626 invoked by first setting up parameters necessary for 627 the loopback test (e.g., set the testTarget), and then 628 setting the value of testType in the testTable equal to 629 'atmLoopbackVpSegment'. The testRowStatus is used to 630 invoke the atmLoopbackVpSegment test on the VP with the 631 VPI corresponding to the testTarget. 633 After invoking a loopback test, wait for the test 634 completion by polling for the object testResult. A 635 value of 'inProgress(3)' will result if the test is 636 still in progress. Once the test is completed, the 637 object testResult will have a value of 'success(2)' if 638 the loopback OAM cell returned to the originator of the 639 test within 5 seconds, if not, a value of 'failed(7)' 640 will result. If the ATM system does not support this 641 type of loopback test, then a value of 642 'notSupported(4)' will be provided. Other possible 643 values for the testResult object are 'unAbleToRun(5)' 644 and 'aborted(6)'." 645 ::= { atmLoopbackTestTypes 3 } 647 atmLoopbackVcSegment OBJECT-IDENTITY 648 STATUS current 649 DESCRIPTION 650 "This is a loopback test performed on a designated 651 segment of a VC (Virtual Channel). To perform this 652 test a segment OAM cell is inserted at one of the 653 segment end-points of the designated VC connection 654 (e.g., at a host) via PTI=4 (the PTI value used for VC 655 OAM segment cells), travels across the segment on the 656 designated VC to the device pre-configured as the 657 corresponding segment end-point, and then loops back to 658 the originating segment end-point on the designated VC. 659 Success is achieved if the loopback OAM cell returns to 660 the originating end-point within 5 seconds, otherwise, 661 the test fails. 663 In order to use the atmLoopbackVcSegment test, a 664 segment must be defined by setting up segment end- 665 points using the atmVclEndptSegmentEndPoint object from 666 the atmVclEndptTable. The atmVclEndptSegmentEndPoint 667 is set to 'isaVcSegmentEndPoint(1)' for each segment 668 end-point. Note that this object is by default set to 669 'isaVcSegmentEndPoint(1)' if the atmVclTable supports 670 one end of a UNI. In such a case, a UNI VC loopback 671 test would be achieved when the atmLoopbackVcSegment 672 test was initiated over the UNI. 674 The manager-station performs a loopback test by making 675 use of the testTable defined in [TestMIB]. In order to 676 run this test the object testType in the testTable 677 shall be set to atmLoopbackVcE2e, and the object 678 testTarget points to the row in the atmVclTable in 679 [RFC2515] corresponding to the VC designated for the 680 test. 682 Before starting a test, a manager-station must first 683 obtain 'ownership' of the entry in the testTable for 684 the interface to be tested (follow procedure defined in 685 [TestMIB]). Once the manager-station obtains 686 ownership, a loopback test for a given interface can be 687 invoked by first setting up parameters necessary for 688 the loopback test (e.g., set the testTarget), and then 689 setting the value of testType in the testTable equal to 690 'atmLoopbackVcSegment'. The testRowStatus is used to 691 invoke the atmLoopbackVcSegment test on the VC with the 692 VPI/VCI corresponding to the testTarget. 694 After invoking a loopback test, wait for the test 695 completion by polling for the object testResult. A 696 value of 'inProgress(3)' will result if the test is 697 still in progress. Once the test is completed, the 698 object testResult will have a value of 'success(2)' if 699 the loopback OAM cell returned to the originator of the 700 test within 5 seconds, if not, a value of 'failed(7)' 701 will result. If the ATM system does not support this 702 type of loopback test, then a value of 703 'notSupported(4)' will be provided. Other possible 704 values for the testResult object are 'unAbleToRun(5)' 705 and 'aborted(6)'." 706 ::= { atmLoopbackTestTypes 4 } 708 atmLoopbackVpLocationId OBJECT-IDENTITY 709 STATUS current 710 DESCRIPTION 711 "This is a loopback test performed on a portion of a 712 designated VP segment. To perform this test a loopback 713 OAM cell is inserted at a connection point of the 714 designated VP connection (e.g., the end-point or a 715 tandem point) with a value inserted in the Location 716 Identifier ID field of the OAM cell that corresponds to 717 the ATM device where the cell is to be looped back. 718 The loopback cell then travels through the VP 719 connection until it reaches the designated ATM device, 720 where it is looped back to the loopback cell insertion 721 point on the designated VP. Success is achieved if the 722 loopback OAM cell returns to the originating point of 723 insertion within 5 seconds, otherwise, the test fails. 725 The manager-station performs a loopback test by making 726 use of the testTable defined in [TestMIB]. In order to 727 run this test the object testType in the testTable 728 shall be set to atmLoopbackVpE2e. The object testTarget 729 points to the row in the atmVplTable in [RFC2515] 730 corresponding to the VP designated for the test. The 731 object testMoreInfo contains the desired Loopback 732 Location ID. 734 Before starting a test, a manager-station must first 735 obtain 'ownership' of the entry in the testTable for 736 the interface to be tested (follow procedure defined in 737 [TestMIB]). Once the manager-station obtains ownership, 738 a loopback test for a given interface can be invoked by 739 first setting up parameters necessary for the loopback 740 test (e.g., set testMoreInfo to AAAABBBBCCCCDDDD and 741 set the testTarget), and then setting the value of 742 testType in the testTable equal to 743 'atmLoopbackVpSegment'. The testRowStatus is used to 744 invoke the atmLoopbackVpLocationId on the VP with the 745 VPI corresponding to the testTarget and looped back at 746 loopback location ID= AAAABBBBCCCCDDDD. 748 After invoking a loopback test, wait for the test 749 completion by polling for the object testResult. A 750 value of 'inProgress(3)' will result if the test is 751 still in progress. Once the test is completed, the 752 object testResult will have a value of 'success(2)' if 753 the loopback OAM cell returned to the originator of the 754 test within 5 seconds, if not, a value of 'failed(7)' 755 will result. If the ATM system does not support this 756 type of loopback test, then a value of 757 'notSupported(4)' will be provided. Other possible 758 values for the testResult object are 'unAbleToRun(5)' 759 and 'aborted(6)'." 760 ::= { atmLoopbackTestTypes 5 } 762 atmLoopbackVcLocationId OBJECT-IDENTITY 763 STATUS current 764 DESCRIPTION 765 "This is a loopback test performed on a portion of a 766 designated Vc segment. To perform this test a loopback 767 OAM cell is inserted at a connection point of the 768 designated VC connection (e.g., the end-point or a 769 tandem point) with a value inserted in the Location 770 Identifier ID field of the OAM cell that corresponds to 771 the ATM device where the cell is to be looped back. 772 The loopback cell then travels through the VC 773 connection until it reaches the designated ATM device, 774 where it is looped back to the loopback cell insertion 775 point on the designated VC. Success is achieved if the 776 loopback OAM cell returns to the originating point of 777 insertion within 5 seconds, otherwise, the test fails. 779 The manager-station performs a loopback test by making 780 use of the testTable defined in [TestMIB]. In order to 781 run this test the object testType in the testTable 782 shall be set to atmLoopbackVcE2e. The object testTarget 783 points to the row in the atmVclTable in [RFC2515] 784 corresponding to the VC designated for the test. The 785 object testMoreInfo contains the desired Loopback 786 Location ID. 788 Before starting a test, a manager-station must first 789 obtain 'ownership' of the entry in the testTable for 790 the interface to be tested (follow procedure defined in 791 [TestMIB]). Once the manager-station obtains ownership, 792 a loopback test for a given interface can be invoked by 793 first setting up parameters necessary for the loopback 794 test (e.g., set testMoreInfo to AAAABBBBCCCCDDDD and 795 set the testTarget), and then setting the value of 796 testType in the testTable equal to 797 'atmLoopbackVcSegment.d'. The testRowStatus is used to 798 invoke the atmLoopbackVcLocationId test on the VC with 799 the VPI/VCI corresponding to the testTarget and looped 800 back at loopback location ID= AAAABBBBCCCCDDDD. 802 After invoking a loopback test, wait for the test 803 completion by polling for the object testResult. A 804 value of 'inProgress(3)' will result if the test is 805 still in progress. Once the test is completed, the 806 object testResult will have a value of 'success(2)' if 807 the loopback OAM cell returned to the originator of the 808 test within 5 seconds, if not, a value of 'failed(7)' 809 will result. If the ATM system does not support this 810 type of loopback test, then a value of 811 'notSupported(4)' will be provided. Other possible 812 values for the testResult object are 'unAbleToRun(5)' 813 and 'aborted(6)'." 814 ::= { atmLoopbackTestTypes 6 } 816 atmLoopbackVpServiceInternal OBJECT-IDENTITY 817 STATUS current 818 DESCRIPTION 819 "This is a loopback test that the manager requests an 820 agent to perform over the managed resource's internal 821 portion of a designated VP (i.e., between the ingress 822 and egress interfaces of the VP connection). The agent 823 is provided with the Ingress VPI, Egress Interface, and 824 Egress VPI in order to run this internal test. This 825 test may be useful in proxy situations where the proxy 826 agent represents a network. Implementations of this 827 test may be specific to the managed resource. One 828 implementation in a managed network may be as follows, 829 the managed network inserts a segment loopback OAM cell 830 at the network internal segment end-point 831 (corresponding to the ingress connection point) for the 832 designated VP connection. The loopback cell then 833 travels through the network's portion of the VP 834 connection until it reaches the networks connection 835 point to the egress, where it is looped back to the 836 network's cell insertion point on the designated VP. 837 Success is achieved if the loopback OAM cell returns to 838 the originating internal network segment end-point 839 within 5 seconds, otherwise, the test fails. 841 The manager-station performs a loopback test by making 842 use of the testTable defined in [TestMIB]. In order to 843 run this test the object testType in the testTable 844 shall be set to atmLoopbackVpServiceInternal, and the 845 object testTarget points to the row in the 846 atmVpCrossConnectTable in [RFC2515] corresponding to 847 the VP designated for the test. 849 Before starting a test, a manager-station must first 850 obtain 'ownership' of the entry in the testTable for 851 the interface to be tested (follow procedure defined in 852 [TestMIB]). Once the manager-station obtains 853 ownership, a loopback test for a given interface can be 854 invoked by first setting up parameters necessary for 855 the loopback test (e.g., set the testTarget), and then 856 setting the value of testType in the testTable equal to 857 'atmLoopbackVpServiceInternal' The testRowStatus is 858 used to invoke the atmLoopbackVpServiceInternal test on 859 the VP crossconnect with the ingress and egress VPI 860 values corresponding to the testTarget. 862 After invoking a loopback test, wait for the test 863 completion by polling for the object testResult. A 864 value of 'inProgress(3)' will result if the test is 865 still in progress. Once the test is completed, the 866 object testResult will have a value of 'success(2)' if 867 the loopback OAM cell returned to the originator of the 868 test within 5 seconds, if not, a value of 'failed(7)' 869 will result. If the ATM system does not support this 870 type of loopback test, then a value of 871 'notSupported(4)' will be provided. Other possible 872 values for the testResult object are 'unAbleToRun(5)' 873 and 'aborted(6)'." 874 ::= { atmLoopbackTestTypes 7 } 876 atmLoopbackVcServiceInternal OBJECT-IDENTITY 877 STATUS current 878 DESCRIPTION 879 "This is a loopback test that the manager requests an 880 agent to perform over the managed resource's internal 881 portion of a designated VC (i.e., between the ingress 882 and egress interfaces of the VC connection). The agent 883 is provided with the Ingress VPI, Ingress VCI, Egress 884 Interface, Egress VPI, and Egress VCI in order to run 885 this internal test. This test may be useful in proxy 886 situations where the proxy agent represents a network. 887 Implementations of this test may be specific to the 888 managed resource. One implemenation in a managed 889 network may be as follows, the managed network inserts 890 a segment loopback OAM cell at the network internal 891 segment end-point (corresponding to the ingress 892 connection point) for the designated VC connection. 893 The loopback cell then travels through the network's 894 portion of the VC connection until it reaches the 895 network's connection point to the egress, where it is 896 looped back to the network's cell insertion point on 897 the designated VC. Success is achieved if the loopback 898 OAM cell returns to the originating internal network 899 segment end-point within 5 seconds, otherwise, the test 900 fails. 902 The manager-station performs a loopback test by making 903 use of the testTable defined in [TestMIB]. In order to 904 run this test the object testType in the testTable 905 shall be set to atmLoopbackVcServiceInternal, and the 906 object testTarget points to the row in the 907 atmVcCrossConnectTable in [RFC2515] corresponding to 908 the VC designated for the test. 910 Before starting a test, a manager-station must first 911 obtain 'ownership' of the entry in the testTable for 912 the interface to be tested (follow procedure defined in 913 [TestMIB]). Once the manager-station obtains 914 ownership, a loopback test for a given interface can be 915 invoked by first setting up parameters necessary for 916 the loopback test (e.g., set the testTarget), and then 917 setting the value of testType in the testTable equal to 918 'atmLoopbackVcServiceInternal'. The testRowStatus is 919 used to invoke the atmLoopbackVcServiceInternal test on 920 the VC crossconnect with the ingress and egress VPI/VCI 921 values corresponding to the testTarget. 923 After invoking a loopback test, wait for the test 924 completion by polling for the object testResult. A 925 value of 'inProgress(3)' will result if the test is 926 still in progress. Once the test is completed, the 927 object testResult will have a value of 'success(2)' if 928 the loopback OAM cell returned to the originator of the 929 test within 5 seconds, if not, a value of 'failed(7)' 930 will result. If the ATM system does not support this 931 type of loopback test, then a value of 932 'notSupported(4)' will be provided. Other possible 933 values for the testResult object are 'unAbleToRun(5)' 934 and 'aborted(6)'." 935 ::= { atmLoopbackTestTypes 8 } 937 -- ************************************************ 938 -- (2) ATM End-Point Tables 940 -- This concerns information for interfaces 941 -- supporting ATM Loopback Tests and includes: 942 -- 1. ATM VP End-Point Table 943 -- 2. ATM VC End-Point Table 945 atmEndptGroup OBJECT IDENTIFIER ::= { 946 atmTESTMIBObjects 2} 948 -- 1. ATM VP End-Point Table 950 atmVplEndptTable OBJECT-TYPE 951 SYNTAX SEQUENCE OF AtmVplEndptEntry 952 MAX-ACCESS not-accessible 953 STATUS current 954 DESCRIPTION 955 "End-point Information for each VP." 956 ::= { atmEndptGroup 1 } 958 atmVplEndptEntry OBJECT-TYPE 959 SYNTAX AtmVplEndptEntry 960 MAX-ACCESS not-accessible 961 STATUS current 962 DESCRIPTION 963 "An entry with end-point information about the ATM 964 VP." 965 AUGMENTS { atmVplEntry } 966 ::= { atmVplEndptTable 1 } 968 AtmVplEndptEntry ::= 969 SEQUENCE { 970 atmVplEndptSegmentEndPoint INTEGER 971 } 973 atmVplEndptSegmentEndPoint OBJECT-TYPE 974 SYNTAX INTEGER { 975 isaVplSegmentEndPoint(1), 976 notaVplSegmentEndPoint(2) 977 } 979 MAX-ACCESS read-create 980 STATUS current 981 DESCRIPTION 982 "An indication of whether or not the VP interface 983 has been configured to represent a VPC Segment 984 End-Point. If the corresponding VP Link is a UNI, 985 the value of this object is permanently set to 986 isaVplSegmentEndPoint(1). Otherwise, the default 987 is set to notaVplSegmentEndPoint(2)." 988 ::= { atmVplEndptEntry 1 } 990 -- 2. ATM VC End-Point Table 992 atmVclEndptTable OBJECT-TYPE 993 SYNTAX SEQUENCE OF AtmVclEndptEntry 994 MAX-ACCESS not-accessible 995 STATUS current 996 DESCRIPTION 997 "End-point Information for each VC." 998 ::= { atmEndptGroup 2 } 1000 atmVclEndptEntry OBJECT-TYPE 1001 SYNTAX AtmVclEndptEntry 1002 MAX-ACCESS not-accessible 1003 STATUS current 1004 DESCRIPTION 1005 "An entry with end-point information about the ATM 1006 VC." 1007 AUGMENTS { atmVclEntry } 1008 ::= { atmVclEndptTable 1 } 1010 AtmVclEndptEntry ::= 1011 SEQUENCE { 1012 atmVclEndptSegmentEndPoint INTEGER 1013 } 1015 atmVclEndptSegmentEndPoint OBJECT-TYPE 1016 SYNTAX INTEGER { 1017 isaVclSegmentEndPoint(1), 1018 notaVclSegmentEndPoint(2) 1019 } 1020 MAX-ACCESS read-create 1021 STATUS current 1022 DESCRIPTION 1023 "An indication of whether or not the VC interface 1024 has been configured to represent a VCC Segment 1025 End-Point. If the corresponding VC Link is a UNI, 1026 the value of this object is permanently set to 1027 isaVclSegmentEndPoint(1). Otherwise, the default 1028 is set to notaVclSegmentEndPoint(2)." 1029 ::= { atmVclEndptEntry 1 } 1031 -- ************************************************ 1033 -- Conformance Information 1035 atmTESTMIBConformance OBJECT IDENTIFIER ::= {atmTESTMIB 2} 1037 atmTESTMIBGroups OBJECT IDENTIFIER 1038 ::= {atmTESTMIBConformance 1} 1040 atmTESTMIBCompliances OBJECT IDENTIFIER 1041 ::= {atmTESTMIBConformance 2} 1043 -- Compliance Statements 1045 atmTESTMIBCompliance MODULE-COMPLIANCE 1046 STATUS current 1047 DESCRIPTION 1048 "The compliance statement for SNMP entities which 1049 represent ATM interfaces. The compliance statements 1050 are used to determine if a particular group or object 1051 applies to hosts, networks/switches, or both." 1053 MODULE -- this module 1055 MANDATORY-GROUPS { atmLoopbackGroup } 1057 -- Objects in the ATM Loopback Test Group 1059 OBJECT atmIfLogicalLoopbackId 1060 MIN-ACCESS read-only 1061 DESCRIPTION 1062 "Write access is not required. This object is 1063 required for ATM systems supporting the 1064 atmLoopbackVpLocationID and atmLoopbackVcLocationID 1065 tests." 1067 OBJECT atmVplEndptSegmentEndPoint 1068 MIN-ACCESS read-only 1069 DESCRIPTION 1070 "Write access is not required. This object is 1071 mandatory for systems that are supporting ATM loopback 1072 tests." 1074 OBJECT atmVclEndptSegmentEndPoint 1075 MIN-ACCESS read-only 1076 DESCRIPTION 1077 "Write access is not required. This object is 1078 mandatory for systems that are supporting ATM loopback 1079 tests." 1081 ::= { atmTESTMIBCompliances 1 } 1083 -- ********************************************** 1085 -- Units of Conformance 1087 atmLoopbackGroup OBJECT-GROUP 1089 OBJECTS { 1090 atmIfLogicalLoopbackId, 1091 atmVplEndptSegmentEndPoint, 1092 atmVclEndptSegmentEndPoint 1093 } 1094 STATUS current 1095 DESCRIPTION 1096 "A collection of objects providing information 1097 for Loopback Tests." 1098 ::= { atmTESTMIBGroups 1 } 1100 END 1101 6. Security Considerations 1103 There are a number of management objects defined in this MIB 1104 that have a MAX-ACCESS clause of read-write and/or read- 1105 create. Such objects may be considered sensitive or 1106 vulnerable in some network environments. The support for SET 1107 operations in a non-secure environment without proper 1108 protection can have a negative effect on network operations. 1110 The managed objects in this MIB contain sensitive information 1111 since, collectively, they allow the invocation of tests on the 1112 managed device. 1114 This MIB contains objects which allow an administrator to 1115 perform tests on ATM interfaces. Tests can only be performed 1116 when using these objects in conjunction with [TestMIB]. 1117 Unauthorized access to the associated objects could cause a 1118 denial of service, or in combination with other (e.g., 1119 physical) security breaches, could cause unauthorized 1120 connectivity to a device. The tests defined in this document 1121 are not service interrupting. 1123 It is thus important to control even GET access to these 1124 objects and possibly to even encrypt the values of these 1125 object when sending them over the network via SNMP. Not all 1126 versions of SNMP provide features for such a secure 1127 environment. 1129 SNMPv1 by itself is not a secure environment. Even if the 1130 network itself is secure (for example by using IPSec), even 1131 then, there is no control as to who on the secure network is 1132 allowed to access and GET/SET (read/change/create/delete) the 1133 objects in this MIB. 1135 It is recommended that the implementers consider the security 1136 features as provided by the SNMPv3 framework. Specifically, 1137 the use of the User-based Security Model RFC 2574 [RFC2574] 1138 and the View-based Access Control Model RFC 2575 [RFC2575] is 1139 recommended. 1141 It is then a customer/user responsibility to ensure that the 1142 SNMP entity giving access to an instance of this MIB, is 1143 properly configured to give access to the objects only to 1144 those principals (users) that have legitimate rights to indeed 1145 GET or SET (change/create/delete) them. 1147 7. Acknowledgments 1149 This document is a product of the AToMMIB Working Group. The 1150 authors would like to acknowledge the following persons for 1151 their valuable suggestions for this memo 1152 - Dawn Xie 1153 - Umberto Bonollo 1154 - Rod Miller 1155 8. References 1157 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 1158 Architecture for Describing SNMP Management 1159 Frameworks", RFC 2571, April 1999 1161 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 1162 Identification of Management Information for 1163 TCP/IP-based Internets", STD 16, RFC 1155, May 1164 1990 1166 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB 1167 Definitions", STD 16, RFC 1212, March 1991 1169 [RFC1215] M. Rose, "A Convention for Defining Traps for use 1170 with the SNMP", RFC 1215, March 1991 1172 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., 1173 Case, J., Rose, M., and S. Waldbusser, "Structure 1174 of Management Information Version 2 (SMIv2)", STD 1175 58, RFC 2578, April 1999 1177 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., 1178 Case, J., Rose, M., and S. Waldbusser, "Textual 1179 Conventions for SMIv2", STD 58, RFC 2579, April 1180 1999 1182 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., 1183 Case, J., Rose, M., and S. Waldbusser, 1184 "Conformance Statements for SMIv2", STD 58, RFC 1185 2580, April 1999 1187 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. 1188 Davin, "Simple Network Management Protocol", STD 1189 15, RFC 1157, May 1990. 1191 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. 1192 Waldbusser, "Introduction to Community-based 1193 SNMPv2", RFC 1901, January 1996. 1195 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. 1196 Waldbusser, "Transport Mappings for Version 2 of 1197 the Simple Network Management Protocol (SNMPv2)", 1198 RFC 1906, January 1996. 1200 [RFC2572] Case, J., Harrington D., Presuhn R., and B. 1201 Wijnen, "Message Processing and Dispatching for 1202 the Simple Network Management Protocol (SNMP)", 1203 RFC 2572, April 1999 1205 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based 1206 Security Model (USM) for version 3 of the Simple 1207 Network Management Protocol (SNMPv3)", RFC 2574, 1208 April 1999 1210 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. 1211 Waldbusser, "Protocol Operations for Version 2 of 1212 the Simple Network Management Protocol (SNMPv2)", 1213 RFC 1905, January 1996. 1215 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 1216 Applications", RFC 2573, April 1999 1218 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, 1219 "View-based Access Control Model (VACM) for the 1220 Simple Network Management Protocol (SNMP)", RFC 1221 2575, April 1999 1223 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1224 "Introduction to Version 3 of the Internet- 1225 standard Network Management Framework", RFC 2570, 1226 April 1999 1228 [RFC2515] Kaj Tesink, "Definitions of Managed Objects for 1229 ATM Management", RFC 2515, Bellcore, February 1230 1999. 1232 [RFC1213] McCloghrie, K., and M. Rose, Editors, "Management 1233 Information Base for Network Management of 1234 TCP/IP-based internets: MIB-II", STD 17, RFC 1213, 1235 Hughes LAN Systems, Performance Systems 1236 International, March 1991. 1238 [RFC2233] McCloghrie, K. and F. Kastenholz, "The Interfaces 1239 Group MIB", RFC2233, cisco Systems, FTP Software, 1240 November 1997. 1242 [UNI3.0] ATM Forum, "ATM User-Network Interface, Version 1243 3.0 (UNI 3.0) Specification, Part I", 1994. 1245 [UNI3.1] ATM Forum, "ATM User-Network Interface, Version 1246 3.1 (UNI 3.1) Specification, Part I", November 1247 1994. 1249 [I.610] ITU-T Recommendation I.610, "Broadband Integrated 1250 Service Digital Network (B-ISDN) Operation and 1251 Maintenance Principles and Functions", July 1995. 1253 [TestMIB] McCloghrie, K., M. Greene, and K. Tesink, 1254 "Definitions of Managed Objects for System and 1255 Interface Testing", RFCxxxx, cisco Systems, Xedia 1256 Corp, Telcordia, ???? 1999. 1258 9. Authors' Addresses 1260 Michael Noto 1261 3Com Corporation 1262 5400 Bayfront Plaza 1263 Santa Clara, CA 95052 1264 Phone: (408) 326-2218 1265 E-mail: mike_noto@3com.com 1267 Kaj Tesink 1268 Telcordia Technologies 1269 331 Newman Springs Road 1270 P.O. Box 7020 1271 Red Bank, NJ 07701-7020 1272 Phone: (732) 758-5254 1273 EMail: kaj@research.telcordia.com 1275 10. RFC Editor and IANA Considerations 1277 Prior to publication of this memo as an RFC, the RFC Editor 1278 and IANA are requested replace xxxx below with the RFC number 1279 of this document, to make a suitable OBJECT IDENTIFIER 1280 assignment for XX below and update the following in the MIB: 1282 "Initial version, published as RFCxxxx" 1283 ::= { mib-2 XX } 1285 -- ******** NOTE TO THE RFC EDITOR / IANA *********** 1286 -- * Before this module is put on the standards track 1287 -- * fill out RFCxxxx with the RFC number of this document 1288 -- * assign XX by IANA. 1289 -- * remove this notice from the MIB 1290 11. Intellectual Property 1292 The IETF takes no position regarding the validity or scope of 1293 any intellectual property or other rights that might be 1294 claimed to pertain to the implementation or use of the 1295 technology described in this document or the extent to which 1296 any license under such rights might or might not be available; 1297 neither does it represent that it has made any effort to 1298 identify any such rights. Information on the IETF's 1299 procedures with respect to rights in standards-track and 1300 standards-related documentation can be found in BCP-11. 1301 Copies of claims of rights made available for publication and 1302 any assurances of licenses to be made available, or the result 1303 of an attempt made to obtain a general license or permission 1304 for the use of such proprietary rights by implementors or 1305 users of this specification can be obtained from the IETF 1306 Secretariat. 1308 The IETF invites any interested party to bring to its 1309 attention any copyrights, patents or patent applications, or 1310 other proprietary rights which may cover technology that may 1311 be required to practice this standard. Please address the 1312 information to the IETF Executive Director. 1314 12. Full Copyright Statement 1316 Copyright (C) The Internet Society (1999). All Rights 1317 Reserved. 1319 This document and translations of it may be copied and 1320 furnished to others, and derivative works that comment on or 1321 otherwise explain it or assist in its implementation may be 1322 prepared, copied, published and distributed, in whole or in 1323 part, without restriction of any kind, provided that the above 1324 copyright notice and this paragraph are included on all such 1325 copies and derivative works. However, this document itself 1326 may not be modified in any way, such as by removing the 1327 copyright notice or references to the Internet Society or 1328 other Internet organizations, except as needed for the purpose 1329 of developing Internet standards in which case the procedures 1330 for copyrights defined in the Internet Standards process must 1331 be followed, or as required to translate it into languages 1332 other than English. 1334 The limited permissions granted above are perpetual and will 1335 not be revoked by the Internet Society or its successors or 1336 assigns. 1338 This document and the information contained herein is provided 1339 on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 1340 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 1341 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE 1342 USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 1343 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 1344 PARTICULAR PURPOSE. 1346 Table of Contents 1348 1 Status of this Memo ................................... 1 1349 2 Abstract .............................................. 2 1350 3 The SNMP Network Management Framework ................. 2 1351 4 Overview .............................................. 4 1352 4.1 Background .......................................... 4 1353 4.2 Terminology ......................................... 5 1354 4.3 Supported Functions ................................. 6 1355 4.3.1 ATM Loopback Testing .............................. 6 1356 4.3.2 ATM End-Point Tables .............................. 10 1357 5 Definitions ........................................... 11 1358 6 Security Considerations ............................... 29 1359 7 Acknowledgments ....................................... 30 1360 8 References ............................................ 31 1361 9 Authors' Addresses .................................... 33 1362 10 RFC Editor and IANA Considerations ................... 33 1363 11 Intellectual Property ................................ 35 1364 12 Full Copyright Statement ............................. 36