idnits 2.17.1 draft-ietf-atommib-atm2TC-09.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 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 (October 19, 1998) is 9320 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 850 looks like a reference -- Missing reference section? '2' on line 857 looks like a reference -- Missing reference section? '3' on line 864 looks like a reference Summary: 13 errors (**), 0 flaws (~~), 3 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 October 19, 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@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 10/19/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 10/19/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 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 89 3. Definitions 91 ATM-TC-MIB DEFINITIONS ::= BEGIN 93 IMPORTS 94 MODULE-IDENTITY, OBJECT-IDENTITY, 95 TimeTicks, mib-2 96 FROM SNMPv2-SMI 97 TEXTUAL-CONVENTION 98 FROM SNMPv2-TC; 100 atmTCMIB MODULE-IDENTITY 101 LAST-UPDATED "9810190200Z" 102 ORGANIZATION "IETF AToMMIB Working Group" 103 CONTACT-INFO 104 " Michael Noto 105 Postal: Network Equipment Technologies 106 800 Saginaw Drive RM 21.1.111 107 Redwood City, CA 94063 108 USA 109 Tel: +1 415 569-7134 110 E-mail: mike_noto@net.com 112 Ethan Mickey Spiegel 113 Postal: Cisco Systems 114 170 W. Tasman Dr. 115 San Jose, CA 95134 116 USA 117 Tel: +1 408 526 6408 118 E-mail: mspiegel@cisco.com 120 Kaj Tesink 121 Postal: Bellcore 122 331 Newman Springs Road 123 Red Bank, NJ 07701 124 USA 125 Tel: +1 732 758 5254 126 Fax: +1 732 758 4177 127 E-mail: kaj@bellcore.com" 128 DESCRIPTION 129 "This MIB Module provides Textual Conventions 130 and OBJECT-IDENTITY Objects to be used by 131 ATM systems." 132 ::= { mib-2 37 3 } -- atmMIB 3 (see [3]) 134 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 136 -- The Textual Conventions defined below are organized 137 -- alphabetically 139 AtmAddr ::= TEXTUAL-CONVENTION 140 DISPLAY-HINT "1x" 141 STATUS current 142 DESCRIPTION 143 "An ATM address. The semantics are implied by 144 the length. The address types are: - no 145 address (0 octets) - E.164 (8 octets) - NSAP 146 (20 octets) In addition, when subaddresses 147 are used the AtmAddr may represent the 148 concatenation of address and subaddress. The 149 associated address types are: - E.164, E.164 150 (16 octets) - E.164, NSAP (28 octets) - NSAP, 151 NSAP (40 octets) Address lengths other than 152 defined in this definition imply address 153 types defined elsewhere. Note: The E.164 154 address is encoded in BCD format." 155 SYNTAX OCTET STRING (SIZE(0..40)) 157 AtmConnCastType ::= TEXTUAL-CONVENTION 158 STATUS current 159 DESCRIPTION 160 "The type of topology of a connection (point- 161 to-point, point-to-multipoint). In the case 162 of point-to-multipoint, the orientation of 163 this VPL or VCL in the connection. 164 On a host: 165 - p2mpRoot indicates that the host 166 is the root of the p2mp connection. 167 - p2mpLeaf indicates that the host 168 is a leaf of the p2mp connection. 169 On a switch interface: 170 - p2mpRoot indicates that cells received 171 by the switching fabric from the interface 172 are from the root of the p2mp connection. 173 - p2mpLeaf indicates that cells transmitted 174 to the interface from the switching fabric 175 are to the leaf of the p2mp connection." 176 SYNTAX INTEGER { 177 p2p(1), 178 p2mpRoot(2), 180 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 182 p2mpLeaf(3) 183 } 185 AtmConnKind ::= TEXTUAL-CONVENTION 186 STATUS current 187 DESCRIPTION 188 "The type of call control used for an ATM 189 connection at a particular interface. The use 190 is as follows: 191 pvc(1) 192 Virtual link of a PVC. Should not be 193 used for an PVC/SVC (i.e., Soft PVC) 194 crossconnect. 195 svcIncoming(2) 196 Virtual link established after a 197 received signaling request to setup 198 an SVC. 199 svcOutgoing(3) 200 Virtual link established after a 201 transmitted or forwarded signaling 202 request to setup an SVC. 203 spvcInitiator(4) 204 Virtual link at the PVC side of an 205 SVC/PVC crossconnect, where the 206 switch is the initiator of the Soft PVC 207 setup. 208 spvcTarget(5) 209 Virtual link at the PVC side of an 210 SVC/PVC crossconnect, where the 211 switch is the target of the Soft PVC 212 setup. 214 For PVCs, a pvc virtual link is always cross- 215 connected to a pvc virtual link. 217 For SVCs, an svcIncoming virtual link is always cross- 218 connected to an svcOutgoing virtual link. 220 For Soft PVCs, an spvcInitiator is either cross-connected to 221 an svcOutgoing or an spvcTarget, and an spvcTarget is either 222 cross-connected to an svcIncoming or an spvcInitiator." 223 SYNTAX INTEGER { 224 pvc(1), 225 svcIncoming(2), 226 svcOutgoing(3), 228 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 230 spvcInitiator(4), 231 spvcTarget(5) 232 } 234 AtmIlmiNetworkPrefix ::= TEXTUAL-CONVENTION 235 STATUS current 236 DESCRIPTION 237 "A network prefix used for ILMI address 238 registration. In the case of ATM endsystem 239 addresses (AESAs), the network prefix is the first 240 13 octets of the address which includes the AFI, 241 IDI, and HO-DSP fields. In the case of native 242 E.164 addresses, the network prefix is the entire 243 E.164 address encoded in 8 octets, as if it were 244 an E.164 IDP in an ATM endsystem address 245 structure." 246 REFERENCE 247 "ATM Forum, Integrated Local Management Interface 248 (ILMI) Specification, Version 4.0, 249 af-ilmi-0065.000, September 1996, Section 9 250 ATM Forum, ATM User-Network Interface Signalling 251 Specification, Version 4.0 (UNI 4.0), 252 af-sig-0061.000, June 1996, Section 3" 253 SYNTAX OCTET STRING (SIZE(8|13)) 255 AtmInterfaceType ::= TEXTUAL-CONVENTION 256 STATUS current 257 DESCRIPTION 258 "The connection setup procedures used for the 259 identified interface. 261 Other: Connection setup procedures other than 262 those listed below. 264 Auto-configuration: 265 Indicates that the connection setup 266 procedures are to be determined dynamically, 267 or that determination has not yet been 268 completed. One such mechanism is via ATM 269 Forum ILMI auto-configuration procedures. 271 ITU-T DSS2: 272 - ITU-T Recommendation Q.2931, Broadband 273 Integrated Service Digital Network (B-ISDN) 274 Digital Subscriber Signalling System No.2 276 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 278 (DSS2) User-Network Interface (UNI) Layer 3 279 Specification for Basic Call/Connection 280 Control (September 1994) 281 - ITU-T Draft Recommendation Q.2961, 282 B-ISDN DSS 2 Support of Additional Traffic 283 Parameters (May 1995) 285 - ITU-T Draft Recommendation Q.2971, 286 B-ISDN DSS 2 User Network Interface Layer 3 287 Specification for Point-to-multipoint 288 Call/connection Control (May 1995) 290 ATM Forum UNI 3.0: 291 ATM Forum, ATM User-Network Interface, 292 Version 3.0 (UNI 3.0) Specification, 293 (1994). 295 ATM Forum UNI 3.1: 296 ATM Forum, ATM User-Network Interface, 297 Version 3.1 (UNI 3.1) Specification, 298 (November 1994). 300 ATM Forum UNI Signalling 4.0: 301 ATM Forum, ATM User-Network Interface (UNI) 302 Signalling Specification Version 4.0, 303 af-sig-0061.000 (June 1996). 305 ATM Forum IISP (based on UNI 3.0 or UNI 3.1) : 306 Interim Inter-switch Signaling Protocol 307 (IISP) Specification, Version 1.0, 308 af-pnni-0026.000, (December 1994). 310 ATM Forum PNNI 1.0 : 311 ATM Forum, Private Network-Network Interface 312 Specification, Version 1.0, af-pnni-0055.000, 313 (March 1996). 315 ATM Forum B-ICI: 316 ATM Forum, B-ICI Specification, Version 2.0, 317 af-bici-0013.002, (November 1995). 319 ATM Forum UNI PVC Only: 320 An ATM Forum compliant UNI with the 321 signalling disabled. 323 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 325 ATM Forum NNI PVC Only: 326 An ATM Forum compliant NNI with the 327 signalling disabled." 328 SYNTAX INTEGER { 329 other(1), 330 autoConfig(2), 331 ituDss2(3), 332 atmfUni3Dot0(4), 333 atmfUni3Dot1(5), 334 atmfUni4Dot0(6), 335 atmfIispUni3Dot0(7), 336 atmfIispUni3Dot1(8), 337 atmfIispUni4Dot0(9), 338 atmfPnni1Dot0(10), 339 atmfBici2Dot0(11), 340 atmfUniPvcOnly(12), 341 atmfNniPvcOnly(13) } 343 AtmServiceCategory ::= TEXTUAL-CONVENTION 344 STATUS current 345 DESCRIPTION 346 "The service category for a connection." 347 REFERENCE 348 "ATM Forum Traffic Management Specification, 349 Version 4.0, af-tm-0056.000, June 1996." 350 SYNTAX INTEGER { 351 other(1), -- none of the following 352 cbr(2), -- constant bit rate 353 rtVbr(3), -- real-time variable bit rate 354 nrtVbr(4), -- non real-time variable bit rate 355 abr(5), -- available bit rate 356 ubr(6) -- unspecified bit rate 357 } 359 AtmSigDescrParamIndex ::= TEXTUAL-CONVENTION 360 STATUS current 361 DESCRIPTION 362 "The value of this object identifies a row in the 363 atmSigDescrParamTable. The value 0 signifies that 364 none of the signalling parameters defined in the 365 atmSigDescrParamTable are applicable." 366 SYNTAX INTEGER (0..2147483647) 368 AtmTrafficDescrParamIndex ::= TEXTUAL-CONVENTION 369 STATUS current 371 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 373 DESCRIPTION 374 "The value of this object identifies a row in the 375 atmTrafficDescrParamTable. The value 0 signifies 376 that no row has been identified." 377 SYNTAX INTEGER (0..2147483647) 379 AtmVcIdentifier ::= TEXTUAL-CONVENTION 380 STATUS current 381 DESCRIPTION 382 "The VCI value for a VCL. The maximum VCI value 383 cannot exceed the value allowable by 384 atmInterfaceMaxVciBits defined in ATM-MIB." 385 SYNTAX INTEGER (0..65535) 387 AtmVpIdentifier ::= TEXTUAL-CONVENTION 388 STATUS current 389 DESCRIPTION 390 "The VPI value for a VPL or VCL. The value VPI=0 391 is only allowed for a VCL. For ATM UNIs supporting 392 VPCs the VPI value ranges from 0 to 255. The VPI 393 value 0 is supported for ATM UNIs conforming to 394 the ATM Forum UNI 4.0 Annex 8 (Virtual UNIs) 395 specification. For ATM UNIs supporting VCCs the 396 VPI value ranges from 0 to 255. For ATM NNIs the 397 VPI value ranges from 0 to 4095. The maximum VPI 398 value cannot exceed the value allowable by 399 atmInterfaceMaxVpiBits defined in ATM-MIB." 400 SYNTAX INTEGER (0..4095) 402 AtmVorXAdminStatus ::= TEXTUAL-CONVENTION 403 STATUS current 404 DESCRIPTION 405 "The value determines the desired administrative 406 status of a virtual link or cross-connect. The up 407 and down states indicate that the traffic flow is 408 enabled or disabled respectively on the virtual 409 link or cross-connect." 410 SYNTAX INTEGER { 411 up(1), 412 down(2) 413 } 415 AtmVorXLastChange ::= TEXTUAL-CONVENTION 416 STATUS current 417 DESCRIPTION 419 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 421 "The value of MIB II's sysUpTime at the time a 422 virtual link or cross-connect entered its current 423 operational state. If the current state was 424 entered prior to the last re-initialization of the 425 agent then this object contains a zero value." 426 SYNTAX TimeTicks 428 AtmVorXOperStatus ::= TEXTUAL-CONVENTION 429 STATUS current 430 DESCRIPTION 431 "The value determines the operational status of a 432 virtual link or cross-connect. The up and down 433 states indicate that the traffic flow is enabled 434 or disabled respectively on the virtual link or 435 cross-connect. The unknown state indicates that 436 the state of it cannot be determined. The state 437 will be down or unknown if the supporting ATM 438 interface(s) is down or unknown respectively." 439 SYNTAX INTEGER { 440 up(1), 441 down(2), 442 unknown(3) 443 } 445 -- OBJECT-IDENTITIES: 447 -- The following atmTrafficDescriptorTypes has been moved 448 -- from RFC1695 and no longer appear in the revision of 449 -- RFC1695[3]. 451 atmTrafficDescriptorTypes OBJECT IDENTIFIER ::= {mib-2 37 1 1} 452 -- atmMIBObjects 453 -- See [3]. 455 -- All other and new OBJECT IDENTITIES 456 -- are defined under the following subtree: 458 atmObjectIdentities OBJECT IDENTIFIER ::= {atmTCMIB 1} 460 -- The following values are defined for use as 461 -- possible values of the ATM traffic descriptor type. 463 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 465 atmNoTrafficDescriptor OBJECT-IDENTITY 466 STATUS deprecated 467 DESCRIPTION 468 "This identifies the no ATM traffic 469 descriptor type. Parameters 1, 2, 3, 4, 470 and 5 are not used. This traffic descriptor 471 type can be used for best effort traffic." 472 ::= {atmTrafficDescriptorTypes 1} 474 atmNoClpNoScr OBJECT-IDENTITY 475 STATUS current 476 DESCRIPTION 477 "This traffic descriptor type is for no CLP 478 and no Sustained Cell Rate. The use of the 479 parameter vector for this type: 480 Parameter 1: peak cell rate in cells/second 481 for CLP=0+1 traffic 482 Parameter 2: not used 483 Parameter 3: not used 484 Parameter 4: not used 485 Parameter 5: not used." 486 REFERENCE 487 "ATM Forum,ATM User-Network Interface, 488 Version 3.0 (UNI 3.0) Specification, 1994. 489 ATM Forum, ATM User-Network Interface, 490 Version 3.1 (UNI 3.1) Specification, 491 November 1994." 492 ::= {atmTrafficDescriptorTypes 2} 494 atmClpNoTaggingNoScr OBJECT-IDENTITY 495 STATUS deprecated 496 DESCRIPTION 497 "This traffic descriptor is for CLP without 498 tagging and no Sustained Cell Rate. The use 499 of the parameter vector for this type: 500 Parameter 1: peak cell rate in cells/second 501 for CLP=0+1 traffic 502 Parameter 2: peak cell rate in cells/second 503 for CLP=0 traffic 504 Parameter 3: not used 505 Parameter 4: not used 506 Parameter 5: not used." 507 ::= {atmTrafficDescriptorTypes 3} 509 atmClpTaggingNoScr OBJECT-IDENTITY 510 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 512 STATUS deprecated 513 DESCRIPTION 514 "This traffic descriptor is for CLP with 515 tagging and no Sustained Cell Rate. The use 516 of the parameter vector for this type: 517 Parameter 1: peak cell rate in cells/second 518 for CLP=0+1 traffic 519 Parameter 2: peak cell rate in cells/second 520 for CLP=0 traffic, excess 521 tagged as CLP=1 522 Parameter 3: not used 523 Parameter 4: not used 524 Parameter 5: not used." 525 ::= {atmTrafficDescriptorTypes 4} 527 atmNoClpScr OBJECT-IDENTITY 528 STATUS current 529 DESCRIPTION 530 "This traffic descriptor type is for no CLP 531 with Sustained Cell Rate. The use of the 532 parameter vector for this type: 533 Parameter 1: peak cell rate in cells/second 534 for CLP=0+1 traffic 535 Parameter 2: sustainable cell rate in cells/second 536 for CLP=0+1 traffic 537 Parameter 3: maximum burst size in cells 538 Parameter 4: not used 539 Parameter 5: not used." 540 REFERENCE 541 "ATM Forum,ATM User-Network Interface, 542 Version 3.0 (UNI 3.0) Specification, 1994. 543 ATM Forum, ATM User-Network Interface, 544 Version 3.1 (UNI 3.1) Specification, 545 November 1994." 546 ::= {atmTrafficDescriptorTypes 5} 548 atmClpNoTaggingScr OBJECT-IDENTITY 549 STATUS current 550 DESCRIPTION 551 "This traffic descriptor type is for CLP with 552 Sustained Cell Rate and no tagging. The use 553 of the parameter vector for this type: 554 Parameter 1: peak cell rate in cells/second 555 for CLP=0+1 traffic 556 Parameter 2: sustainable cell rate in cells/second 558 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 560 for CLP=0 traffic 561 Parameter 3: maximum burst size in cells 562 Parameter 4: not used 563 Parameter 5: not used." 564 REFERENCE 565 "ATM Forum,ATM User-Network Interface, 566 Version 3.0 (UNI 3.0) Specification, 1994. 567 ATM Forum, ATM User-Network Interface, 568 Version 3.1 (UNI 3.1) Specification, 569 November 1994." 570 ::= {atmTrafficDescriptorTypes 6} 572 atmClpTaggingScr OBJECT-IDENTITY 573 STATUS current 574 DESCRIPTION 575 "This traffic descriptor type is for CLP with 576 tagging and Sustained Cell Rate. The use of 577 the parameter vector for this type: 578 Parameter 1: peak cell rate in cells/second 579 for CLP=0+1 traffic 580 Parameter 2: sustainable cell rate in cells/second 581 for CLP=0 traffic, excess tagged as 582 CLP=1 583 Parameter 3: maximum burst size in cells 584 Parameter 4: not used 585 Parameter 5: not used." 586 REFERENCE 587 "ATM Forum,ATM User-Network Interface, 588 Version 3.0 (UNI 3.0) Specification, 1994. 589 ATM Forum, ATM User-Network Interface, 590 Version 3.1 (UNI 3.1) Specification, 591 November 1994." 592 ::= {atmTrafficDescriptorTypes 7} 594 atmClpNoTaggingMcr OBJECT-IDENTITY 595 STATUS current 596 DESCRIPTION 597 "This traffic descriptor type is for CLP with 598 Minimum Cell Rate and no tagging. The use of 599 the parameter vector for this type: 600 Parameter 1: peak cell rate in cells/second 601 for CLP=0+1 traffic 602 Parameter 2: CDVT in tenths of microseconds 603 Parameter 3: minimum cell rate in cells/second 604 Parameter 4: unused 606 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 608 Parameter 5: unused." 609 REFERENCE 610 "ATM Forum,ATM User-Network Interface, 611 Version 3.0 (UNI 3.0) Specification, 1994. 612 ATM Forum, ATM User-Network Interface, 613 Version 3.1 (UNI 3.1) Specification, 614 November 1994." 615 ::= {atmTrafficDescriptorTypes 8} 617 atmClpTransparentNoScr OBJECT-IDENTITY 618 STATUS current 619 DESCRIPTION 620 "This traffic descriptor type is for the CLP- 621 transparent model and no Sustained Cell Rate. 622 The use of the parameter vector for this type: 623 Parameter 1: peak cell rate in cells/second 624 for CLP=0+1 traffic 625 Parameter 2: CDVT in tenths of microseconds 626 Parameter 3: not used 627 Parameter 4: not used 628 Parameter 5: not used. 630 This traffic descriptor type is applicable to 631 connections following the CBR.1 conformance 632 definition. 634 Connections specifying this traffic descriptor 635 type will be rejected at UNI 3.0 or UNI 3.1 636 interfaces. For a similar traffic descriptor 637 type that can be accepted at UNI 3.0 and 638 UNI 3.1 interfaces, see atmNoClpNoScr." 639 REFERENCE 640 "ATM Forum,ATM User-Network Interface, 641 Version 3.0 (UNI 3.0) Specification, 1994. 642 ATM Forum, ATM User-Network Interface, 643 Version 3.1 (UNI 3.1) Specification, 644 November 1994. 645 ATM Forum, Traffic Management Specification, 646 Version 4.0, af-tm-0056.000, June 1996." 647 ::= {atmTrafficDescriptorTypes 9} 649 atmClpTransparentScr OBJECT-IDENTITY 650 STATUS current 651 DESCRIPTION 652 "This traffic descriptor type is for the CLP- 654 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 656 transparent model with Sustained Cell Rate. 657 The use of the parameter vector for this type: 658 Parameter 1: peak cell rate in cells/second 659 for CLP=0+1 traffic 660 Parameter 2: sustainable cell rate in cells/second 661 for CLP=0+1 traffic 662 Parameter 3: maximum burst size in cells 663 Parameter 4: CDVT in tenths of microseconds 664 Parameter 5: not used. 666 This traffic descriptor type is applicable to 667 connections following the VBR.1 conformance 668 definition. 670 Connections specifying this traffic descriptor 671 type will be rejected at UNI 3.0 or UNI 3.1 672 interfaces. For a similar traffic descriptor 673 type that can be accepted at UNI 3.0 and 674 UNI 3.1 interfaces, see atmNoClpScr." 675 REFERENCE 676 "ATM Forum,ATM User-Network Interface, 677 Version 3.0 (UNI 3.0) Specification, 1994. 678 ATM Forum, ATM User-Network Interface, 679 Version 3.1 (UNI 3.1) Specification, 680 November 1994. 681 ATM Forum, Traffic Management Specification, 682 Version 4.0, af-tm-0056.000, June 1996." 683 ::= {atmTrafficDescriptorTypes 10} 685 atmNoClpTaggingNoScr OBJECT-IDENTITY 686 STATUS current 687 DESCRIPTION 688 "This traffic descriptor type is for no CLP 689 with tagging and no Sustained Cell Rate. The 690 use of the parameter vector for this type: 691 Parameter 1: peak cell rate in cells/second 692 for CLP=0+1 traffic 693 Parameter 2: CDVT in tenths of microseconds 694 Parameter 3: not used 695 Parameter 4: not used 696 Parameter 5: not used. 698 This traffic descriptor type is applicable to 699 connections following the UBR.2 conformance 700 definition ." 702 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 704 REFERENCE 705 "ATM Forum,ATM User-Network Interface, 706 Version 3.0 (UNI 3.0) Specification, 1994. 707 ATM Forum, ATM User-Network Interface, 708 Version 3.1 (UNI 3.1) Specification, 709 November 1994. 710 ATM Forum, Traffic Management Specification, 711 Version 4.0, af-tm-0056.000, June 1996." 712 ::= {atmTrafficDescriptorTypes 11} 714 atmNoClpNoScrCdvt OBJECT-IDENTITY 715 STATUS current 716 DESCRIPTION 717 "This traffic descriptor type is for no CLP 718 and no Sustained Cell Rate. The use of the 719 parameter vector for this type: 720 Parameter 1: peak cell rate in cells/second 721 for CLP=0+1 traffic 722 Parameter 2: CDVT in tenths of microseconds 723 Parameter 3: not used 724 Parameter 4: not used 725 Parameter 5: not used. 727 This traffic descriptor type is applicable to 728 CBR connections following the UNI 3.0/3.1 729 conformance definition for PCR CLP=0+1. 730 These CBR connections differ from CBR.1 731 connections in that the CLR objective 732 applies only to the CLP=0 cell flow. 734 This traffic descriptor type is also 735 applicable to connections following the UBR.1 736 conformance definition." 737 REFERENCE 738 "ATM Forum,ATM User-Network Interface, 739 Version 3.0 (UNI 3.0) Specification, 1994. 740 ATM Forum, ATM User-Network Interface, 741 Version 3.1 (UNI 3.1) Specification, 742 November 1994. 743 ATM Forum, Traffic Management Specification, 744 Version 4.0, af-tm-0056.000, June 1996." 745 ::= {atmTrafficDescriptorTypes 12} 747 atmNoClpScrCdvt OBJECT-IDENTITY 748 STATUS current 750 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 752 DESCRIPTION 753 "This traffic descriptor type is for no CLP 754 with Sustained Cell Rate. The use of the 755 parameter vector for this type: 756 Parameter 1: peak cell rate in cells/second 757 for CLP=0+1 traffic 758 Parameter 2: sustainable cell rate in cells/second 759 for CLP=0+1 traffic 760 Parameter 3: maximum burst size in cells 761 Parameter 4: CDVT in tenths of microseconds 762 Parameter 5: not used. 764 This traffic descriptor type is applicable 765 to VBR connections following the UNI 3.0/3.1 766 conformance definition for PCR CLP=0+1 and 767 SCR CLP=0+1. These VBR connections 768 differ from VBR.1 connections in that 769 the CLR objective applies only to the CLP=0 770 cell flow." 771 REFERENCE 772 "ATM Forum,ATM User-Network Interface, 773 Version 3.0 (UNI 3.0) Specification, 1994. 774 ATM Forum, ATM User-Network Interface, 775 Version 3.1 (UNI 3.1) Specification, 776 November 1994. 777 ATM Forum, Traffic Management Specification, 778 Version 4.0, af-tm-0056.000, June 1996." 779 ::= {atmTrafficDescriptorTypes 13} 781 atmClpNoTaggingScrCdvt OBJECT-IDENTITY 782 STATUS current 783 DESCRIPTION 784 "This traffic descriptor type is for CLP with 785 Sustained Cell Rate and no tagging. The use 786 of the parameter vector for this type: 787 Parameter 1: peak cell rate in cells/second 788 for CLP=0+1 traffic 789 Parameter 2: sustainable cell rate in cells/second 790 for CLP=0 traffic 791 Parameter 3: maximum burst size in cells 792 Parameter 4: CDVT in tenths of microseconds 793 Parameter 5: not used. 795 This traffic descriptor type is applicable to 796 connections following the VBR.2 conformance 798 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 800 definition." 801 REFERENCE 802 "ATM Forum,ATM User-Network Interface, 803 Version 3.0 (UNI 3.0) Specification, 1994. 804 ATM Forum, ATM User-Network Interface, 805 Version 3.1 (UNI 3.1) Specification, 806 November 1994. 807 ATM Forum, Traffic Management Specification, 808 Version 4.0, af-tm-0056.000, June 1996." 809 ::= {atmTrafficDescriptorTypes 14} 811 atmClpTaggingScrCdvt OBJECT-IDENTITY 812 STATUS current 813 DESCRIPTION 814 "This traffic descriptor type is for CLP with 815 tagging and Sustained Cell Rate. The use of 816 the parameter vector for this type: 817 Parameter 1: peak cell rate in cells/second 818 for CLP=0+1 traffic 819 Parameter 2: sustainable cell rate in cells/second 820 for CLP=0 traffic, excess tagged as 821 CLP=1 822 Parameter 3: maximum burst size in cells 823 Parameter 4: CDVT in tenths of microseconds 824 Parameter 5: not used. 826 This traffic descriptor type is applicable to 827 connections following the VBR.3 conformance 828 definition." 829 REFERENCE 830 "ATM Forum,ATM User-Network Interface, 831 Version 3.0 (UNI 3.0) Specification, 1994. 832 ATM Forum, ATM User-Network Interface, 833 Version 3.1 (UNI 3.1) Specification, 834 November 1994. 835 ATM Forum, Traffic Management Specification, 836 Version 4.0, af-tm-0056.000, June 1996." 837 ::= {atmTrafficDescriptorTypes 15} 839 END 840 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 842 4. Acknowledgments 844 This document is a product of the AToMMIB Working Group. 846 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 848 5. References 850 [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 851 "Textual Conventions for Version 2 of the Simple Network 852 Management Protocol (SNMPv2)", RFC1903, SNMP 853 Research,Inc., Cisco Systems, Inc., Dover Beach 854 Consulting, Inc., International Network Services, January 855 1996. 857 [2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 858 "Structure of Management Information for Version 2 of the 859 Simple Network Management Protocol (SNMPv2)", RFC1902, 860 SNMP Research,Inc., Cisco Systems, Inc., Dover Beach 861 Consulting, Inc., International Network Services, January 862 1996. 864 [3] Kaj Tesink, "Definitions of Managed Objects for ATM 865 Management", RFC???? (Internet-Draft ), Bellcore, April 1998. 868 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 870 6. Security Considerations 872 This memo defines textual conventions and object identities 873 for use in ATM MIB modules. Security issues for these MIB 874 modules are addressed in the memos defining those modules. 876 7. Authors' Addresses 878 Michael Noto 879 Network Equipment Technologies 880 800 Saginaw Drive RM 21.1.111 881 Redwood City, CA 94063 882 Phone +1 415 569-7134 883 EMail: mike_noto@net.com 885 Ethan Mickey Spiegel 886 Cisco Systems 887 170 W. Tasman Dr. 888 San Jose, CA 95134 889 USA 890 Phone +1 408 526 6408 891 E-mail: mspiegel@cisco.com" 893 Kaj Tesink 894 Bellcore 895 331 Newman Springs Road 896 P.O. Box 7020 897 Red Bank, NJ 07701-7020 898 Phone: (732) 758-5254 899 EMail: kaj@bellcore.com 901 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 903 8. Intellectual Property 905 The IETF takes no position regarding the validity or scope of 906 any intellectual property or other rights that might be 907 claimed to pertain to the implementation or use of the 908 technology described in this document or the extent to which 909 any license under such rights might or might not be available; 910 neither does it represent that it has made any effort to 911 identify any such rights. Information on the IETF's 912 procedures with respect to rights in standards-track and 913 standards-related documentation can be found in BCP-11. 914 Copies of claims of rights made available for publication and 915 any assurances of licenses to be made available, or the result 916 of an attempt made to obtain a general license or permission 917 for the use of such proprietary rights by implementors or 918 users of this specification can be obtained from the IETF 919 Secretariat. 921 The IETF invites any interested party to bring to its 922 attention any copyrights, patents or patent applications, or 923 other proprietary rights which may cover technology that may 924 be required to practice this standard. Please address the 925 information to the IETF Executive Director. 927 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 929 9. Full Copyright Statement 931 Copyright (C) The Internet Society (1998). All Rights 932 Reserved. 934 This document and translations of it may be copied and 935 furnished to others, and derivative works that comment on or 936 otherwise explain it or assist in its implementation may be 937 prepared, copied, published and distributed, in whole or in 938 part, without restriction of any kind, provided that the above 939 copyright notice and this paragraph are included on all such 940 copies and derivative works. However, this document itself 941 may not be modified in any way, such as by removing the 942 copyright notice or references to the Internet Society or 943 other Internet organizations, except as needed for the purpose 944 of developing Internet standards in which case the procedures 945 for copyrights defined in the Internet Standards process must 946 be followed, or as required to translate it into languages 947 other than English. 949 The limited permissions granted above are perpetual and will 950 not be revoked by the Internet Society or its successors or 951 assigns. 953 This document and the information contained herein is provided 954 on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 955 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 956 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE 957 USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 958 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 959 PARTICULAR PURPOSE." 960 draft ATM TCs and OBJECT-IDENTITIES 10/19/1998 962 Table of Contents 964 1 Status of this Memo ................................... 1 965 2 Introduction .......................................... 3 966 3 Definitions ........................................... 4 967 4 Acknowledgments ....................................... 20 968 5 References ............................................ 21 969 6 Security Considerations ............................... 22 970 7 Authors' Addresses .................................... 22 971 8 Intellectual Property ................................. 23 972 9 Full Copyright Statement .............................. 24