Debian Codegraph @

rfc2514.html

raw
1 <pre>Network Working Group M. Noto
2 Request for Comments: 2514 3Com
3 Category: Standards Track E. Spiegel
4 Cisco Systems
5 K. Tesink
6 Bellcore
7 Editors
8 February 1999
9
10
11 <span class="h1">Definitions of Textual Conventions and OBJECT-IDENTITIES</span>
12 <span class="h1">for ATM Management</span>
13
14 Status of this Memo
15
16 This document specifies an Internet standards track protocol for the
17 Internet community, and requests discussion and suggestions for
18 improvements. Please refer to the current edition of the "Internet
19 Official Protocol Standards" (STD 1) for the standardization state
20 and status of this protocol. Distribution of this memo is unlimited.
21
22 Copyright Notice
23
24 Copyright (C) The Internet Society (1999). All Rights Reserved.
25
26 Table of Contents
27
28 <a href="#section-1">1</a> Introduction .......................................... <a href="#page-2">2</a>
29 <a href="#section-2">2</a> Definitions ........................................... <a href="#page-3">3</a>
30 <a href="#section-3">3</a> Acknowledgments ....................................... <a href="#page-17">17</a>
31 <a href="#section-4">4</a> References ............................................ <a href="#page-17">17</a>
32 <a href="#section-5">5</a> Security Considerations ............................... <a href="#page-17">17</a>
33 <a href="#section-6">6</a> Authors' Addresses .................................... <a href="#page-18">18</a>
34 <a href="#section-7">7</a> Intellectual Property ................................. <a href="#page-19">19</a>
35 <a href="#section-8">8</a> Full Copyright Statement .............................. <a href="#page-20">20</a>
36
37 Abstract
38
39 This memo describes Textual Conventions and OBJECT-IDENTITIES used
40 for managing ATM-based interfaces, devices, networks and services.
41
42 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
43
44 This memo describes Textual Conventions and OBJECT-IDENTITIES used
45 for managing ATM-based interfaces, devices, networks and services.
46
47
48
49
50
51
52 <span class="grey">Noto, et. al. Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2514">RFC 2514</a> ATM TCs and OBJECT-IDENTITIES February 1999</span>
55
56
57 When designing a MIB module, it is often useful to define new types
58 similar to those defined in the SMI. In comparison to a type defined
59 in the SMI, each of these new types has a different name, a similar
60 syntax, but a more precise semantics. These newly defined types are
61 termed textual conventions, and are used for the convenience of
62 humans reading the MIB module. This is done through Textual
63 Conventions as defined in <a href="./rfc1903">RFC1903</a> [<a href="#ref-1" title="&quot;Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">1</a>]. It is the purpose of this
64 document to define the set of textual conventions available to ATM
65 MIB modules.
66
67 When designing MIB modules, it is also often useful to register
68 further properties with object identifier assignments so that they
69 can be further used by other MIB modules. This is done through the
70 OBJECT-IDENTITY macro defined in <a href="./rfc1902">RFC1902</a> [<a href="#ref-2" title="&quot;Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">2</a>]. This document defines
71 OBJECT-IDENTITIES available to ATM MIB modules.
72
73 Note that for organizational purposes OBJECT IDENTITIES previously
74 defined in <a href="./rfc1695">RFC1695</a> have been moved to this specification and no
75 longer appear in the revision of <a href="./rfc1695">RFC1695</a> [<a href="#ref-3" title="&quot;Definitions of Managed Objects for ATM Management&quot;">3</a>]. However, the original
76 OBJECT IDENTIFIERs have been preserved.
77
78 For an introduction to the concepts of ATM connections, see [<a href="#ref-3" title="&quot;Definitions of Managed Objects for ATM Management&quot;">3</a>].
79
80 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Definitions</span>
81
82 ATM-TC-MIB DEFINITIONS ::= BEGIN
83
84 IMPORTS
85 MODULE-IDENTITY, OBJECT-IDENTITY,
86 TimeTicks, mib-2
87 FROM SNMPv2-SMI
88 TEXTUAL-CONVENTION
89 FROM SNMPv2-TC;
90
91
92 atmTCMIB MODULE-IDENTITY
93 LAST-UPDATED "9810190200Z"
94 ORGANIZATION "IETF AToMMIB Working Group"
95 CONTACT-INFO
96 " Michael Noto
97 Postal: 3Com Corporation
98 5400 Bayfront Plaza, M/S 3109
99 Santa Clara, CA 95052
100 USA
101 Tel: +1 408 326 2218
102 E-mail: [email protected]
103
104 Ethan Mickey Spiegel
105
106
107
108 <span class="grey">Noto, et. al. Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2514">RFC 2514</a> ATM TCs and OBJECT-IDENTITIES February 1999</span>
111
112
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: [email protected]
119
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: [email protected]"
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 [<a href="#ref-3" title="&quot;Definitions of Managed Objects for ATM Management&quot;">3</a>])
133
134 -- The Textual Conventions defined below are organized
135 -- alphabetically
136
137
138 AtmAddr ::= TEXTUAL-CONVENTION
139 DISPLAY-HINT "1x"
140 STATUS current
141 DESCRIPTION
142 "An ATM address. The semantics are implied by
143 the length. The address types are: - no
144 address (0 octets) - E.164 (8 octets) - NSAP
145 (20 octets) In addition, when subaddresses
146 are used the AtmAddr may represent the
147 concatenation of address and subaddress. The
148 associated address types are: - E.164, E.164
149 (16 octets) - E.164, NSAP (28 octets) - NSAP,
150 NSAP (40 octets) Address lengths other than
151 defined in this definition imply address
152 types defined elsewhere. Note: The E.164
153 address is encoded in BCD format."
154 SYNTAX OCTET STRING (SIZE(0..40))
155
156
157 AtmConnCastType ::= TEXTUAL-CONVENTION
158 STATUS current
159 DESCRIPTION
160 "The type of topology of a connection (point-
161
162
163
164 <span class="grey">Noto, et. al. Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2514">RFC 2514</a> ATM TCs and OBJECT-IDENTITIES February 1999</span>
167
168
169 to-point, point-to-multipoint). In the case
170 of point-to-multipoint, the orientation of
171 this VPL or VCL in the connection.
172 On a host:
173 - p2mpRoot indicates that the host
174 is the root of the p2mp connection.
175 - p2mpLeaf indicates that the host
176 is a leaf of the p2mp connection.
177 On a switch interface:
178 - p2mpRoot indicates that cells received
179 by the switching fabric from the interface
180 are from the root of the p2mp connection.
181 - p2mpLeaf indicates that cells transmitted
182 to the interface from the switching fabric
183 are to the leaf of the p2mp connection."
184 SYNTAX INTEGER {
185 p2p(1),
186 p2mpRoot(2),
187 p2mpLeaf(3)
188 }
189
190 AtmConnKind ::= TEXTUAL-CONVENTION
191 STATUS current
192 DESCRIPTION
193 "The type of call control used for an ATM
194 connection at a particular interface. The use
195 is as follows:
196 pvc(1)
197 Virtual link of a PVC. Should not be
198 used for an PVC/SVC (i.e., Soft PVC)
199 crossconnect.
200 svcIncoming(2)
201 Virtual link established after a
202 received signaling request to setup
203 an SVC.
204 svcOutgoing(3)
205 Virtual link established after a
206 transmitted or forwarded signaling
207 request to setup an SVC.
208 spvcInitiator(4)
209 Virtual link at the PVC side of an
210 SVC/PVC crossconnect, where the
211 switch is the initiator of the Soft PVC
212 setup.
213 spvcTarget(5)
214 Virtual link at the PVC side of an
215 SVC/PVC crossconnect, where the
216 switch is the target of the Soft PVC
217
218
219
220 <span class="grey">Noto, et. al. Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2514">RFC 2514</a> ATM TCs and OBJECT-IDENTITIES February 1999</span>
223
224
225 setup.
226
227 For PVCs, a pvc virtual link is always cross-
228 connected to a pvc virtual link.
229
230 For SVCs, an svcIncoming virtual link is always cross-
231 connected to an svcOutgoing virtual link.
232
233 For Soft PVCs, an spvcInitiator is either cross-connected to
234 an svcOutgoing or an spvcTarget, and an spvcTarget is either
235 cross-connected to an svcIncoming or an spvcInitiator."
236 SYNTAX INTEGER {
237 pvc(1),
238 svcIncoming(2),
239 svcOutgoing(3),
240 spvcInitiator(4),
241 spvcTarget(5)
242 }
243
244 AtmIlmiNetworkPrefix ::= TEXTUAL-CONVENTION
245 STATUS current
246 DESCRIPTION
247 "A network prefix used for ILMI address
248 registration. In the case of ATM endsystem
249 addresses (AESAs), the network prefix is the first
250 13 octets of the address which includes the AFI,
251 IDI, and HO-DSP fields. In the case of native
252 E.164 addresses, the network prefix is the entire
253 E.164 address encoded in 8 octets, as if it were
254 an E.164 IDP in an ATM endsystem address
255 structure."
256 REFERENCE
257 "ATM Forum, Integrated Local Management Interface
258 (ILMI) Specification, Version 4.0,
259 af-ilmi-0065.000, September 1996, <a href="#section-9">Section 9</a>
260 ATM Forum, ATM User-Network Interface Signalling
261 Specification, Version 4.0 (UNI 4.0),
262 af-sig-0061.000, June 1996, <a href="#section-3">Section 3</a>"
263 SYNTAX OCTET STRING (SIZE(8|13))
264
265 AtmInterfaceType ::= TEXTUAL-CONVENTION
266 STATUS current
267 DESCRIPTION
268 "The connection setup procedures used for the
269 identified interface.
270
271 Other: Connection setup procedures other than
272 those listed below.
273
274
275
276 <span class="grey">Noto, et. al. Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2514">RFC 2514</a> ATM TCs and OBJECT-IDENTITIES February 1999</span>
279
280
281 Auto-configuration:
282 Indicates that the connection setup
283 procedures are to be determined dynamically,
284 or that determination has not yet been
285 completed. One such mechanism is via ATM
286 Forum ILMI auto-configuration procedures.
287
288 ITU-T DSS2:
289 - ITU-T Recommendation Q.2931, Broadband
290 Integrated Service Digital Network (B-ISDN)
291 Digital Subscriber Signalling System No.2
292 (DSS2) User-Network Interface (UNI) Layer 3
293 Specification for Basic Call/Connection
294 Control (September 1994)
295 - ITU-T Draft Recommendation Q.2961,
296 B-ISDN DSS 2 Support of Additional Traffic
297 Parameters (May 1995)
298
299 - ITU-T Draft Recommendation Q.2971,
300 B-ISDN DSS 2 User Network Interface Layer 3
301 Specification for Point-to-multipoint
302 Call/connection Control (May 1995)
303
304 ATM Forum UNI 3.0:
305 ATM Forum, ATM User-Network Interface,
306 Version 3.0 (UNI 3.0) Specification,
307 (1994).
308
309 ATM Forum UNI 3.1:
310 ATM Forum, ATM User-Network Interface,
311 Version 3.1 (UNI 3.1) Specification,
312 (November 1994).
313
314 ATM Forum UNI Signalling 4.0:
315 ATM Forum, ATM User-Network Interface (UNI)
316 Signalling Specification Version 4.0,
317 af-sig-0061.000 (June 1996).
318
319 ATM Forum IISP (based on UNI 3.0 or UNI 3.1) :
320 Interim Inter-switch Signaling Protocol
321 (IISP) Specification, Version 1.0,
322 af-pnni-0026.000, (December 1994).
323
324 ATM Forum PNNI 1.0 :
325 ATM Forum, Private Network-Network Interface
326 Specification, Version 1.0, af-pnni-0055.000,
327 (March 1996).
328
329
330
331
332 <span class="grey">Noto, et. al. Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc2514">RFC 2514</a> ATM TCs and OBJECT-IDENTITIES February 1999</span>
335
336
337 ATM Forum B-ICI:
338 ATM Forum, B-ICI Specification, Version 2.0,
339 af-bici-0013.002, (November 1995).
340
341 ATM Forum UNI PVC Only:
342 An ATM Forum compliant UNI with the
343 signalling disabled.
344 ATM Forum NNI PVC Only:
345 An ATM Forum compliant NNI with the
346 signalling disabled."
347 SYNTAX INTEGER {
348 other(1),
349 autoConfig(2),
350 ituDss2(3),
351 atmfUni3Dot0(4),
352 atmfUni3Dot1(5),
353 atmfUni4Dot0(6),
354 atmfIispUni3Dot0(7),
355 atmfIispUni3Dot1(8),
356 atmfIispUni4Dot0(9),
357 atmfPnni1Dot0(10),
358 atmfBici2Dot0(11),
359 atmfUniPvcOnly(12),
360 atmfNniPvcOnly(13) }
361
362 AtmServiceCategory ::= TEXTUAL-CONVENTION
363 STATUS current
364 DESCRIPTION
365 "The service category for a connection."
366 REFERENCE
367 "ATM Forum Traffic Management Specification,
368 Version 4.0, af-tm-0056.000, June 1996."
369 SYNTAX INTEGER {
370 other(1), -- none of the following
371 cbr(2), -- constant bit rate
372 rtVbr(3), -- real-time variable bit rate
373 nrtVbr(4), -- non real-time variable bit rate
374 abr(5), -- available bit rate
375 ubr(6) -- unspecified bit rate
376 }
377
378 AtmSigDescrParamIndex ::= TEXTUAL-CONVENTION
379 STATUS current
380 DESCRIPTION
381 "The value of this object identifies a row in the
382 atmSigDescrParamTable. The value 0 signifies that
383 none of the signalling parameters defined in the
384 atmSigDescrParamTable are applicable."
385
386
387
388 <span class="grey">Noto, et. al. Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc2514">RFC 2514</a> ATM TCs and OBJECT-IDENTITIES February 1999</span>
391
392
393 SYNTAX INTEGER (0..2147483647)
394
395 AtmTrafficDescrParamIndex ::= TEXTUAL-CONVENTION
396 STATUS current
397 DESCRIPTION
398 "The value of this object identifies a row in the
399 atmTrafficDescrParamTable. The value 0 signifies
400 that no row has been identified."
401 SYNTAX INTEGER (0..2147483647)
402
403 AtmVcIdentifier ::= TEXTUAL-CONVENTION
404 STATUS current
405 DESCRIPTION
406 "The VCI value for a VCL. The maximum VCI value
407 cannot exceed the value allowable by
408 atmInterfaceMaxVciBits defined in ATM-MIB."
409 SYNTAX INTEGER (0..65535)
410
411 AtmVpIdentifier ::= TEXTUAL-CONVENTION
412 STATUS current
413 DESCRIPTION
414 "The VPI value for a VPL or VCL. The value VPI=0
415 is only allowed for a VCL. For ATM UNIs supporting
416 VPCs the VPI value ranges from 0 to 255. The VPI
417 value 0 is supported for ATM UNIs conforming to
418 the ATM Forum UNI 4.0 Annex 8 (Virtual UNIs)
419 specification. For ATM UNIs supporting VCCs the
420 VPI value ranges from 0 to 255. For ATM NNIs the
421 VPI value ranges from 0 to 4095. The maximum VPI
422 value cannot exceed the value allowable by
423 atmInterfaceMaxVpiBits defined in ATM-MIB."
424 SYNTAX INTEGER (0..4095)
425
426 AtmVorXAdminStatus ::= TEXTUAL-CONVENTION
427 STATUS current
428 DESCRIPTION
429 "The value determines the desired administrative
430 status of a virtual link or cross-connect. The up
431 and down states indicate that the traffic flow is
432 enabled or disabled respectively on the virtual
433 link or cross-connect."
434 SYNTAX INTEGER {
435 up(1),
436 down(2)
437 }
438
439 AtmVorXLastChange ::= TEXTUAL-CONVENTION
440 STATUS current
441
442
443
444 <span class="grey">Noto, et. al. Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc2514">RFC 2514</a> ATM TCs and OBJECT-IDENTITIES February 1999</span>
447
448
449 DESCRIPTION
450 "The value of MIB II's sysUpTime at the time a
451 virtual link or cross-connect entered its current
452 operational state. If the current state was
453 entered prior to the last re-initialization of the
454 agent then this object contains a zero value."
455 SYNTAX TimeTicks
456
457 AtmVorXOperStatus ::= TEXTUAL-CONVENTION
458 STATUS current
459 DESCRIPTION
460 "The value determines the operational status of a
461 virtual link or cross-connect. The up and down
462 states indicate that the traffic flow is enabled
463 or disabled respectively on the virtual link or
464 cross-connect. The unknown state indicates that
465 the state of it cannot be determined. The state
466 will be down or unknown if the supporting ATM
467 interface(s) is down or unknown respectively."
468 SYNTAX INTEGER {
469 up(1),
470 down(2),
471 unknown(3)
472 }
473
474
475
476
477 -- OBJECT-IDENTITIES:
478
479 -- The following atmTrafficDescriptorTypes has been moved
480 -- from <a href="./rfc1695">RFC1695</a> and no longer appear in the revision of
481 -- <a href="./rfc1695">RFC1695</a>[<a href="#ref-3" title="&quot;Definitions of Managed Objects for ATM Management&quot;">3</a>].
482
483 atmTrafficDescriptorTypes OBJECT IDENTIFIER ::= {mib-2 37 1 1}
484 -- atmMIBObjects
485 -- See [<a href="#ref-3" title="&quot;Definitions of Managed Objects for ATM Management&quot;">3</a>].
486
487 -- All other and new OBJECT IDENTITIES
488 -- are defined under the following subtree:
489
490 atmObjectIdentities OBJECT IDENTIFIER ::= {atmTCMIB 1}
491
492 -- The following values are defined for use as
493 -- possible values of the ATM traffic descriptor type.
494
495 atmNoTrafficDescriptor OBJECT-IDENTITY
496 STATUS deprecated
497
498
499
500 <span class="grey">Noto, et. al. Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc2514">RFC 2514</a> ATM TCs and OBJECT-IDENTITIES February 1999</span>
503
504
505 DESCRIPTION
506 "This identifies the no ATM traffic
507 descriptor type. Parameters 1, 2, 3, 4,
508 and 5 are not used. This traffic descriptor
509 type can be used for best effort traffic."
510 ::= {atmTrafficDescriptorTypes 1}
511
512 atmNoClpNoScr OBJECT-IDENTITY
513 STATUS current
514 DESCRIPTION
515 "This traffic descriptor type is for no CLP
516 and no Sustained Cell Rate. The use of the
517 parameter vector for this type:
518 Parameter 1: peak cell rate in cells/second
519 for CLP=0+1 traffic
520 Parameter 2: not used
521 Parameter 3: not used
522 Parameter 4: not used
523 Parameter 5: not used."
524 REFERENCE
525 "ATM Forum,ATM User-Network Interface,
526 Version 3.0 (UNI 3.0) Specification, 1994.
527 ATM Forum, ATM User-Network Interface,
528 Version 3.1 (UNI 3.1) Specification,
529 November 1994."
530 ::= {atmTrafficDescriptorTypes 2}
531
532 atmClpNoTaggingNoScr OBJECT-IDENTITY
533 STATUS deprecated
534 DESCRIPTION
535 "This traffic descriptor is for CLP without
536 tagging and no Sustained Cell Rate. The use
537 of the parameter vector for this type:
538 Parameter 1: peak cell rate in cells/second
539 for CLP=0+1 traffic
540 Parameter 2: peak cell rate in cells/second
541 for CLP=0 traffic
542 Parameter 3: not used
543 Parameter 4: not used
544 Parameter 5: not used."
545 ::= {atmTrafficDescriptorTypes 3}
546
547 atmClpTaggingNoScr OBJECT-IDENTITY
548 STATUS deprecated
549 DESCRIPTION
550 "This traffic descriptor is for CLP with
551 tagging and no Sustained Cell Rate. The use
552 of the parameter vector for this type:
553
554
555
556 <span class="grey">Noto, et. al. Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc2514">RFC 2514</a> ATM TCs and OBJECT-IDENTITIES February 1999</span>
559
560
561 Parameter 1: peak cell rate in cells/second
562 for CLP=0+1 traffic
563 Parameter 2: peak cell rate in cells/second
564 for CLP=0 traffic, excess
565 tagged as CLP=1
566 Parameter 3: not used
567 Parameter 4: not used
568 Parameter 5: not used."
569 ::= {atmTrafficDescriptorTypes 4}
570
571 atmNoClpScr OBJECT-IDENTITY
572 STATUS current
573 DESCRIPTION
574 "This traffic descriptor type is for no CLP
575 with Sustained Cell Rate. The use of the
576 parameter vector for this type:
577 Parameter 1: peak cell rate in cells/second
578 for CLP=0+1 traffic
579 Parameter 2: sustainable cell rate in cells/second
580 for CLP=0+1 traffic
581 Parameter 3: maximum burst size in cells
582 Parameter 4: not used
583 Parameter 5: not used."
584 REFERENCE
585 "ATM Forum,ATM User-Network Interface,
586 Version 3.0 (UNI 3.0) Specification, 1994.
587 ATM Forum, ATM User-Network Interface,
588 Version 3.1 (UNI 3.1) Specification,
589 November 1994."
590 ::= {atmTrafficDescriptorTypes 5}
591
592 atmClpNoTaggingScr OBJECT-IDENTITY
593 STATUS current
594 DESCRIPTION
595 "This traffic descriptor type is for CLP with
596 Sustained Cell Rate and no tagging. The use
597 of the parameter vector for this type:
598 Parameter 1: peak cell rate in cells/second
599 for CLP=0+1 traffic
600 Parameter 2: sustainable cell rate in cells/second
601 for CLP=0 traffic
602 Parameter 3: maximum burst size in cells
603 Parameter 4: not used
604 Parameter 5: not used."
605 REFERENCE
606 "ATM Forum,ATM User-Network Interface,
607 Version 3.0 (UNI 3.0) Specification, 1994.
608 ATM Forum, ATM User-Network Interface,
609
610
611
612 <span class="grey">Noto, et. al. Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc2514">RFC 2514</a> ATM TCs and OBJECT-IDENTITIES February 1999</span>
615
616
617 Version 3.1 (UNI 3.1) Specification,
618 November 1994."
619 ::= {atmTrafficDescriptorTypes 6}
620
621 atmClpTaggingScr OBJECT-IDENTITY
622 STATUS current
623 DESCRIPTION
624 "This traffic descriptor type is for CLP with
625 tagging and Sustained Cell Rate. The use of
626 the parameter vector for this type:
627 Parameter 1: peak cell rate in cells/second
628 for CLP=0+1 traffic
629 Parameter 2: sustainable cell rate in cells/second
630 for CLP=0 traffic, excess tagged as
631 CLP=1
632 Parameter 3: maximum burst size in cells
633 Parameter 4: not used
634 Parameter 5: not used."
635 REFERENCE
636 "ATM Forum,ATM User-Network Interface,
637 Version 3.0 (UNI 3.0) Specification, 1994.
638 ATM Forum, ATM User-Network Interface,
639 Version 3.1 (UNI 3.1) Specification,
640 November 1994."
641 ::= {atmTrafficDescriptorTypes 7}
642
643 atmClpNoTaggingMcr OBJECT-IDENTITY
644 STATUS current
645 DESCRIPTION
646 "This traffic descriptor type is for CLP with
647 Minimum Cell Rate and no tagging. The use of
648 the parameter vector for this type:
649 Parameter 1: peak cell rate in cells/second
650 for CLP=0+1 traffic
651 Parameter 2: CDVT in tenths of microseconds
652 Parameter 3: minimum cell rate in cells/second
653 Parameter 4: unused
654 Parameter 5: unused."
655 REFERENCE
656 "ATM Forum,ATM User-Network Interface,
657 Version 3.0 (UNI 3.0) Specification, 1994.
658 ATM Forum, ATM User-Network Interface,
659 Version 3.1 (UNI 3.1) Specification,
660 November 1994."
661 ::= {atmTrafficDescriptorTypes 8}
662
663 atmClpTransparentNoScr OBJECT-IDENTITY
664 STATUS current
665
666
667
668 <span class="grey">Noto, et. al. Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc2514">RFC 2514</a> ATM TCs and OBJECT-IDENTITIES February 1999</span>
671
672
673 DESCRIPTION
674 "This traffic descriptor type is for the CLP-
675 transparent model and no Sustained Cell Rate.
676 The use of the parameter vector for this type:
677 Parameter 1: peak cell rate in cells/second
678 for CLP=0+1 traffic
679 Parameter 2: CDVT in tenths of microseconds
680 Parameter 3: not used
681 Parameter 4: not used
682 Parameter 5: not used.
683
684 This traffic descriptor type is applicable to
685 connections following the CBR.1 conformance
686 definition.
687
688 Connections specifying this traffic descriptor
689 type will be rejected at UNI 3.0 or UNI 3.1
690 interfaces. For a similar traffic descriptor
691 type that can be accepted at UNI 3.0 and
692 UNI 3.1 interfaces, see atmNoClpNoScr."
693 REFERENCE
694 "ATM Forum,ATM User-Network Interface,
695 Version 3.0 (UNI 3.0) Specification, 1994.
696 ATM Forum, ATM User-Network Interface,
697 Version 3.1 (UNI 3.1) Specification,
698 November 1994.
699 ATM Forum, Traffic Management Specification,
700 Version 4.0, af-tm-0056.000, June 1996."
701 ::= {atmTrafficDescriptorTypes 9}
702
703 atmClpTransparentScr OBJECT-IDENTITY
704 STATUS current
705 DESCRIPTION
706 "This traffic descriptor type is for the CLP-
707 transparent model with Sustained Cell Rate.
708 The use of the parameter vector for this type:
709 Parameter 1: peak cell rate in cells/second
710 for CLP=0+1 traffic
711 Parameter 2: sustainable cell rate in cells/second
712 for CLP=0+1 traffic
713 Parameter 3: maximum burst size in cells
714 Parameter 4: CDVT in tenths of microseconds
715 Parameter 5: not used.
716
717 This traffic descriptor type is applicable to
718 connections following the VBR.1 conformance
719 definition.
720
721
722
723
724 <span class="grey">Noto, et. al. Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc2514">RFC 2514</a> ATM TCs and OBJECT-IDENTITIES February 1999</span>
727
728
729 Connections specifying this traffic descriptor
730 type will be rejected at UNI 3.0 or UNI 3.1
731 interfaces. For a similar traffic descriptor
732 type that can be accepted at UNI 3.0 and
733 UNI 3.1 interfaces, see atmNoClpScr."
734 REFERENCE
735 "ATM Forum,ATM User-Network Interface,
736 Version 3.0 (UNI 3.0) Specification, 1994.
737 ATM Forum, ATM User-Network Interface,
738 Version 3.1 (UNI 3.1) Specification,
739 November 1994.
740 ATM Forum, Traffic Management Specification,
741 Version 4.0, af-tm-0056.000, June 1996."
742 ::= {atmTrafficDescriptorTypes 10}
743
744 atmNoClpTaggingNoScr OBJECT-IDENTITY
745 STATUS current
746 DESCRIPTION
747 "This traffic descriptor type is for no CLP
748 with tagging and no Sustained Cell Rate. The
749 use of the parameter vector for this type:
750 Parameter 1: peak cell rate in cells/second
751 for CLP=0+1 traffic
752 Parameter 2: CDVT in tenths of microseconds
753 Parameter 3: not used
754 Parameter 4: not used
755 Parameter 5: not used.
756
757 This traffic descriptor type is applicable to
758 connections following the UBR.2 conformance
759 definition ."
760 REFERENCE
761 "ATM Forum,ATM User-Network Interface,
762 Version 3.0 (UNI 3.0) Specification, 1994.
763 ATM Forum, ATM User-Network Interface,
764 Version 3.1 (UNI 3.1) Specification,
765 November 1994.
766 ATM Forum, Traffic Management Specification,
767 Version 4.0, af-tm-0056.000, June 1996."
768 ::= {atmTrafficDescriptorTypes 11}
769
770 atmNoClpNoScrCdvt OBJECT-IDENTITY
771 STATUS current
772 DESCRIPTION
773 "This traffic descriptor type is for no CLP
774 and no Sustained Cell Rate. The use of the
775 parameter vector for this type:
776 Parameter 1: peak cell rate in cells/second
777
778
779
780 <span class="grey">Noto, et. al. Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc2514">RFC 2514</a> ATM TCs and OBJECT-IDENTITIES February 1999</span>
783
784
785 for CLP=0+1 traffic
786 Parameter 2: CDVT in tenths of microseconds
787 Parameter 3: not used
788 Parameter 4: not used
789 Parameter 5: not used.
790
791 This traffic descriptor type is applicable to
792 CBR connections following the UNI 3.0/3.1
793 conformance definition for PCR CLP=0+1.
794 These CBR connections differ from CBR.1
795 connections in that the CLR objective
796 applies only to the CLP=0 cell flow.
797
798 This traffic descriptor type is also
799 applicable to connections following the UBR.1
800 conformance 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 12}
810
811 atmNoClpScrCdvt OBJECT-IDENTITY
812 STATUS current
813 DESCRIPTION
814 "This traffic descriptor type is for no CLP
815 with Sustained Cell Rate. The use of the
816 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+1 traffic
821 Parameter 3: maximum burst size in cells
822 Parameter 4: CDVT in tenths of microseconds
823 Parameter 5: not used.
824
825 This traffic descriptor type is applicable
826 to VBR connections following the UNI 3.0/3.1
827 conformance definition for PCR CLP=0+1 and
828 SCR CLP=0+1. These VBR connections
829 differ from VBR.1 connections in that
830 the CLR objective applies only to the CLP=0
831 cell flow."
832 REFERENCE
833
834
835
836 <span class="grey">Noto, et. al. Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc2514">RFC 2514</a> ATM TCs and OBJECT-IDENTITIES February 1999</span>
839
840
841 "ATM Forum,ATM User-Network Interface,
842 Version 3.0 (UNI 3.0) Specification, 1994.
843 ATM Forum, ATM User-Network Interface,
844 Version 3.1 (UNI 3.1) Specification,
845 November 1994.
846 ATM Forum, Traffic Management Specification,
847 Version 4.0, af-tm-0056.000, June 1996."
848 ::= {atmTrafficDescriptorTypes 13}
849
850 atmClpNoTaggingScrCdvt OBJECT-IDENTITY
851 STATUS current
852 DESCRIPTION
853 "This traffic descriptor type is for CLP with
854 Sustained Cell Rate and no tagging. The use
855 of the parameter vector for this type:
856 Parameter 1: peak cell rate in cells/second
857 for CLP=0+1 traffic
858 Parameter 2: sustainable cell rate in cells/second
859 for CLP=0 traffic
860 Parameter 3: maximum burst size in cells
861 Parameter 4: CDVT in tenths of microseconds
862 Parameter 5: not used.
863
864 This traffic descriptor type is applicable to
865 connections following the VBR.2 conformance
866 definition."
867 REFERENCE
868 "ATM Forum,ATM User-Network Interface,
869 Version 3.0 (UNI 3.0) Specification, 1994.
870 ATM Forum, ATM User-Network Interface,
871 Version 3.1 (UNI 3.1) Specification,
872 November 1994.
873 ATM Forum, Traffic Management Specification,
874 Version 4.0, af-tm-0056.000, June 1996."
875 ::= {atmTrafficDescriptorTypes 14}
876
877 atmClpTaggingScrCdvt OBJECT-IDENTITY
878 STATUS current
879 DESCRIPTION
880 "This traffic descriptor type is for CLP with
881 tagging and Sustained Cell Rate. The use of
882 the parameter vector for this type:
883 Parameter 1: peak cell rate in cells/second
884 for CLP=0+1 traffic
885 Parameter 2: sustainable cell rate in cells/second
886 for CLP=0 traffic, excess tagged as
887 CLP=1
888 Parameter 3: maximum burst size in cells
889
890
891
892 <span class="grey">Noto, et. al. Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc2514">RFC 2514</a> ATM TCs and OBJECT-IDENTITIES February 1999</span>
895
896
897 Parameter 4: CDVT in tenths of microseconds
898 Parameter 5: not used.
899
900 This traffic descriptor type is applicable to
901 connections following the VBR.3 conformance
902 definition."
903 REFERENCE
904 "ATM Forum,ATM User-Network Interface,
905 Version 3.0 (UNI 3.0) Specification, 1994.
906 ATM Forum, ATM User-Network Interface,
907 Version 3.1 (UNI 3.1) Specification,
908 November 1994.
909 ATM Forum, Traffic Management Specification,
910 Version 4.0, af-tm-0056.000, June 1996."
911 ::= {atmTrafficDescriptorTypes 15}
912
913 END
914
915 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Acknowledgments</span>
916
917 This document is a product of the AToMMIB Working Group.
918
919 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. References</span>
920
921 [<a id="ref-1">1</a>] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
922 "Textual Conventions for Version 2 of the Simple Network
923 Management Protocol (SNMPv2)", <a href="./rfc1903">RFC 1903</a>, January 1996.
924
925 [<a id="ref-2">2</a>] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Structure
926 of Management Information for Version 2 of the Simple Network
927 Management Protocol (SNMPv2)", <a href="./rfc1902">RFC 1902</a>, January 1996.
928
929 [<a id="ref-3">3</a>] Tesink, K., Editor, "Definitions of Managed Objects for ATM
930 Management", <a href="./rfc2515">RFC 2515</a>, February 1999.
931
932 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
933
934 This memo defines textual conventions and object identities for use
935 in ATM MIB modules. Security issues for these MIB modules are
936 addressed in the memos defining those modules.
937
938
939
940
941
942
943
944
945
946
947
948 <span class="grey">Noto, et. al. Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc2514">RFC 2514</a> ATM TCs and OBJECT-IDENTITIES February 1999</span>
951
952
953 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Authors' Addresses</span>
954
955 Michael Noto
956 3Com Corporation
957 5400 Bayfront Plaza, M/S 3109
958 Santa Clara, CA 95052
959
960 Phone +1 408 326 2218
961 Email: [email protected]
962
963
964
965 Ethan Mickey Spiegel
966 Cisco Systems
967 170 W. Tasman Dr.
968 San Jose, CA 95134
969 USA
970
971 Phone +1 408 526 6408
972 EMail: [email protected]
973
974
975 Kaj Tesink
976 Bellcore
977 331 Newman Springs Road
978 P.O. Box 7020
979 Red Bank, NJ 07701-7020
980
981 Phone: (732) 758-5254
982 EMail: [email protected]
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004 <span class="grey">Noto, et. al. Standards Track [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc2514">RFC 2514</a> ATM TCs and OBJECT-IDENTITIES February 1999</span>
1007
1008
1009 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Intellectual Property</span>
1010
1011 The IETF takes no position regarding the validity or scope of any
1012 intellectual property or other rights that might be claimed to
1013 pertain to the implementation or use of the technology described in
1014 this document or the extent to which any license under such rights
1015 might or might not be available; neither does it represent that it
1016 has made any effort to identify any such rights. Information on the
1017 IETF's procedures with respect to rights in standards-track and
1018 standards-related documentation can be found in <a href="https://www.rfc-editor.org/bcp/bcp11">BCP-11</a>. Copies of
1019 claims of rights made available for publication and any assurances of
1020 licenses to be made available, or the result of an attempt made to
1021 obtain a general license or permission for the use of such
1022 proprietary rights by implementors or users of this specification can
1023 be obtained from the IETF Secretariat.
1024
1025 The IETF invites any interested party to bring to its attention any
1026 copyrights, patents or patent applications, or other proprietary
1027 rights which may cover technology that may be required to practice
1028 this standard. Please address the information to the IETF Executive
1029 Director.
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060 <span class="grey">Noto, et. al. Standards Track [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc2514">RFC 2514</a> ATM TCs and OBJECT-IDENTITIES February 1999</span>
1063
1064
1065 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Full Copyright Statement</span>
1066
1067 Copyright (C) The Internet Society (1999). All Rights Reserved.
1068
1069 This document and translations of it may be copied and furnished to
1070 others, and derivative works that comment on or otherwise explain it
1071 or assist in its implementation may be prepared, copied, published
1072 and distributed, in whole or in part, without restriction of any
1073 kind, provided that the above copyright notice and this paragraph are
1074 included on all such copies and derivative works. However, this
1075 document itself may not be modified in any way, such as by removing
1076 the copyright notice or references to the Internet Society or other
1077 Internet organizations, except as needed for the purpose of
1078 developing Internet standards in which case the procedures for
1079 copyrights defined in the Internet Standards process must be
1080 followed, or as required to translate it into languages other than
1081 English.
1082
1083 The limited permissions granted above are perpetual and will not be
1084 revoked by the Internet Society or its successors or assigns.
1085
1086 This document and the information contained herein is provided on an
1087 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
1088 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
1089 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
1090 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
1091 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116 Noto, et. al. Standards Track [Page 20]
1117 </pre>