idnits 2.17.1 draft-ietf-atommib-test-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. 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. ** 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. ** Expected the document's filename to be given on the first page, but didn't find any == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 30 longer pages, the longest (page 2) being 117 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 31 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 2. Introduction' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 9. 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 are 2 instances of too long lines in the document, the longest one being 3 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (March 1997) is 9904 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? '1' on line 1126 looks like a reference -- Missing reference section? '2' on line 1129 looks like a reference -- Missing reference section? '3' on line 1134 looks like a reference -- Missing reference section? '4' on line 1139 looks like a reference -- Missing reference section? '5' on line 1145 looks like a reference -- Missing reference section? '6' on line 1150 looks like a reference -- Missing reference section? '10' on line 1164 looks like a reference -- Missing reference section? '8' on line 1157 looks like a reference -- Missing reference section? '9' on line 1160 looks like a reference -- Missing reference section? '7' on line 1154 looks like a reference Summary: 14 errors (**), 0 flaws (~~), 4 warnings (==), 11 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Definitions of Tests 3 for ATM Management 5 March 1997 7 Michael Noto (editor) 8 Network Equipment Technologies 9 mike_noto@net.com 11 Kaj Tesink (editor) 12 Bell Communications Research 13 kaj@cc.bellcore.com 15 1. Status of this Memo 17 This document is an Internet-Draft. Internet-Drafts are 18 working documents of the Internet Engineering Task Force 19 (IETF), its Areas, and its Working Groups. Note that other 20 groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six 24 months and may be updated, replaced, or obsoleted by other 25 documents at any time. It is inappropriate to use Internet- 26 Drafts as reference material or to cite them other than as a 27 "work in progress". 29 To learn the current status of any Internet-Draft, please 30 check the "1id-abstracts.txt" listing contained in the 31 Internet-Drafts Shadow Directories on ds.internic.net (US East 32 Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), 33 or munnari.oz.au (Pacific Rim). 35 draft ATM Test Objects March 1997 37 2. Introduction 39 This memo defines an experimental portion of the Management 40 Information Base (MIB) for use with network management 41 protocols in the Internet community. In particular, it 42 describes objects used for managing ATM-based interfaces, 43 devices, networks and services in addition to those defined in 44 the ATM MIB [1], to provide additional support for the 45 management of ATM Loopback Tests. 47 3. The SNMPv2 Network Management Framework 49 The SNMPv2 Network Management Framework consists of four major 50 components. They are: 52 0 RFC 1902 [2] which defines the SMI, the mechanisms used 53 for describing and naming objects for the purpose of 54 management. 56 0 STD 17, RFC 1213 [3] defines MIB-II, the core set of 57 managed objects for the Internet suite of protocols. 59 0 RFC 1157 [4] and RFC 1905 [5] which define two versions 60 of the protocol used for network access to managed 61 objects. 63 The Framework permits new objects to be defined for the 64 purpose of experimentation and evaluation. 66 draft ATM Test Objects March 1997 68 4. Object Definitions 70 Managed objects are accessed via a virtual information store, 71 termed the Management Information Base or MIB. Objects in the 72 MIB are defined using the subset of Abstract Syntax Notation 73 One (ASN.1) defined in the SMI. In particular, each object 74 type is named by an OBJECT IDENTIFIER, an administratively 75 assigned name. The object type together with an object 76 instance serves to uniquely identify a specific instantiation 77 of the object. For human convenience, we often use a textual 78 string, termed the descriptor, to also refer to the object 79 type. 81 5. Overview 83 The purpose of this memo is to provide additional 84 capabilities, not found in the ATM MIB [1], which are needed 85 to manage ATM interfaces. This memo addresses ATM Testing 86 Support. 88 5.1. Background 90 In addition to the MIB module defined in this memo, other MIB 91 modules are necessary to manage ATM interfaces, links and 92 cross-connects. Examples include MIB II for general system 93 [3] and interface management [6], the DS3 or SONET MIBs for 94 management of SONET and DS3 physical interfaces, and, as 95 appropriate, MIB modules for applications that make use of 96 ATM, such as SMDS and LAN Emulation. These MIB modules are 97 outside the scope of this specification. 99 This MIB module also requires the use of the ATM MIB module 100 defined in [1]. 102 This memo proposes extensions to the ATM MIB in order to 103 support ATM Loopback Tests. An ATM Loopback Test provides the 104 ability to send out a loopback OAM (Operations and 105 Maintenance) cell to verify the exisitence of connectivity for 106 a particular connection. 108 The current specification of this supplemental ATM MIB is 109 based on SNMPv2 SMI. 111 draft ATM Test Objects March 1997 113 5.2. Important Definitions 115 The following terms are defined here and used throughout this 116 MIB: 117 - Virtual Path Link (VPL) 118 - Virtual Path Connection (VPC) 119 - Virtual Path Segment (VP Segment) 120 - Virtual Channel Link (VCL) 121 - Virtual Channel Connection (VCC) 122 - Virtual Channel Segment (VC Segment). 124 _____ _______ _______ _______ _____ 125 | |____| |____| |____| |____| | 126 |Host1| |SwitchA| |SwitchB| |SwitchC| |Host2| 127 | |____| |____| |____| |____| | 128 |_____| |_______| |_______| |_______| |_____| 130 |<----->| Virtual |<----->| Virtual 131 Path Link Path Link 133 |<------------Virtual Path Connection---------->| 134 (between Host1 and Host2) 136 |<--------------->| Virtual Path 137 Segment (between 138 SwitchA and SwitchC) 140 Figure 1: Examples of Virtual Path Links, Virtual Path 141 Connection, and Virtual Path Segment 143 draft ATM Test Objects March 1997 145 _____ _______ _______ _______ _____ 146 | |____| |____| |____| |____| | 147 |Host1|----|SwitchA|----|SwitchB|----|SwitchC|----|Host2| 148 | |____| |____| |____| |____| | 149 |_____| |_______| |_______| |_______| |_____| 151 |<----->| Virtual |<----->| Virtual 152 Channel Link Channel Link 154 |<----------Virtual Channel Connection--------->| 155 (between Host1 and Host2) 157 |<--------------->| Virtual Channel 158 Segment (between 159 SwitchA and SwitchC) 161 Figure 2: Examples of Virtual Channel Links, Virtual 162 Channel Connection, and Virtual Channel Segment 164 5.3. Supported Functions 166 The managed ATM objects are arranged into the following 167 groups: 169 I. ATM Testing Support: 170 (1) ATM Loopback Testing Group 171 (2) ATM End-Point Group. 173 5.3.1. ATM Testing Support 175 5.3.1.1. ATM Loopback Testing Group 177 The loopback test provides the ability to send out a loopback 178 OAM cell to verify the existence of connectivity for a 179 particular connection. Loopback tests can be performed on 180 either an entire connection (i.e., an end-to-end test), a 181 segment of the connection (i.e., a segment test), a portion of 182 a segment (i.e., a loopback location identifier test), or the 183 network portion of a connection (i.e., a service internal 184 test). 186 draft ATM Test Objects March 1997 188 The loopback test makes use of the Test Table defined in [10]. 189 For a given interface, a loopback test can be invoked by 190 obtaining ownership of a test and then by setting the value of 191 'testType' equal to one of the ATM Loopback Test Types defined 192 in Section (8). See procedures in [10] for using the Test 193 Table. After invoking a loopback test, the object 194 'testResult' can be read to determine the outcome of the 195 loopback test (e.g., success(2) if the loopback cell made it 196 back to the originator of the test or failed(7) if the 197 loopback cell did not make it back). 199 This group contains the following types of loopback tests: 201 - End-to-end Loopback Test 202 - Segment Loopback Test 203 - Loopback Test Using Loopback Location Identifier 204 - Network Loopback Test. 206 1) End-to-end Loopback Test 208 The end-to-end loopback (LB) is self-explanatory. For a VP 209 test, the cell is sent on the given VP, via VCI=4 specified in 210 [8]. For a VC test, the LB cell is sent on the VC under test, 211 with the PTI (Payload Type Indicator) set to 5 as specified in 212 [8]. Figure 3 illustrates the end-to-end loopback test. 214 ____ _______ _______ _______ ____ 215 |Host| | | | | | | |Host| 216 |____|----|SwitchA|----|SwitchB|----|SwitchC|----|____| 217 |_______| |_______| |_______| 219 |<--------------------------------------------->| Test 220 Path 222 Figure 3: End-to-end Loopback Test 224 See Section (8) for more details on how to use the End-to-end 225 Loopback Test. 227 2) Segment Loopback Test 229 draft ATM Test Objects March 1997 231 The segment LB test is explained in ITU-T I.610[9]. For a VP 232 segment test, the LB cell is sent on the VP under test via 233 VCI=3 as specified in [8], and the Loopback Location ID field 234 is set to all 1's. For a VC segment test, the LB cell is sent 235 on the VC under test, with the PTI set to 4 as specified in 236 [8], and the Loopback Location ID field is set to all 1's. 238 This test involves a LB cell being inserted at a pre-defined 239 segment end-point, and looped back at the corresponding 240 segment end-point encountered. The pair of segment end-points 241 define a segment (which is used for the segment loopback 242 test). A VP/VC connection can have multiple segments, but 243 multiple segments cannot overlap. 245 A UNI interface is by definition defined as a segment end- 246 point (hence a UNI would be considered a segment). A segment 247 can also define: 248 - a B-ICI 249 - a public carrier's 'piece' of the connection 250 - a private network's 'piece' of the connection. 252 In order to support this functionality, the VP/VC link 253 termination needs to be able to be defined as a segment. This 254 can be done using either the atmVplSegmentEndPoint or 255 atmVclSegmentEndPoint object depending on whether it is for a 256 VPC or VCC. A segment loopback test is illustrated in Figure 257 4. 259 ____ _______ _______ _______ ____ 260 |Host| | | | | | | |Host| 261 |____|----|SwitchA|----|SwitchB|----|SwitchC|----|____| 262 |_______| |_______| |_______| 264 |<----------------------->| Segment 266 Figure 4: Segment Loopback Test 268 Section (8) describes the use of the ATM Segment Loopback 269 Tests. 271 3) Loopback Test Using Loopback Location Identifier 273 draft ATM Test Objects March 1997 275 This loopback test is a special type of 2) where the Loopback 276 Location ID field is set to a value that corresponds to a 277 specific node in a given network (Note that the format of this 278 field is not standardized, that is, the value is significant 279 only within an administrative domain). In this case, the 280 device initiating the LB test inserts the appropriate Loop 281 Back Location ID. When the LB cell reaches the corresponding 282 device, that device recognizes the Loopback Location ID as its 283 own, and loops it back. This test is useful for performing 284 fault sectionalization without having to provision segment 285 end-points. An additional object, the atmLoopbackID, is 286 defined to determine the loopback point. Figure 5 shows a 287 loopback test using a location identifier. Note that the 288 loopback test using location identifier can be used to perform 289 a loopback test over a portion of a defined segment. See 290 Figure 5. 292 ____ _______ _______ _______ ____ 293 |Host| | | | | | | |Host| 294 |____|----|SwitchA|----|SwitchB|----|SwitchC|----|____| 295 |_______| |_______| |_______| 297 |<---------->| Portion of Segment that 298 Loopback test is 299 performed on 301 |<----------------------->| Segment 303 Figure 5: Loopback Test Using Location Identifier 305 See Section (8) for more details. 307 4) Network Loopback Test 309 This is a loopback test that the manager requests an agent in 310 a network to perform over the internal portion of a designated 311 connection. The Network then initiates the internal network 312 loopback test by inserting an OAM loopback cell at one of the 313 end-points of the internal network portion of the connection. 314 When the loopback cell reaches the other end-point of the 315 internal Network , the cell is looped back. This test is 316 useful for verifying connectivity through a particular 317 network. Figure 6 illustrates the Network loopback test. 319 draft ATM Test Objects March 1997 321 ____ _______ _______ _______ ____ 322 |Host| |Netwk 1| |Netwk 1| |Netwk 1| |Host| 323 |____|----|SwitchA|----|SwitchB|----|SwitchC|----|____| 324 |_______| |_______| |_______| 326 |<----------------------->| LB Test Path 327 thru Network 1 329 Figure 6: Network Loopback Test 331 See Section (8) for more details. 333 5.3.1.2. ATM End-Point Group 335 The ATM End-Point Group contains two tables: the ATM VP End- 336 point Table and the ATM VC End-point Table. The ATM VP End- 337 point Table augments the atmVplTable and provides the 338 atmVplEndptSegmentEndPoint object to represent whether or not 339 a specified VPL is a segment end-point. Similarly for Virtual 340 Channels, the ATM VC End-point Table and the 341 atmVclEndptSegmentEndPoint object are used to represent 342 whether or not a specified VCL is a segment end-point. 344 draft ATM Test Objects March 1997 346 6. Definitions 348 ATMTEST-MIB DEFINITIONS ::= BEGIN 350 IMPORTS 351 MODULE-IDENTITY, OBJECT-IDENTITY, 352 OBJECT-TYPE, experimental 353 FROM SNMPv2-SMI 354 MODULE-COMPLIANCE, OBJECT-GROUP 355 FROM SNMPv2-CONF 356 mib-2 357 FROM RFC1213-MIB 358 atmVplEntry, atmVclEntry 359 FROM ATM-MIB; 361 atmTESTMIB MODULE-IDENTITY 362 LAST-UPDATED "9703251200Z" 363 ORGANIZATION "IETF AToMMIB Working Group" 364 CONTACT-INFO 365 " Michael Noto 366 Postal: Network Equipment Technologies 367 800 Saginaw Drive RM 21.1.111 368 Redwood City, CA 94063 369 Tel: +1 415 569-7134 370 E-mail: noto@net.com 372 Kaj Tesink 373 Postal: Bell Communications Research 374 331 Newman Springs Road 375 Red Bank, NJ 07701 376 US 377 Tel: +1 908 758 5254 378 Fax: +1 908 758 4177 379 E-mail: kaj@cc.bellcore.com" 380 DESCRIPTION 381 "This MIB Module provides 382 ATM Loopback Tests and supporting objects 383 that must be supported by ATM devices 384 providing ATM Loopback Tests." 385 ::= { experimental XX } 387 atmTESTMIBObjects OBJECT IDENTIFIER ::= {atmTESTMIB 1} 389 -- ******** NOTE TO THE RFC EDITOR ************** 391 draft ATM Test Objects March 1997 393 -- In case this module is put on the standards track 394 -- replace the following: 395 -- "atmTESTMIB MODULE-IDENTITY ::= {experimental XX}" with 396 -- "atmTESTMIB MODULE-IDENTITY ::= {mib-2 YY}" 397 -- and assign YY by IANA. 399 -- This ATMTEST-MIB Module consists of the following groups: 400 -- ATM Testing Support: 401 -- (1) ATM Loopback Testing Group 402 -- (2) ATM End-Point Group 404 draft ATM Test Objects March 1997 406 -- ************************************************ 407 -- (1) ATM Loopback Testing Group 409 -- This group contains information for interfaces 410 -- supporting ATM Loopback Tests 411 -- This group includes the following: 412 -- 1. ATM Loopback Objects 413 -- 2. List of ATM Loopback Test Types 415 atmLoopbackTestGroup OBJECT IDENTIFIER::= { 416 atmTESTMIBObjects 1} 418 -- 1. ATM Loopback Objects 419 -- The following objects are defined for use in 420 -- performing ATM Loopback Tests. 422 atmLoopbackID OBJECT-TYPE 423 SYNTAX OCTET STRING(SIZE(16)) 424 MAX-ACCESS read-write 425 STATUS current 426 DESCRIPTION 427 "This identifier is used to identify this local 428 ATM device. The value of this object can be used 429 by other ATM devices to identify this local ATM 430 device as the device that is being requested to 431 loopback the OAM Loopback cell. The default for 432 this field is all 1's, which would indicate a 433 segment OAM Loopback Test. Location Identifiers of 434 less than 16 octets are left justified, and padded 435 with all '0's." 436 DEFVAL { 'ffffffffffffffffffffffffffffffff'H } 437 ::= { atmLoopbackTestGroup 1 } 439 -- 2. List of ATM Loopback Test Types 440 -- The following loopback test types are defined: 441 -- atmLoopbackVpE2e 442 -- atmLoopbackVcE2e 443 -- atmLoopbackVpSegment 444 -- atmLoopbackVcSegment 445 -- atmLoopbackVpLocationID 446 -- atmLoopbackVcLocationID 447 -- atmLoopbackVpServcInternal 448 -- atmLoopbackVcServcInternal 450 draft ATM Test Objects March 1997 452 atmLoopbackTestTypes OBJECT IDENTIFIER ::= { 453 atmLoopbackTestGroup 4 } 455 atmLoopbackVpE2e OBJECT-IDENTITY 456 STATUS current 457 DESCRIPTION 458 "This is an end-to-end loopback test performed on a 459 designated VP (Virtual Path). To perform this test 460 an end-to-end loopback OAM cell is inserted at one 461 of the end-points of the designated VP connection 462 (e.g., at a host) via VCI=4 (the VCI value for VP 463 OAM end-to-end cells), travels to the other end- 464 point of the VP connection, and then loops back to 465 the originating end-point on the designated VP. 466 Success is achieved if the loopback OAM cell 467 returns to the originating end-point within 5 468 seconds, otherwise, the test fails. 470 The manager-station performs a loopback test by 471 making use of the testTable) defined in [10]. In 472 order to run this test the object 'testType' in the 473 testTable shall be set to atmLoopbackVpE2e, and the 474 object testTarget points to the row in the 475 atmVplTable in [1] corresponding to the VP 476 designated for the test. 478 Before starting a test, a manager-station must 479 first obtain 'ownership' of the entry in the 480 testTable for the interface to be tested (follow 481 procedure defined in [10]). Once the manager- 482 station obtains ownership, a loopback test for a 483 given interface can be invoked by first setting up 484 parameters necessary for the loopback test (e.g., 485 set the testTarget), and then setting the value of 486 'testType' in the testTable equal to 487 'atmLoopbackVpE2e'. This will cause the 488 atmLoopbackVpE2e test to be invoked on the VP with 489 the VPI corresponding to the testTarget. 491 After invoking a loopback test, wait for the test 492 completion by polling for the object 'testResult'. 493 A value of 'inProgress(3)' will result if the test 494 is still in progress. Once the test is completed, 495 the object 'testResult' will have a value of 497 draft ATM Test Objects March 1997 499 'success(2)' if the loopback OAM cell returned to 500 the originator of the test within 5 seconds, if 501 not, a value of 'failed(7)' will result. If the 502 ATM system does not support this type of loopback 503 test, then a value of 'notSupported(4)' will be 504 provided. Other possible values for the 505 'testResult' object are 'unAbleToRun(5)' and 506 'aborted(6)'." 507 ::= { atmLoopbackTestTypes 1 } 509 atmLoopbackVcE2e OBJECT-IDENTITY 510 STATUS current 511 DESCRIPTION 512 "This is an end-to-end loopback test performed on a 513 designated VC (Virtual Channel). To perform this 514 test an end-to-end loopback OAM cell is inserted at 515 one of the end-points of the designated VC 516 connection (e.g., at a host) via PTI=5 (the PTI 517 value used for VC OAM end-to-end cells), travels to 518 the other end-point of the VC connection, and then 519 loops back to the originating end-point on the 520 designated VC. Success is achieved if the loopback 521 OAM cell returns to the originating end-point within 522 5 seconds, otherwise, the test fails. 524 The manager-station performs a loopback test by 525 making use of the testTable) defined in [10]. In 526 order to run this test the object 'testType' in the 527 testTable shall be set to atmLoopbackVcE2e, and the 528 object testTarget points to the row in the 529 atmVclTable in [1] corresponding to the VC 530 designated for the test. 532 Before starting a test, a manager-station must first 533 obtain 'ownership' of the entry in the testTable for 534 the interface to be tested (follow procedure defined 535 in [10]). Once the manager-station obtains 536 ownership, a loopback test for a given interface can 537 be invoked by first setting up parameters necessary 538 for the loopback test (e.g., set the testTarget), 539 and then setting the value of 'testType' in the 540 testTable equal to 'atmLoopbackVcE2e'. This will 541 cause the atmLoopbackVcE2e test to be invoked on the 542 VC with the VPI/VCI corresponding to the testTarget. 544 draft ATM Test Objects March 1997 546 After invoking a loopback test, wait for the test 547 completion by polling for the object 'testResult'. 548 A value of 'inProgress(3)' will result if the test 549 is still in progress. Once the test is completed, 550 the object 'testResult' will have a value of 551 'success(2)' if the loopback OAM cell returned to 552 the originator of the test within 5 seconds, if not, 553 a value of 'failed(7)' will result. If the ATM 554 system does not support this type of loopback test, 555 then a value of 'notSupported(4)' will be provided. 556 Other possible values for the 'testResult' object 557 are 'unAbleToRun(5)' and 'aborted(6)'." 558 ::= { atmLoopbackTestTypes 2 } 560 atmLoopbackVpSegment OBJECT-IDENTITY 561 STATUS current 562 DESCRIPTION 563 "This is a loopback test performed on a designated 564 segment of a VP (Virtual Path). To perform this test 565 a segment OAM cell is inserted at one of the segment 566 end-points of the designated VP connection (e.g., at 567 a host) via VCI=3 (the VCI used for VP OAM segment 568 cells), travels across the segment on the designated 569 VP to the device pre-configured as the corresponding 570 segment end-point, and then loops back to the 571 originating segment end-point on the designated VP. 572 Success is achieved if the loopback OAM cell returns 573 to the originating end-point within 5 seconds, 574 otherwise, the test fails. 576 In order to use the atmLoopbackVpSegment test, a 577 segment must be defined by setting up segment end- 578 points using the atmVplEndptSegmentEndPoint object 579 from the atmVplEndptTable. The 580 atmVplEndptSegmentEndPoint is set to 581 isaVpSegmentEndPoint(1) for each segment end-point. 582 Note that this object is by default set to 583 isaVpSegmentEndPoint(1) if the atmVplTable supports 584 one end of a UNI. In such a case, a UNI VP loopback 585 test would be achieved when the atmLoopbackVpSegment 586 test was initiated over the UNI. 588 The manager-station performs a loopback test by 589 making use of the testTable) defined in [10]. In 591 draft ATM Test Objects March 1997 593 order to run this test the object 'testType' in the 594 testTable shall be set to atmLoopbackVpE2e, and the 595 object testTarget points to the row in the 596 atmVplTable in [1] corresponding to the VP designated 597 for the test. 599 Before starting a test, a manager-station must first 600 obtain 'ownership' of the entry in the testTable for 601 the interface to be tested (follow procedure defined 602 in [10]). Once the manager-station obtains 603 ownership, a loopback test for a given interface can 604 be invoked by first setting up parameters necessary 605 for the loopback test (e.g., set the testTarget), and 606 then setting the value of 'testType' in the testTable 607 equal to 'atmLoopbackVpSegment'. This will cause the 608 atmLoopbackVpSegment test to be invoked on the VP 609 with the VPI corresponding to the testTarget. 611 After invoking a loopback test, wait for the test 612 completion by polling for the object 'testResult'. A 613 value of 'inProgress(3)' will result if the test is 614 still in progress. Once the test is completed, the 615 object 'testResult' will have a value of 'success(2)' 616 if the loopback OAM cell returned to the originator 617 of the test within 5 seconds, if not, a value of 618 'failed(7)' will result. If the ATM system does not 619 support this type of loopback test, then a value of 620 'notSupported(4)' will be provided. Other possible 621 values for the 'testResult' object are 622 'unAbleToRun(5)' and 'aborted(6)'." 623 ::= { atmLoopbackTestTypes 3 } 625 atmLoopbackVcSegment OBJECT-IDENTITY 626 STATUS current 627 DESCRIPTION 628 "This is a loopback test performed on a designated 629 segment of a VC (Virtual Channel). To perform this 630 test a segment OAM cell is inserted at one of the 631 segment end-points of the designated VC connection 632 (e.g., at a host) via PTI=4 (the PTI value used for VC 633 OAM segment cells), travels across the segment on the 634 designated VC to the device pre-configured as the 635 corresponding segment end-point, and then loops back 636 to the originating segment end-point on the designated 638 draft ATM Test Objects March 1997 640 VC. Success is achieved if the loopback OAM cell 641 returns to the originating end-point within 5 seconds, 642 otherwise, the test fails. 644 In order to use the atmLoopbackVcSegment test, a 645 segment must be defined by setting up segment end- 646 points using the atmVclEndptSegmentEndPoint object 647 from the atmVclEndptTable. The 648 atmVclEndptSegmentEndPoint is set to 649 isaVcSegmentEndPoint(1) for each segment end-point. 650 Note that this object is by default set to 651 isaVcSegmentEndPoint(1) if the atmVclTable supports 652 one end of a UNI. In such a case, a UNI VC loopback 653 test would be achieved when the atmLoopbackVcSegment 654 test was initiated over the UNI. 656 The manager-station performs a loopback test by making 657 use of the testTable) defined in [10]. In order to 658 run this test the object 'testType' in the testTable 659 shall be set to atmLoopbackVcE2e, and the object 660 testTarget points to the row in the atmVclTable in [1] 661 corresponding to the VC designated for the test. 663 Before starting a test, a manager-station must first 664 obtain 'ownership' of the entry in the testTable for 665 the interface to be tested (follow procedure defined 666 in [10]). Once the manager-station obtains ownership, 667 a loopback test for a given interface can be invoked 668 by first setting up parameters necessary for the 669 loopback test (e.g., set the testTarget), and then 670 setting the value of 'testType' in the testTable equal 671 to 'atmLoopbackVcSegment'. This will cause the 672 atmLoopbackVcSegment test to be invoked on the VC with 673 the VPI/VCI corresponding to the testTarget. 675 After invoking a loopback test, wait for the test 676 completion by polling for the object 'testResult'. A 677 value of 'inProgress(3)' will result if the test is 678 still in progress. Once the test is completed, the 679 object 'testResult' will have a value of 'success(2)' 680 if the loopback OAM cell returned to the originator of 681 the test within 5 seconds, if not, a value of 682 'failed(7)' will result. If the ATM system does not 683 support this type of loopback test, then a value of 684 'notSupported(4)' will be provided. Other possible 686 draft ATM Test Objects March 1997 688 values for the 'testResult' object are 689 'unAbleToRun(5)' and 'aborted(6)'." 690 ::= { atmLoopbackTestTypes 4 } 692 atmLoopbackVpLocationId OBJECT-IDENTITY 693 STATUS current 694 DESCRIPTION 695 "This is a loopback test performed on a portion of a 696 designated VP segment. To perform this test a loopback 697 OAM cell is inserted at a connection point of the 698 designated VP connection (e.g., the end-point or a 699 tandem point) with a value inserted in the Location 700 Identifier ID field of the OAM cell that corresponds to 701 the ATM device where the cell is to be looped back. 702 The loopback cell then travels through the VP 703 connection until it reaches the designated ATM device, 704 where it is looped back to the loopback cell insertion 705 point on the designated VP. Success is achieved if the 706 loopback OAM cell returns to the originating point of 707 insertion within 5 seconds, otherwise, the test fails. 709 The manager-station performs a loopback test by making 710 use of the testTable) defined in [10]. In order to run 711 this test the object 'testType' in the testTable shall 712 be set to atmLoopbackVpE2e.d, where the subidentifier 713 'd' consists of 16 subidentifiers with each 714 subidentifier corresponding to the value of a 715 subsequent octet of the Loopback Location ID defined in 716 I.610[9] starting with the most significant octet. The 717 object testTarget points to the row in the atmVplTable 718 in [1] corresponding to the VP designated for the test. 720 Before starting a test, a manager-station must first 721 obtain 'ownership' of the entry in the testTable for 722 the interface to be tested (follow procedure defined in 723 [10]). Once the manager-station obtains ownership, a 724 loopback test for a given interface can be invoked by 725 first setting up parameters necessary for the loopback 726 test (e.g., set d to AAAABBBBCCCCDDDD and set the 727 testTarget), and then setting the value of 'testType' 728 in the testTable equal to 'atmLoopbackVpSegment.d'. 729 This will cause the atmLoopbackVpLocationId test to be 730 invoked on the VP with the VPI corresponding to the 731 testTarget and looped back at loopback location ID= 733 draft ATM Test Objects March 1997 735 AAAABBBBCCCCDDDD. 737 After invoking a loopback test, wait for the test 738 completion by polling for the object 'testResult'. A 739 value of 'inProgress(3)' will result if the test is 740 still in progress. Once the test is completed, the 741 object 'testResult' will have a value of 'success(2)' 742 if the loopback OAM cell returned to the originator of 743 the test within 5 seconds, if not, a value of 744 'failed(7)' will result. If the ATM system does not 745 support this type of loopback test, then a value of 746 'notSupported(4)' will be provided. Other possible 747 values for the 'testResult' object are 'unAbleToRun(5)' 748 and 'aborted(6)'." 749 ::= { atmLoopbackTestTypes 5 } 751 atmLoopbackVcLocationId OBJECT-IDENTITY 752 STATUS current 753 DESCRIPTION 754 "This is a loopback test performed on a portion of a 755 designated Vc segment. To perform this test a loopback 756 OAM cell is inserted at a connection point of the 757 designated VC connection (e.g., the end-point or a 758 tandem point) with a value inserted in the Location 759 Identifier ID field of the OAM cell that corresponds to 760 the ATM device where the cell is to be looped back. 761 The loopback cell then travels through the VC 762 connection until it reaches the designated ATM device, 763 where it is looped back to the loopback cell insertion 764 point on the designated VC. Success is achieved if the 765 loopback OAM cell returns to the originating point of 766 insertion within 5 seconds, otherwise, the test fails. 768 The manager-station performs a loopback test by making 769 use of the testTable) defined in [10]. In order to run 770 this test the object 'testType' in the testTable shall 771 be set to atmLoopbackVcE2e.d, where the subidentifier 772 'd' consists of 16 subidentifiers with each 773 subidentifier corresponding to the value of a 774 subsequent octet of the Loopback Location ID defined in 775 I.610[9] starting with the most significant octet. The 776 object testTarget points to the row in the atmVclTable 777 in [1] corresponding to the VC designated for the test. 779 draft ATM Test Objects March 1997 781 Before starting a test, a manager-station must first 782 obtain 'ownership' of the entry in the testTable for 783 the interface to be tested (follow procedure defined in 784 [10]). Once the manager-station obtains ownership, a 785 loopback test for a given interface can be invoked by 786 first setting up parameters necessary for the loopback 787 test (e.g., set d to AAAABBBBCCCCDDDD and set the 788 testTarget), and then setting the value of 'testType' 789 in the testTable equal to 'atmLoopbackVcSegment.d'. 790 This will cause the atmLoopbackVcLocationId test to be 791 invoked on the VC with the VPI/VCI corresponding to the 792 testTarget and looped back at loopback location ID= 793 AAAABBBBCCCCDDDD. 795 After invoking a loopback test, wait for the test 796 completion by polling for the object 'testResult'. A 797 value of 'inProgress(3)' will result if the test is 798 still in progress. Once the test is completed, the 799 object 'testResult' will have a value of 'success(2)' 800 if the loopback OAM cell returned to the originator of 801 the test within 5 seconds, if not, a value of 802 'failed(7)' will result. If the ATM system does not 803 support this type of loopback test, then a value of 804 'notSupported(4)' will be provided. Other possible 805 values for the 'testResult' object are 'unAbleToRun(5)' 806 and 'aborted(6)'." 807 ::= { atmLoopbackTestTypes 6 } 809 atmLoopbackVpServcInternal OBJECT-IDENTITY 810 STATUS current 811 DESCRIPTION 812 "This is a loopback test that the manager requests an 813 agent to perform over the managed resource's internal 814 portion of a designated VP (i.e., between the ingress 815 and egress interfaces of the VP connection). The agent 816 is provided with the Ingress VPI, Egress Interface, and 817 Egress VPI in order to run this internal test. This 818 test may be useful in proxy situations where the proxy 819 agent represents a network. Implementations of this 820 test may be specific to the managed resource. One 821 implementation in a managed network may be as follows, 822 the managed network inserts a segment loopback OAM cell 823 at the network internal segment end-point 824 (corresponding to the ingress connection point) for the 825 designated VP connection. The loopback cell then 827 draft ATM Test Objects March 1997 829 travels through the network's portion of the VP 830 connection until it reaches the networks connection 831 point to the egress, where it is looped back to the 832 network's cell insertion point on the designated VP. 833 Success is achieved if the loopback OAM cell returns to 834 the originating internal network segment end-point 835 within 5 seconds, otherwise, the test fails. 837 The manager-station performs a loopback test by making 838 use of the testTable) defined in [10]. In order to run 839 this test the object 'testType' in the testTable shall 840 be set to atmLoopbackVpServcInternal, and the object 841 testTarget points to the row in the 842 atmVpCrossConnectTable in [1] corresponding to the VP 843 designated for the test. 845 Before starting a test, a manager-station must first 846 obtain 'ownership' of the entry in the testTable for 847 the interface to be tested (follow procedure defined in 848 [10]). Once the manager-station obtains ownership, a 849 loopback test for a given interface can be invoked by 850 first setting up parameters necessary for the loopback 851 test (e.g., set the testTarget), and then setting the 852 value of 'testType' in the testTable equal to 853 'atmLoopbackVpServcInternal'. This will cause the 854 atmLoopbackVpServcInternal test to be invoked on the VP 855 crossconnect with the ingress and egress VPI values 856 corresponding to the testTarget. 858 After invoking a loopback test, wait for the test 859 completion by polling for the object 'testResult'. A 860 value of 'inProgress(3)' will result if the test is 861 still in progress. Once the test is completed, the 862 object 'testResult' will have a value of 'success(2)' 863 if the loopback OAM cell returned to the originator of 864 the test within 5 seconds, if not, a value of 865 'failed(7)' will result. If the ATM system does not 866 support this type of loopback test, then a value of 867 'notSupported(4)' will be provided. Other possible 868 values for the 'testResult' object are 'unAbleToRun(5)' 869 and 'aborted(6)'." 870 ::= { atmLoopbackTestTypes 7 } 872 atmLoopbackVcServcInternal OBJECT-IDENTITY 873 STATUS current 875 draft ATM Test Objects March 1997 877 DESCRIPTION 878 "This is a loopback test that the manager requests an 879 agent to perform over the managed resource's internal 880 portion of a designated VC (i.e., between the ingress 881 and egress interfaces of the VC connection). The agent 882 is provided with the Ingress VPI, Ingress VCI, Egress 883 Interface, Egress VPI, and Egress VCI in order to run 884 this internal test. This test may be useful in proxy 885 situations where the proxy agent represents a network. 886 Implementations of this test may be specific to the 887 managed resource. One implemenation in a managed 888 network may be as follows, the managed network inserts 889 a segment loopback OAM cell at the network internal 890 segment end-point (corresponding to the ingress 891 connection point) for the designated VC connection. 892 The loopback cell then travels through the network's 893 portion of the VC connection until it reaches the 894 networks connection point to the egress, where it is 895 looped back to the network's cell insertion point on 896 the designated VC. Success is achieved if the loopback 897 OAM cell returns to the originating internal network 898 segment end-point within 5 seconds, otherwise, the test 899 fails. 901 The manager-station performs a loopback test by making 902 use of the testTable) defined in [10]. In order to run 903 this test the object 'testType' in the testTable shall 904 be set to atmLoopbackVcServcInternal, and the object 905 testTarget points to the row in the 906 atmVcCrossConnectTable in [1] corresponding to the VC 907 designated for the test. 909 Before starting a test, a manager-station must first 910 obtain 'ownership' of the entry in the testTable for 911 the interface to be tested (follow procedure defined in 912 [10]). Once the manager-station obtains ownership, a 913 loopback test for a given interface can be invoked by 914 first setting up parameters necessary for the loopback 915 test (e.g., set the testTarget), and then setting the 916 value of 'testType' in the testTable equal to 917 'atmLoopbackVcServcInternal'. This will cause the 918 atmLoopbackVcServcInternal test to be invoked on the VC 919 crossconnect with the ingress and egress VPI/VCI values 920 corresponding to the testTarget. 922 draft ATM Test Objects March 1997 924 After invoking a loopback test, wait for the test 925 completion by polling for the object 'testResult'. A 926 value of 'inProgress(3)' will result if the test is 927 still in progress. Once the test is completed, the 928 object 'testResult' will have a value of 'success(2)' 929 if the loopback OAM cell returned to the originator of 930 the test within 5 seconds, if not, a value of 931 'failed(7)' will result. If the ATM system does not 932 support this type of loopback test, then a value of 933 'notSupported(4)' will be provided. Other possible 934 values for the 'testResult' object are 'unAbleToRun(5)' 935 and 'aborted(6)'." 936 ::= { atmLoopbackTestTypes 8 } 938 draft ATM Test Objects March 1997 940 -- ************************************************ 941 -- (2) ATM End-Point Group 943 -- This group contains information for interfaces 944 -- supporting ATM Loopback Tests 945 -- This group includes the following: 946 -- 1. ATM VP End-Point Table 947 -- 2. ATM VC End-Point Table 949 atmEndptGroup OBJECT IDENTIFIER::= { 950 atmTESTMIBObjects 2} 952 -- 1. ATM VP End-Point Table 954 atmVplEndptTable OBJECT-TYPE 955 SYNTAX SEQUENCE OF AtmVplEndptEntry 956 MAX-ACCESS not-accessible 957 STATUS current 958 DESCRIPTION 959 "End-point Information for each VP." 960 ::= { atmEndptGroup 1 } 962 atmVplEndptEntry OBJECT-TYPE 963 SYNTAX AtmVplEndptEntry 964 MAX-ACCESS not-accessible 965 STATUS current 966 DESCRIPTION 967 "An entry with end-point information about the ATM 968 VP." 969 AUGMENTS { atmVplEntry } 970 ::= { atmVplEndptTable 1 } 972 AtmVplEndptEntry ::= 973 SEQUENCE { 974 atmVplEndptSegmentEndPoint INTEGER 975 } 977 atmVplEndptSegmentEndPoint OBJECT-TYPE 978 SYNTAX INTEGER { 979 isaVplSegmentEndPoint(1), 980 notaVplSegmentEndPoint(2) 982 draft ATM Test Objects March 1997 984 } 985 MAX-ACCESS read-create 986 STATUS current 987 DESCRIPTION 988 "An indication of whether or not the VP interface 989 has been configured to represent a VPC Segment 990 End-Point. If the corresponding VP Link is a UNI, 991 the value of this object is permanently set to 1 992 (isaVplSegmentEndPoint). Otherwise, the default is 993 set to 2 (notaVplSegmentEndPoint)." 994 ::= { atmVplEndptEntry 1 } 996 -- 2. ATM VC End-Point Table 998 atmVclEndptTable OBJECT-TYPE 999 SYNTAX SEQUENCE OF AtmVclEndptEntry 1000 MAX-ACCESS not-accessible 1001 STATUS current 1002 DESCRIPTION 1003 "End-point Information for each VC." 1004 ::= { atmEndptGroup 2 } 1006 atmVclEndptEntry OBJECT-TYPE 1007 SYNTAX AtmVclEndptEntry 1008 MAX-ACCESS not-accessible 1009 STATUS current 1010 DESCRIPTION 1011 "An entry with end-point information about the ATM 1012 VC." 1013 AUGMENTS { atmVclEntry } 1014 ::= { atmVclEndptTable 1 } 1016 AtmVclEndptEntry ::= 1017 SEQUENCE { 1018 atmVclEndptSegmentEndPoint INTEGER 1019 } 1021 atmVclEndptSegmentEndPoint OBJECT-TYPE 1022 SYNTAX INTEGER { 1023 isaVclSegmentEndPoint(1), 1024 notaVclSegmentEndPoint(2) 1025 } 1027 draft ATM Test Objects March 1997 1029 MAX-ACCESS read-create 1030 STATUS current 1031 DESCRIPTION 1032 "An indication of whether or not the VC interface 1033 has been configured to represent a VCC Segment 1034 End-Point. If the corresponding VC Link is a UNI, 1035 the value of this object is permanently set to 1 1036 (isaVclSegmentEndPoint). Otherwise, the default is 1037 set to 2 (notaVclSegmentEndPoint)." 1038 ::= { atmVclEndptEntry 1 } 1040 -- ************************************************ 1042 -- Conformance Information 1044 atmTESTMIBConformance OBJECT IDENTIFIER ::= {atmTESTMIB 2} 1046 atmTESTMIBGroups OBJECT IDENTIFIER 1047 ::= {atmTESTMIBConformance 1} 1049 atmTESTMIBCompliances OBJECT IDENTIFIER 1050 ::= {atmTESTMIBConformance 2} 1052 -- Compliance Statements 1054 atmTESTMIBCompliance MODULE-COMPLIANCE 1055 STATUS current 1056 DESCRIPTION 1057 "The compliance statement for SNMP entities which 1058 represent ATM interfaces. The compliance statements 1059 are used to determine if a particular group or object 1060 applies to hosts, networks/switches, or both." 1062 MODULE -- this module 1064 MANDATORY-GROUPS { atmLoopbackGroup } 1066 -- Objects in the ATM Loopback Test Group 1068 OBJECT atmLoopbackID 1069 MIN-ACCESS read-only 1070 DESCRIPTION 1071 "Write access is not required. This object is 1072 required for ATM systems supporting the 1073 atmLoopbackVpLocationID and atmLoopbackVcLocationID 1075 draft ATM Test Objects March 1997 1077 tests." 1079 OBJECT atmVplEndptSegmentEndPoint 1080 MIN-ACCESS read-only 1081 DESCRIPTION 1082 "Write access is not required. This object is 1083 mandatory for systems that are supporting ATM loopback 1084 tests." 1086 OBJECT atmVclEndptSegmentEndPoint 1087 MIN-ACCESS read-only 1088 DESCRIPTION 1089 "Write access is not required. This object is 1090 mandatory for systems that are supporting ATM loopback 1091 tests." 1093 ::= { atmTESTMIBCompliances 1 } 1095 -- ********************************************** 1097 -- Units of Conformance 1099 atmLoopbackGroup OBJECT-GROUP 1101 OBJECTS { 1102 atmLoopbackID, 1103 atmVplEndptSegmentEndPoint, 1104 atmVclEndptSegmentEndPoint 1105 } 1106 STATUS current 1107 DESCRIPTION 1108 "A collection of objects providing information 1109 for Loopback Tests." 1110 ::= { atmTESTMIBGroups 1 } 1112 END 1114 draft ATM Test Objects March 1997 1116 7. Acknowledgments 1118 This document is a product of the AToMMIB Working Group. The 1119 authors would like to acknowledge Dawn Xie for her valuable 1120 suggestions for this memo. 1122 draft ATM Test Objects March 1997 1124 8. References 1126 [1] Kaj Tesink, "Definitions of Managed Objects for ATM 1127 Management", Internet-Draft, Bellcore, October 1996. 1129 [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1130 and S. Waldbusser, "Structure of Management Information 1131 for version 2 of the Simple Network Management Protocol 1132 (SNMPv2)", RFC 1902, January 1996. 1134 [3] McCloghrie, K., and M. Rose, Editors, "Management 1135 Information Base for Network Management of TCP/IP-based 1136 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 1137 Performance Systems International, March 1991. 1139 [4] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 1140 "Simple Network Management Protocol", RFC 1157, SNMP 1141 Research, Performance Systems International, Performance 1142 Systems International, MIT Laboratory for Computer 1143 Science, May 1990. 1145 [5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1146 and S. Waldbusser, "Protocol Operations for version 2 of 1147 the Simple Network Management Protocol (SNMPv2)", RFC 1148 1905, January 1996. 1150 [6] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1151 MIB", Internet-Draft, cisco Systems, FTP Software, 1152 February 1996. 1154 [7] ATM Forum, "ATM User-Network Interface, Version 3.0 (UNI 1155 3.0) Specification, Part I", 1994. 1157 [8] ATM Forum, "ATM User-Network Interface, Version 3.1 (UNI 1158 3.1) Specification, Part I", November 1994. 1160 [9] ITU-T Recommendation I.610, "Broadband Integrated Service 1161 Digital Network (B-ISDN) Operation and Maintenance 1162 Principles and Functions", July 1995. 1164 [10] McCloghrie, K., M. Greene, and K. Tesink, "Definitions of 1165 Managed Objects for System and Interface Testing", 1166 Internet-Draft, cisco Systems, Ascom Nexion, Bellcore, 1167 November 1996. 1169 draft ATM Test Objects March 1997 1171 9. Security Considerations 1173 Security issues are not discussed in this memo. 1175 10. Authors' Addresses 1177 Michael Noto 1178 Network Equipment Technologies 1179 800 Saginaw Drive RM 21.1.111 1180 Redwood City, CA 94063 1181 Phone +1 415 569-7134 1182 EMail: mike_noto@net.com 1184 Kaj Tesink 1185 Bell Communications Research 1186 331 Newman Springs Road 1187 P.O. Box 7020 1188 Red Bank, NJ 07701-7020 1189 Phone: (908) 758-5254 1190 EMail: kaj@cc.bellcore.com 1192 draft ATM Test Objects March 1997 1194 Table of Contents 1196 1 Status of this Memo ................................... 1 1197 2 Introduction .......................................... 2 1198 3 The SNMPv2 Network Management Framework ............... 2 1199 4 Object Definitions .................................... 3 1200 5 Overview .............................................. 3 1201 5.1 Background .......................................... 3 1202 5.2 Important Definitions ............................... 4 1203 5.3 Supported Functions ................................. 5 1204 5.3.1 ATM Testing Support ............................... 5 1205 5.3.1.1 ATM Loopback Testing Group ...................... 5 1206 5.3.1.2 ATM End-Point Group ............................. 9 1207 6 Definitions ........................................... 10 1208 7 Acknowledgments ....................................... 28 1209 8 References ............................................ 29 1210 9 Security Considerations ............................... 30 1211 10 Authors' Addresses ................................... 30