idnits 2.17.1 draft-ietf-atommib-atm2TC-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** Expected the document's filename to be given on the first page, but didn't find any == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 23 longer pages, the longest (page 2) being 117 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 24 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** 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. ** The abstract seems to contain references ([2], [3], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == 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 (August 15, 1998) is 9386 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 855 looks like a reference -- Missing reference section? '2' on line 862 looks like a reference -- Missing reference section? '3' on line 869 looks like a reference Summary: 13 errors (**), 0 flaws (~~), 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 August 15, 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 Bellcore 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 31 ``work in progress.'' 33 To learn the current status of any Internet-Draft, please 34 check the ``1id-abstracts.txt'' listing contained in the 35 Internet- Drafts Shadow Directories on ftp.ietf.org (US East 36 Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), 37 or munnari.oz.au (Pacific Rim). 39 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 41 Copyright Notice 43 Copyright (C) The Internet Society (1998). All Rights 44 Reserved. 46 Abstract 48 This memo describes Textual Conventions and OBJECT-IDENTITIES 49 used for managing ATM-based interfaces, devices, networks and 50 services. 52 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 54 2. Introduction 56 This memo describes Textual Conventions and OBJECT-IDENTITIES 57 used for managing ATM-based interfaces, devices, networks and 58 services. 60 When designing a MIB module, it is often useful to define new 61 types similar to those defined in the SMI. In comparison to a 62 type defined in the SMI, each of these new types has a 63 different name, a similar syntax, but a more precise 64 semantics. These newly defined types are termed textual 65 conventions, and are used for the convenience of humans 66 reading the MIB module. This is done through Textual 67 Conventions as defined in RFC1903[1]. It is the purpose of 68 this document to define the set of textual conventions 69 available to ATM MIB modules. 71 When designing MIB modules, it is also often useful to 72 register further properties with object identifier assignments 73 so that they can be further used by other MIB modules. This 74 is done through the OBJECT-IDENTITY macro defined in 75 RFC1902[2]. This document defines OBJECT-IDENTITIES available 76 to ATM MIB modules. 78 Note that for organizational purposes OBJECT IDENTITIES 79 previously defined in RFC1695 have been moved to this 80 specification and no longer appear in the revision of 81 RFC1695[3]. However, the original OBJECT IDENTIFIERs have been 82 preserved. 84 For an introduction to the concepts of ATM connections, see 85 [3]. 87 This memo does not specify a standard for the Internet 88 community. 90 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 92 3. Definitions 94 ATM-TC-MIB DEFINITIONS ::= BEGIN 96 IMPORTS 97 MODULE-IDENTITY, OBJECT-IDENTITY, 98 Integer32, TimeTicks, mib-2 99 FROM SNMPv2-SMI 100 TEXTUAL-CONVENTION 101 FROM SNMPv2-TC; 103 atmTCMIB MODULE-IDENTITY 104 LAST-UPDATED "9808150200Z" 105 ORGANIZATION "IETF AToMMIB Working Group" 106 CONTACT-INFO 107 " Michael Noto 108 Postal: Network Equipment Technologies 109 800 Saginaw Drive RM 21.1.111 110 Redwood City, CA 94063 111 USA 112 Tel: +1 415 569-7134 113 E-mail: mike_noto@net.com 115 Ethan Mickey Spiegel 116 Postal: Cisco Systems 117 170 W. Tasman Dr. 118 San Jose, CA 95134 119 USA 120 Tel: +1 408 526 6408 121 E-mail: mspiegel@cisco.com 123 Kaj Tesink 124 Postal: Bellcore 125 331 Newman Springs Road 126 Red Bank, NJ 07701 127 USA 128 Tel: +1 732 758 5254 129 Fax: +1 732 758 4177 130 E-mail: kaj@cc.bellcore.com" 131 DESCRIPTION 132 "This MIB Module provides Textual Conventions 133 and OBJECT-IDENTITY Objects to be used by 134 ATM systems." 135 ::= { mib-2 37 3 } -- atmMIB 3 (see [3]) 137 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 139 -- The Textual Conventions defined below are organized 140 -- alphabetically 142 AtmAddr ::= TEXTUAL-CONVENTION 143 DISPLAY-HINT "1x" 144 STATUS current 145 DESCRIPTION 146 "An ATM address. The semantics are implied by 147 the length. The address types are: - no 148 address (0 octets) - E.164 (8 octets) - NSAP 149 (20 octets) In addition, when subaddresses 150 are used the AtmAddr may represent the 151 concatenation of address and subaddress. The 152 associated address types are: - E.164, E.164 153 (16 octets) - E.164, NSAP (28 octets) - NSAP, 154 NSAP (40 octets) Address lengths other than 155 defined in this definition imply address 156 types defined elsewhere. Note: The E.164 157 address is encoded in BCD format." 158 SYNTAX OCTET STRING (SIZE(0..40)) 160 AtmConnCastType ::= TEXTUAL-CONVENTION 161 STATUS current 162 DESCRIPTION 163 "The type of topology of a connection (point- 164 to-point, point-to-multipoint). In the case 165 of point-to-multipoint, the orientation of 166 this VPL or VCL in the connection. 167 On a host: 168 - p2mpRoot indicates that the host 169 is the root of the p2mp connection. 170 - p2mpLeaf indicates that the host 171 is a leaf of the p2mp connection. 172 On a switch interface: 173 - p2mpRoot indicates that cells received 174 by the switching fabric from the interface 175 are from the root of the p2mp connection. 176 - p2mpLeaf indicates that cells transmitted 177 to the interface from the switching fabric 178 are to the leaf of the p2mp connection." 179 SYNTAX INTEGER { 180 p2p(1), 181 p2mpRoot(2), 183 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 185 p2mpLeaf(3) 186 } 188 AtmConnKind ::= TEXTUAL-CONVENTION 189 STATUS current 190 DESCRIPTION 191 "The type of call control used for an ATM 192 connection at a particular interface. The use 193 is as follows: 194 pvc(1) 195 Virtual link of a PVC. Should not be 196 used for an PVC/SVC (i.e., Soft PVC) 197 crossconnect. 198 svcIncoming(2) 199 Virtual link established after a 200 received signaling request to setup 201 an SVC. 202 svcOutgoing(3) 203 Virtual link established after a 204 transmitted or forwarded signaling 205 request to setup an SVC. 206 spvcInitiator(4) 207 Virtual link at the PVC side of an 208 SVC/PVC crossconnect, where the 209 switch is the initiator of the Soft PVC 210 setup. 211 spvcTarget(5) 212 Virtual link at the PVC side of an 213 SVC/PVC crossconnect, where the 214 switch is the target of the Soft PVC 215 setup. 217 For PVCs, a pvc virtual link is always cross- 218 connected to a pvc virtual link. 220 For SVCs, an svcIncoming virtual link is always cross- 221 connected to an svcOutgoing virtual link. 223 For Soft PVCs, an spvcInitiator is either cross-connected to 224 an svcOutgoing or an spvcTarget, and an spvcTarget is either 225 cross-connected to an svcIncoming or an spvcInitiator." 226 SYNTAX INTEGER { 227 pvc(1), 228 svcIncoming(2), 229 svcOutgoing(3), 231 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 233 spvcInitiator(4), 234 spvcTarget(5) 235 } 237 AtmIlmiNetworkPrefix ::= TEXTUAL-CONVENTION 238 STATUS current 239 DESCRIPTION 240 "A network prefix used for ILMI address 241 registration. In the case of ATM endsystem 242 addresses (AESAs), the network prefix is the first 243 13 octets of the address which includes the AFI, 244 IDI, and HO-DSP fields. In the case of native 245 E.164 addresses, the network prefix is the entire 246 E.164 address encoded in 8 octets, as if it were 247 an E.164 IDP in an ATM endsystem address 248 structure." 249 REFERENCE 250 "ATM Forum, Integrated Local Management Interface 251 (ILMI) Specification, Version 4.0, 252 af-ilmi-0065.000, September 1996, Section 9 253 ATM Forum, ATM User-Network Interface Signalling 254 Specification, Version 4.0 (UNI 4.0), 255 af-sig-0061.000, June 1996, Section 3" 256 SYNTAX OCTET STRING (SIZE(8|13)) 258 AtmInterfaceType ::= TEXTUAL-CONVENTION 259 STATUS current 260 DESCRIPTION 261 "The connection setup procedures used for the 262 identified interface. 264 Other: Connection setup procedures other than 265 those listed below. 267 Auto-configuration: 268 Indicates that the connection setup 269 procedures are to be determined dynamically, 270 or that determination has not yet been 271 completed. One such mechanism is via ATM 272 Forum ILMI auto-configuration procedures. 274 ITU-T DSS2: 275 - ITU-T Recommendation Q.2931, Broadband 276 Integrated Service Digital Network (B-ISDN) 277 Digital Subscriber Signalling System No.2 279 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 281 (DSS2) User-Network Interface (UNI) Layer 3 282 Specification for Basic Call/Connection 283 Control (September 1994) 284 - ITU-T Draft Recommendation Q.2961, 285 B-ISDN DSS 2 Support of Additional Traffic 286 Parameters (May 1995) 288 - ITU-T Draft Recommendation Q.2971, 289 B-ISDN DSS 2 User Network Interface Layer 3 290 Specification for Point-to-multipoint 291 Call/connection Control (May 1995) 293 ATM Forum UNI 3.0: 294 ATM Forum, ATM User-Network Interface, 295 Version 3.0 (UNI 3.0) Specification, 296 (1994). 298 ATM Forum UNI 3.1: 299 ATM Forum, ATM User-Network Interface, 300 Version 3.1 (UNI 3.1) Specification, 301 (November 1994). 303 ATM Forum UNI Signalling 4.0: 304 ATM Forum, ATM User-Network Interface (UNI) 305 Signalling Specification Version 4.0, 306 af-sig-0061.000 (June 1996). 308 ATM Forum IISP (based on UNI 3.0 or UNI 3.1) : 309 Interim Inter-switch Signaling Protocol 310 (IISP) Specification, Version 1.0, 311 af-pnni-0026.000, (December 1994). 313 ATM Forum PNNI 1.0 : 314 ATM Forum, Private Network-Network Interface 315 Specification, Version 1.0, af-pnni-0055.000, 316 (March 1996). 318 ATM Forum B-ICI: 319 ATM Forum, B-ICI Specification, Version 2.0, 320 af-bici-0013.002, (November 1995). 322 ATM Forum UNI PVC Only: 323 An ATM Forum compliant UNI with the 324 signalling disabled. 326 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 328 ATM Forum NNI PVC Only: 329 An ATM Forum compliant NNI with the 330 signalling disabled." 331 SYNTAX INTEGER { 332 other(1), 333 autoConfig(2), 334 ituDss2(3), 335 atmfUni3Dot0(4), 336 atmfUni3Dot1(5), 337 atmfUni4Dot0(6), 338 atmfIispUni3Dot0(7), 339 atmfIispUni3Dot1(8), 340 atmfIispUni4Dot0(9), 341 atmfPnni1Dot0(10), 342 atmfBici2Dot0(11), 343 atmfUniPvcOnly(12), 344 atmfNniPvcOnly(13) } 346 AtmServiceCategory ::= TEXTUAL-CONVENTION 347 STATUS current 348 DESCRIPTION 349 "The service category for a connection." 350 REFERENCE 351 "ATM Forum Traffic Management Specification, 352 Version 4.0, af-tm-0056.000, June 1996." 353 SYNTAX INTEGER { 354 other(1), -- none of the following 355 cbr(2), -- constant bit rate 356 rtVbr(3), -- real-time variable bit rate 357 nrtVbr(4), -- non real-time variable bit rate 358 abr(5), -- available bit rate 359 ubr(6) -- unspecified bit rate 360 } 362 AtmSigDescrParamIndex ::= TEXTUAL-CONVENTION 363 STATUS current 364 DESCRIPTION 365 "The value of this object identifies a row in the 366 atmSigDescrParamTable. The value 0 signifies that 367 none of the signalling parameters defined in the 368 atmSigDescrParamTable are applicable." 369 SYNTAX INTEGER (0..2147483647) 371 AtmTrafficDescrParamIndex ::= TEXTUAL-CONVENTION 372 STATUS current 374 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 376 DESCRIPTION 377 "The value of this object identifies a row in the 378 atmTrafficDescrParamTable. The value 0 signifies 379 that no row has been identified." 380 SYNTAX INTEGER (0..2147483647) 382 AtmVcIdentifier ::= TEXTUAL-CONVENTION 383 STATUS current 384 DESCRIPTION 385 "The VCI value for a VCL. The maximum VCI value 386 cannot exceed the value allowable by 387 atmInterfaceMaxVciBits defined in ATM-MIB." 388 SYNTAX INTEGER (0..65535) 390 AtmVpIdentifier ::= TEXTUAL-CONVENTION 391 STATUS current 392 DESCRIPTION 393 "The VPI value for a VPL or VCL. The value VPI=0 394 is only allowed for a VCL. For ATM UNIs supporting 395 VPCs the VPI value ranges from 0 to 255. The VPI 396 value 0 is supported for ATM UNIs conforming to 397 the ATM Forum UNI 4.0 Annex 8 (Virtual UNIs) 398 specification. For ATM UNIs supporting VCCs the 399 VPI value ranges from 0 to 255. For ATM NNIs the 400 VPI value ranges from 0 to 4095. The maximum VPI 401 value cannot exceed the value allowable by 402 atmInterfaceMaxVpiBits defined in ATM-MIB." 403 SYNTAX INTEGER (0..4095) 405 AtmVorXAdminStatus ::= TEXTUAL-CONVENTION 406 STATUS current 407 DESCRIPTION 408 "The value determines the desired administrative 409 status of a virtual link or cross-connect. The up 410 and down states indicate that the traffic flow is 411 enabled or disabled respectively on the virtual 412 link or cross-connect." 413 SYNTAX INTEGER { 414 up(1), 415 down(2) 416 } 418 AtmVorXLastChange ::= TEXTUAL-CONVENTION 419 STATUS current 420 DESCRIPTION 422 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 424 "The value of MIB II's sysUpTime at the time a 425 virtual link or cross-connect entered its current 426 operational state. If the current state was 427 entered prior to the last re-initialization of the 428 agent then this object contains a zero value." 429 SYNTAX TimeTicks 431 AtmVorXOperStatus ::= TEXTUAL-CONVENTION 432 STATUS current 433 DESCRIPTION 434 "The value determines the operational status of a 435 virtual link or cross-connect. The up and down 436 states indicate that the traffic flow is enabled 437 or disabled respectively on the virtual link or 438 cross-connect. The unknown state indicates that 439 the state of it cannot be determined. The state 440 will be down or unknown if the supporting ATM 441 interface(s) is down or unknown respectively." 442 SYNTAX INTEGER { 443 up(1), 444 down(2), 445 unknown(3) 446 } 448 -- OBJECT-IDENTITIES: 450 -- The following atmTrafficDescriptorTypes has been moved 451 -- from RFC1695 and no longer appear in the revision of 452 -- RFC1695[3]. 454 atmTrafficDescriptorTypes OBJECT IDENTIFIER ::= {mib-2 37 1 1} 455 -- atmMIBObjects 456 -- See [3]. 458 -- All other and new OBJECT IDENTITIES 459 -- are defined under the following subtree: 461 atmObjectIdentities OBJECT IDENTIFIER ::= {atmTCMIB 1} 463 -- The following values are defined for use as 464 -- possible values of the ATM traffic descriptor type. 466 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 468 atmNoTrafficDescriptor OBJECT-IDENTITY 469 STATUS deprecated 470 DESCRIPTION 471 "This identifies the no ATM traffic 472 descriptor type. Parameters 1, 2, 3, 4, 473 and 5 are not used. This traffic descriptor 474 type can be used for best effort traffic." 475 ::= {atmTrafficDescriptorTypes 1} 477 atmNoClpNoScr OBJECT-IDENTITY 478 STATUS current 479 DESCRIPTION 480 "This traffic descriptor type is for no CLP 481 and no Sustained Cell Rate. The use of the 482 parameter vector for this type: 483 Parameter 1: peak cell rate in cells/second 484 for CLP=0+1 traffic 485 Parameter 2: not used 486 Parameter 3: not used 487 Parameter 4: not used 488 Parameter 5: not used." 489 REFERENCE 490 "ATM Forum,ATM User-Network Interface, 491 Version 3.0 (UNI 3.0) Specification, 1994. 492 ATM Forum, ATM User-Network Interface, 493 Version 3.1 (UNI 3.1) Specification, 494 November 1994." 495 ::= {atmTrafficDescriptorTypes 2} 497 atmClpNoTaggingNoScr OBJECT-IDENTITY 498 STATUS deprecated 499 DESCRIPTION 500 "This traffic descriptor is for CLP without 501 tagging and no Sustained Cell Rate. The use 502 of the parameter vector for this type: 503 Parameter 1: peak cell rate in cells/second 504 for CLP=0+1 traffic 505 Parameter 2: peak cell rate in cells/second 506 for CLP=0 traffic 507 Parameter 3: not used 508 Parameter 4: not used 509 Parameter 5: not used." 510 ::= {atmTrafficDescriptorTypes 3} 512 atmClpTaggingNoScr OBJECT-IDENTITY 514 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 516 STATUS deprecated 517 DESCRIPTION 518 "This traffic descriptor is for CLP with 519 tagging and no Sustained Cell Rate. The use 520 of the parameter vector for this type: 521 Parameter 1: peak cell rate in cells/second 522 for CLP=0+1 traffic 523 Parameter 2: peak cell rate in cells/second 524 for CLP=0 traffic, excess 525 tagged as CLP=1 526 Parameter 3: not used 527 Parameter 4: not used 528 Parameter 5: not used." 529 ::= {atmTrafficDescriptorTypes 4} 531 atmNoClpScr OBJECT-IDENTITY 532 STATUS current 533 DESCRIPTION 534 "This traffic descriptor type is for no CLP 535 with Sustained Cell Rate. The use of the 536 parameter vector for this type: 537 Parameter 1: peak cell rate in cells/second 538 for CLP=0+1 traffic 539 Parameter 2: sustainable cell rate in cells/second 540 for CLP=0+1 traffic 541 Parameter 3: maximum burst size in cells 542 Parameter 4: not used 543 Parameter 5: not used." 544 REFERENCE 545 "ATM Forum,ATM User-Network Interface, 546 Version 3.0 (UNI 3.0) Specification, 1994. 547 ATM Forum, ATM User-Network Interface, 548 Version 3.1 (UNI 3.1) Specification, 549 November 1994." 550 ::= {atmTrafficDescriptorTypes 5} 552 atmClpNoTaggingScr OBJECT-IDENTITY 553 STATUS current 554 DESCRIPTION 555 "This traffic descriptor type is for CLP with 556 Sustained Cell Rate and no tagging. The use 557 of the parameter vector for this type: 558 Parameter 1: peak cell rate in cells/second 559 for CLP=0+1 traffic 560 Parameter 2: sustainable cell rate in cells/second 562 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 564 for CLP=0 traffic 565 Parameter 3: maximum burst size in cells 566 Parameter 4: not used 567 Parameter 5: not used." 568 REFERENCE 569 "ATM Forum,ATM User-Network Interface, 570 Version 3.0 (UNI 3.0) Specification, 1994. 571 ATM Forum, ATM User-Network Interface, 572 Version 3.1 (UNI 3.1) Specification, 573 November 1994." 574 ::= {atmTrafficDescriptorTypes 6} 576 atmClpTaggingScr OBJECT-IDENTITY 577 STATUS current 578 DESCRIPTION 579 "This traffic descriptor type is for CLP with 580 tagging and Sustained Cell Rate. The use of 581 the parameter vector for this type: 582 Parameter 1: peak cell rate in cells/second 583 for CLP=0+1 traffic 584 Parameter 2: sustainable cell rate in cells/second 585 for CLP=0 traffic, excess tagged as 586 CLP=1 587 Parameter 3: maximum burst size in cells 588 Parameter 4: not used 589 Parameter 5: not used." 590 REFERENCE 591 "ATM Forum,ATM User-Network Interface, 592 Version 3.0 (UNI 3.0) Specification, 1994. 593 ATM Forum, ATM User-Network Interface, 594 Version 3.1 (UNI 3.1) Specification, 595 November 1994." 596 ::= {atmTrafficDescriptorTypes 7} 598 atmClpNoTaggingMcr OBJECT-IDENTITY 599 STATUS current 600 DESCRIPTION 601 "This traffic descriptor type is for CLP with 602 Minimum Cell Rate and no tagging. The use of 603 the parameter vector for this type: 604 Parameter 1: peak cell rate in cells/second 605 for CLP=0+1 traffic 606 Parameter 2: CDVT in tenths of microseconds 607 Parameter 3: minimum cell rate in cells/second 608 Parameter 4: unused 610 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 612 Parameter 5: unused." 613 REFERENCE 614 "ATM Forum,ATM User-Network Interface, 615 Version 3.0 (UNI 3.0) Specification, 1994. 616 ATM Forum, ATM User-Network Interface, 617 Version 3.1 (UNI 3.1) Specification, 618 November 1994." 619 ::= {atmTrafficDescriptorTypes 8} 621 atmClpTransparentNoScr OBJECT-IDENTITY 622 STATUS current 623 DESCRIPTION 624 "This traffic descriptor type is for the CLP- 625 transparent model and no Sustained Cell Rate. 626 The use of the parameter vector for this type: 627 Parameter 1: peak cell rate in cells/second 628 for CLP=0+1 traffic 629 Parameter 2: CDVT in tenths of microseconds 630 Parameter 3: not used 631 Parameter 4: not used 632 Parameter 5: not used. 634 This traffic descriptor type is applicable to 635 connections following the CBR.1 conformance 636 definition. 638 Connections specifying this traffic descriptor 639 type will be rejected at UNI 3.0 or UNI 3.1 640 interfaces. For a similar traffic descriptor 641 type that can be accepted at UNI 3.0 and 642 UNI 3.1 interfaces, see atmNoClpNoScr." 643 REFERENCE 644 "ATM Forum,ATM User-Network Interface, 645 Version 3.0 (UNI 3.0) Specification, 1994. 646 ATM Forum, ATM User-Network Interface, 647 Version 3.1 (UNI 3.1) Specification, 648 November 1994. 649 ATM Forum, Traffic Management Specification, 650 Version 4.0, af-tm-0056.000, June 1996." 651 ::= {atmTrafficDescriptorTypes 9} 653 atmClpTransparentScr OBJECT-IDENTITY 654 STATUS current 655 DESCRIPTION 656 "This traffic descriptor type is for the CLP- 658 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 660 transparent model with Sustained Cell Rate. 661 The use of the parameter vector for this type: 662 Parameter 1: peak cell rate in cells/second 663 for CLP=0+1 traffic 664 Parameter 2: sustainable cell rate in cells/second 665 for CLP=0+1 traffic 666 Parameter 3: maximum burst size in cells 667 Parameter 4: CDVT in tenths of microseconds 668 Parameter 5: not used. 670 This traffic descriptor type is applicable to 671 connections following the VBR.1 conformance 672 definition. 674 Connections specifying this traffic descriptor 675 type will be rejected at UNI 3.0 or UNI 3.1 676 interfaces. For a similar traffic descriptor 677 type that can be accepted at UNI 3.0 and 678 UNI 3.1 interfaces, see atmNoClpScr." 679 REFERENCE 680 "ATM Forum,ATM User-Network Interface, 681 Version 3.0 (UNI 3.0) Specification, 1994. 682 ATM Forum, ATM User-Network Interface, 683 Version 3.1 (UNI 3.1) Specification, 684 November 1994. 685 ATM Forum, Traffic Management Specification, 686 Version 4.0, af-tm-0056.000, June 1996." 687 ::= {atmTrafficDescriptorTypes 10} 689 atmNoClpTaggingNoScr OBJECT-IDENTITY 690 STATUS current 691 DESCRIPTION 692 "This traffic descriptor type is for no CLP 693 with tagging and no Sustained Cell Rate. The 694 use of the parameter vector for this type: 695 Parameter 1: peak cell rate in cells/second 696 for CLP=0+1 traffic 697 Parameter 2: CDVT in tenths of microseconds 698 Parameter 3: not used 699 Parameter 4: not used 700 Parameter 5: not used. 702 This traffic descriptor type is applicable to 703 connections following the UBR.2 conformance 704 definition ." 706 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 708 REFERENCE 709 "ATM Forum,ATM User-Network Interface, 710 Version 3.0 (UNI 3.0) Specification, 1994. 711 ATM Forum, ATM User-Network Interface, 712 Version 3.1 (UNI 3.1) Specification, 713 November 1994. 714 ATM Forum, Traffic Management Specification, 715 Version 4.0, af-tm-0056.000, June 1996." 716 ::= {atmTrafficDescriptorTypes 11} 718 atmNoClpNoScrCdvt OBJECT-IDENTITY 719 STATUS current 720 DESCRIPTION 721 "This traffic descriptor type is for no CLP 722 and no Sustained Cell Rate. The use of the 723 parameter vector for this type: 724 Parameter 1: peak cell rate in cells/second 725 for CLP=0+1 traffic 726 Parameter 2: CDVT in tenths of microseconds 727 Parameter 3: not used 728 Parameter 4: not used 729 Parameter 5: not used. 731 This traffic descriptor type is applicable to 732 CBR connections following the UNI 3.0/3.1 733 conformance definition for PCR CLP=0+1. 734 These CBR connections differ from CBR.1 735 connections in that the CLR objective 736 applies only to the CLP=0 cell flow. 738 This traffic descriptor type is also 739 applicable to connections following the UBR.1 740 conformance definition." 741 REFERENCE 742 "ATM Forum,ATM User-Network Interface, 743 Version 3.0 (UNI 3.0) Specification, 1994. 744 ATM Forum, ATM User-Network Interface, 745 Version 3.1 (UNI 3.1) Specification, 746 November 1994. 747 ATM Forum, Traffic Management Specification, 748 Version 4.0, af-tm-0056.000, June 1996." 749 ::= {atmTrafficDescriptorTypes 12} 751 atmNoClpScrCdvt OBJECT-IDENTITY 752 STATUS current 754 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 756 DESCRIPTION 757 "This traffic descriptor type is for no CLP 758 with Sustained Cell Rate. The use of the 759 parameter vector for this type: 760 Parameter 1: peak cell rate in cells/second 761 for CLP=0+1 traffic 762 Parameter 2: sustainable cell rate in cells/second 763 for CLP=0+1 traffic 764 Parameter 3: maximum burst size in cells 765 Parameter 4: CDVT in tenths of microseconds 766 Parameter 5: not used. 768 This traffic descriptor type is applicable 769 to VBR connections following the UNI 3.0/3.1 770 conformance definition for PCR CLP=0+1 and 771 SCR CLP=0+1. These VBR connections 772 differ from VBR.1 connections in that 773 the CLR objective applies only to the CLP=0 774 cell flow." 775 REFERENCE 776 "ATM Forum,ATM User-Network Interface, 777 Version 3.0 (UNI 3.0) Specification, 1994. 778 ATM Forum, ATM User-Network Interface, 779 Version 3.1 (UNI 3.1) Specification, 780 November 1994. 781 ATM Forum, Traffic Management Specification, 782 Version 4.0, af-tm-0056.000, June 1996." 783 ::= {atmTrafficDescriptorTypes 13} 785 atmClpNoTaggingScrCdvt OBJECT-IDENTITY 786 STATUS current 787 DESCRIPTION 788 "This traffic descriptor type is for CLP with 789 Sustained Cell Rate and no tagging. The use 790 of the parameter vector for this type: 791 Parameter 1: peak cell rate in cells/second 792 for CLP=0+1 traffic 793 Parameter 2: sustainable cell rate in cells/second 794 for CLP=0 traffic 795 Parameter 3: maximum burst size in cells 796 Parameter 4: CDVT in tenths of microseconds 797 Parameter 5: not used. 799 This traffic descriptor type is applicable to 800 connections following the VBR.2 conformance 802 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 804 definition." 805 REFERENCE 806 "ATM Forum,ATM User-Network Interface, 807 Version 3.0 (UNI 3.0) Specification, 1994. 808 ATM Forum, ATM User-Network Interface, 809 Version 3.1 (UNI 3.1) Specification, 810 November 1994. 811 ATM Forum, Traffic Management Specification, 812 Version 4.0, af-tm-0056.000, June 1996." 813 ::= {atmTrafficDescriptorTypes 14} 815 atmClpTaggingScrCdvt OBJECT-IDENTITY 816 STATUS current 817 DESCRIPTION 818 "This traffic descriptor type is for CLP with 819 tagging and Sustained Cell Rate. The use of 820 the parameter vector for this type: 821 Parameter 1: peak cell rate in cells/second 822 for CLP=0+1 traffic 823 Parameter 2: sustainable cell rate in cells/second 824 for CLP=0 traffic, excess tagged as 825 CLP=1 826 Parameter 3: maximum burst size in cells 827 Parameter 4: CDVT in tenths of microseconds 828 Parameter 5: not used. 830 This traffic descriptor type is applicable to 831 connections following the VBR.3 conformance 832 definition." 833 REFERENCE 834 "ATM Forum,ATM User-Network Interface, 835 Version 3.0 (UNI 3.0) Specification, 1994. 836 ATM Forum, ATM User-Network Interface, 837 Version 3.1 (UNI 3.1) Specification, 838 November 1994. 839 ATM Forum, Traffic Management Specification, 840 Version 4.0, af-tm-0056.000, June 1996." 841 ::= {atmTrafficDescriptorTypes 15} 843 END 845 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 847 4. Acknowledgments 849 This document is a product of the AToMMIB Working Group. 851 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 853 5. References 855 [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 856 "Textual Conventions for Version 2 of the Simple Network 857 Management Protocol (SNMPv2)", RFC1903, SNMP 858 Research,Inc., Cisco Systems, Inc., Dover Beach 859 Consulting, Inc., International Network Services, January 860 1996. 862 [2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 863 "Structure of Management Information for Version 2 of the 864 Simple Network Management Protocol (SNMPv2)", RFC1902, 865 SNMP Research,Inc., Cisco Systems, Inc., Dover Beach 866 Consulting, Inc., International Network Services, January 867 1996. 869 [3] Kaj Tesink, "Definitions of Managed Objects for ATM 870 Management", RFC???? (Internet-Draft ), Bellcore, April 1998. 873 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 875 6. Security Considerations 877 This memo defines textual conventions and object identities 878 for use in ATM MIB modules. Security issues for these MIB 879 modules are addressed in the memos defining those modules. 881 7. Authors' Addresses 883 Michael Noto 884 Network Equipment Technologies 885 800 Saginaw Drive RM 21.1.111 886 Redwood City, CA 94063 887 Phone +1 415 569-7134 888 EMail: mike_noto@net.com 890 Ethan Mickey Spiegel 891 Cisco Systems 892 170 W. Tasman Dr. 893 San Jose, CA 95134 894 USA 895 Phone +1 408 526 6408 896 E-mail: mspiegel@cisco.com" 898 Kaj Tesink 899 Bellcore 900 331 Newman Springs Road 901 P.O. Box 7020 902 Red Bank, NJ 07701-7020 903 Phone: (732) 758-5254 904 EMail: kaj@cc.bellcore.com 906 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 908 8. Full Copyright Statement 910 Copyright (C) The Internet Society (1998). All Rights 911 Reserved. 913 This document and translations of it may be copied and 914 furnished to others, and derivative works that comment on or 915 otherwise explain it or assist in its implementation may be 916 prepared, copied, published and distributed, in whole or in 917 part, without restriction of any kind, provided that the above 918 copyright notice and this paragraph are included on all such 919 copies and derivative works. However, this document itself 920 may not be modified in any way, such as by removing the 921 copyright notice or references to the Internet Society or 922 other Internet organizations, except as needed for the purpose 923 of developing Internet standards in which case the procedures 924 for copyrights defined in the Internet Standards process must 925 be followed, or as required to translate it into languages 926 other than English. 928 The limited permissions granted above are perpetual and will 929 not be revoked by the Internet Society or its successors or 930 assigns. 932 This document and the information contained herein is provided 933 on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 934 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 935 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE 936 USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 937 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 938 PARTICULAR PURPOSE." 940 draft ATM TCs and OBJECT-IDENTITIES 8/15/1998 942 Table of Contents 944 1 Status of this Memo ................................... 1 945 2 Introduction .......................................... 3 946 3 Definitions ........................................... 4 947 4 Acknowledgments ....................................... 20 948 5 References ............................................ 21 949 6 Security Considerations ............................... 22 950 7 Authors' Addresses .................................... 22 951 8 Full Copyright Statement .............................. 23