idnits 2.17.1 draft-ietf-atommib-atm2TC-05.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-25) 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 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-05', contains other characters than digits, lowercase letters and dash. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 16 longer pages, the longest (page 2) being 116 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 17 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: ' 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 (October 22, 1996) is 10047 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 536 looks like a reference -- Missing reference section? '2' on line 543 looks like a reference -- Missing reference section? '14' on line 597 looks like a reference -- Missing reference section? '12' on line 591 looks like a reference -- Missing reference section? '5' on line 556 looks like a reference -- Missing reference section? '8' on line 570 looks like a reference -- Missing reference section? '9' on line 575 looks like a reference -- Missing reference section? '3' on line 550 looks like a reference -- Missing reference section? '4' on line 553 looks like a reference -- Missing reference section? '7' on line 566 looks like a reference -- Missing reference section? '10' on line 584 looks like a reference -- Missing reference section? '6' on line 562 looks like a reference -- Missing reference section? '11' on line 588 looks like a reference -- Missing reference section? '13' on line 594 looks like a reference Summary: 12 errors (**), 0 flaws (~~), 3 warnings (==), 16 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT 2 4 Definitions of Textual Conventions and OBJECT-IDENTITIES 5 for ATM Management 7 October 22, 1996 9 Michael Noto (editor) 10 Bell Communications Research 11 noto@cc.bellcore.com 13 Kaj Tesink (editor) 14 Bell Communications Research 15 kaj@cc.bellcore.com 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 10/22/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 Note that for organizational purposes OBJECT IDENTITIES 64 previously defined in RFC1695 have been moved to this 65 specification and no longer appear in the revision of 66 RFC1695[14]. However, the original OBJECT IDENTIFIERs have 67 been preserved. 69 This memo does not specify a standard for the Internet 70 community. 72 draft ATM Textual Conventions and OBJECT-IDENTITIES 10/22/96 74 3. Definitions 76 ATM-TC-MIB DEFINITIONS ::= BEGIN 78 IMPORTS 79 MODULE-IDENTITY, OBJECT-IDENTITY, 80 Integer32, TimeTicks 81 FROM SNMPv2-SMI 82 TEXTUAL-CONVENTION 83 FROM SNMPv2-TC 84 mib-2 85 FROM RFC1213-MIB; 87 atmTCMIB MODULE-IDENTITY 88 LAST-UPDATED "9610220200Z" 89 ORGANIZATION "IETF AToMMIB Working Group" 90 CONTACT-INFO 91 " Michael Noto 92 Postal: Bell Communications Research 93 331 Newman Springs Road 94 Red Bank, NJ 07701 95 USA 96 Tel: +1 908 758 5104 97 Fax: +1 908 758 4177 98 E-mail: noto@cc.bellcore.com 100 Kaj Tesink 101 Postal: Bell Communications Research 102 331 Newman Springs Road 103 Red Bank, NJ 07701 104 USA 105 Tel: +1 908 758 5254 106 Fax: +1 908 758 4177 107 E-mail: kaj@cc.bellcore.com" 108 DESCRIPTION 109 "This MIB Module provides Textual Conventions 110 and OBJECT-IDENTITY Objects to be used by 111 ATM systems." 112 ::= { mib-2 37 3 } -- atmMIB 3 113 -- See [14]. 115 -- The Textual Conventions defined below are organized 116 -- alphabetically 118 draft ATM Textual Conventions and OBJECT-IDENTITIES 10/22/96 120 AtmAddr ::= TEXTUAL-CONVENTION 121 DISPLAY-HINT "1x" 122 STATUS current 123 DESCRIPTION 124 "The ATM address used by the network entity. 125 The address types are: no address (0 octets), 126 E.164 (8 octets), and NSAP (20 octets). 127 Note: The E.164 address is encoded in BCD 128 format." 129 SYNTAX OCTET STRING (SIZE(0|8|20)) 131 AtmConnCastType ::= TEXTUAL-CONVENTION 132 STATUS current 133 DESCRIPTION 134 "The type of topology of a connection (point- 135 to-point, point-to-multipoint). In the case 136 of point-to-multipoint, the orientation of 137 this VPL or VCL in the connection. 138 On a host: 139 - p2mpRoot indicates that the host 140 is the root of the p2mp connection. 141 - p2mpLeaf indicates that the host 142 is a leaf of the p2mp connection. 143 On a switch: 144 - p2mpRoot indicates that cells received 145 by the switching fabric from the interface 146 are from the root of the p2mp connection. 147 - p2mpLeaf indicates that cells transmitted 148 to the interface from the switching fabric 149 are to the leaf of the p2mp connection." 150 SYNTAX INTEGER { 151 p2p(1), 152 p2mpRoot(2), 153 p2mpLeaf(3) 154 } 156 AtmConnKind ::= TEXTUAL-CONVENTION 157 STATUS current 158 DESCRIPTION 159 "The use of call control. The use is as 160 follows: 161 pvc(1) 162 Virtual link of a PVC. Should not be 163 used in an PVC/SVC (i.e., SPVC) 164 crossconnect. 166 draft ATM Textual Conventions and OBJECT-IDENTITIES 10/22/96 168 svcIncoming(2) 169 Virtual link established after a 170 received signaling request to setup 171 an SVC. 172 svcOutgoing(3) 173 Virtual link established after a 174 transmitted or forwarded signaling 175 request to setup an SVC. 176 spvcInitiator(4) 177 Virtual link at the PVC side of an 178 SVC/PVC crossconnect, where the 179 switch is the initiator of the SPVC 180 setup. 181 spvcTarget(5) 182 Virtual link at the PVC side of an 183 SVC/PVC crossconnect, where the 184 switch is the target of the SPVC 185 setup. 187 An spvcInitiator is always cross-connected to 188 an svcOutgoing, and an spvcTarget is always 189 cross-connected to an svcIncoming." 190 SYNTAX INTEGER { 191 pvc(1), 192 svcIncoming(2), 193 svcOutgoing(3), 194 spvcInitiator(4), 195 spvcTarget(5) 196 } 198 AtmServiceCategory ::= TEXTUAL-CONVENTION 199 STATUS current 200 DESCRIPTION 201 "The service category for a connection." 202 REFERENCE 203 "ATM Forum Traffic Management 4.0." 204 SYNTAX INTEGER { 205 other(1), -- none of the following 206 cbr(2), -- constant bit rate 207 rtVbr(3), -- real-time variable bit rate 208 nrtVbr(4), -- non real-time variable bit rate 209 abr(5), -- available bit rate 210 ubr(6) -- unspecified bit rate 211 } 213 draft ATM Textual Conventions and OBJECT-IDENTITIES 10/22/96 215 AtmSigDescrParamIndex ::= TEXTUAL-CONVENTION 216 STATUS current 217 DESCRIPTION 218 "The value of this object identifies a row in the 219 atmSigDescrParamTable. The value 0 signifies that 220 none of the signalling parameters defined in the 221 atmSigDescrParamTable are applicable." 222 SYNTAX Integer32 224 AtmSignallingType ::= TEXTUAL-CONVENTION 225 STATUS current 226 DESCRIPTION 227 "The type of signalling that is used for the 228 identified interface and protocol suite. 230 other: A signalling protocol other than those 231 listed below. 233 Auto-configuration: 234 Indicates that the signalling protocol is to be 235 or has yet to be determined. One such mechanism 236 is via ATM Forum ILMI auto-configuration 237 procedures. 239 ATM Forum UNI 4.0: 240 ATM Forum, Integrated Local Management 241 Interface Specification Version 4.0, 242 July 1996 [12]. 244 ITU-T DSS2: 245 - ITU-T Recommendation Q.2931, Broadband 246 Integrated Service Digital Network (B-ISDN) 247 Digital Subscriber Signalling System No.2 248 (DSS2) User-Network Interface (UNI) Layer 3 249 Specification for Basic Call/Connection 250 Control (September 1994) [5] 251 - ITU-T Draft Recommendation Q.2961, 252 B-ISDN DSS 2 Support of Additional Traffic 253 Parameters (May 1995) [8] 254 NOTE: Update this reference when the draft 255 matures 256 - ITU-T Draft Recommendation Q.2971, 257 B-ISDN DSS 2 User Network Interface Layer 3 258 Specification for Point-to-multipoint 259 Call/connection Control (May 1995) [9] 261 draft ATM Textual Conventions and OBJECT-IDENTITIES 10/22/96 263 ATM Forum UNI 3.0: 264 ATM Forum, ATM User-Network Interface, 265 Version 3.0 (UNI 3.0) Specification, 266 (1994) [3]. 268 ATM Forum UNI 3.1: 269 ATM Forum, ATM User-Network Interface, 270 Version 3.1 (UNI 3.1) Specification, 271 (November 1994) [4]. 273 ATM Forum UNI 4.0: 274 ATM Forum, ATM User-Network Interface, 275 Version 4.0 (UNI 4.0) Specification, 276 af-sig-0061.000 (June 1996) [7]. 278 ATM Forum IISP (based on UNI 3.0 or UNI 3.1) : 279 Interim Inter-switch Signaling Protocol 280 (IISP)Specification, Version 1.0, 281 af-pnni-0026.000, (December 1994) [10]. 283 ATM Forum PNNI 1.0 : 284 ATM Forum, Private Network-Network Interface 285 Specification, Version 1.0, af-pnni-0055.000, 286 (March 1996) [6]. 288 ATM Forum B-ICI: 289 ATM Forum, B-ICI Specification, Version 2.0, 290 af-bici-0013.002, (November 1995) [11]." 291 SYNTAX INTEGER { 292 other(1), 293 autoConfig(2), 294 ituDss2(3), 295 atmfUni3Dot0(4), 296 atmfUni3Dot1(5), 297 atmfUni4Dot0(6), 298 atmfIispUni3Dot0(7), 299 atmfIispUni3Dot1(8), 300 atmfIispUni4Dot0(9), 301 atmfPnni1Dot0(10), 302 atmfBici2Dot0(11) } 304 AtmTrafficDescrParamIndex ::= TEXTUAL-CONVENTION 305 STATUS current 306 DESCRIPTION 307 "The value of this object identifies a row in the 309 draft ATM Textual Conventions and OBJECT-IDENTITIES 10/22/96 311 atmTrafficDescrParamTable. The value 0 signifies 312 that no row has been identified." 313 SYNTAX INTEGER (0..4294967295) 315 AtmVcIdentifier ::= TEXTUAL-CONVENTION 316 STATUS current 317 DESCRIPTION 318 "The VCI value for a VCL. The maximum VCI value 319 cannot exceed the value allowable by 320 atmInterfaceMaxVciBits defined in ATM-MIB." 321 SYNTAX INTEGER (0..65535) 323 AtmVpIdentifier ::= TEXTUAL-CONVENTION 324 STATUS current 325 DESCRIPTION 326 "The VPI value for a VPL or VCL. The value VPI=0 327 is only allowed for a VCL. For ATM UNIs supporting 328 VPCs the VPI value ranges from 1 to 255. For ATM 329 UNIs supporting VCCs the VPI value ranges from 0 330 to 255. The maximum VPI value cannot exceed the 331 value allowable by atmInterfaceMaxVpiBits defined 332 in ATM-MIB." 333 SYNTAX INTEGER (0..4095) 335 AtmVorXAdminStatus ::= TEXTUAL-CONVENTION 336 STATUS current 337 DESCRIPTION 338 "The value determines the desired administrative 339 status of a virtual link or cross-connect. The up 340 and down states indicate that the traffic flow is 341 enabled or disabled respectively on the virtual 342 link or cross-connect." 343 SYNTAX INTEGER { 344 up(1), 345 down(2) 346 } 348 AtmVorXLastChange ::= TEXTUAL-CONVENTION 349 STATUS current 350 DESCRIPTION 351 "The value of MIB II's sysUpTime at the time this 352 virtual link or cross-connect entered its current 353 operational state. If the current state was 354 entered prior to the last re-initialization of the 355 agent then this object contains a zero value." 357 draft ATM Textual Conventions and OBJECT-IDENTITIES 10/22/96 359 SYNTAX TimeTicks 361 AtmVorXOperStatus ::= TEXTUAL-CONVENTION 362 STATUS current 363 DESCRIPTION 364 "The value determines the operational status of a 365 virtual link or cross-connect. The up and down 366 states indicate that the traffic flow is enabled 367 or disabled respectively on the virtual link or 368 cross-connect. The unknown state indicates that 369 the state of it cannot be determined. The state 370 will be down or unknown if the supporting ATM 371 interface(s) is down or unknown respectively." 372 SYNTAX INTEGER { 373 up(1), 374 down(2), 375 unknown(3) 376 } 378 -- OBJECT-IDENTITIES: 380 -- The following atmTrafficDescriptorTypes has been moved 381 -- from [14]. 383 atmTrafficDescriptorTypes OBJECT IDENTIFIER ::= {mib-2 37 1 1} 384 -- atmMIBObjects 385 -- See [14]. 387 -- All other and new OBJECT IDENTITIES go here: 389 atmObjectIdentities OBJECT IDENTIFIER ::= {atmTCMIB 1} 391 -- The following values are defined for use as 392 -- possible values of the ATM traffic descriptor type. 394 atmNoTrafficDescriptor OBJECT-IDENTITY 395 STATUS deprecated 396 DESCRIPTION 397 "This identifies the no ATM traffic 398 descriptor type. Parameters 1, 2, 3, 4, 399 and 5 are not used. This traffic descriptor 400 type can be used for best effort traffic." 402 draft ATM Textual Conventions and OBJECT-IDENTITIES 10/22/96 404 ::= {atmTrafficDescriptorTypes 1} 406 atmNoClpNoScr OBJECT-IDENTITY 407 STATUS current 408 DESCRIPTION 409 "Indicates the CBR.1 Conformance Definition [13] 410 if Best Effort is No. 411 Indicates the UBR.1 and UBR.2 Conformance 412 Definitions [13] if Best Effort is Yes. 413 This traffic descriptor is for no CLP and 414 no Sustained Cell Rate. The use of the 415 parameter vector for this type: 416 Parameter 1: peak cell rate in cells/second 417 for CLP=0+1 traffic 418 Parameter 2: CDVT in tenths of microseconds 419 Parameter 3: not used 420 Parameter 4: not used 421 Parameter 5: not used. 422 This traffic descriptor type can be used 423 for best effort traffic." 424 ::= {atmTrafficDescriptorTypes 2} 426 atmClpNoTaggingNoScr OBJECT-IDENTITY 427 STATUS deprecated 428 DESCRIPTION 429 "This traffic descriptor is for CLP without 430 tagging and no Sustained Cell Rate. The use 431 of the parameter vector for this type: 432 Parameter 1: peak cell rate in cells/second 433 for CLP=0+1 traffic 434 Parameter 2: peak cell rate in cells/second 435 for CLP=0 traffic 436 Parameter 3: not used 437 Parameter 4: not used 438 Parameter 5: not used." 439 ::= {atmTrafficDescriptorTypes 3} 441 atmClpTaggingNoScr OBJECT-IDENTITY 442 STATUS deprecated 443 DESCRIPTION 444 "This traffic descriptor is for CLP with 445 tagging and no Sustained Cell Rate. The use 446 of the parameter vector for this type: 447 Parameter 1: peak cell rate in cells/second 448 for CLP=0+1 traffic 450 draft ATM Textual Conventions and OBJECT-IDENTITIES 10/22/96 452 Parameter 2: peak cell rate in cells/second 453 for CLP=0 traffic, excess 454 tagged as CLP=1 455 Parameter 3: not used 456 Parameter 4: not used 457 Parameter 5: not used." 458 ::= {atmTrafficDescriptorTypes 4} 460 atmNoClpScr OBJECT-IDENTITY 461 STATUS current 462 DESCRIPTION 463 "Indicates the VBR.1 Conformance Definition [13]. 464 This traffic descriptor is for no CLP with 465 Sustained Cell Rate. The use 466 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+1 traffic 471 Parameter 3: maximum burst size in cells 472 Parameter 4: CDVT in tenths of microseconds 473 Parameter 5: not used." 474 ::= {atmTrafficDescriptorTypes 5} 476 atmClpNoTaggingScr OBJECT-IDENTITY 477 STATUS current 478 DESCRIPTION 479 "Indicates the VBR.2 Conformance Definition [13]. 480 This traffic descriptor is for CLP with 481 Sustained Cell Rate and no tagging. 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 487 Parameter 3: maximum burst size in cells 488 Parameter 4: CDVT in tenths of microseconds 489 Parameter 5: not used." 490 ::= {atmTrafficDescriptorTypes 6} 492 atmClpTaggingScr OBJECT-IDENTITY 493 STATUS current 494 DESCRIPTION 495 "Indicates the VBR.3 Conformance Definition [13]. 496 This traffic descriptor is for CLP 498 draft ATM Textual Conventions and OBJECT-IDENTITIES 10/22/96 500 with tagging and Sustained Cell Rate. 501 The use of the parameter vector for this type: 502 Parameter 1: peak cell rate in cells/second 503 for CLP=0+1 traffic 504 Parameter 2: sustainable cell rate in cells/second 505 for CLP=0 traffic, excess tagged as 506 CLP=1 507 Parameter 3: maximum burst size in cells 508 Parameter 4: CDVT in tenths of microseconds 509 Parameter 5: not used." 510 ::= {atmTrafficDescriptorTypes 7} 512 atmClpNoTaggingMCR OBJECT-IDENTITY 513 STATUS current 514 DESCRIPTION 515 "Indicates the ABR Conformance Definition [13]. 516 The use of the parameter vector for this type: 517 Parameter 1: Peak Cell Rate (PCR) 518 Parameter 2: CDVT (PCR) 519 Parameter 3: Minimum Cell Rate (MCR) 520 Parameter 4: unused 521 Parameter 5: unused." 522 ::= {atmTrafficDescriptorTypes 8} 524 END 526 draft ATM Textual Conventions and OBJECT-IDENTITIES 10/22/96 528 4. Acknowledgments 530 This document is a product of the AToMMIB Working Group. 532 draft ATM Textual Conventions and OBJECT-IDENTITIES 10/22/96 534 5. References 536 [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 537 "Textual Conventions for Version 2 of the Simple Network 538 Management Protocol (SNMPv2)", RFC1903, SNMP 539 Research,Inc., Cisco Systems, Inc., Dover Beach 540 Consulting, Inc., International Network Services, January 541 1996. 543 [2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 544 "Structure of Management Information for Version 2 of the 545 Simple Network Management Protocol (SNMPv2)", RFC1902, 546 SNMP Research,Inc., Cisco Systems, Inc., Dover Beach 547 Consulting, Inc., International Network Services, January 548 1996. 550 [3] ATM Forum, "ATM User-Network Interface, Version 3.0 (UNI 551 3.0) Specification", 1994. 553 [4] ATM Forum, "ATM User-Network Interface, Version 3.1 (UNI 554 3.1) Specification", November 1994. 556 [5] ITU-T Recommendation Q.2931, "Broadband Integrated 557 Service Digital Network (B-ISDN) Digital Subscriber 558 Signalling System No.2 (DSS2) User-Network Interface 559 (UNI) Layer 3 Specification for Basic Call/Connection 560 Control", September 1994. 562 [6] ATM Forum, "Private Network-Network Interface 563 Specification Version 1.0 (P-NNI 1.0)", af-pnni-0055.000, 564 March 1996. 566 [7] ATM Forum, "ATM User-Network Interface Signalling 567 Specification, Version 4.0 (UNI 4.0)", af-sig-0061.000, 568 June 1996. 570 [8] ITU-T Draft Recommendation Q.2961, "Broadband Integrated 571 Service Digital Network (B-ISDN) Digital Subscriber 572 Signalling System No.2 (DSS2) Support of Additional 573 Traffic Parameters", May 1995. 575 [9] ITU-T Draft Recommendation Q.2971, "Broadband Integrated 576 Service Digital Network (B-ISDN) Digital Subscriber 577 Signalling System No.2 (DSS2) User Network Interface 578 Layer 3 Specification for Point-to-multipoint 580 draft ATM Textual Conventions and OBJECT-IDENTITIES 10/22/96 582 Call/connection Control", May 1995. 584 [10] ATM Forum, "Interim Inter-switch Signaling Protocol 585 (IISP)Specification, Version 1.0", af-pnni-0026.000, 586 December 1994. 588 [11] ATM Forum, "B-ICI Specification, Version 2.0", af-bici- 589 0013.002, November 1995. 591 [12] ATM Forum, "Integrated Local Management Interface 592 Specification, Version 4.0", af-ilmi-0065.000, July 1996. 594 [13] ATM Forum, "Traffic Management Specification, Version 595 4.0", af-tm-0056.000, June 1996. 597 [14] Kaj Tesink, "Definitions of Managed Objects for ATM 598 Management", RFC???? (Internet-Draft ), Bellcore, October 1996. 601 draft ATM Textual Conventions and OBJECT-IDENTITIES 10/22/96 603 6. Security Considerations 605 Security issues are not discussed in this memo. 607 7. Authors' Addresses 609 Michael Noto 610 Bell Communications Research 611 Room 1E-348 612 331 Newman Springs Road 613 P.O. Box 7020 614 Red Bank, NJ 07701-7020 615 Phone: (908) 758-5104 616 EMail: noto@cc.bellcore.com 618 Kaj Tesink 619 Bell Communications Research 620 Room 1A-427 621 331 Newman Springs Road 622 P.O. Box 7020 623 Red Bank, NJ 07701-7020 624 Phone: (908) 758-5254 625 EMail: kaj@cc.bellcore.com 627 draft ATM Textual Conventions and OBJECT-IDENTITIES 10/22/96 629 Table of Contents 631 1 Status of this Memo ................................... 1 632 2 Introduction .......................................... 2 633 3 Definitions ........................................... 3 634 4 Acknowledgments ....................................... 13 635 5 References ............................................ 14 636 6 Security Considerations ............................... 16 637 7 Authors' Addresses .................................... 16