idnits 2.17.1 draft-ietf-atommib-atm2TC-04.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. ** Bad filename characters: the document name given in the document, 'draft-ietf-atommib-atm2TC-04', contains other characters than digits, lowercase letters and dash. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack 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: ' 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. Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 (June 26, 1996) is 10166 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 519 looks like a reference -- Missing reference section? '2' on line 526 looks like a reference -- Missing reference section? '12' on line 574 looks like a reference -- Missing reference section? '5' on line 539 looks like a reference -- Missing reference section? '8' on line 553 looks like a reference -- Missing reference section? '9' on line 558 looks like a reference -- Missing reference section? '3' on line 533 looks like a reference -- Missing reference section? '4' on line 536 looks like a reference -- Missing reference section? '7' on line 549 looks like a reference -- Missing reference section? '10' on line 567 looks like a reference -- Missing reference section? '6' on line 545 looks like a reference -- Missing reference section? '11' on line 571 looks like a reference -- Missing reference section? '13' on line 577 looks like a reference Summary: 13 errors (**), 0 flaws (~~), 1 warning (==), 15 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Definitions of Textual Conventions and OBJECT-IDENTITIES 3 for ATM Management 5 June 26, 1996 7 Michael Noto (editor) 8 Bell Communications Research 9 noto@cc.bellcore.com 11 Kaj Tesink (editor) 12 Bell Communications Research 13 kaj@cc.bellcore.com 15 17 1. Status of this Memo 19 This document is an Internet-Draft. Internet-Drafts are 20 working documents of the Internet Engineering Task Force 21 (IETF), its Areas, and its Working Groups. Note that other 22 groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six 26 months and may be updated, replaced, or obsoleted by other 27 documents at any time. It is inappropriate to use Internet- 28 Drafts as reference material or to cite them other than as a 29 "work in progress". 31 To learn the current status of any Internet-Draft, please 32 check the "1id-abstracts.txt" listing contained in the 33 Internet-Drafts Shadow Directories on ds.internic.net (US East 34 Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), 35 or munnari.oz.au (Pacific Rim). 37 draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 39 2. Introduction 41 This memo describes Textual Conventions and OBJECT-IDENTITIES 42 used for managing ATM-based interfaces, devices, networks and 43 services. 45 When designing a MIB module, it is often useful to define new 46 types similar to those defined in the SMI. In comparison to a 47 type defined in the SMI, each of these new types has a 48 different name, a similar syntax, but a more precise 49 semantics. These newly defined types are termed textual 50 conventions, and are used for the convenience of humans 51 reading the MIB module. This is done through Textual 52 Conventions as defined in RFC1903[1]. It is the purpose of 53 this document to define the set of textual conventions 54 available to ATM MIB modules. 56 When designing MIB modules, it is also often useful to 57 register further properties with object identifier assignments 58 so that they can be further used by other MIB modules. This 59 is done through the OBJECT-IDENTITY macro defined in 60 RFC1902[2]. This document defines OBJECT-IDENTITIES available 61 to ATM MIB modules. 63 This memo does not specify a standard for the Internet 64 community. 66 draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 68 3. Definitions 70 ATM-TC-MIB DEFINITIONS ::= BEGIN 72 IMPORTS 73 MODULE-IDENTITY, OBJECT-IDENTITY, 74 Integer32 75 FROM SNMPv2-SMI 76 TEXTUAL-CONVENTION, TimeStamp 77 FROM SNMPv2-TC 78 atmMIB, atmTrafficDescriptorTypes 79 FROM ATM-MIB; 81 atmTCMIB MODULE-IDENTITY 82 LAST-UPDATED "9606261200Z" 83 ORGANIZATION "IETF AToMMIB Working Group" 84 CONTACT-INFO 85 " Michael Noto 86 Postal: Bell Communications Research 87 331 Newman Springs Road 88 Red Bank, NJ 07701 89 USA 90 Tel: +1 908 758 5104 91 Fax: +1 908 758 4177 92 E-mail: noto@cc.bellcore.com 94 Kaj Tesink 95 Postal: Bell Communications Research 96 331 Newman Springs Road 97 Red Bank, NJ 07701 98 USA 99 Tel: +1 908 758 5254 100 Fax: +1 908 758 4177 101 E-mail: kaj@cc.bellcore.com" 102 DESCRIPTION 103 "This MIB Module provides Textual Conventions 104 and OBJECT-IDENTITY Objects to be used by 105 ATM systems." 106 ::= { atmMIB 3 } 108 -- The Textual Conventions defined below are organized 109 -- alphabetically 111 draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 113 AtmAddr ::= TEXTUAL-CONVENTION 114 DISPLAY-HINT "1x" 115 STATUS current 116 DESCRIPTION 117 "The ATM address used by the network entity. 118 The address types are: no address (0 octets), 119 E.164 (8 octets), and NSAP (20 octets). 120 Note: The E.164 address is encoded in BCD 121 format." 122 SYNTAX OCTET STRING (SIZE(0|8|20)) 124 AtmConnCastType ::= TEXTUAL-CONVENTION 125 STATUS current 126 DESCRIPTION 127 "The type of topology of a connection (point- 128 to-point, point-to-multipoint). In the case 129 of point-to-multipoint, the orientation of 130 this VPL or VCL in the connection. 131 On a host: 132 - p2mpRoot indicates that the host 133 is the root of the p2mp connection. 134 - p2mpLeaf indicates that the host 135 is a leaf of the p2mp connection. 136 On a switch: 137 - p2mpRoot indicates that cells received 138 by the switching fabric from the interface 139 are from the root of the p2mp connection. 140 - p2mpLeaf indicates that cells transmitted 141 to the interface from the switching fabric 142 are to the leaf of the p2mp connection." 143 SYNTAX INTEGER { 144 p2p(1), 145 p2mpRoot(2), 146 p2mpLeaf(3) 147 } 149 AtmConnKind ::= TEXTUAL-CONVENTION 150 STATUS current 151 DESCRIPTION 152 "The use of call control. The use is as 153 follows: 154 pvc(1) 155 Virtual link of a PVC. Should not be 156 used in an PVC/SVC (i.e., SPVC) 157 crossconnect. 159 draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 161 svcIncoming(2) 162 Virtual link established after a 163 received signaling request to setup 164 an SVC. 165 svcOutgoing(3) 166 Virtual link established after a 167 transmitted or forwarded signaling 168 request to setup an SVC. 169 spvcInitiator(4) 170 Virtual link at the PVC side of an 171 SVC/PVC crossconnect, where the 172 switch is the initiator of the SPVC 173 setup. 174 spvcTarget(5) 175 Virtual link at the PVC side of an 176 SVC/PVC crossconnect, where the 177 switch is the target of the SPVC 178 setup. 180 An spvcInitiator is always cross-connected to 181 an svcOutgoing, and an spvcTarget is always 182 cross-connected to an svcIncoming." 183 SYNTAX INTEGER { 184 pvc(1), 185 svcIncoming(2), 186 svcOutgoing(3), 187 spvcInitiator(4), 188 spvcTarget(5) 189 } 191 AtmServiceCategory ::= TEXTUAL-CONVENTION 192 STATUS current 193 DESCRIPTION 194 "The service category for a connection." 195 REFERENCE 196 "ATM Forum Traffic Management 4.0." 197 SYNTAX INTEGER { 198 other(1), -- none of the following 199 cbr(2), -- constant bit rate 200 rtVbr(3), -- real-time variable bit rate 201 nrtVbr(4), -- non real-time variable bit rate 202 abr(5), -- available bit rate 203 ubr(6) -- unspecified bit rate 204 } 206 draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 208 AtmSigDescrParamIndex ::= TEXTUAL-CONVENTION 209 STATUS current 210 DESCRIPTION 211 "The value of this object identifies a row in the 212 atmSigDescrParamTable. The value 0 signifies that 213 none of the signalling parameters defined in the 214 atmSigDescrParamTable are applicable." 215 SYNTAX Integer32 217 AtmSignallingType ::= TEXTUAL-CONVENTION 218 STATUS current 219 DESCRIPTION 220 "The type of signalling that is used for the 221 identified interface and protocol suite. 223 other: A signalling protocol other than those 224 listed below. 226 Auto-configuration: 227 Indicates that the signalling protocol is to be 228 or has yet to be determined. One such mechanism 229 is via ATM Forum ILMI auto-configuration 230 procedures. 232 ATM Forum UNI 4.0: 233 ATM Forum, Integrated Local Management 234 Interface Specification Version 4.0, 235 July 1996 [12]. 237 ITU-T DSS2: 238 - ITU-T Recommendation Q.2931, Broadband 239 Integrated Service Digital Network (B-ISDN) 240 Digital Subscriber Signalling System No.2 241 (DSS2) User-Network Interface (UNI) Layer 3 242 Specification for Basic Call/Connection 243 Control (September 1994) [5] 244 - ITU-T Draft Recommendation Q.2961, 245 B-ISDN DSS 2 Support of Additional Traffic 246 Parameters (May 1995) [8] 247 NOTE: Update this reference when the draft 248 matures 249 - ITU-T Draft Recommendation Q.2971, 250 B-ISDN DSS 2 User Network Interface Layer 3 251 Specification for Point-to-multipoint 252 Call/connection Control (May 1995) [9] 254 draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 256 ATM Forum UNI 3.0: 257 ATM Forum, ATM User-Network Interface, 258 Version 3.0 (UNI 3.0) Specification, 259 (1994) [3]. 261 ATM Forum UNI 3.1: 262 ATM Forum, ATM User-Network Interface, 263 Version 3.1 (UNI 3.1) Specification, 264 (November 1994) [4]. 266 ATM Forum UNI 4.0: 267 ATM Forum, ATM User-Network Interface, 268 Version 4.0 (UNI 4.0) Specification, 269 af-sig-0061.000 (June 1996) [7]. 271 ATM Forum IISP (based on UNI 3.0 or UNI 3.1) : 272 Interim Inter-switch Signaling Protocol 273 (IISP)Specification, Version 1.0, 274 af-pnni-0026.000, (December 1994) [10]. 276 ATM Forum PNNI 1.0 : 277 ATM Forum, Private Network-Network Interface 278 Specification, Version 1.0, af-pnni-0055.000, 279 (March 1996) [6]. 281 ATM Forum B-ICI: 282 ATM Forum, B-ICI Specification, Version 2.0, 283 af-bici-0013.002, (November 1995) [11]." 284 SYNTAX INTEGER { 285 other(1), 286 autoConfig(2), 287 ituDss2(3), 288 atmfUni3Dot0(4), 289 atmfUni3Dot1(5), 290 atmfUni4Dot0(6), 291 atmfIispUni3Dot0(7), 292 atmfIispUni3Dot1(8), 293 atmfIispUni4Dot0 (9) 294 atmfPnni1Dot0(10), 295 atmfBici2Dot0(11) } 297 AtmTrafficDescrParamIndex ::= TEXTUAL-CONVENTION 298 STATUS current 299 DESCRIPTION 300 "The value of this object identifies a row in the 302 draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 304 atmTrafficDescrParamTable. The value 0 signifies 305 that no row has been identified." 306 SYNTAX INTEGER (0..4294967295) 308 AtmVcIdentifier ::= TEXTUAL-CONVENTION 309 STATUS current 310 DESCRIPTION 311 "The VCI value for a VCL. The maximum VCI value 312 cannot exceed the value allowable by 313 atmInterfaceMaxVciBits defined in ATM-MIB." 314 SYNTAX INTEGER (0..65535) 316 AtmVpIdentifier ::= TEXTUAL-CONVENTION 317 STATUS current 318 DESCRIPTION 319 "The VPI value for a VPL or VCL. The value VPI=0 320 is only allowed for a VCL. For ATM UNIs supporting 321 VPCs the VPI value ranges from 1 to 255. For ATM 322 UNIs supporting VCCs the VPI value ranges from 0 323 to 255. The maximum VPI value cannot exceed the 324 value allowable by atmInterfaceMaxVpiBits defined 325 in ATM-MIB." 326 SYNTAX INTEGER (0..4095) 328 AtmVorXAdminStatus ::= TEXTUAL-CONVENTION 329 STATUS current 330 DESCRIPTION 331 "The value determines the desired administrative 332 status of a virtual link or cross-connect. The up 333 and down states indicate that the traffic flow is 334 enabled or disabled respectively on the virtual 335 link or cross-connect." 336 SYNTAX INTEGER { 337 up(1), 338 down(2) 339 } 341 AtmVorXLastChange ::= TEXTUAL-CONVENTION 342 STATUS current 343 DESCRIPTION 344 "The value of MIB II's sysUpTime at the time this 345 virtual link or cross-connect entered its current 346 operational state. If the current state was 347 entered prior to the last re-initialization of the 348 agent then this object contains a zero value." 350 draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 352 SYNTAX TimeStamp 354 AtmVorXOperStatus ::= TEXTUAL-CONVENTION 355 STATUS current 356 DESCRIPTION 357 "The value determines the desired administrative 358 status of a virtual link or cross-connect. The up 359 and down states indicate that the traffic flow is 360 enabled or disabled respectively on the virtual 361 link or cross-connect. The unknown state indicates 362 that the state of it cannot be determined. The 363 state will be down or unknown if the supporting 364 ATM interface(s) is down or unknown respectively." 365 SYNTAX INTEGER { 366 up(1), 367 down(2), 368 unknown(3) 369 } 371 -- OBJECT-IDENTITIES: 373 atmObjectIdentities OBJECT IDENTIFIER ::= {atmTCMIB 1} 375 -- The following values are defined for use as 376 -- possible values of the ATM traffic descriptor type. 378 atmNoTrafficDescriptor OBJECT-IDENTITY 379 STATUS deprecated 380 DESCRIPTION 381 "This identifies the no ATM traffic 382 descriptor type. Parameters 1, 2, 3, 4, 383 and 5 are not used. This traffic descriptor 384 type can be used for best effort traffic." 385 ::= {atmTrafficDescriptorTypes 1} 387 atmNoClpNoScr OBJECT-IDENTITY 388 STATUS current 389 DESCRIPTION 390 "Indicates the CBR.1 Conformance Definition [13] 391 if Best Effort is No. 392 Indicates the UBR.1 and UBR.2 Conformance 393 Definitions [13] if Best Effort is Yes. 395 draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 397 This traffic descriptor is for no CLP and 398 no Sustained Cell Rate. The use of the 399 parameter vector for this type: 400 Parameter 1: peak cell rate in cells/second 401 for CLP=0+1 traffic 402 Parameter 2: CDVT in tenths of microseconds 403 Parameter 3: not used 404 Parameter 4: not used 405 Parameter 5: not used. 406 This traffic descriptor type can be used 407 for best effort traffic." 408 ::= {atmTrafficDescriptorTypes 2} 410 atmClpNoTaggingNoScr OBJECT-IDENTITY 411 STATUS deprecated 412 DESCRIPTION 413 "This traffic descriptor is for CLP without 414 tagging and no Sustained Cell Rate. The use 415 of the parameter vector for this type: 416 Parameter 1: peak cell rate in cells/second 417 for CLP=0+1 traffic 418 Parameter 2: peak cell rate in cells/second 419 for CLP=0 traffic 420 Parameter 3: not used 421 Parameter 4: not used 422 Parameter 5: not used." 423 ::= {atmTrafficDescriptorTypes 3} 425 atmClpTaggingNoScr OBJECT-IDENTITY 426 STATUS deprecated 427 DESCRIPTION 428 "This traffic descriptor is for CLP with 429 tagging and no Sustained Cell Rate. The use 430 of the parameter vector for this type: 431 Parameter 1: peak cell rate in cells/second 432 for CLP=0+1 traffic 433 Parameter 2: peak cell rate in cells/second 434 for CLP=0 traffic, excess 435 tagged as CLP=1 436 Parameter 3: not used 437 Parameter 4: not used 438 Parameter 5: not used." 439 ::= {atmTrafficDescriptorTypes 4} 441 atmNoClpScr OBJECT-IDENTITY 443 draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 445 STATUS current 446 DESCRIPTION 447 "Indicates the VBR.1 Conformance Definition [13]. 448 This traffic descriptor is for no CLP with 449 Sustained Cell Rate. The use 450 of the parameter vector for this type: 451 Parameter 1: peak cell rate in cells/second 452 for CLP=0+1 traffic 453 Parameter 2: sustainable cell rate in cells/second 454 for CLP=0+1 traffic 455 Parameter 3: maximum burst size in cells 456 Parameter 4: CDVT in tenths of microseconds 457 Parameter 5: not used." 458 ::= {atmTrafficDescriptorTypes 5} 460 atmClpNoTaggingScr OBJECT-IDENTITY 461 STATUS current 462 DESCRIPTION 463 "Indicates the VBR.2 Conformance Definition [13]. 464 This traffic descriptor is for CLP with 465 Sustained Cell Rate and no tagging. 466 The use of the parameter vector for this type: 467 Parameter 1: peak cell rate in cells/second 468 for CLP=0+1 traffic 469 Parameter 2: sustainable cell rate in cells/second 470 for CLP=0 traffic 471 Parameter 3: maximum burst size in cells 472 Parameter 4: CDVT in tenths of microseconds 473 Parameter 5: not used." 474 ::= {atmTrafficDescriptorTypes 6} 476 atmClpTaggingScr OBJECT-IDENTITY 477 STATUS current 478 DESCRIPTION 479 "Indicates the VBR.3 Conformance Definition [13]. 480 This traffic descriptor is for CLP 481 with tagging and Sustained Cell Rate. 482 The use of the parameter vector for this type: 483 Parameter 1: peak cell rate in cells/second 484 for CLP=0+1 traffic 485 Parameter 2: sustainable cell rate in cells/second 486 for CLP=0 traffic, excess tagged as 487 CLP=1 488 Parameter 3: maximum burst size in cells 489 Parameter 4: CDVT in tenths of microseconds 491 draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 493 Parameter 5: not used." 494 ::= {atmTrafficDescriptorTypes 7} 496 atmClpNoTaggingMCR OBJECT-IDENTITY 497 STATUS current 498 DESCRIPTION 499 "Indicates the ABR Conformance Definition [13]. 500 The use of the parameter vector for this type: 501 Parameter 1: Peak Cell Rate (PCR) 502 Parameter 2: CDVT (PCR) 503 Parameter 3: Minimum Cell Rate (MCR) 504 Parameter 4: unused 505 Parameter 5: unused." 506 ::= {atmTrafficDescriptorTypes 8} 508 END 509 draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 511 4. Acknowledgments 513 This document is a product of the AToMMIB Working Group. 515 draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 517 5. References 519 [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 520 "Textual Conventions for Version 2 of the Simple Network 521 Management Protocol (SNMPv2)", RFC1903, SNMP 522 Research,Inc., Cisco Systems, Inc., Dover Beach 523 Consulting, Inc., International Network Services, January 524 1996. 526 [2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 527 "Structure of Management Information for Version 2 of the 528 Simple Network Management Protocol (SNMPv2)", RFC1902, 529 SNMP Research,Inc., Cisco Systems, Inc., Dover Beach 530 Consulting, Inc., International Network Services, January 531 1996. 533 [3] ATM Forum, "ATM User-Network Interface, Version 3.0 (UNI 534 3.0) Specification", 1994. 536 [4] ATM Forum, "ATM User-Network Interface, Version 3.1 (UNI 537 3.1) Specification", November 1994. 539 [5] ITU-T Recommendation Q.2931, "Broadband Integrated 540 Service Digital Network (B-ISDN) Digital Subscriber 541 Signalling System No.2 (DSS2) User-Network Interface 542 (UNI) Layer 3 Specification for Basic Call/Connection 543 Control", September 1994. 545 [6] ATM Forum, "Private Network-Network Interface 546 Specification Version 1.0 (P-NNI 1.0)", af-pnni-0055.000, 547 March 1996. 549 [7] ATM Forum, "ATM User-Network Interface Signalling 550 Specification, Version 4.0 (UNI 4.0)", af-sig-0061.000, 551 June 1996. 553 [8] ITU-T Draft Recommendation Q.2961, "Broadband Integrated 554 Service Digital Network (B-ISDN) Digital Subscriber 555 Signalling System No.2 (DSS2) Support of Additional 556 Traffic Parameters", May 1995. 558 [9] ITU-T Draft Recommendation Q.2971, "Broadband Integrated 559 Service Digital Network (B-ISDN) Digital Subscriber 560 Signalling System No.2 (DSS2) User Network Interface 561 Layer 3 Specification for Point-to-multipoint 563 draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 565 Call/connection Control", May 1995. 567 [10] ATM Forum, "Interim Inter-switch Signaling Protocol 568 (IISP)Specification, Version 1.0", af-pnni-0026.000, 569 December 1994. 571 [11] ATM Forum, "B-ICI Specification, Version 2.0", af-bici- 572 0013.002, November 1995. 574 [12] ATM Forum, "Integrated Local Management Interface 575 Specification, Version 4.0", af-ilmi-0065.000, July 1996. 577 [13] ATM Forum, "Traffic Management Specification, Version 578 4.0", af-tm-0056.000, June 1996. 580 draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 582 6. Security Considerations 584 Security issues are not discussed in this memo. 586 7. Authors' Addresses 588 Michael Noto 589 Bell Communications Research 590 Room 1E-348 591 331 Newman Springs Road 592 P.O. Box 7020 593 Red Bank, NJ 07701-7020 594 Phone: (908) 758-5104 595 EMail: noto@cc.bellcore.com 597 Kaj Tesink 598 Bell Communications Research 599 Room 1A-427 600 331 Newman Springs Road 601 P.O. Box 7020 602 Red Bank, NJ 07701-7020 603 Phone: (908) 758-5254 604 EMail: kaj@cc.bellcore.com 606 draft ATM Textual Conventions and OBJECT-IDENTITIES 6/26/96 608 Table of Contents 610 1 Status of this Memo ................................... 1 611 2 Introduction .......................................... 2 612 3 Definitions ........................................... 3 613 4 Acknowledgments ....................................... 13 614 5 References ............................................ 14 615 6 Security Considerations ............................... 16 616 7 Authors' Addresses .................................... 16