idnits 2.17.1 draft-ietf-atommib-atm2TC-07.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 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 file name of the draft, 'draft-ietf-atommib-atm2TC-07', contains other characters than digits, lowercase letters and dash. ** Missing revision: the document name given in the document, 'draft-ietf-', does not give the document revision number ~~ Missing draftname component: the document name given in the document, 'draft-ietf-', does not seem to contain all the document name components required ('draft' prefix, document source, document name, and revision) -- see https://www.ietf.org/id-info/guidelines#naming for more information. == Mismatching filename: the document gives the document name as 'draft-ietf-', but the file name used is 'draft-ietf-atommib-atm2TC-07' == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 21 longer pages, the longest (page 2) being 118 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 22 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. ** There are 24 instances of too long lines in the document, the longest one being 8 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 (April 4, 1998) is 9518 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 843 looks like a reference -- Missing reference section? '2' on line 850 looks like a reference -- Missing reference section? '3' on line 857 looks like a reference Summary: 15 errors (**), 1 flaw (~~), 5 warnings (==), 4 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 April 4, 1998 7 Michael Noto (editor) 8 Network Equipment Technologies 9 mike_noto@net.com 11 Ethan Mickey Spiegel (editor) 12 Cisco Systems 13 mspiegel@cisco.com 15 Kaj Tesink (editor) 16 Bell Communications Research 17 kaj@cc.bellcore.com 19 1. Status of this Memo 21 This document is an Internet-Draft. Internet-Drafts are 22 working documents of the Internet Engineering Task Force 23 (IETF), its Areas, and its Working Groups. Note that other 24 groups may also distribute working documents as Internet- 25 Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six 28 months and may be updated, replaced, or obsoleted by other 29 documents at any time. It is inappropriate to use Internet- 30 Drafts as reference material or to cite them other than as a 31 "work in progress". 33 To view the entire list of current Internet-Drafts, please check 34 the "1id-abstracts.txt" listing contained in the Internet-Drafts 35 Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net 36 (Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au 37 (Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu 38 (US West Coast). 40 draft ATM Textual Conventions and OBJECT-IDENTITIES~~~~April 4, 1997 42 2. Introduction 44 This memo describes Textual Conventions and OBJECT-IDENTITIES 45 used for managing ATM-based interfaces, devices, networks and 46 services. 48 When designing a MIB module, it is often useful to define new 49 types similar to those defined in the SMI. In comparison to a 50 type defined in the SMI, each of these new types has a 51 different name, a similar syntax, but a more precise 52 semantics. These newly defined types are termed textual 53 conventions, and are used for the convenience of humans 54 reading the MIB module. This is done through Textual 55 Conventions as defined in RFC1903[1]. It is the purpose of 56 this document to define the set of textual conventions 57 available to ATM MIB modules. 59 When designing MIB modules, it is also often useful to 60 register further properties with object identifier assignments 61 so that they can be further used by other MIB modules. This 62 is done through the OBJECT-IDENTITY macro defined in 63 RFC1902[2]. This document defines OBJECT-IDENTITIES available 64 to ATM MIB modules. 66 Note that for organizational purposes OBJECT IDENTITIES 67 previously defined in RFC1695 have been moved to this 68 specification and no longer appear in the revision of 69 RFC1695[3]. However, the original OBJECT IDENTIFIERs have been 70 preserved. 72 For an introduction to the concepts of ATM connections, see 73 [3]. 75 This memo does not specify a standard for the Internet 76 community. 78 draft ATM Textual Conventions and OBJECT-IDENTITIES~~~~April 4, 1997 80 3. Definitions 82 ATM-TC-MIB DEFINITIONS ::= BEGIN 84 IMPORTS 85 MODULE-IDENTITY, OBJECT-IDENTITY, 86 Integer32, TimeTicks, mib-2 87 FROM SNMPv2-SMI 88 TEXTUAL-CONVENTION 89 FROM SNMPv2-TC; 91 atmTCMIB MODULE-IDENTITY 92 LAST-UPDATED "9804040200Z" 93 ORGANIZATION "IETF AToMMIB Working Group" 94 CONTACT-INFO 95 " Michael Noto 96 Postal: Network Equipment Technologies 97 800 Saginaw Drive RM 21.1.111 98 Redwood City, CA 94063 99 USA 100 Tel: +1 415 569-7134 101 E-mail: mike_noto@net.com 103 Ethan Mickey Spiegel 104 Postal: Cisco Systems 105 170 W. Tasman Dr. 106 San Jose, CA 95134 107 USA 108 Tel: +1 408 526 6408 109 E-mail: mspiegel@cisco.com 111 Kaj Tesink 112 Postal: Bell Communications Research 113 331 Newman Springs Road 114 Red Bank, NJ 07701 115 USA 116 Tel: +1 908 758 5254 117 Fax: +1 908 758 4177 118 E-mail: kaj@cc.bellcore.com" 119 DESCRIPTION 120 "This MIB Module provides Textual Conventions 121 and OBJECT-IDENTITY Objects to be used by 122 ATM systems." 123 ::= { mib-2 37 3 } -- atmMIB 3 (see [3]) 125 draft ATM Textual Conventions and OBJECT-IDENTITIES~~~~April 4, 1997 127 -- The Textual Conventions defined below are organized 128 -- alphabetically 130 AtmAddr ::= TEXTUAL-CONVENTION 131 DISPLAY-HINT "1x" 132 STATUS current 133 DESCRIPTION 134 "An ATM address. The semantics are implied by 135 the length. The address types are: - no 136 address (0 octets) - E.164 (8 octets) - NSAP 137 (20 octets) In addition, when subaddresses 138 are used the AtmAddr may represent the 139 concatenation of address and subaddress. The 140 associated address types are: - E.164, E.164 141 (16 octets) - E.164, NSAP (28 octets) - NSAP, 142 NSAP (40 octets) Address lengths other than 143 defined in this definition imply address 144 types defined elsewhere. Note: The E.164 145 address is encoded in BCD format." 146 SYNTAX OCTET STRING (SIZE(0..40)) 148 AtmConnCastType ::= TEXTUAL-CONVENTION 149 STATUS current 150 DESCRIPTION 151 "The type of topology of a connection (point- 152 to-point, point-to-multipoint). In the case 153 of point-to-multipoint, the orientation of 154 this VPL or VCL in the connection. 155 On a host: 156 - p2mpRoot indicates that the host 157 is the root of the p2mp connection. 158 - p2mpLeaf indicates that the host 159 is a leaf of the p2mp connection. 160 On a switch interface: 161 - p2mpRoot indicates that cells received 162 by the switching fabric from the interface 163 are from the root of the p2mp connection. 164 - p2mpLeaf indicates that cells transmitted 165 to the interface from the switching fabric 166 are to the leaf of the p2mp connection." 167 SYNTAX INTEGER { 169 draft ATM Textual Conventions and OBJECT-IDENTITIES~~~~April 4, 1997 171 p2p(1), 172 p2mpRoot(2), 173 p2mpLeaf(3) 174 } 176 AtmConnKind ::= TEXTUAL-CONVENTION 177 STATUS current 178 DESCRIPTION 179 "The type of call control used for an ATM 180 connection at a particular interface. The use 181 is as follows: 182 pvc(1) 183 Virtual link of a PVC. Should not be 184 used for an PVC/SVC (i.e., Soft PVC) 185 crossconnect. 186 svcIncoming(2) 187 Virtual link established after a 188 received signaling request to setup 189 an SVC. 190 svcOutgoing(3) 191 Virtual link established after a 192 transmitted or forwarded signaling 193 request to setup an SVC. 194 spvcInitiator(4) 195 Virtual link at the PVC side of an 196 SVC/PVC crossconnect, where the 197 switch is the initiator of the Soft PVC 198 setup. 199 spvcTarget(5) 200 Virtual link at the PVC side of an 201 SVC/PVC crossconnect, where the 202 switch is the target of the Soft PVC 203 setup. 205 For PVCs, a pvc virtual link is always cross- 206 connected to a pvc virtual link. 208 For SVCs, an svcIncoming virtual link is always cross- 209 connected to an svcOutgoing virtual link. 211 For Soft PVCs, an spvcInitiator is either cross-connected to 212 an svcOutgoing or an spvcTarget, and an spvcTarget is either 213 cross-connected to an svcIncoming or an spvcInitiator." 214 SYNTAX INTEGER { 215 pvc(1), 217 draft ATM Textual Conventions and OBJECT-IDENTITIES~~~~April 4, 1997 219 svcIncoming(2), 220 svcOutgoing(3), 221 spvcInitiator(4), 222 spvcTarget(5) 223 } 225 AtmIlmiNetworkPrefix ::= TEXTUAL-CONVENTION 226 STATUS current 227 DESCRIPTION 228 "A network prefix used for ILMI address 229 registration. In the case of ATM endsystem 230 addresses (AESAs), the network prefix is the first 231 13 octets of the address which includes the AFI, 232 IDI, and HO-DSP fields. In the case of native 233 E.164 addresses, the network prefix is the entire 234 E.164 address encoded in 8 octets, as if it were 235 an E.164 IDP in an ATM endsystem address 236 structure." 237 REFERENCE 238 "ATM Forum, Integrated Local Management Interface 239 (ILMI) Specification, Version 4.0, 240 af-ilmi-0065.000, September 1996, Section 9 241 ATM Forum, ATM User-Network Interface Signalling 242 Specification, Version 4.0 (UNI 4.0), 243 af-sig-0061.000, June 1996, Section 3" 244 SYNTAX OCTET STRING (SIZE(8|13)) 246 AtmInterfaceType ::= TEXTUAL-CONVENTION 247 STATUS current 248 DESCRIPTION 249 "The connection setup procedures used for the 250 identified interface. 252 Other: Connection setup procedures other than 253 those listed below. 255 Auto-configuration: 256 Indicates that the connection setup 257 procedures are to be determined dynamically, 258 or that determination has not yet been 259 completed. One such mechanism is via ATM 260 Forum ILMI auto-configuration procedures. 262 ITU-T DSS2: 263 - ITU-T Recommendation Q.2931, Broadband 265 draft ATM Textual Conventions and OBJECT-IDENTITIES~~~~April 4, 1997 267 Integrated Service Digital Network (B-ISDN) 268 Digital Subscriber Signalling System No.2 269 (DSS2) User-Network Interface (UNI) Layer 3 270 Specification for Basic Call/Connection 271 Control (September 1994) 272 - ITU-T Draft Recommendation Q.2961, 273 B-ISDN DSS 2 Support of Additional Traffic 274 Parameters (May 1995) 276 - ITU-T Draft Recommendation Q.2971, 277 B-ISDN DSS 2 User Network Interface Layer 3 278 Specification for Point-to-multipoint 279 Call/connection Control (May 1995) 281 ATM Forum UNI 3.0: 282 ATM Forum, ATM User-Network Interface, 283 Version 3.0 (UNI 3.0) Specification, 284 (1994). 286 ATM Forum UNI 3.1: 287 ATM Forum, ATM User-Network Interface, 288 Version 3.1 (UNI 3.1) Specification, 289 (November 1994). 291 ATM Forum UNI Signalling 4.0: 292 ATM Forum, ATM User-Network Interface (UNI) 293 Signalling Specification Version 4.0, 294 af-sig-0061.000 (June 1996). 296 ATM Forum IISP (based on UNI 3.0 or UNI 3.1) : 297 Interim Inter-switch Signaling Protocol 298 (IISP) Specification, Version 1.0, 299 af-pnni-0026.000, (December 1994). 301 ATM Forum PNNI 1.0 : 302 ATM Forum, Private Network-Network Interface 303 Specification, Version 1.0, af-pnni-0055.000, 304 (March 1996). 306 ATM Forum B-ICI: 307 ATM Forum, B-ICI Specification, Version 2.0, 308 af-bici-0013.002, (November 1995). 310 ATM Forum UNI PVC Only: 311 An ATM Forum compliant UNI with the 313 draft ATM Textual Conventions and OBJECT-IDENTITIES~~~~April 4, 1997 315 signalling disabled. 317 ATM Forum NNI PVC Only: 318 An ATM Forum compliant NNI with the 319 signalling disabled." 320 SYNTAX INTEGER { 321 other(1), 322 autoConfig(2), 323 ituDss2(3), 324 atmfUni3Dot0(4), 325 atmfUni3Dot1(5), 326 atmfUni4Dot0(6), 327 atmfIispUni3Dot0(7), 328 atmfIispUni3Dot1(8), 329 atmfIispUni4Dot0(9), 330 atmfPnni1Dot0(10), 331 atmfBici2Dot0(11), 332 atmfUniPvcOnly(12), 333 atmfNniPvcOnly(13) } 335 AtmServiceCategory ::= TEXTUAL-CONVENTION 336 STATUS current 337 DESCRIPTION 338 "The service category for a connection." 339 REFERENCE 340 "ATM Forum Traffic Management Specification, 341 Version 4.0, af-tm-0056.000, June 1996." 342 SYNTAX INTEGER { 343 other(1), -- none of the following 344 cbr(2), -- constant bit rate 345 rtVbr(3), -- real-time variable bit rate 346 nrtVbr(4), -- non real-time variable bit rate 347 abr(5), -- available bit rate 348 ubr(6) -- unspecified bit rate 349 } 351 AtmSigDescrParamIndex ::= TEXTUAL-CONVENTION 352 STATUS current 353 DESCRIPTION 354 "The value of this object identifies a row in the 355 atmSigDescrParamTable. The value 0 signifies that 356 none of the signalling parameters defined in the 357 atmSigDescrParamTable are applicable." 358 SYNTAX INTEGER (0..2147483647) 360 draft ATM Textual Conventions and OBJECT-IDENTITIES~~~~April 4, 1997 362 AtmTrafficDescrParamIndex ::= TEXTUAL-CONVENTION 363 STATUS current 364 DESCRIPTION 365 "The value of this object identifies a row in the 366 atmTrafficDescrParamTable. The value 0 signifies 367 that no row has been identified." 368 SYNTAX INTEGER (0..2147483647) 370 AtmVcIdentifier ::= TEXTUAL-CONVENTION 371 STATUS current 372 DESCRIPTION 373 "The VCI value for a VCL. The maximum VCI value 374 cannot exceed the value allowable by 375 atmInterfaceMaxVciBits defined in ATM-MIB." 376 SYNTAX INTEGER (0..65535) 378 AtmVpIdentifier ::= TEXTUAL-CONVENTION 379 STATUS current 380 DESCRIPTION 381 "The VPI value for a VPL or VCL. The value VPI=0 382 is only allowed for a VCL. For ATM UNIs supporting 383 VPCs the VPI value ranges from 0 to 255. The VPI 384 value 0 is supported for ATM UNIs conforming to 385 the ATM Forum UNI 4.0 Annex 8 (Virtual UNIs) 386 specification. For ATM UNIs supporting VCCs the 387 VPI value ranges from 0 to 255. For ATM NNIs the 388 VPI value ranges from 0 to 4095. The maximum VPI 389 value cannot exceed the value allowable by 390 atmInterfaceMaxVpiBits defined in ATM-MIB." 391 SYNTAX INTEGER (0..4095) 393 AtmVorXAdminStatus ::= TEXTUAL-CONVENTION 394 STATUS current 395 DESCRIPTION 396 "The value determines the desired administrative 397 status of a virtual link or cross-connect. The up 398 and down states indicate that the traffic flow is 399 enabled or disabled respectively on the virtual 400 link or cross-connect." 401 SYNTAX INTEGER { 402 up(1), 403 down(2) 404 } 406 AtmVorXLastChange ::= TEXTUAL-CONVENTION 408 draft ATM Textual Conventions and OBJECT-IDENTITIES~~~~April 4, 1997 410 STATUS current 411 DESCRIPTION 412 "The value of MIB II's sysUpTime at the time a 413 virtual link or cross-connect entered its current 414 operational state. If the current state was 415 entered prior to the last re-initialization of the 416 agent then this object contains a zero value." 417 SYNTAX TimeTicks 419 AtmVorXOperStatus ::= TEXTUAL-CONVENTION 420 STATUS current 421 DESCRIPTION 422 "The value determines the operational status of a 423 virtual link or cross-connect. The up and down 424 states indicate that the traffic flow is enabled 425 or disabled respectively on the virtual link or 426 cross-connect. The unknown state indicates that 427 the state of it cannot be determined. The state 428 will be down or unknown if the supporting ATM 429 interface(s) is down or unknown respectively." 430 SYNTAX INTEGER { 431 up(1), 432 down(2), 433 unknown(3) 434 } 436 -- OBJECT-IDENTITIES: 438 -- The following atmTrafficDescriptorTypes has been moved 439 -- from RFC1695 and no longer appear in the revision of 440 -- RFC1695[3]. 442 atmTrafficDescriptorTypes OBJECT IDENTIFIER ::= {mib-2 37 1 1} 443 -- atmMIBObjects 444 -- See [3]. 446 -- All other and new OBJECT IDENTITIES 447 -- are defined under the following subtree: 449 atmObjectIdentities OBJECT IDENTIFIER ::= {atmTCMIB 1} 451 -- The following values are defined for use as 453 draft ATM Textual Conventions and OBJECT-IDENTITIES~~~~April 4, 1997 455 -- possible values of the ATM traffic descriptor type. 457 atmNoTrafficDescriptor OBJECT-IDENTITY 458 STATUS deprecated 459 DESCRIPTION 460 "This identifies the no ATM traffic 461 descriptor type. Parameters 1, 2, 3, 4, 462 and 5 are not used. This traffic descriptor 463 type can be used for best effort traffic." 464 ::= {atmTrafficDescriptorTypes 1} 466 atmNoClpNoScr OBJECT-IDENTITY 467 STATUS current 468 DESCRIPTION 469 "This traffic descriptor type is for no CLP 470 and no Sustained Cell Rate. The use of the 471 parameter vector for this type: 472 Parameter 1: peak cell rate in cells/second 473 for CLP=0+1 traffic 474 Parameter 2: not used 475 Parameter 3: not used 476 Parameter 4: not used 477 Parameter 5: not used." 478 REFERENCE 479 "ATM Forum,ATM User-Network Interface, 480 Version 3.0 (UNI 3.0) Specification, 1994. 481 ATM Forum, ATM User-Network Interface, 482 Version 3.1 (UNI 3.1) Specification, 483 November 1994." 484 ::= {atmTrafficDescriptorTypes 2} 486 atmClpNoTaggingNoScr OBJECT-IDENTITY 487 STATUS deprecated 488 DESCRIPTION 489 "This traffic descriptor is for CLP without 490 tagging and no Sustained Cell Rate. The use 491 of the parameter vector for this type: 492 Parameter 1: peak cell rate in cells/second 493 for CLP=0+1 traffic 494 Parameter 2: peak cell rate in cells/second 495 for CLP=0 traffic 496 Parameter 3: not used 497 Parameter 4: not used 498 Parameter 5: not used." 499 ::= {atmTrafficDescriptorTypes 3} 501 draft ATM Textual Conventions and OBJECT-IDENTITIES~~~~April 4, 1997 503 atmClpTaggingNoScr OBJECT-IDENTITY 504 STATUS deprecated 505 DESCRIPTION 506 "This traffic descriptor is for CLP with 507 tagging and no Sustained Cell Rate. The use 508 of the parameter vector for this type: 509 Parameter 1: peak cell rate in cells/second 510 for CLP=0+1 traffic 511 Parameter 2: peak cell rate in cells/second 512 for CLP=0 traffic, excess 513 tagged as CLP=1 514 Parameter 3: not used 515 Parameter 4: not used 516 Parameter 5: not used." 517 ::= {atmTrafficDescriptorTypes 4} 519 atmNoClpScr OBJECT-IDENTITY 520 STATUS current 521 DESCRIPTION 522 "This traffic descriptor type is for no CLP 523 with Sustained Cell Rate. The use of the 524 parameter vector for this type: 525 Parameter 1: peak cell rate in cells/second 526 for CLP=0+1 traffic 527 Parameter 2: sustainable cell rate in cells/second 528 for CLP=0+1 traffic 529 Parameter 3: maximum burst size in cells 530 Parameter 4: not used 531 Parameter 5: not used." 532 REFERENCE 533 "ATM Forum,ATM User-Network Interface, 534 Version 3.0 (UNI 3.0) Specification, 1994. 535 ATM Forum, ATM User-Network Interface, 536 Version 3.1 (UNI 3.1) Specification, 537 November 1994." 538 ::= {atmTrafficDescriptorTypes 5} 540 atmClpNoTaggingScr OBJECT-IDENTITY 541 STATUS current 542 DESCRIPTION 543 "This traffic descriptor type is for CLP with 544 Sustained Cell Rate and no tagging. The use 545 of the parameter vector for this type: 546 Parameter 1: peak cell rate in cells/second 547 for CLP=0+1 traffic 549 draft ATM Textual Conventions and OBJECT-IDENTITIES~~~~April 4, 1997 551 Parameter 2: sustainable cell rate in cells/second 552 for CLP=0 traffic 553 Parameter 3: maximum burst size in cells 554 Parameter 4: not used 555 Parameter 5: not used." 556 REFERENCE 557 "ATM Forum,ATM User-Network Interface, 558 Version 3.0 (UNI 3.0) Specification, 1994. 559 ATM Forum, ATM User-Network Interface, 560 Version 3.1 (UNI 3.1) Specification, 561 November 1994." 562 ::= {atmTrafficDescriptorTypes 6} 564 atmClpTaggingScr OBJECT-IDENTITY 565 STATUS current 566 DESCRIPTION 567 "This traffic descriptor type is for CLP with 568 tagging and Sustained Cell Rate. The use of 569 the parameter vector for this type: 570 Parameter 1: peak cell rate in cells/second 571 for CLP=0+1 traffic 572 Parameter 2: sustainable cell rate in cells/second 573 for CLP=0 traffic, excess tagged as 574 CLP=1 575 Parameter 3: maximum burst size in cells 576 Parameter 4: not used 577 Parameter 5: not used." 578 REFERENCE 579 "ATM Forum,ATM User-Network Interface, 580 Version 3.0 (UNI 3.0) Specification, 1994. 581 ATM Forum, ATM User-Network Interface, 582 Version 3.1 (UNI 3.1) Specification, 583 November 1994." 584 ::= {atmTrafficDescriptorTypes 7} 586 atmClpNoTaggingMcr OBJECT-IDENTITY 587 STATUS current 588 DESCRIPTION 589 "This traffic descriptor type is for CLP with 590 Minimum Cell Rate and no tagging. The use of 591 the parameter vector for this type: 592 Parameter 1: peak cell rate in cells/second 593 for CLP=0+1 traffic 594 Parameter 2: CDVT in tenths of microseconds 595 Parameter 3: minimum cell rate in cells/second 597 draft ATM Textual Conventions and OBJECT-IDENTITIES~~~~April 4, 1997 599 Parameter 4: unused 600 Parameter 5: unused." 601 REFERENCE 602 "ATM Forum,ATM User-Network Interface, 603 Version 3.0 (UNI 3.0) Specification, 1994. 604 ATM Forum, ATM User-Network Interface, 605 Version 3.1 (UNI 3.1) Specification, 606 November 1994." 607 ::= {atmTrafficDescriptorTypes 8} 609 atmClpTransparentNoScr OBJECT-IDENTITY 610 STATUS current 611 DESCRIPTION 612 "This traffic descriptor type is for the CLP- 613 transparent model and no Sustained Cell Rate. 614 The use of the parameter vector for this type: 615 Parameter 1: peak cell rate in cells/second 616 for CLP=0+1 traffic 617 Parameter 2: CDVT in tenths of microseconds 618 Parameter 3: not used 619 Parameter 4: not used 620 Parameter 5: not used. 622 This traffic descriptor type is applicable to 623 connections following the CBR.1 conformance 624 definition. 626 Connections specifying this traffic descriptor 627 type will be rejected at UNI 3.0 or UNI 3.1 628 interfaces. For a similar traffic descriptor 629 type that can be accepted at UNI 3.0 and 630 UNI 3.1 interfaces, see atmNoClpNoScr." 631 REFERENCE 632 "ATM Forum,ATM User-Network Interface, 633 Version 3.0 (UNI 3.0) Specification, 1994. 634 ATM Forum, ATM User-Network Interface, 635 Version 3.1 (UNI 3.1) Specification, 636 November 1994. 637 ATM Forum, Traffic Management Specification, 638 Version 4.0, af-tm-0056.000, June 1996." 639 ::= {atmTrafficDescriptorTypes 9} 641 atmClpTransparentScr OBJECT-IDENTITY 642 STATUS current 643 DESCRIPTION 645 draft ATM Textual Conventions and OBJECT-IDENTITIES~~~~April 4, 1997 647 "This traffic descriptor type is for the CLP- 648 transparent model with Sustained Cell Rate. 649 The use of the parameter vector for this type: 650 Parameter 1: peak cell rate in cells/second 651 for CLP=0+1 traffic 652 Parameter 2: sustainable cell rate in cells/second 653 for CLP=0+1 traffic 654 Parameter 3: maximum burst size in cells 655 Parameter 4: CDVT in tenths of microseconds 656 Parameter 5: not used. 658 This traffic descriptor type is applicable to 659 connections following the VBR.1 conformance 660 definition. 662 Connections specifying this traffic descriptor 663 type will be rejected at UNI 3.0 or UNI 3.1 664 interfaces. For a similar traffic descriptor 665 type that can be accepted at UNI 3.0 and 666 UNI 3.1 interfaces, see atmNoClpScr." 667 REFERENCE 668 "ATM Forum,ATM User-Network Interface, 669 Version 3.0 (UNI 3.0) Specification, 1994. 670 ATM Forum, ATM User-Network Interface, 671 Version 3.1 (UNI 3.1) Specification, 672 November 1994. 673 ATM Forum, Traffic Management Specification, 674 Version 4.0, af-tm-0056.000, June 1996." 675 ::= {atmTrafficDescriptorTypes 10} 677 atmNoClpTaggingNoScr OBJECT-IDENTITY 678 STATUS current 679 DESCRIPTION 680 "This traffic descriptor type is for no CLP 681 with tagging and no Sustained Cell Rate. The 682 use of the parameter vector for this type: 683 Parameter 1: peak cell rate in cells/second 684 for CLP=0+1 traffic 685 Parameter 2: CDVT in tenths of microseconds 686 Parameter 3: not used 687 Parameter 4: not used 688 Parameter 5: not used. 690 This traffic descriptor type is applicable to 691 connections following the UBR.2 conformance 693 draft ATM Textual Conventions and OBJECT-IDENTITIES~~~~April 4, 1997 695 definition ." 696 REFERENCE 697 "ATM Forum,ATM User-Network Interface, 698 Version 3.0 (UNI 3.0) Specification, 1994. 699 ATM Forum, ATM User-Network Interface, 700 Version 3.1 (UNI 3.1) Specification, 701 November 1994. 702 ATM Forum, Traffic Management Specification, 703 Version 4.0, af-tm-0056.000, June 1996." 704 ::= {atmTrafficDescriptorTypes 11} 706 atmNoClpNoScrCdvt OBJECT-IDENTITY 707 STATUS current 708 DESCRIPTION 709 "This traffic descriptor type is for no CLP 710 and no Sustained Cell Rate. The use of the 711 parameter vector for this type: 712 Parameter 1: peak cell rate in cells/second 713 for CLP=0+1 traffic 714 Parameter 2: CDVT in tenths of microseconds 715 Parameter 3: not used 716 Parameter 4: not used 717 Parameter 5: not used. 719 This traffic descriptor type is applicable to 720 CBR connections following the UNI 3.0/3.1 721 conformance definition for PCR CLP=0+1. 722 These CBR connections differ from CBR.1 723 connections in that the CLR objective 724 applies only to the CLP=0 cell flow. 726 This traffic descriptor type is also 727 applicable to connections following the UBR.1 728 conformance definition." 729 REFERENCE 730 "ATM Forum,ATM User-Network Interface, 731 Version 3.0 (UNI 3.0) Specification, 1994. 732 ATM Forum, ATM User-Network Interface, 733 Version 3.1 (UNI 3.1) Specification, 734 November 1994. 735 ATM Forum, Traffic Management Specification, 736 Version 4.0, af-tm-0056.000, June 1996." 737 ::= {atmTrafficDescriptorTypes 12} 739 atmNoClpScrCdvt OBJECT-IDENTITY 741 draft ATM Textual Conventions and OBJECT-IDENTITIES~~~~April 4, 1997 743 STATUS current 744 DESCRIPTION 745 "This traffic descriptor type is for no CLP 746 with Sustained Cell Rate. The use of the 747 parameter vector for this type: 748 Parameter 1: peak cell rate in cells/second 749 for CLP=0+1 traffic 750 Parameter 2: sustainable cell rate in cells/second 751 for CLP=0+1 traffic 752 Parameter 3: maximum burst size in cells 753 Parameter 4: CDVT in tenths of microseconds 754 Parameter 5: not used. 756 This traffic descriptor type is applicable 757 to VBR connections following the UNI 3.0/3.1 758 conformance definition for PCR CLP=0+1 and 759 SCR CLP=0+1. These VBR connections 760 differ from VBR.1 connections in that 761 the CLR objective applies only to the CLP=0 762 cell flow." 763 REFERENCE 764 "ATM Forum,ATM User-Network Interface, 765 Version 3.0 (UNI 3.0) Specification, 1994. 766 ATM Forum, ATM User-Network Interface, 767 Version 3.1 (UNI 3.1) Specification, 768 November 1994. 769 ATM Forum, Traffic Management Specification, 770 Version 4.0, af-tm-0056.000, June 1996." 771 ::= {atmTrafficDescriptorTypes 13} 773 atmClpNoTaggingScrCdvt OBJECT-IDENTITY 774 STATUS current 775 DESCRIPTION 776 "This traffic descriptor type is for CLP with 777 Sustained Cell Rate and no tagging. The use 778 of the parameter vector for this type: 779 Parameter 1: peak cell rate in cells/second 780 for CLP=0+1 traffic 781 Parameter 2: sustainable cell rate in cells/second 782 for CLP=0 traffic 783 Parameter 3: maximum burst size in cells 784 Parameter 4: CDVT in tenths of microseconds 785 Parameter 5: not used. 787 This traffic descriptor type is applicable to 789 draft ATM Textual Conventions and OBJECT-IDENTITIES~~~~April 4, 1997 791 connections following the VBR.2 conformance 792 definition." 793 REFERENCE 794 "ATM Forum,ATM User-Network Interface, 795 Version 3.0 (UNI 3.0) Specification, 1994. 796 ATM Forum, ATM User-Network Interface, 797 Version 3.1 (UNI 3.1) Specification, 798 November 1994. 799 ATM Forum, Traffic Management Specification, 800 Version 4.0, af-tm-0056.000, June 1996." 801 ::= {atmTrafficDescriptorTypes 14} 803 atmClpTaggingScrCdvt OBJECT-IDENTITY 804 STATUS current 805 DESCRIPTION 806 "This traffic descriptor type is for CLP with 807 tagging and Sustained Cell Rate. The use of 808 the parameter vector for this type: 809 Parameter 1: peak cell rate in cells/second 810 for CLP=0+1 traffic 811 Parameter 2: sustainable cell rate in cells/second 812 for CLP=0 traffic, excess tagged as 813 CLP=1 814 Parameter 3: maximum burst size in cells 815 Parameter 4: CDVT in tenths of microseconds 816 Parameter 5: not used. 818 This traffic descriptor type is applicable to 819 connections following the VBR.3 conformance 820 definition." 821 REFERENCE 822 "ATM Forum,ATM User-Network Interface, 823 Version 3.0 (UNI 3.0) Specification, 1994. 824 ATM Forum, ATM User-Network Interface, 825 Version 3.1 (UNI 3.1) Specification, 826 November 1994. 827 ATM Forum, Traffic Management Specification, 828 Version 4.0, af-tm-0056.000, June 1996." 829 ::= {atmTrafficDescriptorTypes 15} 831 END 833 draft ATM Textual Conventions and OBJECT-IDENTITIES~~~~April 4, 1997 835 4. Acknowledgments 837 This document is a product of the AToMMIB Working Group. 839 draft ATM Textual Conventions and OBJECT-IDENTITIES~~~~April 4, 1997 841 5. References 843 [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 844 "Textual Conventions for Version 2 of the Simple Network 845 Management Protocol (SNMPv2)", RFC1903, SNMP 846 Research,Inc., Cisco Systems, Inc., Dover Beach 847 Consulting, Inc., International Network Services, January 848 1996. 850 [2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 851 "Structure of Management Information for Version 2 of the 852 Simple Network Management Protocol (SNMPv2)", RFC1902, 853 SNMP Research,Inc., Cisco Systems, Inc., Dover Beach 854 Consulting, Inc., International Network Services, January 855 1996. 857 [3] Kaj Tesink, "Definitions of Managed Objects for ATM 858 Management", RFC???? (Internet-Draft ), Bellcore, April 1998. 861 draft ATM Textual Conventions and OBJECT-IDENTITIES~~~~April 4, 1997 863 6. Security Considerations 865 This memo defines textual conventions and object identities 866 for use in ATM MIB modules. Security issues for these MIB 867 modules are addressed in the memos defining those modules. 869 7. Authors' Addresses 871 Michael Noto 872 Network Equipment Technologies 873 800 Saginaw Drive RM 21.1.111 874 Redwood City, CA 94063 875 Phone +1 415 569-7134 876 EMail: mike_noto@net.com 878 Ethan Mickey Spiegel 879 Cisco Systems 880 170 W. Tasman Dr. 881 San Jose, CA 95134 882 USA 883 Phone +1 408 526 6408 884 E-mail: mspiegel@cisco.com" 886 Kaj Tesink 887 Bell Communications Research 888 Room 1A-317 889 331 Newman Springs Road 890 P.O. Box 7020 891 Red Bank, NJ 07701-7020 892 Phone: (908) 758-5254 893 EMail: kaj@cc.bellcore.com 895 draft ATM Textual Conventions and OBJECT-IDENTITIES~~~~April 4, 1997 897 Table of Contents 899 1 Status of this Memo ................................... 1 900 2 Introduction .......................................... 2 901 3 Definitions ........................................... 3 902 4 Acknowledgments ....................................... 19 903 5 References ............................................ 20 904 6 Security Considerations ............................... 21 905 7 Authors' Addresses .................................... 21