draft-ietf-mpls-tc-mib-05.txt   draft-ietf-mpls-tc-mib-06.txt 
Network Working Group Thomas D. Nadeau Network Working Group T. Nadeau
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Expires: May 2003 Joan Cucchiara Expires: September 2003 J. Cucchiara
Consultant Artel
Cheenu Srinivasan (Editors)
Parama Networks, Inc.
Arun Viswanathan
Force10 Networks, Inc.
Hans Sjostrand
ipUnplugged
November 2002 March 2003
Definitions of Textual Conventions for Multiprotocol Label Definitions of Textual Conventions for Multiprotocol Label
Switching (MPLS) Management Switching (MPLS) Management
<draft-ietf-mpls-tc-mib-05.txt> <draft-ietf-mpls-tc-mib-06.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. Internet-Drafts are all provisions of Section 10 of RFC 2026. Internet-Drafts are
working documents of the Internet Engineering Task Force (IETF), its working documents of the Internet Engineering Task Force (IETF), its
areas, and its working groups. Note that other groups may also areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts. distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 1, line 45 skipping to change at page 1, line 40
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
Distribution of this document is unlimited. Please send comments to Distribution of this document is unlimited. Please send comments to
the Multiprotocol Label Switching (mpls) Working Group, mpls@uu.net. the Multiprotocol Label Switching (mpls) Working Group, mpls@uu.net.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
This memo describes Textual Conventions for use in definitions of This memo defines a Management Information Base (MIB) module which
management information for Multiprotocol Label Switching (MPLS) contains Textual Conventions to represent commonly used Mulitprotocol
networks. Label Switching (MPLS) management information. The intent is that
these TEXTUAL CONVENTIONS (TCs) will be imported and used in MPLS
related MIB modules that would otherwise define their own
representations.
Table of Contents Table of Contents
1 Introduction ................................................. 3 1 Introduction ................................................. 4
2 The SNMP Management Framework ................................ 3 2 The Internet-Standard Management Framework ................... 4
3 MPLS Textual Conventions MIB Definitions ..................... 4 3 MPLS Textual Conventions MIB Definitions ..................... 4
4 References ................................................... 15 4 Normative References ......................................... 18
5 Security Considerations ...................................... 16 5 Informative References ....................................... 19
6 Authors' Addresses ........................................... 17 6 Security Considerations ...................................... 19
7 Full Copyright Statement ..................................... 17 7 IANA Considerations .......................................... 19
8 Contributors ................................................. 19
9 Intellectual Property Notice ................................. 20
10 Authors' Addresses .......................................... 21
11 Full Copyright Statement .................................... 21
1. Introduction 1. Introduction
This document defines a MIB which contains Textual Conventions for This document defines a MIB module which contains Textual Conventions
use in definitions of management information for Multi-Protocol Label for Multi-Protocol Label Switching (MPLS) networks. These Textual
Switching (MPLS) networks. Conventions should be imported by MIB modules which manage MPLS
networks.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [21]. document are to be interpreted as described in RFC 2119 [RFC2119].
For an introduction to the concepts of MPLS, see [RFC3031]. For an introduction to the concepts of MPLS, see [RFC3031].
2. The SNMP Management Framework 2. The Internet-Standard Management Framework
The SNMP Management Framework presently consists of five major
components:
o An overall architecture, described in RFC 2571 [RFC2571].
o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in
STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
1215 [RFC1215]. The second version, called SMIv2, is described
in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and
STD 58, RFC 2580 [RFC2580].
o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [RFC1157]. A second version of
the SNMP message protocol, which is not an Internet standards
track protocol, is called SNMPv2c and described in RFC 1901
[RFC1901] and RFC 1906 [RFC1906]. The third version of the
message protocol is called SNMPv3 and described in RFC 1906
[RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574].
o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [RFC1157]. A second set of
protocol operations and associated PDU formats is described in
RFC 1905 [RFC1905].
o A set of fundamental applications described in RFC 2573
[RFC2573] and the view-based access control mechanism described
in RFC 2575 [RFC2575].
A more detailed introduction to the current SNMP Management Framework For a detailed overview of the documents that describe the current
can be found in RFC 2570 [RFC2570]. Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. MIB objects are generally
defined using the mechanisms defined in the SMI. accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
This memo specifies a MIB module that is compliant to the SMIv2. A Structure of Management Information (SMI). This memo specifies a MIB
MIB conforming to the SMIv1 can be produced through the appropriate module that is compliant to the SMIv2, which is described in STD 58,
translations. The resulting translated MIB must be semantically RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
equivalent, except where objects or events are omitted because no [RFC2580].
translation is possible. Some machine readable information in SMIv2
will be converted into textual descriptions in SMIv1 during the
translation process. However, this loss of machine readable
information is not considered to change the semantics of the MIB.
3. MPLS Textual Conventions MIB Definitions 3. MPLS Textual Conventions MIB Definitions
MPLS-TC-MIB DEFINITIONS ::= BEGIN MPLS-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, Unsigned32, Integer32, transmission MODULE-IDENTITY, Unsigned32, Integer32, transmission
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; FROM SNMPv2-TC;
mplsTCMIB MODULE-IDENTITY mplsTCMIB MODULE-IDENTITY
LAST-UPDATED "200211031200Z" -- 3 Nov 2002 12:00:00 GMT LAST-UPDATED "200303171200Z" -- 17 March 2003 12:00:00 GMT
ORGANIZATION ORGANIZATION
"IETF Multiprotocol Label Switching (MPLS) Working "IETF Multiprotocol Label Switching (MPLS) Working
Group." Group."
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
tnadeau@cisco.com tnadeau@cisco.com
Joan Cucchiara Joan Cucchiara
Consultant Artel
jcucchiara@mindspring.com jcucchiara@artel.com
Cheenu Srinivasan Cheenu Srinivasan
Parama Networks, Inc. Parama Networks, Inc.
cheenu@paramanet.com cheenu@paramanet.com
Arun Viswanathan Arun Viswanathan
Force10 Networks, Inc. Force10 Networks, Inc.
arun@force10networks.com arun@force10networks.com
Hans Sjostrand Hans Sjostrand
ipUnplugged ipUnplugged
hans@ipunplugged.com hans@ipunplugged.com
Kireeti Kompella
Juniper Networks
kireeti@juniper.net
Email comments to the MPLS WG Mailing List at Email comments to the MPLS WG Mailing List at
mpls@uu.net." mpls@uu.net."
DESCRIPTION DESCRIPTION
"This MIB module defines Textual Conventions "Copyright (C) The Internet Society (2003). This
for use in definitions of management version of this MIB module is part of RFCXXX; see
information for Multi-Protocol Label Switching the RFC itself for full legal notices.
(MPLS) networks."
REVISION "200211031200Z" -- 3 Nov 2002 12:00:00 GMT This MIB module defines Textual Conventions
for concepts used in Multi-Protocol Label
Switching (MPLS) networks."
REVISION "200303171200Z" -- 17 March 2003 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial version published as part of RFC XXXX." "Initial version published as part of RFC XXXX."
::= { mplsMIB 1 } ::= { mplsMIB 1 }
-- This object identifier needs to be assigned by IANA. -- This object identifier needs to be assigned by IANA.
-- Since mpls has been assigned an ifType of 166 we recommend -- Since mpls has been assigned an ifType of 166 we recommend
-- that this OID be 166 as well. -- that this OID be 166 as well.
mplsMIB OBJECT IDENTIFIER mplsMIB OBJECT IDENTIFIER
::= { transmission XXX } ::= { transmission XXX }
-- Textual Conventions are in alphabetical order.
MplsAtmVcIdentifier ::= TEXTUAL-CONVENTION MplsAtmVcIdentifier ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A Label Switching Router (LSR) that "A Label Switching Router (LSR) that
creates LDP sessions on ATM interfaces creates LDP sessions on ATM interfaces
uses the VCI or VPI/VCI field to hold the uses the VCI or VPI/VCI field to hold the
LDP Label. LDP Label.
VCI values MUST NOT be in the 0-31 range. VCI values MUST NOT be in the 0-31 range.
skipping to change at page 5, line 52 skipping to change at page 6, line 32
configured for the Control VC. configured for the Control VC.
If a value from 0 to 31 is used for a VCI If a value from 0 to 31 is used for a VCI
the management entity controlling the LDP the management entity controlling the LDP
subsystem should reject this with an subsystem should reject this with an
inconsistentValue error. Also, if inconsistentValue error. Also, if
the value of 32 is used for a VC which is the value of 32 is used for a VC which is
NOT the Control VC, this should NOT the Control VC, this should
result in an inconsistentValue error." result in an inconsistentValue error."
REFERENCE REFERENCE
"[RFC3035] Davie, B., Lawerence J., McCloghrie, K., "MPLS using LDP and ATM VC Switching, RFC3035."
Rosen, E., Swallow G., Rekhter, Y., and
P. Doolan, 'MPLS using LDP and ATM VC Switching',
RFC 3035, January 2001."
SYNTAX Integer32 (32..65535) SYNTAX Integer32 (32..65535)
MplsBitRate ::= TEXTUAL-CONVENTION MplsBitRate ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An estimate of bandwidth in units of 1,000 bits per "If the value of this object is greater than zero,
second. If this object reports a value of 'n' then then this represents the bandwidth of this MPLS
the rate of the object is somewhere in the range of interface (or Label Switched Path) in units of
'n-500' to 'n+499'. For objects which do not vary '1,000 bits per second'.
in bit rate, or for those where no accurate
estimation can be made, this object should contain The value, when greater than zero, represents the
the nominal bit rate. A value of 0 indicates best bandwidth of this MPLS interface (rounded to the
effort treatment." nearest 1,000) in units of 1,000 bits per second.
SYNTAX Integer32 (0|500..2147483647) If the bandwidth of the MPLS interface is between
((n * 1000) - 500) and ((n * 1000) + 499), the value
of this object is n, such that n > 0.
If the value of this object is 0 (zero), this
means that the traffic over this MPLS interface is
considered to be best effort."
SYNTAX Unsigned32 (0|1..4294967295)
MplsBurstSize ::= TEXTUAL-CONVENTION MplsBurstSize ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets of MPLS data that the stream "The number of octets of MPLS data that the stream
may send back-to-back without concern for policing. may send back-to-back without concern for policing.
The value of zero indicates that an implementation The value of zero indicates that an implementation
does not support Burst Size." does not support Burst Size."
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
MplsExtendedTunnelId ::= TEXTUAL-CONVENTION MplsExtendedTunnelId ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A unique identifier for an MPLS Tunnel. This may "A unique identifier for an MPLS Tunnel. This may
represent an IPv4 address of the ingress or egress represent an IPv4 address of the ingress or egress
LSR for the tunnel. This value is derived from the LSR for the tunnel. This value is derived from the
Extended Tunnel Id in RSVP or the Ingress Router ID Extended Tunnel Id in RSVP or the Ingress Router ID
for CR-LDP." for CR-LDP."
REFERENCE REFERENCE
"[RFC3209] Awduche, D., et al., 'RSVP-TE: Extensions "RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209.
to RSVP for LSP Tunnels', RFC 3209, December 2001.
[RFC3212] Jamoussi, B., et al., 'Constraint-Based Constraint-Based LSP Setup using LDP, RFC 3212."
LSP Setup using LDP', RFC 3212, January 2002."
SYNTAX Unsigned32 SYNTAX Unsigned32
MplsOwner ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The entity that originally created the object in
question. The values of this enumeration are
defined as follows:
other(1) - This is used when an entity which has not
been enumerated in this textual convention but
which is known by the agent.
snmp(2) - The Simple Network Management Protocol was
used to configure this object initially.
ldp(3 - The Label Distribution Protocol was used to
configure this object initially.
rsvp(4) - The Resource Reservation Protocol was used
to configure this object initially.
crldp(5) - The Constraint-Based Label Distribution
Protocol was used to configure this object
initially.
policyAgent(6) - A policy agent (perhaps in
combination with one of the above protocols) was
used to configure this object initially.
unknown(7) - the agent cannot discern which
component created the object.
An object created by the ldp(3), rsvp(4), crldp(5)
or policyAgent(6) MAY be modified through operator
intervention using other(1) or snmp(2). In
particular, operators may bring rows in and
out of service or modify their values.
In all other respects, the MplsOwner is
the only source allowed to modify the status of
the object.
Agents receiving requests which violate these
guidelines MUST return an inconsistentValue(12)
error."
SYNTAX INTEGER {
other(1),
snmp(2),
ldp(3),
rsvp(4),
crldp(5),
policyAgent(6),
unknown (7)
}
MplsLSPID ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A unique identifier within an MPLS network that is
assigned to each LSP. This is assigned at the head
end of the LSP and can be used by all LSRs
to identify this LSP. This value is piggybacked by
the signaling protocol when this LSP is signaled
within the network. This identifier can then be
used at each LSR to identify which labels are being
swapped to other labels for this LSP. This object
can also be used to disambiguate LSPs that
share the same RSVP sessions between the same
source and destination.
For LSPs established using CR-LDP, the LSPID is
composed of the ingress LSR Router ID (or any of
its own IPv4 addresses) and a locally unique
CR-LSP ID to that LSR. The first two bytes carry
the CR-LSPID, and the remaining 4 bytes carry
the Router ID. The LSPID is useful in network
management, in CR-LSP repair, and in using
an already established CR-LSP as a hop in an ER-TLV.
For LSPs signaled using RSVP-TE, the LSP ID is
defined as a 16-bit (2 byte) identifier used
in the SENDER_TEMPLATE and the FILTER_SPEC
that can be changed to allow a sender to
share resources with itself. The length of this
object should only be 2 or 6 bytes. If the length
of this octet string is 2 bytes, then it must
identify an RSVP-TE LSPID, or it is 6 bytes,
it must contain a CR-LDP LSPID."
REFERENCE
"See [RFC3209] for RSVP-TE LSPID and [RFC3212] for
LSPID in CR-LDP."
SYNTAX OCTET STRING (SIZE (2|6))
MplsLabel ::= TEXTUAL-CONVENTION MplsLabel ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents an MPLS label as defined in "This value represents an MPLS label as defined in
[RFC3031], [RFC3032], [RFC3034], [RFC3035] and (RFC3031), (RFC3032), (RFC3034), (RFC3035) and
[CCAMP-ARCH]. (CCAMP-ARCH).
The label contents are specific to the label being The label contents are specific to the label being
represented, such as: represented, such as:
* The label carried in an MPLS shim header * The label carried in an MPLS shim header
(for LDP this is the Generic Label) is a 20-bit (for LDP this is the Generic Label) is a 20-bit
number represented by 4 octets. Bits 0-19 contain number represented by 4 octets. Bits 0-19 contain
a label or a reserved label value. Bits 20-31 a label or a reserved label value. Bits 20-31
MUST be zero. MUST be zero.
skipping to change at page 10, line 26 skipping to change at page 9, line 28
* For an ATM label the lower 16-bits represents the * For an ATM label the lower 16-bits represents the
VCI, the next 12-bits represents the VPI and the VCI, the next 12-bits represents the VPI and the
remaining bits MUST be zero. remaining bits MUST be zero.
* The Generalized-MPLS (GMPLS) label contains a * The Generalized-MPLS (GMPLS) label contains a
value greater than 2^24-1 and used in GMPLS value greater than 2^24-1 and used in GMPLS
as defined in [CCAMP-ARCH]." as defined in [CCAMP-ARCH]."
REFERENCE REFERENCE
"[RFC3031] Multiprotocol Label Switching "Multiprotocol Label Switching Architecture,
Architecture, Rosen et al., RFC 3031, August 1999. RFC 3031.
[RFC3032] MPLS Label Stack Encoding, Rosen et al., MPLS Label Stack Encoding, RFC 3032.
RFC 3032, January 2001.
[RFC3034] Use of Label Switching on Frame Relay Use of Label Switching on Frame Relay Networks,
Networks, Conta et al., RFC 3034, January 2001. RFC 3034.
[RFC3035] MPLS using LDP and ATM VC Switching, MPLS using LDP and ATM VC Switching, RFC 3035.
Davie et al., RFC 3035, January 2001.
[CCAMP-ARCH] Generalized Multi-Protocol Label Generalized Multi-Protocol Label Switching
Switching (GMPLS) Architecture, Mannie (Editor), (GMPLS) Architecture,
draft-ietf-ccamp-gmpls-architecture-02.txt, draft-ietf-ccamp-gmpls-architecture-02.txt."
March 2002."
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
MplsLabelDistributionMethod ::= TEXTUAL-CONVENTION MplsLabelDistributionMethod ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The label distribution method which is also called "The label distribution method which is also called
the label advertisement mode (see LDP Specification). the label advertisement mode (see LDP Specification).
Each interface on an LSR is configured to operate Each interface on an LSR is configured to operate
in either Downstream Unsolicited or Downstream in either Downstream Unsolicited or Downstream
on Demand." on Demand."
REFERENCE REFERENCE
"[RFC3031] Multiprotocol Label Switching "Multiprotocol Label Switching Architecture,
Architecture, Rosen et al., RFC 3031, August 1999. RFC 3031.
[RFC3036] LDP Specification, Andersson, L., et. al., LDP Specification, RFC 3036, Section 2.6.3."
RFC 3036, Section 2.6.3., January 2001."
SYNTAX INTEGER { SYNTAX INTEGER {
downstreamOnDemand(1), downstreamOnDemand(1),
downstreamUnsolicited(2) downstreamUnsolicited(2)
} }
MplsLdpIdentifier ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d.1d.1d.1d:2d"
STATUS current
DESCRIPTION
"The LDP identifier is a six octet
quantity which is used to identify a
Label Switching Router (LSR) label space.
The first four octets identify the LSR and must be
a globally unique value, such as a 32-bit router ID
assigned to the LSR, and the last two octets
identify a specific label space within the LSR."
SYNTAX OCTET STRING (SIZE (6))
MplsLsrIdentifier ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The Label Switching Router (LSR) identifier is the
first 4 bytes of the Label Distribution Protocol
(LDP) identifier."
SYNTAX OCTET STRING (SIZE (4))
MplsLdpLabelType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The Layer 2 label types which are defined for MPLS
LDP and/or CR-LDP are generic(1), atm(2), or
frameRelay(3)."
SYNTAX INTEGER {
generic(1),
atm(2),
frameRelay(3)
}
MplsLSPID ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A unique identifier within an MPLS network that is
assigned to each LSP. This is assigned at the head
end of the LSP and can be used by all LSRs
to identify this LSP. This value is piggybacked by
the signaling protocol when this LSP is signaled
within the network. This identifier can then be
used at each LSR to identify which labels are being
swapped to other labels for this LSP. This object
can also be used to disambiguate LSPs that
share the same RSVP sessions between the same
source and destination.
For LSPs established using CR-LDP, the LSPID is
composed of the ingress LSR Router ID (or any of
its own IPv4 addresses) and a locally unique
CR-LSP ID to that LSR. The first two bytes carry
the CR-LSPID, and the remaining 4 bytes carry
the Router ID. The LSPID is useful in network
management, in CR-LSP repair, and in using
an already established CR-LSP as a hop in an ER-TLV.
For LSPs signaled using RSVP-TE, the LSP ID is
defined as a 16-bit (2 byte) identifier used
in the SENDER_TEMPLATE and the FILTER_SPEC
that can be changed to allow a sender to
share resources with itself. The length of this
object should only be 2 or 6 bytes. If the length
of this octet string is 2 bytes, then it must
identify an RSVP-TE LSPID, or it is 6 bytes,
it must contain a CR-LDP LSPID."
REFERENCE
"RSVP-TE: Extensions to RSVP for LSP Tunnels,
RFC 3209.
Constraint-Based LSP Setup using LDP, RFC 3212."
SYNTAX OCTET STRING (SIZE (2|6))
MplsLspType ::= TEXTUAL-CONVENTION MplsLspType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Types types of Label Switch Paths (LSPs) "Types types of Label Switch Paths (LSPs)
on an Label Switching Router (LSR) are: on an Label Switching Router (LSR) ir a
Label Edge Router (LER) are:
unknown(1) -- if the LSP is not known unknown(1) -- if the LSP is not known
to be one of the following. to be one of the following.
terminatingLsp(2) -- if the LSP terminates terminatingLsp(2) -- if the LSP terminates
on the LSR, then this on the LSR/LER, then this
is an ingressing LSP is an egressing LSP
which ends on the LSR, which ends on the LSR/LER,
originatingLsp(3) -- if the LSP originates originatingLsp(3) -- if the LSP originates
from the LSR, then this from this LSR/LER, then this
is an egressing LSP which is is an ingressing LSP which is
the head-end of the LSP, the head-end of the LSP,
crossConnectingLsp(4) -- if the LSP ingresses crossConnectingLsp(4) -- if the LSP ingresses
and egresses on the LSR, and egresses on the LSR,
then it is cross-connecting then it is cross-connecting
on that LSR." on that LSR."
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(1), unknown(1),
terminatingLsp(2), terminatingLsp(2),
originatingLsp(3), originatingLsp(3),
crossConnectingLsp(4) crossConnectingLsp(4)
} }
MplsLsrIndex ::= TEXTUAL-CONVENTION MplsOwner ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a generic index used throughout the "This object indicates the local network management
MPLS-LSR-MIB as a general index in the subsystem that originally created the object(s) in
mplsInSegmentTable, mplsOutSegmentTable question. The values of this enumeration are
and mplsXCTable." defined as follows:
SYNTAX OCTET STRING (SIZE(1..34))
unknown(1) - the local network management
subsystem cannot discern which
component created the object.
other(2) - the local network management
subsystem is able to discern which component
created the object, but the component is not
listed within the following choices,
e.g. command line interface (cli).
snmp(3) - The Simple Network Management Protocol was
used to configure this object initially.
ldp(4) - The Label Distribution Protocol was used to
configure this object initially.
crldp(5) - The Constraint-Based Label Distribution
Protocol was used to configure this object
initially.
rsvpTe(6) - The Resource Reservation Protocol was used
to configure this object initially.
policyAgent(7) - A policy agent (perhaps in
combination with one of the above protocols) was
used to configure this object initially.
An object created by any of the above choices
MAY be modified or destroyed by the same or a
different choice."
SYNTAX INTEGER {
unknown(1),
other(2),
snmp(3),
ldp(4),
crldp(5),
rsvpTe(6),
policyAgent(7)
}
MplsPathIndexOrZero ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A unique identifier used to identify a specific path
used by a tunnel. A value of 0 (zero) means that
no path is in use."
SYNTAX Unsigned32
MplsPathIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A unique value to index (by Path number) an entry
in a table."
SYNTAX Unsigned32(1..4294967295)
MplsRetentionMode ::= TEXTUAL-CONVENTION MplsRetentionMode ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The label retention mode which specifies whether "The label retention mode which specifies whether
an LSR maintains a label binding for a FEC learned an LSR maintains a label binding for a FEC learned
from a neighbor that is not its next hop for the from a neighbor that is not its next hop for the
FEC. FEC.
If the value is conservative(1) then advertised If the value is conservative(1) then advertised
label mappings are retained only if they will be label mappings are retained only if they will be
used to forward packets, i.e. if label came from used to forward packets, i.e. if label came from
a valid next hop. a valid next hop.
If the value is liberal(2) then all advertised label If the value is liberal(2) then all advertised label
mappings are retained whether they are from a mappings are retained whether they are from a
valid next hop or not." valid next hop or not."
REFERENCE REFERENCE
"[RFC3031] Multiprotocol Label Switching "Multiprotocol Label Switching Architecture,
Architecture, Rosen et al., RFC 3031, August 1999. RFC 3031.
[RFC3036] LDP Specification, Andersson, L., et. al., LDP Specification, RFC 3036, Section 2.6.2."
RFC 3036, Section 2.6.2., January 2001."
SYNTAX INTEGER { SYNTAX INTEGER {
conservative(1), conservative(1),
liberal(2) liberal(2)
} }
MplsLdpIdentifier ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The LDP identifier is a six octet quantity which is
used to identify an Label Switching Router (LSR)
label space.
The first four octets identify the LSR and must be
a globally unique value, such as a 32-bit router ID
assigned to the LSR, and the last two octets
identify a specific label space within the LSR."
SYNTAX OCTET STRING (SIZE (6))
MplsLdpLabelType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The Layer 2 label types which are defined for MPLS
LDP and/or CR-LDP are generic(1), atm(2), or
frameRelay(3)."
SYNTAX INTEGER {
generic(1),
atm(2),
frameRelay(3)
}
MplsLsrIdentifier ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The Label Switching Router (LSR) identifier is the
first 4 bytes of the Label Distribution Protocol
(LDP) identifier."
SYNTAX OCTET STRING (SIZE (4))
MplsPathIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A unique value to index (by Path number) an entry
in a table."
SYNTAX Unsigned32(1..4294967295)
MplsPathIndexOrZero ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A unique identifier used to identify a specific path
used by a tunnel. A value of 0 (zero) means that
no path is in use."
SYNTAX Unsigned32
MplsTunnelAffinity ::= TEXTUAL-CONVENTION MplsTunnelAffinity ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes the configured 32-bit Include-any, "Describes the configured 32-bit Include-any,
include-all, or exclude-all constraint for include-all, or exclude-all constraint for
constraint-based link selection." constraint-based link selection."
REFERENCE REFERENCE
"See section 4.7.4 in [RFC3209]." "RSVP-TE: Extensions to RSVP for LSP Tunnels,
RFC 3209, Section 4.7.4."
SYNTAX Unsigned32 SYNTAX Unsigned32
MplsTunnelIndex ::= TEXTUAL-CONVENTION MplsTunnelIndex ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A unique index into mplsTunnelTable. "A unique index into mplsTunnelTable.
For tunnels signaled using RSVP, this value For tunnels signaled using RSVP, this value
should correspond to the RSVP destination should correspond to the RSVP destination
port used for the RSVP-TE session." port used for the RSVP-TE session."
SYNTAX Integer32 (1..65535) SYNTAX Unsigned32 (0..65535)
MplsTunnelInstanceIndex ::= TEXTUAL-CONVENTION MplsTunnelInstanceIndex ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Instance index into mplsTunnelTable. The "Instance index into mplsTunnelTable. The
tunnel entry with instance index 0 should tunnel entry with instance index 0 should
refer to the configured tunnel interface refer to the configured tunnel interface
(if one exists), and values greater an 0 (if one exists), and values greater an 0 but
less than or equal to 65535
should be used to indicate signaled (or backup) should be used to indicate signaled (or backup)
tunnel LSP instances. For tunnel LSPs signaled using tunnel LSP instances. For tunnel LSPs signaled using
RSVP, this value should correspond to the RSVP, this value should correspond to the
RSVP source port used for the RSVP-TE session." RSVP source port used for the RSVP-TE session.
SYNTAX Unsigned32 (0..65535)
END Values greater than 65535 apply to FRR detour
instances."
SYNTAX Unsigned32
4. References TeHopAddressType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A value that represents a type of address a Traffic
Engineered (TE) Tunnel hop.
[RFC3212] Jamoussi, B., (editor), et. al. "Constraint-Based LSP Setup unknown(0) An unknown address type. This value
using LDP", RFC 3212, January 2002. MUST be used if the value of the
corresponding TeHopAddress object is a
zero-length string. It may also be used
to indicate a TeHopAddress which is not
in one of the formats defined below.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., ipv4(1) An IPv4 network address as defined by
Swallow, G., "RSVP-TE: Extensions to RSVP for LSP Tunnels", the InetAddressIPv4 TEXTUAL-CONVENTION
RFC 3209, December 2001. (RFC 3291).
[RFC3031] Rosen, E., Viswananthan, A., and R. Callon, "Multiprotocol ipv6(2) A global IPv6 address as defined by the
Label Switching Architecture", RFC 3031, January 2001. InetAddressIPv6 TEXTUAL-CONVENTION (RFC 3291).
[RFC3032] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., asnumber(3) An Autonomous System (AS) number as defined
Federokow, G., Li, T., and A. Conta, "MPLS Label Stack by the TeHopAddressAS TEXTUAL-CONVENTION.
Encoding", RFC 3032, January 2001.
[RFC3034] Conta, A., Doolan, P., and A. Malis, "Use of Label Switching unnum(4) An unnumbered interface index as defined by
on Frame Relay Networks Specification", RFC 3034, January the TeHopAddressUnnum TEXTUAL-CONVETION.
2001.
[RFC3035] Davie, B., Lawrence, J., McCloghrie, K., Rosen, E., Swallow, lspid(5) An LSP ID for CR-LDP Tunnels (RFC 3212) as
G., Rekhter, Y., and P. Doolan, "MPLS using LDP and ATM VC defined by the MplsLSPID TEXTUAL-CONVENTION.
Switching", RFC 3035, January 2001.
[RFC3036] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and B. Each definition of a concrete TeHopAddress value must
Thomas, "LDP Specification", RFC 3036, January 2001. be accompanied by a definition of a textual convention
for use with that TeHopAddressType.
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture To support future extensions, the TeHopAddressType
for Describing SNMP Management Frameworks", RFC 2571, April TEXTUAL-CONVENTION SHOULD NOT be sub-typed in object
1999. type definitions. It MAY be sub-typed in compliance
statements in order to require only a subset of these
address types for a compliant implementation.
[RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification Implementations must ensure that TeHopAddressType objects
of Management Information for TCP/IP-based Internets", STD and any dependent objects (e.g. TeHopAddress objects) are
16, RFC 1155, May 1990. consistent. An inconsistentValue error must be generated
if an attempt to change a TeHopAddressType object would,
for example, lead to an undefined TeHopAddress value.
In particular, TeHopAddressType/TeHopAddress pairs
must be changed together if the address type changes
(e.g. from ipv6(3) to ipv4(2))."
REFERENCE
"Textual Conventions for Internet Network
Addresses, RFC3291.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD Constraint-Based LSP Setup using LDP,
16, RFC 1212, March 1991. RFC3212."
[RFC1215] M. Rose, "A Convention for Defining Traps for use with the SYNTAX INTEGER {
SNMP", RFC 1215, March 1991. unknown(0),
ipv4(1),
ipv6(2),
asnumber(3),
unnum(4),
lspid(5)
}
TeHopAddress ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Denotes a generic Tunnel hop address.
A TeHopAddress value is always interpreted within the
context of an TeHopAddressType value. Every usage of the
TeHopInetAddress TEXTUAL-CONVENTION is required to specify
the TeHopAddressType object which provides the context.
It is suggested that the TeHopAddressType object is
logically registered before the object(s) which use the
TeHopAddress TEXTUAL-CONVENTION if they appear in the
same logical row.
The value of a TeHopAddress object must always be
consistent with the value of the associated
TeHopAddressType object. Attempts to set a TeHopAddress
object to a value which is inconsistent with the
associated TeHopAddressType must fail with an
inconsistentValue error.
When this TEXTUAL-CONVENTION is used as the syntax of an
index object, there may be issues which the limit of 128
sub-identifiers specified in SMIv2, STD 58. In this case,
the object definition MUST include a 'SIZE' clause to
limit the number of potential instance sub-identifiers."
SYNTAX OCTET STRING (SIZE (0..255))
TeHopAddressAS ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents a two or four octet AS number.
The AS number is represented in network byte
order (MSB first). A two-octet AS number has
the two MSB octets set to zero."
SYNTAX OCTET STRING (SIZE (4))
TeHopAddressUnnum ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents an unnumbered interface:
octets contents encoding
1-4 unnumbered interface network-byte order
The corresponding TeHopAddressType value is unnum(5)."
SYNTAX OCTET STRING(SIZE(4))
END
4. Normative References
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP: 26, RFC 2434,
October 1998.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Structure of Management Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Textual Conventions for Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2",
SMIv2", STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple [RFC3031] Rosen, E., Viswananthan, A., and R. Callon, "Multiprotocol
Network Management Protocol", STD 15, RFC 1157, May 1990. Label Switching Architecture", RFC 3031, January 2001.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC3032] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D.,
"Introduction to Community-based SNMPv2", RFC 1901, January Federokow, G., Li, T., and A. Conta, "MPLS Label Stack
1996. Encoding", RFC 3032, January 2001.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC3034] Conta, A., Doolan, P., and A. Malis, "Use of Label Switching
"Transport Mappings for Version 2 of the Simple Network on Frame Relay Networks Specification", RFC 3034, January
Management Protocol (SNMPv2)", RFC 1906, January 1996. 2001.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [RFC3035] Davie, B., Lawrence, J., McCloghrie, K., Rosen, E., Swallow,
Processing and Dispatching for the Simple Network Management G., Rekhter, Y., and P. Doolan, "MPLS using LDP and ATM VC
Protocol (SNMP)", RFC 2572, April 1999. Switching", RFC 3035, January 2001.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model [RFC3036] Andersson, L., Doolan, P., Feldman, N., Fredette, A., and B.
(USM) for version 3 of the Simple Network Management Thomas, "LDP Specification", RFC 3036, January 2001.
Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
"Protocol Operations for Version 2 of the Simple Network Swallow, G., "RSVP-TE: Extensions to RSVP for LSP Tunnels",
Management Protocol (SNMPv2)", RFC 1905, January 1996. RFC 3209, December 2001.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", [RFC3212] Jamoussi, B., (editor), et. al. "Constraint-Based LSP Setup
RFC 2573, April 1999. using LDP", RFC 3212, January 2002.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC3291] Daniele, M., Haberman, B., Routhier, S., and J.
Access Control Model (VACM) for the Simple Network Schoenwaelder, "Textual Conventions for Internet Network
Management Protocol (SNMP)", RFC 2575, April 1999. Addresses", RFC 3291, May 2002.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 5. Informative References
"Introduction to Version 3 of the Internet-standard Network
Management Framework", RFC 2570, April 1999.
5. Security Considerations [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
6. Security Considerations
This module does not define any management objects. Instead, it This module does not define any management objects. Instead, it
defines a set of textual conventions which may be used by other MPLS defines a set of textual conventions which may be used by other MPLS
MIB modules to define management objects. MIB modules to define management objects.
Meaningful security considerations can only be written in the MIB Meaningful security considerations can only be written in the MIB
modules that define management objects. Therefore, this document has modules that define management objects. Therefore, this document has
no impact on the security of the Internet. no impact on the security of the Internet.
6. Authors' Addresses 7. IANA Considerations
Thomas D. Nadeau IANA is requested to make a MIB OID assignment under the transmission
Cisco Systems, Inc. branch, that is, assign the mplsMIB under { transmission 166 }. This
250 Apollo Drive sub-id is requested because 166 is the ifType for mpls(166) and is
Chelmsford, MA 01824 available under transmission.
Phone: +1-978-244-3051
Email: tnadeau@cisco.com
Joan Cucchiara In the future, MPLS related standards track MIB modules should be
Consultant rooted under the mplsMIB subtree. The IANA is requested to manage
PO Box 1010 that namespace. New assignments can only be made via a Standards
Concord, MA Action as specified in [RFC2434].
Phone: +1-508-303-8200 x302
Email: jcucchiara@mindspring.com This document also requests IANA to assign { mplsMIB 1 } to the MPLS-
TC-MIB specified in this document.
8. Contributors
This document was created by combining TEXTUAL-CONVENTIONS from
current MPLS MIBs and a TE-WG MIB. Co-authors on each of these MIBs
contributed to the TEXTUAL-CONVENTIONS contained in this MIB and also
contributed greatly to the revisions of this document. These co-
authors addresses are included here because they are useful future
contacts for information about this document. These co-authors are:
Cheenu Srinivasan Cheenu Srinivasan
Parama Networks, Inc. Parama Networks, Inc.
1030 Broad Street 1030 Broad Street
Shrewsbury, NJ 07702 Shrewsbury, NJ 07702
Phone: +1-732-544-9120 x731 Phone: +1-732-544-9120 x731
Email: cheenu@paramanet.com Email: cheenu@paramanet.com
Arun Viswanathan Arun Viswanathan
Force10 Networks, Inc. Force10 Networks, Inc.
skipping to change at page 17, line 42 skipping to change at page 20, line 27
Phone: +1-408-571-3516 Phone: +1-408-571-3516
Email: arun@force10networks.com Email: arun@force10networks.com
Hans Sjostrand Hans Sjostrand
ipUnplugged ipUnplugged
P.O. Box 101 60 P.O. Box 101 60
S-121 28 Stockholm, Sweden S-121 28 Stockholm, Sweden
Phone: +46-8-725-5930 Phone: +46-8-725-5930
Email: hans@ipunplugged.com Email: hans@ipunplugged.com
7. Full Copyright Statement Kireeti Kompella
Juniper Networks
1194 Mathilda Ave
Sunnyvale, CA 94089
Phone: +1-408-745-2000
Email: kireeti@juniper.net
Copyright (C) The Internet Society (2002). All Rights Reserved. 9. Intellectual Property Notice
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11 [RFC2028].
Copies of claims of rights made available for publication and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementors or users of this
specification can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
10. Authors' Addresses
Thomas D. Nadeau
Cisco Systems, Inc.
250 Apollo Drive
Chelmsford, MA 01824
Phone: +1-978-936-1470
Email: tnadeau@cisco.com
Joan Cucchiara
Artel
237 Cedar Hill Street
Marlborough, MA 01752
Phone: +1-508-303-8200 x302
Email: jcucchiara@artel.com
11. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/