Debian Codegraph @

rfc3811.html

raw
1 <pre>Network Working Group T. Nadeau, Ed.
2 Request for Comments: 3811 Cisco Systems, Inc.
3 Category: Standards Track J. Cucchiara, Ed.
4 Marconi Communications, Inc.
5 June 2004
6
7
8 <span class="h1">Definitions of Textual Conventions (TCs) for</span>
9 <span class="h1">Multiprotocol Label Switching (MPLS) Management</span>
10
11 Status of this Memo
12
13 This document specifies an Internet standards track protocol for the
14 Internet community, and requests discussion and suggestions for
15 improvements. Please refer to the current edition of the "Internet
16 Official Protocol Standards" (STD 1) for the standardization state
17 and status of this protocol. Distribution of this memo is unlimited.
18
19 Copyright Notice
20
21 Copyright (C) The Internet Society (2004).
22
23 Abstract
24
25 This memo defines a Management Information Base (MIB) module which
26 contains Textual Conventions to represent commonly used Multiprotocol
27 Label Switching (MPLS) management information. The intent is that
28 these TEXTUAL CONVENTIONS (TCs) will be imported and used in MPLS
29 related MIB modules that would otherwise define their own
30 representations.
31
32 Table of Contents
33
34 <a href="#section-1">1</a>. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
35 <a href="#section-2">2</a>. The Internet-Standard Management Framework. . . . . . . . . . <a href="#page-2">2</a>
36 <a href="#section-3">3</a>. MPLS Textual Conventions MIB Definitions. . . . . . . . . . . <a href="#page-2">2</a>
37 <a href="#section-4">4</a>. References. . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
38 <a href="#section-4.1">4.1</a>. Normative References. . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
39 <a href="#section-4.2">4.2</a>. Informative References. . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
40 <a href="#section-5">5</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
41 <a href="#section-6">6</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
42 <a href="#section-7">7</a>. Contributors. . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
43 <a href="#section-8">8</a> Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
44 <a href="#section-9">9</a>. Authors' Addresses. . . . . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
45 <a href="#section-10">10</a>. Full Copyright Statement. . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a>
46
47
48
49
50
51
52 <span class="grey">Nadeau &amp; Cucchiara 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="./rfc3811">RFC 3811</a> MPLS TC MIB June 2004</span>
55
56
57 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
58
59 This document defines a MIB module which contains Textual Conventions
60 for Multiprotocol Label Switching (MPLS) networks. These Textual
61 Conventions should be imported by MIB modules which manage MPLS
62 networks.
63
64 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
65 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
66 document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
67
68 For an introduction to the concepts of MPLS, see [<a href="./rfc3031" title="&quot;Multiprotocol Label Switching Architecture&quot;">RFC3031</a>].
69
70 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The Internet-Standard Management Framework</span>
71
72 For a detailed overview of the documents that describe the current
73 Internet-Standard Management Framework, please refer to <a href="./rfc3410#section-7">section&nbsp;7 of
74 RFC 3410</a> [<a href="./rfc3410" title="&quot;Introduction and Applicability Statements for Internet- Standard Management Framework&quot;">RFC3410</a>].
75
76 Managed objects are accessed via a virtual information store, termed
77 the Management Information Base or MIB. MIB objects are generally
78 accessed through the Simple Network Management Protocol (SNMP).
79 Objects in the MIB are defined using the mechanisms defined in the
80 Structure of Management Information (SMI). This memo specifies a MIB
81 module that is compliant to the SMIv2, which is described in STD 58,
82 <a href="./rfc2578">RFC 2578</a> [<a href="./rfc2578" title="&quot;Structure of Management Information Version 2 (SMIv2)&quot;">RFC2578</a>], STD 58, <a href="./rfc2579">RFC 2579</a> [<a href="./rfc2579" title="&quot;Textual Conventions for SMIv2&quot;">RFC2579</a>] and STD 58, <a href="./rfc2580">RFC 2580</a>
83 [<a href="./rfc2580" title="&quot;Conformance Statements for SMIv2&quot;">RFC2580</a>].
84
85 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. MPLS Textual Conventions MIB Definitions</span>
86
87 MPLS-TC-STD-MIB DEFINITIONS ::= BEGIN
88
89 IMPORTS
90
91 MODULE-IDENTITY,
92 Unsigned32, Integer32,
93 transmission FROM SNMPv2-SMI -- [<a href="./rfc2578" title="&quot;Structure of Management Information Version 2 (SMIv2)&quot;">RFC2578</a>]
94
95 TEXTUAL-CONVENTION
96 FROM SNMPv2-TC; -- [<a href="./rfc2579" title="&quot;Textual Conventions for SMIv2&quot;">RFC2579</a>]
97
98 mplsTCStdMIB MODULE-IDENTITY
99 LAST-UPDATED "200406030000Z" -- June 3, 2004
100 ORGANIZATION
101 "IETF Multiprotocol Label Switching (MPLS) Working
102 Group."
103 CONTACT-INFO
104 " Thomas D. Nadeau
105
106
107
108 <span class="grey">Nadeau &amp; Cucchiara 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="./rfc3811">RFC 3811</a> MPLS TC MIB June 2004</span>
111
112
113 Cisco Systems, Inc.
114 [email protected]
115
116 Joan Cucchiara
117 Marconi Communications, Inc.
118 [email protected]
119
120 Cheenu Srinivasan
121 Bloomberg L.P.
122 [email protected]
123
124 Arun Viswanathan
125 Force10 Networks, Inc.
126 [email protected]
127
128 Hans Sjostrand
129 ipUnplugged
130 [email protected]
131
132 Kireeti Kompella
133 Juniper Networks
134 [email protected]
135
136 Email comments to the MPLS WG Mailing List at
137 [email protected]."
138 DESCRIPTION
139 "Copyright (C) The Internet Society (2004). The
140 initial version of this MIB module was published
141 in <a href="./rfc3811">RFC 3811</a>. For full legal notices see the RFC
142 itself or see:
143 <a href="http://www.ietf.org/copyrights/ianamib.html">http://www.ietf.org/copyrights/ianamib.html</a>
144
145 This MIB module defines TEXTUAL-CONVENTIONs
146 for concepts used in Multiprotocol Label
147 Switching (MPLS) networks."
148
149 REVISION "200406030000Z" -- June 3, 2004
150 DESCRIPTION
151 "Initial version published as part of <a href="./rfc3811">RFC 3811</a>."
152
153 ::= { mplsStdMIB 1 }
154
155 mplsStdMIB OBJECT IDENTIFIER
156
157 ::= { transmission 166 }
158
159 MplsAtmVcIdentifier ::= TEXTUAL-CONVENTION
160 DISPLAY-HINT "d"
161
162
163
164 <span class="grey">Nadeau &amp; Cucchiara 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="./rfc3811">RFC 3811</a> MPLS TC MIB June 2004</span>
167
168
169 STATUS current
170 DESCRIPTION
171 "A Label Switching Router (LSR) that
172 creates LDP sessions on ATM interfaces
173 uses the VCI or VPI/VCI field to hold the
174 LDP Label.
175
176 VCI values MUST NOT be in the 0-31 range.
177 The values 0 to 31 are reserved for other uses
178 by the ITU and ATM Forum. The value
179 of 32 can only be used for the Control VC,
180 although values greater than 32 could be
181 configured for the Control VC.
182
183 If a value from 0 to 31 is used for a VCI
184 the management entity controlling the LDP
185 subsystem should reject this with an
186 inconsistentValue error. Also, if
187 the value of 32 is used for a VC which is
188 NOT the Control VC, this should
189 result in an inconsistentValue error."
190 REFERENCE
191 "MPLS using LDP and ATM VC Switching, <a href="./rfc3035">RFC3035</a>."
192 SYNTAX Integer32 (32..65535)
193
194 MplsBitRate ::= TEXTUAL-CONVENTION
195 DISPLAY-HINT "d"
196 STATUS current
197 DESCRIPTION
198 "If the value of this object is greater than zero,
199 then this represents the bandwidth of this MPLS
200 interface (or Label Switched Path) in units of
201 '1,000 bits per second'.
202
203 The value, when greater than zero, represents the
204 bandwidth of this MPLS interface (rounded to the
205 nearest 1,000) in units of 1,000 bits per second.
206 If the bandwidth of the MPLS interface is between
207 ((n * 1000) - 500) and ((n * 1000) + 499), the value
208 of this object is n, such that n &gt; 0.
209
210 If the value of this object is 0 (zero), this
211 means that the traffic over this MPLS interface is
212 considered to be best effort."
213 SYNTAX Unsigned32 (0|1..4294967295)
214
215 MplsBurstSize ::= TEXTUAL-CONVENTION
216 DISPLAY-HINT "d"
217
218
219
220 <span class="grey">Nadeau &amp; Cucchiara 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="./rfc3811">RFC 3811</a> MPLS TC MIB June 2004</span>
223
224
225 STATUS current
226 DESCRIPTION
227 "The number of octets of MPLS data that the stream
228 may send back-to-back without concern for policing.
229 The value of zero indicates that an implementation
230 does not support Burst Size."
231 SYNTAX Unsigned32 (0..4294967295)
232
233 MplsExtendedTunnelId ::= TEXTUAL-CONVENTION
234 STATUS current
235 DESCRIPTION
236 "A unique identifier for an MPLS Tunnel. This may
237 represent an IPv4 address of the ingress or egress
238 LSR for the tunnel. This value is derived from the
239 Extended Tunnel Id in RSVP or the Ingress Router ID
240 for CR-LDP."
241 REFERENCE
242 "RSVP-TE: Extensions to RSVP for LSP Tunnels,
243 [<a href="./rfc3209" title="&quot;RSVP-TE: Extensions to RSVP for LSP Tunnels&quot;">RFC3209</a>].
244
245 Constraint-Based LSP Setup using LDP, [<a href="./rfc3212" title="&quot;Constraint-Based LSP Setup using LDP&quot;">RFC3212</a>]."
246 SYNTAX Unsigned32(0..4294967295)
247
248 MplsLabel ::= TEXTUAL-CONVENTION
249 STATUS current
250 DESCRIPTION
251 "This value represents an MPLS label as defined in
252 [<a href="./rfc3031" title="&quot;Multiprotocol Label Switching Architecture&quot;">RFC3031</a>], [<a href="./rfc3032" title="&quot;MPLS Label Stack Encoding&quot;">RFC3032</a>], [<a href="./rfc3034" title="&quot;Use of Label Switching on Frame Relay Networks Specification&quot;">RFC3034</a>], [<a href="./rfc3035" title="&quot;MPLS using LDP and ATM VC Switching&quot;">RFC3035</a>] and
253 [<a href="./rfc3471" title="&quot;Generalized Multi-Protocol Label Switching (GMPLS) Architecture&quot;">RFC3471</a>].
254
255 The label contents are specific to the label being
256 represented, such as:
257
258 * The label carried in an MPLS shim header
259 (for LDP this is the Generic Label) is a 20-bit
260 number represented by 4 octets. Bits 0-19 contain
261 a label or a reserved label value. Bits 20-31
262 MUST be zero.
263
264 The following is quoted directly from [<a href="./rfc3032" title="&quot;MPLS Label Stack Encoding&quot;">RFC3032</a>].
265 There are several reserved label values:
266
267 i. A value of 0 represents the
268 'IPv4 Explicit NULL Label'. This label
269 value is only legal at the bottom of the
270 label stack. It indicates that the label
271 stack must be popped, and the forwarding
272 of the packet must then be based on the
273
274
275
276 <span class="grey">Nadeau &amp; Cucchiara 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="./rfc3811">RFC 3811</a> MPLS TC MIB June 2004</span>
279
280
281 IPv4 header.
282
283 ii. A value of 1 represents the
284 'Router Alert Label'. This label value is
285 legal anywhere in the label stack except at
286 the bottom. When a received packet
287 contains this label value at the top of
288 the label stack, it is delivered to a
289 local software module for processing.
290 The actual forwarding of the packet
291 is determined by the label beneath it
292 in the stack. However, if the packet is
293 forwarded further, the Router Alert Label
294 should be pushed back onto the label stack
295 before forwarding. The use of this label
296 is analogous to the use of the
297 'Router Alert Option' in IP packets
298 [<a href="./rfc2113" title="&quot;IP Router Alert Option&quot;">RFC2113</a>]. Since this label
299 cannot occur at the bottom of the stack,
300 it is not associated with a
301 particular network layer protocol.
302
303 iii. A value of 2 represents the
304 'IPv6 Explicit NULL Label'. This label
305 value is only legal at the bottom of the
306 label stack. It indicates that the label
307 stack must be popped, and the forwarding
308 of the packet must then be based on the
309 IPv6 header.
310
311 iv. A value of 3 represents the
312 'Implicit NULL Label'.
313 This is a label that an LSR may assign and
314 distribute, but which never actually
315 appears in the encapsulation. When an
316 LSR would otherwise replace the label
317 at the top of the stack with a new label,
318 but the new label is 'Implicit NULL',
319 the LSR will pop the stack instead of
320 doing the replacement. Although
321 this value may never appear in the
322 encapsulation, it needs to be specified in
323 the Label Distribution Protocol, so a value
324 is reserved.
325
326 v. Values 4-15 are reserved.
327
328 * The frame relay label can be either 10-bits or
329
330
331
332 <span class="grey">Nadeau &amp; Cucchiara 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="./rfc3811">RFC 3811</a> MPLS TC MIB June 2004</span>
335
336
337 23-bits depending on the DLCI field size and the
338 upper 22-bits or upper 9-bits must be zero,
339 respectively.
340
341 * For an ATM label the lower 16-bits represents the
342 VCI, the next 12-bits represents the VPI and the
343 remaining bits MUST be zero.
344
345 * The Generalized-MPLS (GMPLS) label contains a
346 value greater than 2^24-1 and used in GMPLS
347 as defined in [<a href="./rfc3471" title="&quot;Generalized Multi-Protocol Label Switching (GMPLS) Architecture&quot;">RFC3471</a>]."
348 REFERENCE
349 "Multiprotocol Label Switching Architecture,
350 <a href="./rfc3031">RFC3031</a>.
351
352 MPLS Label Stack Encoding, [<a href="./rfc3032" title="&quot;MPLS Label Stack Encoding&quot;">RFC3032</a>].
353
354 Use of Label Switching on Frame Relay Networks,
355 <a href="./rfc3034">RFC3034</a>.
356
357 MPLS using LDP and ATM VC Switching, <a href="./rfc3035">RFC3035</a>.
358 Generalized Multiprotocol Label Switching
359 (GMPLS) Architecture, [<a href="./rfc3471" title="&quot;Generalized Multi-Protocol Label Switching (GMPLS) Architecture&quot;">RFC3471</a>]."
360 SYNTAX Unsigned32 (0..4294967295)
361
362 MplsLabelDistributionMethod ::= TEXTUAL-CONVENTION
363 STATUS current
364 DESCRIPTION
365 "The label distribution method which is also called
366 the label advertisement mode [<a href="./rfc3036" title="&quot;LDP Specification&quot;">RFC3036</a>].
367 Each interface on an LSR is configured to operate
368 in either Downstream Unsolicited or Downstream
369 on Demand."
370 REFERENCE
371 "Multiprotocol Label Switching Architecture,
372 <a href="./rfc3031">RFC3031</a>.
373
374 LDP Specification, <a href="./rfc3036#section-2.6.3">RFC3036, Section&nbsp;2.6.3</a>."
375 SYNTAX INTEGER {
376 downstreamOnDemand(1),
377 downstreamUnsolicited(2)
378 }
379
380 MplsLdpIdentifier ::= TEXTUAL-CONVENTION
381 DISPLAY-HINT "1d.1d.1d.1d:2d"
382 STATUS current
383 DESCRIPTION
384 "The LDP identifier is a six octet
385
386
387
388 <span class="grey">Nadeau &amp; Cucchiara 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="./rfc3811">RFC 3811</a> MPLS TC MIB June 2004</span>
391
392
393 quantity which is used to identify a
394 Label Switching Router (LSR) label space.
395
396 The first four octets identify the LSR and
397 must be a globally unique value, such as a
398 32-bit router ID assigned to the LSR, and the
399 last two octets identify a specific label
400 space within the LSR."
401 SYNTAX OCTET STRING (SIZE (6))
402
403 MplsLsrIdentifier ::= TEXTUAL-CONVENTION
404 STATUS current
405 DESCRIPTION
406 "The Label Switching Router (LSR) identifier is the
407 first 4 bytes of the Label Distribution Protocol
408 (LDP) identifier."
409 SYNTAX OCTET STRING (SIZE (4))
410 MplsLdpLabelType ::= TEXTUAL-CONVENTION
411 STATUS current
412 DESCRIPTION
413 "The Layer 2 label types which are defined for MPLS
414 LDP and/or CR-LDP are generic(1), atm(2), or
415 frameRelay(3)."
416 SYNTAX INTEGER {
417 generic(1),
418 atm(2),
419 frameRelay(3)
420 }
421
422 MplsLSPID ::= TEXTUAL-CONVENTION
423 STATUS current
424 DESCRIPTION
425 "A unique identifier within an MPLS network that is
426 assigned to each LSP. This is assigned at the head
427 end of the LSP and can be used by all LSRs
428 to identify this LSP. This value is piggybacked by
429 the signaling protocol when this LSP is signaled
430 within the network. This identifier can then be
431 used at each LSR to identify which labels are
432 being swapped to other labels for this LSP. This
433 object can also be used to disambiguate LSPs that
434 share the same RSVP sessions between the same
435 source and destination.
436
437 For LSPs established using CR-LDP, the LSPID is
438 composed of the ingress LSR Router ID (or any of
439 its own IPv4 addresses) and a locally unique
440 CR-LSP ID to that LSR. The first two bytes carry
441
442
443
444 <span class="grey">Nadeau &amp; Cucchiara 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="./rfc3811">RFC 3811</a> MPLS TC MIB June 2004</span>
447
448
449 the CR-LSPID, and the remaining 4 bytes carry
450 the Router ID. The LSPID is useful in network
451 management, in CR-LSP repair, and in using
452 an already established CR-LSP as a hop in
453 an ER-TLV.
454
455 For LSPs signaled using RSVP-TE, the LSP ID is
456 defined as a 16-bit (2 byte) identifier used
457 in the SENDER_TEMPLATE and the FILTER_SPEC
458 that can be changed to allow a sender to
459 share resources with itself. The length of this
460 object should only be 2 or 6 bytes. If the length
461 of this octet string is 2 bytes, then it must
462 identify an RSVP-TE LSPID, or it is 6 bytes,
463 it must contain a CR-LDP LSPID."
464 REFERENCE
465 "RSVP-TE: Extensions to RSVP for LSP Tunnels,
466 [<a href="./rfc3209" title="&quot;RSVP-TE: Extensions to RSVP for LSP Tunnels&quot;">RFC3209</a>].
467
468 Constraint-Based LSP Setup using LDP,
469 [<a href="./rfc3212" title="&quot;Constraint-Based LSP Setup using LDP&quot;">RFC3212</a>]."
470 SYNTAX OCTET STRING (SIZE (2|6))
471
472 MplsLspType ::= TEXTUAL-CONVENTION
473 STATUS current
474 DESCRIPTION
475 "Types of Label Switch Paths (LSPs)
476 on a Label Switching Router (LSR) or a
477 Label Edge Router (LER) are:
478
479 unknown(1) -- if the LSP is not known
480 to be one of the following.
481
482 terminatingLsp(2) -- if the LSP terminates
483 on the LSR/LER, then this
484 is an egressing LSP
485 which ends on the LSR/LER,
486
487 originatingLsp(3) -- if the LSP originates
488 from this LSR/LER, then
489 this is an ingressing LSP
490 which is the head-end of
491 the LSP,
492
493 crossConnectingLsp(4) -- if the LSP ingresses
494 and egresses on the LSR,
495 then it is
496 cross-connecting on that
497
498
499
500 <span class="grey">Nadeau &amp; Cucchiara 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="./rfc3811">RFC 3811</a> MPLS TC MIB June 2004</span>
503
504
505 LSR."
506 SYNTAX INTEGER {
507 unknown(1),
508 terminatingLsp(2),
509 originatingLsp(3),
510 crossConnectingLsp(4)
511 }
512
513 MplsOwner ::= TEXTUAL-CONVENTION
514 STATUS current
515 DESCRIPTION
516 "This object indicates the local network
517 management subsystem that originally created
518 the object(s) in question. The values of
519 this enumeration are defined as follows:
520
521 unknown(1) - the local network management
522 subsystem cannot discern which
523 component created the object.
524
525 other(2) - the local network management
526 subsystem is able to discern which component
527 created the object, but the component is not
528 listed within the following choices,
529 e.g., command line interface (cli).
530
531 snmp(3) - The Simple Network Management Protocol
532 was used to configure this object initially.
533
534 ldp(4) - The Label Distribution Protocol was
535 used to configure this object initially.
536
537 crldp(5) - The Constraint-Based Label Distribution
538 Protocol was used to configure this object
539 initially.
540
541 rsvpTe(6) - The Resource Reservation Protocol was
542 used to configure this object initially.
543
544 policyAgent(7) - A policy agent (perhaps in
545 combination with one of the above protocols) was
546 used to configure this object initially.
547
548 An object created by any of the above choices
549 MAY be modified or destroyed by the same or a
550 different choice."
551 SYNTAX INTEGER {
552 unknown(1),
553
554
555
556 <span class="grey">Nadeau &amp; Cucchiara 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="./rfc3811">RFC 3811</a> MPLS TC MIB June 2004</span>
559
560
561 other(2),
562 snmp(3),
563 ldp(4),
564 crldp(5),
565 rsvpTe(6),
566 policyAgent(7)
567 }
568
569 MplsPathIndexOrZero ::= TEXTUAL-CONVENTION
570 STATUS current
571 DESCRIPTION
572 "A unique identifier used to identify a specific
573 path used by a tunnel. A value of 0 (zero) means
574 that no path is in use."
575 SYNTAX Unsigned32(0..4294967295)
576
577 MplsPathIndex ::= TEXTUAL-CONVENTION
578 STATUS current
579 DESCRIPTION
580 "A unique value to index (by Path number) an
581 entry in a table."
582 SYNTAX Unsigned32(1..4294967295)
583
584 MplsRetentionMode ::= TEXTUAL-CONVENTION
585 STATUS current
586 DESCRIPTION
587 "The label retention mode which specifies whether
588 an LSR maintains a label binding for a FEC
589 learned from a neighbor that is not its next hop
590 for the FEC.
591
592 If the value is conservative(1) then advertised
593 label mappings are retained only if they will be
594 used to forward packets, i.e., if label came from
595 a valid next hop.
596
597 If the value is liberal(2) then all advertised
598 label mappings are retained whether they are from
599 a valid next hop or not."
600 REFERENCE
601 "Multiprotocol Label Switching Architecture,
602 <a href="./rfc3031">RFC3031</a>.
603
604 LDP Specification, <a href="./rfc3036#section-2.6.2">RFC3036, Section&nbsp;2.6.2</a>."
605 SYNTAX INTEGER {
606 conservative(1),
607 liberal(2)
608 }
609
610
611
612 <span class="grey">Nadeau &amp; Cucchiara 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="./rfc3811">RFC 3811</a> MPLS TC MIB June 2004</span>
615
616
617 MplsTunnelAffinity ::= TEXTUAL-CONVENTION
618 STATUS current
619 DESCRIPTION
620 "Describes the configured 32-bit Include-any,
621 include-all, or exclude-all constraint for
622 constraint-based link selection."
623 REFERENCE
624 "RSVP-TE: Extensions to RSVP for LSP Tunnels,
625 <a href="./rfc3209#section-4.7.4">RFC3209, Section&nbsp;4.7.4</a>."
626 SYNTAX Unsigned32(0..4294967295)
627
628 MplsTunnelIndex ::= TEXTUAL-CONVENTION
629 STATUS current
630 DESCRIPTION
631 "A unique index into mplsTunnelTable.
632 For tunnels signaled using RSVP, this value
633 should correspond to the RSVP Tunnel ID
634 used for the RSVP-TE session."
635 SYNTAX Unsigned32 (0..65535)
636
637 MplsTunnelInstanceIndex ::= TEXTUAL-CONVENTION
638 STATUS current
639 DESCRIPTION
640 "The tunnel entry with instance index 0
641 should refer to the configured tunnel
642 interface (if one exists).
643
644 Values greater than 0, but less than or
645 equal to 65535, should be used to indicate
646 signaled (or backup) tunnel LSP instances.
647 For tunnel LSPs signaled using RSVP,
648 this value should correspond to the
649 RSVP LSP ID used for the RSVP-TE
650 LSP.
651
652 Values greater than 65535 apply to FRR
653 detour instances."
654 SYNTAX Unsigned32(0|1..65535|65536..4294967295)
655
656 TeHopAddressType ::= TEXTUAL-CONVENTION
657 STATUS current
658 DESCRIPTION
659 "A value that represents a type of address for a
660 Traffic Engineered (TE) Tunnel hop.
661
662 unknown(0) An unknown address type. This value
663 MUST be used if the value of the
664 corresponding TeHopAddress object is a
665
666
667
668 <span class="grey">Nadeau &amp; Cucchiara 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="./rfc3811">RFC 3811</a> MPLS TC MIB June 2004</span>
671
672
673 zero-length string. It may also be
674 used to indicate a TeHopAddress which
675 is not in one of the formats defined
676 below.
677
678 ipv4(1) An IPv4 network address as defined by
679 the InetAddressIPv4 TEXTUAL-CONVENTION
680 [<a href="./rfc3291" title="&quot;Textual Conventions for Internet Network Addresses&quot;">RFC3291</a>].
681
682 ipv6(2) A global IPv6 address as defined by
683 the InetAddressIPv6 TEXTUAL-CONVENTION
684 [<a href="./rfc3291" title="&quot;Textual Conventions for Internet Network Addresses&quot;">RFC3291</a>].
685
686 asnumber(3) An Autonomous System (AS) number as
687 defined by the TeHopAddressAS
688 TEXTUAL-CONVENTION.
689
690 unnum(4) An unnumbered interface index as
691 defined by the TeHopAddressUnnum
692 TEXTUAL-CONVENTION.
693
694 lspid(5) An LSP ID for TE Tunnels
695 (<a href="./rfc3212">RFC3212</a>) as defined by the
696 MplsLSPID TEXTUAL-CONVENTION.
697
698 Each definition of a concrete TeHopAddressType
699 value must be accompanied by a definition
700 of a TEXTUAL-CONVENTION for use with that
701 TeHopAddress.
702
703 To support future extensions, the TeHopAddressType
704 TEXTUAL-CONVENTION SHOULD NOT be sub-typed in
705 object type definitions. It MAY be sub-typed in
706 compliance statements in order to require only a
707 subset of these address types for a compliant
708 implementation.
709
710 Implementations must ensure that TeHopAddressType
711 objects and any dependent objects
712 (e.g., TeHopAddress objects) are consistent.
713 An inconsistentValue error must be generated
714 if an attempt to change a TeHopAddressType
715 object would, for example, lead to an
716 undefined TeHopAddress value that is
717 not defined herein. In particular,
718 TeHopAddressType/TeHopAddress pairs
719 must be changed together if the address
720 type changes (e.g., from ipv6(2) to ipv4(1))."
721
722
723
724 <span class="grey">Nadeau &amp; Cucchiara 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="./rfc3811">RFC 3811</a> MPLS TC MIB June 2004</span>
727
728
729 REFERENCE
730 "TEXTUAL-CONVENTIONs for Internet Network
731 Addresses, <a href="./rfc3291">RFC3291</a>.
732
733 Constraint-Based LSP Setup using LDP,
734 [<a href="./rfc3212" title="&quot;Constraint-Based LSP Setup using LDP&quot;">RFC3212</a>]"
735
736 SYNTAX INTEGER {
737 unknown(0),
738 ipv4(1),
739 ipv6(2),
740 asnumber(3),
741 unnum(4),
742 lspid(5)
743 }
744
745 TeHopAddress ::= TEXTUAL-CONVENTION
746 STATUS current
747 DESCRIPTION
748 "Denotes a generic Tunnel hop address,
749 that is, the address of a node which
750 an LSP traverses, including the source
751 and destination nodes. An address may be
752 very concrete, for example, an IPv4 host
753 address (i.e., with prefix length 32);
754 if this IPv4 address is an interface
755 address, then that particular interface
756 must be traversed. An address may also
757 specify an 'abstract node', for example,
758 an IPv4 address with prefix length
759 less than 32, in which case, the LSP
760 can traverse any node whose address
761 falls in that range. An address may
762 also specify an Autonomous System (AS),
763 in which case the LSP can traverse any
764 node that falls within that AS.
765
766 A TeHopAddress value is always interpreted within
767 the context of an TeHopAddressType value. Every
768 usage of the TeHopAddress TEXTUAL-CONVENTION
769 is required to specify the TeHopAddressType object
770 which provides the context. It is suggested that
771 the TeHopAddressType object is logically registered
772 before the object(s) which use the TeHopAddress
773 TEXTUAL-CONVENTION if they appear in the
774 same logical row.
775
776 The value of a TeHopAddress object must always be
777
778
779
780 <span class="grey">Nadeau &amp; Cucchiara 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="./rfc3811">RFC 3811</a> MPLS TC MIB June 2004</span>
783
784
785 consistent with the value of the associated
786 TeHopAddressType object. Attempts to set a
787 TeHopAddress object to a value which is
788 inconsistent with the associated TeHopAddressType
789 must fail with an inconsistentValue error."
790 SYNTAX OCTET STRING (SIZE (0..32))
791
792 TeHopAddressAS ::= TEXTUAL-CONVENTION
793 STATUS current
794 DESCRIPTION
795 "Represents a two or four octet AS number.
796 The AS number is represented in network byte
797 order (MSB first). A two-octet AS number has
798 the two MSB octets set to zero."
799 REFERENCE
800 "Textual Conventions for Internet Network
801 Addresses, [<a href="./rfc3291" title="&quot;Textual Conventions for Internet Network Addresses&quot;">RFC3291</a>]. The
802 InetAutonomousSystemsNumber TEXTUAL-CONVENTION
803 has a SYNTAX of Unsigned32, whereas this TC
804 has a SYNTAX of OCTET STRING (SIZE (4)).
805 Both TCs represent an autonomous system number
806 but use different syntaxes to do so."
807 SYNTAX OCTET STRING (SIZE (4))
808
809 TeHopAddressUnnum ::= TEXTUAL-CONVENTION
810 STATUS current
811 DESCRIPTION
812 "Represents an unnumbered interface:
813
814 octets contents encoding
815 1-4 unnumbered interface network-byte order
816
817 The corresponding TeHopAddressType value is
818 unnum(5)."
819 SYNTAX OCTET STRING(SIZE(4))
820
821 END
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836 <span class="grey">Nadeau &amp; Cucchiara 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="./rfc3811">RFC 3811</a> MPLS TC MIB June 2004</span>
839
840
841 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. References</span>
842
843 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Normative References</span>
844
845 [<a id="ref-RFC2113">RFC2113</a>] Katz, D., "IP Router Alert Option", <a href="./rfc2113">RFC 2113</a>, February
846 1997.
847
848 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
849 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
850
851 [<a id="ref-RFC2434">RFC2434</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
852 IANA Considerations Section in RFCs", BCP: 26, <a href="./rfc2434">RFC 2434</a>,
853 October 1998.
854
855 [<a id="ref-RFC2578">RFC2578</a>] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
856 "Structure of Management Information Version 2 (SMIv2)",
857 STD 58, <a href="./rfc2578">RFC 2578</a>, April 1999.
858
859 [<a id="ref-RFC2579">RFC2579</a>] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual
860 Conventions for SMIv2", STD 58, <a href="./rfc2579">RFC 2579</a>, April 1999.
861
862 [<a id="ref-RFC2580">RFC2580</a>] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
863 "Conformance Statements for SMIv2", STD 58, <a href="./rfc2580">RFC 2580</a>, April
864 1999.
865
866 [<a id="ref-RFC3031">RFC3031</a>] Rosen, E., Viswananthan, A., and R. Callon, "Multiprotocol
867 Label Switching Architecture", <a href="./rfc3031">RFC 3031</a>, January 2001.
868
869 [<a id="ref-RFC3032">RFC3032</a>] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D.,
870 Federokow, G., Li, T., and A. Conta, "MPLS Label Stack
871 Encoding", <a href="./rfc3032">RFC 3032</a>, January 2001.
872
873 [<a id="ref-RFC3034">RFC3034</a>] Conta, A., Doolan, P., and A. Malis, "Use of Label
874 Switching on Frame Relay Networks Specification", <a href="./rfc3034">RFC 3034</a>,
875 January 2001.
876
877 [<a id="ref-RFC3035">RFC3035</a>] Davie, B., Lawrence, J., McCloghrie, K., Rosen, E.,
878 Swallow, G., Rekhter, Y., and P. Doolan, "MPLS using LDP
879 and ATM VC Switching", <a href="./rfc3035">RFC 3035</a>, January 2001.
880
881 [<a id="ref-RFC3036">RFC3036</a>] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and
882 B. Thomas, "LDP Specification", <a href="./rfc3036">RFC 3036</a>, January 2001.
883
884 [<a id="ref-RFC3209">RFC3209</a>] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
885 and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
886 Tunnels", <a href="./rfc3209">RFC 3209</a>, December 2001.
887
888
889
890
891
892 <span class="grey">Nadeau &amp; Cucchiara 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="./rfc3811">RFC 3811</a> MPLS TC MIB June 2004</span>
895
896
897 [<a id="ref-RFC3212">RFC3212</a>] Jamoussi, B., Ed., Andersson, L., Callon, R., Dantu, R.,
898 Wu, L., Doolan, P., Worster, T., Feldman, N., Fredette, A.,
899 Girish, M., Gray, E., Heinanen, J., Kilty, T., and A.
900 Malis, "Constraint-Based LSP Setup using LDP", <a href="./rfc3212">RFC 3212</a>,
901 January 2002.
902
903 [<a id="ref-RFC3291">RFC3291</a>] Daniele, M., Haberman, B., Routhier, S., and J.
904 Schoenwaelder, "Textual Conventions for Internet Network
905 Addresses", <a href="./rfc3291">RFC 3291</a>, May 2002.
906
907 [<a id="ref-RFC3471">RFC3471</a>] Berger, L., Editor, "Generalized Multi-Protocol Label
908 Switching (GMPLS) Architecture", <a href="./rfc3471">RFC 3471</a>, January 2003.
909
910 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Informative References</span>
911
912 [<a id="ref-RFC3410">RFC3410</a>] Case, J., Mundy, R., Partain, D., and B. Stewart,
913 "Introduction and Applicability Statements for Internet-
914 Standard Management Framework", <a href="./rfc3410">RFC 3410</a>, December 2002.
915
916 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
917
918 This module does not define any management objects. Instead, it
919 defines a set of textual conventions which may be used by other MPLS
920 MIB modules to define management objects.
921
922 Meaningful security considerations can only be written in the MIB
923 modules that define management objects. Therefore, this document has
924 no impact on the security of the Internet.
925
926 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
927
928 IANA has made a MIB OID assignment under the transmission branch,
929 that is, assigned the mplsStdMIB under { transmission 166 }. This
930 sub-id is requested because 166 is the ifType for mpls(166) and is
931 available under transmission.
932
933 In the future, MPLS related standards track MIB modules should be
934 rooted under the mplsStdMIB subtree. The IANA is requested to manage
935 that namespace. New assignments can only be made via a Standards
936 Action as specified in [<a href="./rfc2434" title="">RFC2434</a>].
937
938 The IANA has also assigned { mplsStdMIB 1 } to the MPLS-TC-STD-MIB
939 specified in this document.
940
941
942
943
944
945
946
947
948 <span class="grey">Nadeau &amp; Cucchiara 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="./rfc3811">RFC 3811</a> MPLS TC MIB June 2004</span>
951
952
953 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Contributors</span>
954
955 This document was created by combining TEXTUAL-CONVENTIONS from
956 current MPLS MIBs and a TE-WG MIB. Co-authors on each of these MIBs
957 contributed to the TEXTUAL-CONVENTIONS contained in this MIB and also
958 contributed greatly to the revisions of this document. These co-
959 authors addresses are included here because they are useful future
960 contacts for information about this document. These co-authors are:
961
962 Cheenu Srinivasan
963 Bloomberg L.P.
964 499 Park Ave.
965 New York, NY 10022
966
967 Phone: +1-212-893-3682
968 EMail: [email protected]
969
970
971 Arun Viswanathan
972 Force10 Networks, Inc.
973 1440 McCarthy Blvd
974 Milpitas, CA 95035
975
976 Phone: +1-408-571-3516
977 EMail: [email protected]
978
979
980 Hans Sjostrand
981 ipUnplugged
982 P.O. Box 101 60
983 S-121 28 Stockholm, Sweden
984
985 Phone: +46-8-725-5900
986 EMail: [email protected]
987
988
989 Kireeti Kompella
990 Juniper Networks
991 1194 Mathilda Ave
992 Sunnyvale, CA 94089
993
994 Phone: +1-408-745-2000
995 EMail: [email protected]
996
997
998
999
1000
1001
1002
1003
1004 <span class="grey">Nadeau &amp; Cucchiara 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="./rfc3811">RFC 3811</a> MPLS TC MIB June 2004</span>
1007
1008
1009 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgements</span>
1010
1011 This document is a product of the MPLS Working Group. The editors
1012 and contributors would like to thank Mike MacFadden and Adrian Farrel
1013 for their helpful comments on several reviews. Also, the editors and
1014 contributors would like to give a special acknowledgement to Bert
1015 Wijnen for his many detailed reviews. Bert's assistance and guidance
1016 is greatly appreciated.
1017
1018 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Authors' Addresses</span>
1019
1020 Thomas D. Nadeau
1021 Cisco Systems, Inc.
1022 BXB300/2/
1023 300 Beaver Brook Road
1024 Boxborough, MA 01719
1025
1026 Phone: +1-978-936-1470
1027 EMail: [email protected]
1028
1029
1030 Joan E. Cucchiara
1031 Marconi Communications, Inc.
1032 900 Chelmsford Street
1033 Lowell, MA 01851
1034
1035 Phone: +1-978-275-7400
1036 EMail: [email protected]
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">Nadeau &amp; Cucchiara 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="./rfc3811">RFC 3811</a> MPLS TC MIB June 2004</span>
1063
1064
1065 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Full Copyright Statement</span>
1066
1067 Copyright (C) The Internet Society (2004). This document is subject
1068 to the rights, licenses and restrictions contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and
1069 except as set forth therein, the authors retain all their rights.
1070
1071 This document and the information contained herein are provided on an
1072 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
1073 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
1074 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
1075 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
1076 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
1077 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1078
1079 Intellectual Property
1080
1081 The IETF takes no position regarding the validity or scope of any
1082 Intellectual Property Rights or other rights that might be claimed to
1083 pertain to the implementation or use of the technology described in
1084 this document or the extent to which any license under such rights
1085 might or might not be available; nor does it represent that it has
1086 made any independent effort to identify any such rights. Information
1087 on the procedures with respect to rights in RFC documents can be
1088 found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
1089
1090 Copies of IPR disclosures made to the IETF Secretariat and any
1091 assurances of licenses to be made available, or the result of an
1092 attempt made to obtain a general license or permission for the use of
1093 such proprietary rights by implementers or users of this
1094 specification can be obtained from the IETF on-line IPR repository at
1095 <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
1096
1097 The IETF invites any interested party to bring to its attention any
1098 copyrights, patents or patent applications, or other proprietary
1099 rights that may cover technology that may be required to implement
1100 this standard. Please address the information to the IETF at ietf-
1101 [email protected].
1102
1103 Acknowledgement
1104
1105 Funding for the RFC Editor function is currently provided by the
1106 Internet Society.
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116 Nadeau &amp; Cucchiara Standards Track [Page 20]
1117 </pre>