1 ATM-TC-MIB DEFINITIONS ::= BEGIN 2 3 IMPORTS 4 MODULE-IDENTITY, OBJECT-IDENTITY, 5 TimeTicks, mib-2 6 FROM SNMPv2-SMI 7 TEXTUAL-CONVENTION 8 FROM SNMPv2-TC; 9 10 11 atmTCMIB MODULE-IDENTITY 12 LAST-UPDATED "9810190200Z" 13 ORGANIZATION "IETF AToMMIB Working Group" 14 CONTACT-INFO 15 " Michael Noto 16 Postal: 3Com Corporation 17 5400 Bayfront Plaza, M/S 3109 18 Santa Clara, CA 95052 19 USA 20 Tel: +1 408 326 2218 21 E-mail: mike_noto@3com.com 22 23 Ethan Mickey Spiegel 24 Postal: Cisco Systems 25 170 W. Tasman Dr. 26 San Jose, CA 95134 27 USA 28 Tel: +1 408 526 6408 29 E-mail: mspiegel@cisco.com 30 31 Kaj Tesink 32 Postal: Bellcore 33 331 Newman Springs Road 34 Red Bank, NJ 07701 35 USA 36 Tel: +1 732 758 5254 37 Fax: +1 732 758 4177 38 E-mail: kaj@bellcore.com" 39 DESCRIPTION 40 "This MIB Module provides Textual Conventions 41 and OBJECT-IDENTITY Objects to be used by 42 ATM systems." 43 ::= { mib-2 37 3 } -- atmMIB 3 (see [3]) 44 45 -- The Textual Conventions defined below are organized 46 -- alphabetically 47 48 49 AtmAddr ::= TEXTUAL-CONVENTION 50 DISPLAY-HINT "1x" 51 STATUS current 52 DESCRIPTION 53 "An ATM address. The semantics are implied by 54 the length. The address types are: - no 55 address (0 octets) - E.164 (8 octets) - NSAP 56 (20 octets) In addition, when subaddresses 57 are used the AtmAddr may represent the 58 concatenation of address and subaddress. The 59 associated address types are: - E.164, E.164 60 (16 octets) - E.164, NSAP (28 octets) - NSAP, 61 NSAP (40 octets) Address lengths other than 62 defined in this definition imply address 63 types defined elsewhere. Note: The E.164 64 address is encoded in BCD format." 65 SYNTAX OCTET STRING (SIZE(0..40)) 66 67 68 AtmConnCastType ::= TEXTUAL-CONVENTION 69 STATUS current 70 DESCRIPTION 71 "The type of topology of a connection (point- 72 to-point, point-to-multipoint). In the case 73 of point-to-multipoint, the orientation of 74 this VPL or VCL in the connection. 75 On a host: 76 - p2mpRoot indicates that the host 77 is the root of the p2mp connection. 78 - p2mpLeaf indicates that the host 79 is a leaf of the p2mp connection. 80 On a switch interface: 81 - p2mpRoot indicates that cells received 82 by the switching fabric from the interface 83 are from the root of the p2mp connection. 84 - p2mpLeaf indicates that cells transmitted 85 to the interface from the switching fabric 86 are to the leaf of the p2mp connection." 87 SYNTAX INTEGER { 88 p2p(1), 89 p2mpRoot(2), 90 p2mpLeaf(3) 91 } 92 93 AtmConnKind ::= TEXTUAL-CONVENTION 94 STATUS current 95 DESCRIPTION 96 "The type of call control used for an ATM 97 connection at a particular interface. The use 98 is as follows: 99 pvc(1) 100 Virtual link of a PVC. Should not be 101 used for an PVC/SVC (i.e., Soft PVC) 102 crossconnect. 103 svcIncoming(2) 104 Virtual link established after a 105 received signaling request to setup 106 an SVC. 107 svcOutgoing(3) 108 Virtual link established after a 109 transmitted or forwarded signaling 110 request to setup an SVC. 111 spvcInitiator(4) 112 Virtual link at the PVC side of an 113 SVC/PVC crossconnect, where the 114 switch is the initiator of the Soft PVC 115 setup. 116 spvcTarget(5) 117 Virtual link at the PVC side of an 118 SVC/PVC crossconnect, where the 119 switch is the target of the Soft PVC 120 setup. 121 122 For PVCs, a pvc virtual link is always cross- 123 connected to a pvc virtual link. 124 125 For SVCs, an svcIncoming virtual link is always cross- 126 connected to an svcOutgoing virtual link. 127 128For Soft PVCs, an spvcInitiator is either cross-connected to 129an svcOutgoing or an spvcTarget, and an spvcTarget is either 130cross-connected to an svcIncoming or an spvcInitiator." 131 SYNTAX INTEGER { 132 pvc(1), 133 svcIncoming(2), 134 svcOutgoing(3), 135 spvcInitiator(4), 136 spvcTarget(5) 137 } 138 139 AtmIlmiNetworkPrefix ::= TEXTUAL-CONVENTION 140 STATUS current 141 DESCRIPTION 142 "A network prefix used for ILMI address 143 registration. In the case of ATM endsystem 144 addresses (AESAs), the network prefix is the first 145 13 octets of the address which includes the AFI, 146 IDI, and HO-DSP fields. In the case of native 147 E.164 addresses, the network prefix is the entire 148 E.164 address encoded in 8 octets, as if it were 149 an E.164 IDP in an ATM endsystem address 150 structure." 151 REFERENCE 152 "ATM Forum, Integrated Local Management Interface 153 (ILMI) Specification, Version 4.0, 154 af-ilmi-0065.000, September 1996, Section 9 155 ATM Forum, ATM User-Network Interface Signalling 156 Specification, Version 4.0 (UNI 4.0), 157 af-sig-0061.000, June 1996, Section 3" 158 SYNTAX OCTET STRING (SIZE(8|13)) 159 160AtmInterfaceType ::= TEXTUAL-CONVENTION 161 STATUS current 162 DESCRIPTION 163 "The connection setup procedures used for the 164 identified interface. 165 166 Other: Connection setup procedures other than 167 those listed below. 168 Auto-configuration: 169 Indicates that the connection setup 170 procedures are to be determined dynamically, 171 or that determination has not yet been 172 completed. One such mechanism is via ATM 173 Forum ILMI auto-configuration procedures. 174 175 ITU-T DSS2: 176 - ITU-T Recommendation Q.2931, Broadband 177 Integrated Service Digital Network (B-ISDN) 178 Digital Subscriber Signalling System No.2 179 (DSS2) User-Network Interface (UNI) Layer 3 180 Specification for Basic Call/Connection 181 Control (September 1994) 182 - ITU-T Draft Recommendation Q.2961, 183 B-ISDN DSS 2 Support of Additional Traffic 184 Parameters (May 1995) 185 186 - ITU-T Draft Recommendation Q.2971, 187 B-ISDN DSS 2 User Network Interface Layer 3 188 Specification for Point-to-multipoint 189 Call/connection Control (May 1995) 190 191 ATM Forum UNI 3.0: 192 ATM Forum, ATM User-Network Interface, 193 Version 3.0 (UNI 3.0) Specification, 194 (1994). 195 196 ATM Forum UNI 3.1: 197 ATM Forum, ATM User-Network Interface, 198 Version 3.1 (UNI 3.1) Specification, 199 (November 1994). 200 201 ATM Forum UNI Signalling 4.0: 202 ATM Forum, ATM User-Network Interface (UNI) 203 Signalling Specification Version 4.0, 204 af-sig-0061.000 (June 1996). 205 206 ATM Forum IISP (based on UNI 3.0 or UNI 3.1) : 207 Interim Inter-switch Signaling Protocol 208 (IISP) Specification, Version 1.0, 209 af-pnni-0026.000, (December 1994). 210 211 ATM Forum PNNI 1.0 : 212 ATM Forum, Private Network-Network Interface 213 Specification, Version 1.0, af-pnni-0055.000, 214 (March 1996). 215 ATM Forum B-ICI: 216 ATM Forum, B-ICI Specification, Version 2.0, 217 af-bici-0013.002, (November 1995). 218 219 ATM Forum UNI PVC Only: 220 An ATM Forum compliant UNI with the 221 signalling disabled. 222 ATM Forum NNI PVC Only: 223 An ATM Forum compliant NNI with the 224 signalling disabled." 225 SYNTAX INTEGER { 226 other(1), 227 autoConfig(2), 228 ituDss2(3), 229 atmfUni3Dot0(4), 230 atmfUni3Dot1(5), 231 atmfUni4Dot0(6), 232 atmfIispUni3Dot0(7), 233 atmfIispUni3Dot1(8), 234 atmfIispUni4Dot0(9), 235 atmfPnni1Dot0(10), 236 atmfBici2Dot0(11), 237 atmfUniPvcOnly(12), 238 atmfNniPvcOnly(13) } 239 240AtmServiceCategory ::= TEXTUAL-CONVENTION 241 STATUS current 242 DESCRIPTION 243 "The service category for a connection." 244 REFERENCE 245 "ATM Forum Traffic Management Specification, 246 Version 4.0, af-tm-0056.000, June 1996." 247 SYNTAX INTEGER { 248 other(1), -- none of the following 249 cbr(2), -- constant bit rate 250 rtVbr(3), -- real-time variable bit rate 251 nrtVbr(4), -- non real-time variable bit rate 252 abr(5), -- available bit rate 253 ubr(6) -- unspecified bit rate 254 } 255 256AtmSigDescrParamIndex ::= TEXTUAL-CONVENTION 257 STATUS current 258 DESCRIPTION 259 "The value of this object identifies a row in the 260 atmSigDescrParamTable. The value 0 signifies that 261 none of the signalling parameters defined in the 262 atmSigDescrParamTable are applicable." 263 SYNTAX INTEGER (0..2147483647) 264 265AtmTrafficDescrParamIndex ::= TEXTUAL-CONVENTION 266 STATUS current 267 DESCRIPTION 268 "The value of this object identifies a row in the 269 atmTrafficDescrParamTable. The value 0 signifies 270 that no row has been identified." 271 SYNTAX INTEGER (0..2147483647) 272 273AtmVcIdentifier ::= TEXTUAL-CONVENTION 274 STATUS current 275 DESCRIPTION 276 "The VCI value for a VCL. The maximum VCI value 277 cannot exceed the value allowable by 278 atmInterfaceMaxVciBits defined in ATM-MIB." 279 SYNTAX INTEGER (0..65535) 280 281AtmVpIdentifier ::= TEXTUAL-CONVENTION 282 STATUS current 283 DESCRIPTION 284 "The VPI value for a VPL or VCL. The value VPI=0 285 is only allowed for a VCL. For ATM UNIs supporting 286 VPCs the VPI value ranges from 0 to 255. The VPI 287 value 0 is supported for ATM UNIs conforming to 288 the ATM Forum UNI 4.0 Annex 8 (Virtual UNIs) 289 specification. For ATM UNIs supporting VCCs the 290 VPI value ranges from 0 to 255. For ATM NNIs the 291 VPI value ranges from 0 to 4095. The maximum VPI 292 value cannot exceed the value allowable by 293 atmInterfaceMaxVpiBits defined in ATM-MIB." 294 SYNTAX INTEGER (0..4095) 295 296AtmVorXAdminStatus ::= TEXTUAL-CONVENTION 297 STATUS current 298 DESCRIPTION 299 "The value determines the desired administrative 300 status of a virtual link or cross-connect. The up 301 and down states indicate that the traffic flow is 302 enabled or disabled respectively on the virtual 303 link or cross-connect." 304 SYNTAX INTEGER { 305 up(1), 306 down(2) 307 } 308 309AtmVorXLastChange ::= TEXTUAL-CONVENTION 310 STATUS current 311 DESCRIPTION 312 "The value of MIB II's sysUpTime at the time a 313 virtual link or cross-connect entered its current 314 operational state. If the current state was 315 entered prior to the last re-initialization of the 316 agent then this object contains a zero value." 317 SYNTAX TimeTicks 318 319AtmVorXOperStatus ::= TEXTUAL-CONVENTION 320 STATUS current 321 DESCRIPTION 322 "The value determines the operational status of a 323 virtual link or cross-connect. The up and down 324 states indicate that the traffic flow is enabled 325 or disabled respectively on the virtual link or 326 cross-connect. The unknown state indicates that 327 the state of it cannot be determined. The state 328 will be down or unknown if the supporting ATM 329 interface(s) is down or unknown respectively." 330 SYNTAX INTEGER { 331 up(1), 332 down(2), 333 unknown(3) 334 } 335 336 337 338 339-- OBJECT-IDENTITIES: 340 341-- The following atmTrafficDescriptorTypes has been moved 342-- from RFC1695 and no longer appear in the revision of 343-- RFC1695[3]. 344 345atmTrafficDescriptorTypes OBJECT IDENTIFIER ::= {mib-2 37 1 1} 346 -- atmMIBObjects 347 -- See [3]. 348 349-- All other and new OBJECT IDENTITIES 350-- are defined under the following subtree: 351 352 atmObjectIdentities OBJECT IDENTIFIER ::= {atmTCMIB 1} 353 354-- The following values are defined for use as 355-- possible values of the ATM traffic descriptor type. 356 357atmNoTrafficDescriptor OBJECT-IDENTITY 358 STATUS deprecated 359 DESCRIPTION 360 "This identifies the no ATM traffic 361 descriptor type. Parameters 1, 2, 3, 4, 362 and 5 are not used. This traffic descriptor 363 type can be used for best effort traffic." 364 ::= {atmTrafficDescriptorTypes 1} 365 366atmNoClpNoScr OBJECT-IDENTITY 367 STATUS current 368 DESCRIPTION 369 "This traffic descriptor type is for no CLP 370 and no Sustained Cell Rate. The use of the 371 parameter vector for this type: 372 Parameter 1: peak cell rate in cells/second 373 for CLP=0+1 traffic 374 Parameter 2: not used 375 Parameter 3: not used 376 Parameter 4: not used 377 Parameter 5: not used." 378 REFERENCE 379 "ATM Forum,ATM User-Network Interface, 380 Version 3.0 (UNI 3.0) Specification, 1994. 381 ATM Forum, ATM User-Network Interface, 382 Version 3.1 (UNI 3.1) Specification, 383 November 1994." 384 ::= {atmTrafficDescriptorTypes 2} 385 386atmClpNoTaggingNoScr OBJECT-IDENTITY 387 STATUS deprecated 388 DESCRIPTION 389 "This traffic descriptor is for CLP without 390 tagging and no Sustained Cell Rate. The use 391 of the parameter vector for this type: 392 Parameter 1: peak cell rate in cells/second 393 for CLP=0+1 traffic 394 Parameter 2: peak cell rate in cells/second 395 for CLP=0 traffic 396 Parameter 3: not used 397 Parameter 4: not used 398 Parameter 5: not used." 399 ::= {atmTrafficDescriptorTypes 3} 400 401atmClpTaggingNoScr OBJECT-IDENTITY 402 STATUS deprecated 403 DESCRIPTION 404 "This traffic descriptor is for CLP with 405 tagging and no Sustained Cell Rate. The use 406 of the parameter vector for this type: 407 Parameter 1: peak cell rate in cells/second 408 for CLP=0+1 traffic 409 Parameter 2: peak cell rate in cells/second 410 for CLP=0 traffic, excess 411 tagged as CLP=1 412 Parameter 3: not used 413 Parameter 4: not used 414 Parameter 5: not used." 415 ::= {atmTrafficDescriptorTypes 4} 416 417atmNoClpScr OBJECT-IDENTITY 418 STATUS current 419 DESCRIPTION 420 "This traffic descriptor type is for no CLP 421 with Sustained Cell Rate. The use of the 422 parameter vector for this type: 423 Parameter 1: peak cell rate in cells/second 424 for CLP=0+1 traffic 425 Parameter 2: sustainable cell rate in cells/second 426 for CLP=0+1 traffic 427 Parameter 3: maximum burst size in cells 428 Parameter 4: not used 429 Parameter 5: not used." 430 REFERENCE 431 "ATM Forum,ATM User-Network Interface, 432 Version 3.0 (UNI 3.0) Specification, 1994. 433 ATM Forum, ATM User-Network Interface, 434 Version 3.1 (UNI 3.1) Specification, 435 November 1994." 436 ::= {atmTrafficDescriptorTypes 5} 437 438atmClpNoTaggingScr OBJECT-IDENTITY 439 STATUS current 440 DESCRIPTION 441 "This traffic descriptor type is for CLP with 442 Sustained Cell Rate and no tagging. The use 443 of the parameter vector for this type: 444 Parameter 1: peak cell rate in cells/second 445 for CLP=0+1 traffic 446 Parameter 2: sustainable cell rate in cells/second 447 for CLP=0 traffic 448 Parameter 3: maximum burst size in cells 449 Parameter 4: not used 450 Parameter 5: not used." 451 REFERENCE 452 "ATM Forum,ATM User-Network Interface, 453 Version 3.0 (UNI 3.0) Specification, 1994. 454 ATM Forum, ATM User-Network Interface, 455 Version 3.1 (UNI 3.1) Specification, 456 November 1994." 457 ::= {atmTrafficDescriptorTypes 6} 458 459atmClpTaggingScr OBJECT-IDENTITY 460 STATUS current 461 DESCRIPTION 462 "This traffic descriptor type is for CLP with 463 tagging and Sustained Cell Rate. The use of 464 the parameter vector for this type: 465 Parameter 1: peak cell rate in cells/second 466 for CLP=0+1 traffic 467 Parameter 2: sustainable cell rate in cells/second 468 for CLP=0 traffic, excess tagged as 469 CLP=1 470 Parameter 3: maximum burst size in cells 471 Parameter 4: not used 472 Parameter 5: not used." 473 REFERENCE 474 "ATM Forum,ATM User-Network Interface, 475 Version 3.0 (UNI 3.0) Specification, 1994. 476 ATM Forum, ATM User-Network Interface, 477 Version 3.1 (UNI 3.1) Specification, 478 November 1994." 479 ::= {atmTrafficDescriptorTypes 7} 480 481atmClpNoTaggingMcr OBJECT-IDENTITY 482 STATUS current 483 DESCRIPTION 484 "This traffic descriptor type is for CLP with 485 Minimum Cell Rate and no tagging. The use of 486 the parameter vector for this type: 487 Parameter 1: peak cell rate in cells/second 488 for CLP=0+1 traffic 489 Parameter 2: CDVT in tenths of microseconds 490 Parameter 3: minimum cell rate in cells/second 491 Parameter 4: unused 492 Parameter 5: unused." 493 REFERENCE 494 "ATM Forum,ATM User-Network Interface, 495 Version 3.0 (UNI 3.0) Specification, 1994. 496 ATM Forum, ATM User-Network Interface, 497 Version 3.1 (UNI 3.1) Specification, 498 November 1994." 499 ::= {atmTrafficDescriptorTypes 8} 500 501atmClpTransparentNoScr OBJECT-IDENTITY 502 STATUS current 503 DESCRIPTION 504 "This traffic descriptor type is for the CLP- 505 transparent model and no Sustained Cell Rate. 506 The use of the parameter vector for this type: 507 Parameter 1: peak cell rate in cells/second 508 for CLP=0+1 traffic 509 Parameter 2: CDVT in tenths of microseconds 510 Parameter 3: not used 511 Parameter 4: not used 512 Parameter 5: not used. 513 514 This traffic descriptor type is applicable to 515 connections following the CBR.1 conformance 516 definition. 517 518 Connections specifying this traffic descriptor 519 type will be rejected at UNI 3.0 or UNI 3.1 520 interfaces. For a similar traffic descriptor 521 type that can be accepted at UNI 3.0 and 522 UNI 3.1 interfaces, see atmNoClpNoScr." 523 REFERENCE 524 "ATM Forum,ATM User-Network Interface, 525 Version 3.0 (UNI 3.0) Specification, 1994. 526 ATM Forum, ATM User-Network Interface, 527 Version 3.1 (UNI 3.1) Specification, 528 November 1994. 529 ATM Forum, Traffic Management Specification, 530 Version 4.0, af-tm-0056.000, June 1996." 531 ::= {atmTrafficDescriptorTypes 9} 532 533atmClpTransparentScr OBJECT-IDENTITY 534 STATUS current 535 DESCRIPTION 536 "This traffic descriptor type is for the CLP- 537 transparent model with Sustained Cell Rate. 538 The use of the parameter vector for this type: 539 Parameter 1: peak cell rate in cells/second 540 for CLP=0+1 traffic 541 Parameter 2: sustainable cell rate in cells/second 542 for CLP=0+1 traffic 543 Parameter 3: maximum burst size in cells 544 Parameter 4: CDVT in tenths of microseconds 545 Parameter 5: not used. 546 547 This traffic descriptor type is applicable to 548 connections following the VBR.1 conformance 549 definition. 550 Connections specifying this traffic descriptor 551 type will be rejected at UNI 3.0 or UNI 3.1 552 interfaces. For a similar traffic descriptor 553 type that can be accepted at UNI 3.0 and 554 UNI 3.1 interfaces, see atmNoClpScr." 555 REFERENCE 556 "ATM Forum,ATM User-Network Interface, 557 Version 3.0 (UNI 3.0) Specification, 1994. 558 ATM Forum, ATM User-Network Interface, 559 Version 3.1 (UNI 3.1) Specification, 560 November 1994. 561 ATM Forum, Traffic Management Specification, 562 Version 4.0, af-tm-0056.000, June 1996." 563 ::= {atmTrafficDescriptorTypes 10} 564 565atmNoClpTaggingNoScr OBJECT-IDENTITY 566 STATUS current 567 DESCRIPTION 568 "This traffic descriptor type is for no CLP 569 with tagging and no Sustained Cell Rate. The 570 use of the parameter vector for this type: 571 Parameter 1: peak cell rate in cells/second 572 for CLP=0+1 traffic 573 Parameter 2: CDVT in tenths of microseconds 574 Parameter 3: not used 575 Parameter 4: not used 576 Parameter 5: not used. 577 578 This traffic descriptor type is applicable to 579 connections following the UBR.2 conformance 580 definition ." 581 REFERENCE 582 "ATM Forum,ATM User-Network Interface, 583 Version 3.0 (UNI 3.0) Specification, 1994. 584 ATM Forum, ATM User-Network Interface, 585 Version 3.1 (UNI 3.1) Specification, 586 November 1994. 587 ATM Forum, Traffic Management Specification, 588 Version 4.0, af-tm-0056.000, June 1996." 589 ::= {atmTrafficDescriptorTypes 11} 590 591atmNoClpNoScrCdvt OBJECT-IDENTITY 592 STATUS current 593 DESCRIPTION 594 "This traffic descriptor type is for no CLP 595 and no Sustained Cell Rate. The use of the 596 parameter vector for this type: 597 Parameter 1: peak cell rate in cells/second 598 for CLP=0+1 traffic 599 Parameter 2: CDVT in tenths of microseconds 600 Parameter 3: not used 601 Parameter 4: not used 602 Parameter 5: not used. 603 604 This traffic descriptor type is applicable to 605 CBR connections following the UNI 3.0/3.1 606 conformance definition for PCR CLP=0+1. 607 These CBR connections differ from CBR.1 608 connections in that the CLR objective 609 applies only to the CLP=0 cell flow. 610 611 This traffic descriptor type is also 612 applicable to connections following the UBR.1 613 conformance definition." 614 REFERENCE 615 "ATM Forum,ATM User-Network Interface, 616 Version 3.0 (UNI 3.0) Specification, 1994. 617 ATM Forum, ATM User-Network Interface, 618 Version 3.1 (UNI 3.1) Specification, 619 November 1994. 620 ATM Forum, Traffic Management Specification, 621 Version 4.0, af-tm-0056.000, June 1996." 622 ::= {atmTrafficDescriptorTypes 12} 623 624atmNoClpScrCdvt OBJECT-IDENTITY 625 STATUS current 626 DESCRIPTION 627 "This traffic descriptor type is for no CLP 628 with Sustained Cell Rate. The use of the 629 parameter vector for this type: 630 Parameter 1: peak cell rate in cells/second 631 for CLP=0+1 traffic 632 Parameter 2: sustainable cell rate in cells/second 633 for CLP=0+1 traffic 634 Parameter 3: maximum burst size in cells 635 Parameter 4: CDVT in tenths of microseconds 636 Parameter 5: not used. 637 638 This traffic descriptor type is applicable 639 to VBR connections following the UNI 3.0/3.1 640 conformance definition for PCR CLP=0+1 and 641 SCR CLP=0+1. These VBR connections 642 differ from VBR.1 connections in that 643 the CLR objective applies only to the CLP=0 644 cell flow." 645 REFERENCE 646 "ATM Forum,ATM User-Network Interface, 647 Version 3.0 (UNI 3.0) Specification, 1994. 648 ATM Forum, ATM User-Network Interface, 649 Version 3.1 (UNI 3.1) Specification, 650 November 1994. 651 ATM Forum, Traffic Management Specification, 652 Version 4.0, af-tm-0056.000, June 1996." 653 ::= {atmTrafficDescriptorTypes 13} 654 655atmClpNoTaggingScrCdvt OBJECT-IDENTITY 656 STATUS current 657 DESCRIPTION 658 "This traffic descriptor type is for CLP with 659 Sustained Cell Rate and no tagging. The use 660 of the parameter vector for this type: 661 Parameter 1: peak cell rate in cells/second 662 for CLP=0+1 traffic 663 Parameter 2: sustainable cell rate in cells/second 664 for CLP=0 traffic 665 Parameter 3: maximum burst size in cells 666 Parameter 4: CDVT in tenths of microseconds 667 Parameter 5: not used. 668 669 This traffic descriptor type is applicable to 670 connections following the VBR.2 conformance 671 definition." 672 REFERENCE 673 "ATM Forum,ATM User-Network Interface, 674 Version 3.0 (UNI 3.0) Specification, 1994. 675 ATM Forum, ATM User-Network Interface, 676 Version 3.1 (UNI 3.1) Specification, 677 November 1994. 678 ATM Forum, Traffic Management Specification, 679 Version 4.0, af-tm-0056.000, June 1996." 680 ::= {atmTrafficDescriptorTypes 14} 681 682atmClpTaggingScrCdvt OBJECT-IDENTITY 683 STATUS current 684 DESCRIPTION 685 "This traffic descriptor type is for CLP with 686 tagging and Sustained Cell Rate. The use of 687 the parameter vector for this type: 688 Parameter 1: peak cell rate in cells/second 689 for CLP=0+1 traffic 690 Parameter 2: sustainable cell rate in cells/second 691 for CLP=0 traffic, excess tagged as 692 CLP=1 693 Parameter 3: maximum burst size in cells 694 Parameter 4: CDVT in tenths of microseconds 695 Parameter 5: not used. 696 697 This traffic descriptor type is applicable to 698 connections following the VBR.3 conformance 699 definition." 700 REFERENCE 701 "ATM Forum,ATM User-Network Interface, 702 Version 3.0 (UNI 3.0) Specification, 1994. 703 ATM Forum, ATM User-Network Interface, 704 Version 3.1 (UNI 3.1) Specification, 705 November 1994. 706 ATM Forum, Traffic Management Specification, 707 Version 4.0, af-tm-0056.000, June 1996." 708 ::= {atmTrafficDescriptorTypes 15} 709 710END 711