1 MPLS-TC-STD-MIB DEFINITIONS ::= BEGIN
7 transmission FROM SNMPv2-SMI -- [RFC2578]
10 FROM SNMPv2-TC; -- [RFC2579]
12 mplsTCStdMIB MODULE-IDENTITY
13 LAST-UPDATED "200406030000Z" -- June 3, 2004
15 "IETF Multiprotocol Label Switching (MPLS) Working
26 Marconi Communications, Inc.
27 jcucchiara@mindspring.com
34 Force10 Networks, Inc.
35 arunv@force10networks.com
45 Email comments to the MPLS WG Mailing List at
48 "Copyright (C) The Internet Society (2004). The
49 initial version of this MIB module was published
50 in RFC 3811. For full legal notices see the RFC
52 http://www.ietf.org/copyrights/ianamib.html
54 This MIB module defines TEXTUAL-CONVENTIONs
55 for concepts used in Multiprotocol Label
56 Switching (MPLS) networks."
58 REVISION "200406030000Z" -- June 3, 2004
60 "Initial version published as part of RFC 3811."
64 mplsStdMIB OBJECT IDENTIFIER
66 ::= { transmission 166 }
68 MplsAtmVcIdentifier ::= TEXTUAL-CONVENTION
75 "A Label Switching Router (LSR) that
76 creates LDP sessions on ATM interfaces
77 uses the VCI or VPI/VCI field to hold the
80 VCI values MUST NOT be in the 0-31 range.
81 The values 0 to 31 are reserved for other uses
82 by the ITU and ATM Forum. The value
83 of 32 can only be used for the Control VC,
84 although values greater than 32 could be
85 configured for the Control VC.
87 If a value from 0 to 31 is used for a VCI
88 the management entity controlling the LDP
89 subsystem should reject this with an
90 inconsistentValue error. Also, if
91 the value of 32 is used for a VC which is
92 NOT the Control VC, this should
93 result in an inconsistentValue error."
95 "MPLS using LDP and ATM VC Switching, RFC3035."
96 SYNTAX Integer32 (32..65535)
98 MplsBitRate ::= TEXTUAL-CONVENTION
102 "If the value of this object is greater than zero,
103 then this represents the bandwidth of this MPLS
104 interface (or Label Switched Path) in units of
105 '1,000 bits per second'.
107 The value, when greater than zero, represents the
108 bandwidth of this MPLS interface (rounded to the
109 nearest 1,000) in units of 1,000 bits per second.
110 If the bandwidth of the MPLS interface is between
111 ((n * 1000) - 500) and ((n * 1000) + 499), the value
112 of this object is n, such that n > 0.
114 If the value of this object is 0 (zero), this
115 means that the traffic over this MPLS interface is
116 considered to be best effort."
117 SYNTAX Unsigned32 (0|1..4294967295)
119 MplsBurstSize ::= TEXTUAL-CONVENTION
126 "The number of octets of MPLS data that the stream
127 may send back-to-back without concern for policing.
128 The value of zero indicates that an implementation
129 does not support Burst Size."
130 SYNTAX Unsigned32 (0..4294967295)
132 MplsExtendedTunnelId ::= TEXTUAL-CONVENTION
135 "A unique identifier for an MPLS Tunnel. This may
136 represent an IPv4 address of the ingress or egress
137 LSR for the tunnel. This value is derived from the
138 Extended Tunnel Id in RSVP or the Ingress Router ID
141 "RSVP-TE: Extensions to RSVP for LSP Tunnels,
144 Constraint-Based LSP Setup using LDP, [RFC3212]."
145 SYNTAX Unsigned32(0..4294967295)
147 MplsLabel ::= TEXTUAL-CONVENTION
150 "This value represents an MPLS label as defined in
151 [RFC3031], [RFC3032], [RFC3034], [RFC3035] and
154 The label contents are specific to the label being
155 represented, such as:
157 * The label carried in an MPLS shim header
158 (for LDP this is the Generic Label) is a 20-bit
159 number represented by 4 octets. Bits 0-19 contain
160 a label or a reserved label value. Bits 20-31
163 The following is quoted directly from [RFC3032].
164 There are several reserved label values:
166 i. A value of 0 represents the
167 'IPv4 Explicit NULL Label'. This label
168 value is only legal at the bottom of the
169 label stack. It indicates that the label
170 stack must be popped, and the forwarding
171 of the packet must then be based on the
177 ii. A value of 1 represents the
178 'Router Alert Label'. This label value is
179 legal anywhere in the label stack except at
180 the bottom. When a received packet
181 contains this label value at the top of
182 the label stack, it is delivered to a
183 local software module for processing.
184 The actual forwarding of the packet
185 is determined by the label beneath it
186 in the stack. However, if the packet is
187 forwarded further, the Router Alert Label
188 should be pushed back onto the label stack
189 before forwarding. The use of this label
190 is analogous to the use of the
191 'Router Alert Option' in IP packets
192 [RFC2113]. Since this label
193 cannot occur at the bottom of the stack,
194 it is not associated with a
195 particular network layer protocol.
197 iii. A value of 2 represents the
198 'IPv6 Explicit NULL Label'. This label
199 value is only legal at the bottom of the
200 label stack. It indicates that the label
201 stack must be popped, and the forwarding
202 of the packet must then be based on the
205 iv. A value of 3 represents the
206 'Implicit NULL Label'.
207 This is a label that an LSR may assign and
208 distribute, but which never actually
209 appears in the encapsulation. When an
210 LSR would otherwise replace the label
211 at the top of the stack with a new label,
212 but the new label is 'Implicit NULL',
213 the LSR will pop the stack instead of
214 doing the replacement. Although
215 this value may never appear in the
216 encapsulation, it needs to be specified in
217 the Label Distribution Protocol, so a value
220 v. Values 4-15 are reserved.
222 * The frame relay label can be either 10-bits or
226 23-bits depending on the DLCI field size and the
227 upper 22-bits or upper 9-bits must be zero,
230 * For an ATM label the lower 16-bits represents the
231 VCI, the next 12-bits represents the VPI and the
232 remaining bits MUST be zero.
234 * The Generalized-MPLS (GMPLS) label contains a
235 value greater than 2^24-1 and used in GMPLS
236 as defined in [RFC3471]."
238 "Multiprotocol Label Switching Architecture,
241 MPLS Label Stack Encoding, [RFC3032].
243 Use of Label Switching on Frame Relay Networks,
246 MPLS using LDP and ATM VC Switching, RFC3035.
247 Generalized Multiprotocol Label Switching
248 (GMPLS) Architecture, [RFC3471]."
249 SYNTAX Unsigned32 (0..4294967295)
251 MplsLabelDistributionMethod ::= TEXTUAL-CONVENTION
254 "The label distribution method which is also called
255 the label advertisement mode [RFC3036].
256 Each interface on an LSR is configured to operate
257 in either Downstream Unsolicited or Downstream
260 "Multiprotocol Label Switching Architecture,
263 LDP Specification, RFC3036, Section 2.6.3."
265 downstreamOnDemand(1),
266 downstreamUnsolicited(2)
269 MplsLdpIdentifier ::= TEXTUAL-CONVENTION
270 DISPLAY-HINT "1d.1d.1d.1d:2d"
273 "The LDP identifier is a six octet
277 quantity which is used to identify a
278 Label Switching Router (LSR) label space.
280 The first four octets identify the LSR and
281 must be a globally unique value, such as a
282 32-bit router ID assigned to the LSR, and the
283 last two octets identify a specific label
284 space within the LSR."
285 SYNTAX OCTET STRING (SIZE (6))
287 MplsLsrIdentifier ::= TEXTUAL-CONVENTION
290 "The Label Switching Router (LSR) identifier is the
291 first 4 bytes of the Label Distribution Protocol
293 SYNTAX OCTET STRING (SIZE (4))
294 MplsLdpLabelType ::= TEXTUAL-CONVENTION
297 "The Layer 2 label types which are defined for MPLS
298 LDP and/or CR-LDP are generic(1), atm(2), or
306 MplsLSPID ::= TEXTUAL-CONVENTION
309 "A unique identifier within an MPLS network that is
310 assigned to each LSP. This is assigned at the head
311 end of the LSP and can be used by all LSRs
312 to identify this LSP. This value is piggybacked by
313 the signaling protocol when this LSP is signaled
314 within the network. This identifier can then be
315 used at each LSR to identify which labels are
316 being swapped to other labels for this LSP. This
317 object can also be used to disambiguate LSPs that
318 share the same RSVP sessions between the same
319 source and destination.
321 For LSPs established using CR-LDP, the LSPID is
322 composed of the ingress LSR Router ID (or any of
323 its own IPv4 addresses) and a locally unique
324 CR-LSP ID to that LSR. The first two bytes carry
328 the CR-LSPID, and the remaining 4 bytes carry
329 the Router ID. The LSPID is useful in network
330 management, in CR-LSP repair, and in using
331 an already established CR-LSP as a hop in
334 For LSPs signaled using RSVP-TE, the LSP ID is
335 defined as a 16-bit (2 byte) identifier used
336 in the SENDER_TEMPLATE and the FILTER_SPEC
337 that can be changed to allow a sender to
338 share resources with itself. The length of this
339 object should only be 2 or 6 bytes. If the length
340 of this octet string is 2 bytes, then it must
341 identify an RSVP-TE LSPID, or it is 6 bytes,
342 it must contain a CR-LDP LSPID."
344 "RSVP-TE: Extensions to RSVP for LSP Tunnels,
347 Constraint-Based LSP Setup using LDP,
349 SYNTAX OCTET STRING (SIZE (2|6))
351 MplsLspType ::= TEXTUAL-CONVENTION
354 "Types of Label Switch Paths (LSPs)
355 on a Label Switching Router (LSR) or a
356 Label Edge Router (LER) are:
358 unknown(1) -- if the LSP is not known
359 to be one of the following.
361 terminatingLsp(2) -- if the LSP terminates
362 on the LSR/LER, then this
364 which ends on the LSR/LER,
366 originatingLsp(3) -- if the LSP originates
367 from this LSR/LER, then
368 this is an ingressing LSP
369 which is the head-end of
372 crossConnectingLsp(4) -- if the LSP ingresses
373 and egresses on the LSR,
375 cross-connecting on that
384 crossConnectingLsp(4)
387 MplsOwner ::= TEXTUAL-CONVENTION
390 "This object indicates the local network
391 management subsystem that originally created
392 the object(s) in question. The values of
393 this enumeration are defined as follows:
395 unknown(1) - the local network management
396 subsystem cannot discern which
397 component created the object.
399 other(2) - the local network management
400 subsystem is able to discern which component
401 created the object, but the component is not
402 listed within the following choices,
403 e.g., command line interface (cli).
405 snmp(3) - The Simple Network Management Protocol
406 was used to configure this object initially.
408 ldp(4) - The Label Distribution Protocol was
409 used to configure this object initially.
411 crldp(5) - The Constraint-Based Label Distribution
412 Protocol was used to configure this object
415 rsvpTe(6) - The Resource Reservation Protocol was
416 used to configure this object initially.
418 policyAgent(7) - A policy agent (perhaps in
419 combination with one of the above protocols) was
420 used to configure this object initially.
422 An object created by any of the above choices
423 MAY be modified or destroyed by the same or a
438 MplsPathIndexOrZero ::= TEXTUAL-CONVENTION
441 "A unique identifier used to identify a specific
442 path used by a tunnel. A value of 0 (zero) means
443 that no path is in use."
444 SYNTAX Unsigned32(0..4294967295)
446 MplsPathIndex ::= TEXTUAL-CONVENTION
449 "A unique value to index (by Path number) an
451 SYNTAX Unsigned32(1..4294967295)
453 MplsRetentionMode ::= TEXTUAL-CONVENTION
456 "The label retention mode which specifies whether
457 an LSR maintains a label binding for a FEC
458 learned from a neighbor that is not its next hop
461 If the value is conservative(1) then advertised
462 label mappings are retained only if they will be
463 used to forward packets, i.e., if label came from
466 If the value is liberal(2) then all advertised
467 label mappings are retained whether they are from
468 a valid next hop or not."
470 "Multiprotocol Label Switching Architecture,
473 LDP Specification, RFC3036, Section 2.6.2."
481 MplsTunnelAffinity ::= TEXTUAL-CONVENTION
484 "Describes the configured 32-bit Include-any,
485 include-all, or exclude-all constraint for
486 constraint-based link selection."
488 "RSVP-TE: Extensions to RSVP for LSP Tunnels,
489 RFC3209, Section 4.7.4."
490 SYNTAX Unsigned32(0..4294967295)
492 MplsTunnelIndex ::= TEXTUAL-CONVENTION
495 "A unique index into mplsTunnelTable.
496 For tunnels signaled using RSVP, this value
497 should correspond to the RSVP Tunnel ID
498 used for the RSVP-TE session."
499 SYNTAX Unsigned32 (0..65535)
501 MplsTunnelInstanceIndex ::= TEXTUAL-CONVENTION
504 "The tunnel entry with instance index 0
505 should refer to the configured tunnel
506 interface (if one exists).
508 Values greater than 0, but less than or
509 equal to 65535, should be used to indicate
510 signaled (or backup) tunnel LSP instances.
511 For tunnel LSPs signaled using RSVP,
512 this value should correspond to the
513 RSVP LSP ID used for the RSVP-TE
516 Values greater than 65535 apply to FRR
518 SYNTAX Unsigned32(0|1..65535|65536..4294967295)
520 TeHopAddressType ::= TEXTUAL-CONVENTION
523 "A value that represents a type of address for a
524 Traffic Engineered (TE) Tunnel hop.
526 unknown(0) An unknown address type. This value
527 MUST be used if the value of the
528 corresponding TeHopAddress object is a
532 zero-length string. It may also be
533 used to indicate a TeHopAddress which
534 is not in one of the formats defined
537 ipv4(1) An IPv4 network address as defined by
538 the InetAddressIPv4 TEXTUAL-CONVENTION
541 ipv6(2) A global IPv6 address as defined by
542 the InetAddressIPv6 TEXTUAL-CONVENTION
545 asnumber(3) An Autonomous System (AS) number as
546 defined by the TeHopAddressAS
549 unnum(4) An unnumbered interface index as
550 defined by the TeHopAddressUnnum
553 lspid(5) An LSP ID for TE Tunnels
554 (RFC3212) as defined by the
555 MplsLSPID TEXTUAL-CONVENTION.
557 Each definition of a concrete TeHopAddressType
558 value must be accompanied by a definition
559 of a TEXTUAL-CONVENTION for use with that
562 To support future extensions, the TeHopAddressType
563 TEXTUAL-CONVENTION SHOULD NOT be sub-typed in
564 object type definitions. It MAY be sub-typed in
565 compliance statements in order to require only a
566 subset of these address types for a compliant
569 Implementations must ensure that TeHopAddressType
570 objects and any dependent objects
571 (e.g., TeHopAddress objects) are consistent.
572 An inconsistentValue error must be generated
573 if an attempt to change a TeHopAddressType
574 object would, for example, lead to an
575 undefined TeHopAddress value that is
576 not defined herein. In particular,
577 TeHopAddressType/TeHopAddress pairs
578 must be changed together if the address
579 type changes (e.g., from ipv6(2) to ipv4(1))."
584 "TEXTUAL-CONVENTIONs for Internet Network
587 Constraint-Based LSP Setup using LDP,
599 TeHopAddress ::= TEXTUAL-CONVENTION
602 "Denotes a generic Tunnel hop address,
603 that is, the address of a node which
604 an LSP traverses, including the source
605 and destination nodes. An address may be
606 very concrete, for example, an IPv4 host
607 address (i.e., with prefix length 32);
608 if this IPv4 address is an interface
609 address, then that particular interface
610 must be traversed. An address may also
611 specify an 'abstract node', for example,
612 an IPv4 address with prefix length
613 less than 32, in which case, the LSP
614 can traverse any node whose address
615 falls in that range. An address may
616 also specify an Autonomous System (AS),
617 in which case the LSP can traverse any
618 node that falls within that AS.
620 A TeHopAddress value is always interpreted within
621 the context of an TeHopAddressType value. Every
622 usage of the TeHopAddress TEXTUAL-CONVENTION
623 is required to specify the TeHopAddressType object
624 which provides the context. It is suggested that
625 the TeHopAddressType object is logically registered
626 before the object(s) which use the TeHopAddress
627 TEXTUAL-CONVENTION if they appear in the
630 The value of a TeHopAddress object must always be
634 consistent with the value of the associated
635 TeHopAddressType object. Attempts to set a
636 TeHopAddress object to a value which is
637 inconsistent with the associated TeHopAddressType
638 must fail with an inconsistentValue error."
639 SYNTAX OCTET STRING (SIZE (0..32))
641 TeHopAddressAS ::= TEXTUAL-CONVENTION
644 "Represents a two or four octet AS number.
645 The AS number is represented in network byte
646 order (MSB first). A two-octet AS number has
647 the two MSB octets set to zero."
649 "Textual Conventions for Internet Network
650 Addresses, [RFC3291]. The
651 InetAutonomousSystemsNumber TEXTUAL-CONVENTION
652 has a SYNTAX of Unsigned32, whereas this TC
653 has a SYNTAX of OCTET STRING (SIZE (4)).
654 Both TCs represent an autonomous system number
655 but use different syntaxes to do so."
656 SYNTAX OCTET STRING (SIZE (4))
658 TeHopAddressUnnum ::= TEXTUAL-CONVENTION
661 "Represents an unnumbered interface:
663 octets contents encoding
664 1-4 unnumbered interface network-byte order
666 The corresponding TeHopAddressType value is
668 SYNTAX OCTET STRING(SIZE(4))