Network Working Group Thomas D. Nadeau
Cisco Systems, Inc.
Expires: October 2001
Joan Cucchiara
Cheenu Srinivasan
Tachion Networks, Inc.
Arun Viswanathan
Force10 Networks, Inc.
Hans Sjostrand
ipUnplugged
April 2001
Definitions of Textual Conventions and OBJECT-IDENTITIES
for Multi-Protocol Label Switching Management
draft-nadeau-mpls-tc-mib-00.txt
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as "work
in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Table of Contents
1. Abstract............................................2
2. Introduction........................................2
3. Terminology.........................................2
4. The SNMP Management Framework.......................3
5. Definitions.........................................3
6. Security Considerations.............................9
7. References..........................................9
Nadeau et al. Expires October 2001 [Page 1]
Internet Draft MPLS TC MIB April 10, 2001
8. Authors' Addresses.................................12
9. Full Copyright Statement...........................12
1. Abstract
This memo describes Textual Conventions and OBJECT-IDENTITIES used
for managing MPLS networks.
2. Introduction
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it defines Textual Conventions used in IETF MPLS and
MPLS-related MIBs.
Comments should be made directly to the MPLS mailing list at
mpls@uu.net.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
RFC 2119, reference [BCP14].
For an introduction to the concepts of MPLS, see [MPLSArch].
3. Terminology
This document uses terminology from the document describing the
MPLS architecture [MPLSArch].
4. The SNMP 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
Nadeau et al. Expires October 2001 [Page 2]
Internet Draft MPLS TC MIB April 10, 2001
[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
can be found in RFC 2570 [RFC2570].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). 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.
5. Definitions
MPLS-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, Integer32, Unsigned32, transmission
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC;
mplsTCMIB MODULE-IDENTITY
LAST-UPDATED "200104101200Z" -- 10 April 2001 12:00:00 GMT
ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO
" Thomas D. Nadeau
Cisco Systems, Inc.
tnadeau@cisco.com
Nadeau et al. Expires October 2001 [Page 3]
Internet Draft MPLS TC MIB April 10, 2001
Joan Cucchiara
jcucchiara@mindspring.com
Cheenu Srinivasan
Tachion Networks, Inc.
cheenu@tachion.com
Arun Viswanathan
Force10 Networks, Inc.
arun@force10networks.com
Hans Sjostrand
ipUnplugged
hans@ipunplugged.com
Working Group Mailing List: mpls@uu.net"
DESCRIPTION
"This MIB Module provides Textual Conventions
and OBJECT-IDENTITY Objects to be used by
MPLS networks."
-- Revision history.
REVISION "200104101200Z" -- 10 April 2001 12:00:00 GMT
DESCRIPTION
"Initial version."
::= { mplsMIB 1 } -- mplsMIB To Be Assigned by IANA
mplsMIB OBJECT IDENTIFIER
::= { transmission xxx } -- To be assigned by IANA
-- Since mpls is ifType: 166
-- we recommend xxx to be 166
-- The Textual Conventions defined below are organized
-- alphabetically
MplsBitRate ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An estimate of bandwidth in units of 1,000 bits per
second. If this object reports a value of 'n' then
the rate of the object is somewhere in the range of
'n-500' to 'n+499'. For objects which do not vary in
bit rate, or for those where no accurate estimation
can be made, this object should contain the nominal
bit rate."
SYNTAX Integer32 (1..2147483647)
Nadeau et al. Expires October 2001 [Page 4]
Internet Draft MPLS TC MIB April 10, 2001
MplsBurstSize ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The number of octets of MPLS data that the stream
may send back-to-back without concern for policing."
SYNTAX Unsigned32 (1..4294967295)
MplsExtendedTunnelId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A unique identifier for an MPLS Tunnel. This MAY
represent an IpV4 address of the ingress or egress
LSR for the tunnel. This value is derived from
the Extended Tunnel Id in RSVP or the Ingress
Router ID for CR-LDP."
SYNTAX Unsigned32
REFERENCE
"1. Awduche, D., et al., RSVP-TE: Extensions to RSVP
for LSP Tunnels,
draft-ietf-mpls-rsvp-lsp-tunnel-08.txt,
February 2001.
2. Constraint-Based LSP Setup using LDP, Jamoussi,
B., et al., draft-ietf-mpls-cr-ldp-05.txt,
February 2001."
MplsLabel ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This value represents an MPLS label.
The label contents are specific to
the label being represented.
The label carried in an MPLS shim header
(for LDP, the Generic Label) is a 20-bit number
represented by 4 octets. Bits 0-19 contain a
label or a reserved label value. Bits 20-31 MUST
be zero.
The frame relay label can be represented by either
10-bits or 23-bits depending on the DLCI field size and
the upper 22-bits or upper 9-bits must be zero,
respectively.
For an ATM label the lower 16-bits represents the VCI,
the next 12-bits represents the VPI and the remaining
Nadeau et al. Expires October 2001 [Page 5]
Internet Draft MPLS TC MIB April 10, 2001
bits MUST be zero."
REFERENCE
"1. MPLS Label Stack Encoding, Rosen et al, RFC 3032,
January 2001.
2. Use of Label Switching on Frame Relay Networks,
Conta et al, RFC 3034, January 2001.
3. MPLS using LDP and ATM VC switching, Davie et al,
RFC 3035, January 2001."
SYNTAX Unsigned32 (0..4294967295)
-- A similar TC is also used in RFC2677.txt. NOTE: since
-- MPLS's goal is to be any layer2 over any layer3, this
-- MIB makes every attempt to define a TC which would
-- satisfy L2 and L3 address sizes for now and in
-- the future.
MplsLdpGenAddr ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The value of an network layer or data link
layer address."
SYNTAX OCTET STRING (SIZE (0..64))
MplsLdpIdentifier ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The LDP identifier is a six octet quantity
which is used to identify an Label Switch Router
(LSR) label space.
The first four octets encode an IP address
assigned to the LSR, and the last two octets
identify a specific label space within the LSR."
SYNTAX OCTET STRING (SIZE (6))
MplsLdpLabelTypes ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The Layer 2 label types which are defined for
MPLS LDP/CRLDP are generic(1), atm(2), or
frameRelay(3)."
SYNTAX INTEGER {
generic(1),
atm(2),
frameRelay(3)
}
Nadeau et al. Expires October 2001 [Page 6]
Internet Draft MPLS TC MIB April 10, 2001
-- This was taken from rfc2514.txt (AtmVcIdentifier) and
-- modified here for MPLS.
-- This TC agrees with "MPLS using LDP and ATM VC Switching"
-- document which specifies that VC values need
-- to be greater than 31, or in other words, 0-31 are
-- reserved for other uses by the ITU and ATM Forum.
MplsAtmVcIdentifier ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The VCI value for a VCL. The maximum VCI value
cannot exceed the value allowable by
atmInterfaceMaxVciBits defined in ATM-MIB.
The minimum value is 32, values 0 to 31 are
reserved for other uses by the ITU and ATM
Forum. 32 is typically the default value
for the Control VC."
SYNTAX Integer32 (32..65535)
MplsLSPID ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An identifier that is assigned to each LSP and is
used to uniquely identify it. 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. For IPv4
addresses this results in a 6-octet long cookie."
SYNTAX OCTET STRING (SIZE (0..31))
MplsLsrIdentifier ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The Label Switch Router (LSR) identifier is the
first 4 bytes or the Router Id component
of the Label Distribution Protocol (LDP)
identifier."
SYNTAX OCTET STRING (SIZE (4))
MplsInitialCreationSource ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The entity that originally created the object in
question. The values of this enumeration are
Nadeau et al. Expires October 2001 [Page 7]
Internet Draft MPLS TC MIB April 10, 2001
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."
SYNTAX INTEGER {
other(1),
snmp(2),
ldp(3),
rsvp(4),
crldp(5),
policyAgent(6),
unknown (7)
}
MplsPathIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A unique identifier used to identify a specific path
used by a tunnel."
SYNTAX Unsigned32
MplsPathIndexOrZero ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A unique identifier used to identify a specific path
used by a tunnel. If this value is set to 0, it
Nadeau et al. Expires October 2001 [Page 8]
Internet Draft MPLS TC MIB April 10, 2001
indicates that no path is in use."
SYNTAX Unsigned32
MplsTunnelAffinity ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Include-any, include-all, or exclude-all constraint
for link selection."
SYNTAX Unsigned32
MplsTunnelIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Index into mplsTunnelTable."
SYNTAX Integer32 (1..65535)
MplsTunnelInstanceIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Instance index into mplsTunnelTable."
SYNTAX Unsigned32 (0..65535)
-- End of MPLS-TC-MIB
END
6. Security Considerations
This memo defines textual conventions and object identities for use
in MPLS MIB modules. Security issues for these MIB modules are
addressed in the memos defining those modules.
7. References
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture
for Describing SNMP Management Frameworks", RFC 2571, April
1999.
[RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification
of Management Information for TCP/IP-based Internets", STD
16, RFC 1155, May 1990.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD
16, RFC 1212, March 1991.
Nadeau et al. Expires October 2001 [Page 9]
Internet Draft MPLS TC MIB April 10, 2001
[RFC1215] M. Rose, "A Convention for Defining Traps for use with the
SNMP", RFC 1215, March 1991.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Network Management Protocol", STD 15, RFC 1157, May 1990.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, January
1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1906, January 1996.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2572, April 1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Protocol Operations for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1905, January 1996.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications",
RFC 2573, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard Network
Management Framework", RFC 2570, April 1999.
Nadeau et al. Expires October 2001 [Page 10]
Internet Draft MPLS TC MIB April 10, 2001
[MPLSArch] Rosen, E., Viswanathan, A., and R. Callon,
"Multiprotocol Label Switching Architecture",
RFC 3031, August 1999.
[LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D.,
Federokow, G., Li, T., and A. Conta, "MPLS Label
Stack Encoding", RFC 3032, January 2001.
label-encaps-07.txt>, September 1999.
[LWFRN] Conta, A., Doolan, P., Malis, A., "Use of Label
Switching on Frame Relay Networks Specification",
RFC 3034, January 2001.
[MLDPATM] Davie, B., Lawrence, J., McCloghrie, K., Rosen, E.,
Swallow, G., Rekhter, Y., Doolan, P., "MPLS using
LDP and ATM VC switching", RFC 3035, January 2001.
[Assigned] Reynolds, J., and J. Postel, "Assigned Numbers",
RFC 1700, October 1994. See also:
http://www.isi.edu/in-notes/iana/assignments/smi-
numbers
[IPSEC] Kent, S., and Atkinson, R., "Security Architecture
for the Internet Protocol", RFC 2401, November
1998.
[IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces
Group MIB", RFC 2863, June 2000.
[ATOMMIBTC] Noto, et. al., "Definitions of Textual Conventions and
OBJECT-IDENTITIES for ATM Management", RFC 2514,
Feb. 1999
[BCP14] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RSVPTE] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan,
V., Swallow, G., RSVP-TE: Extensions to RSVP
for LSP Tunnels, draft-ietf-mpls-rsvp-lsp-tunnel-08.txt,
February 2001.
[CRLDP] Jamoussi, B., Aboul-Magd, O., Andersson, L.,
Ashwood-Smith, P., Hellstrand, F., Sundell, K.,
Callon, R., Dantu, R., Wu, L., Doolan, P., Worster, T.,
Feldman, N., Fredette, A., Girish, M., Gray, E.,
Halpern, J., Heinanen, J., Kilty, T., Malis, A.,
Vaananen, P., Constraint-Based LSP Setup using LDP,
draft-ietf-mpls-cr-ldp-05.txt, February 2001."
Nadeau et al. Expires October 2001 [Page 11]
Internet Draft MPLS TC MIB April 10, 2001
8. Authors' Addresses
Thomas D. Nadeau
Cisco Systems, Inc.
250 Apollo Drive
Chelmsford, MA 01824
Phone: +1-978-244-3051
Email: tnadeau@cisco.com
Joan Cucchiara
Phone:
Email: jcucchiara@mindspring.com
Cheenu Srinivasan
Tachion Networks, Inc.
Monmouth Park Corporate Center I
Building C, 185 Monmouth Parkway
West Long Branch, NJ 07764
Phone: +1-732-542-7750 x1234
Email: cheenu@tachion.com
Arun Viswanathan
Force10 Networks, Inc.
1440 McCarthy Blvd
Milpitas, CA 95035
Phone: +1-408-571-3516
Email: arun@force10networks.com
Hans Sjostrand
ipUnplugged
P.O. Box 101 60
S-121 28 Stockholm, Sweden
Phone: +46 8 725 5930
Email: hans@ipunplugged.com
9. Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved.
This document and translations of it may be copied and furnished
to others, and derivative works that comment on or otherwise
explain it or assist in its implementation may be prepared,
copied, published and distributed, in whole or in part, without
restriction of any kind, provided that the above copyright notice
and this paragraph are included on all such copies and derivative
works. However, this document itself may not be modified in any
way, such as by removing the copyright notice or references to the
Internet Society or other Internet organizations, except as needed
Nadeau et al. Expires October 2001 [Page 12]
Internet Draft MPLS TC MIB April 10, 2001
for the purpose of developing Internet standards in which case
the procedures for copyrights defined in the Internet Standards
process must be followed, or as required to translate it into
languages other than English.
The limited permissions granted above are perpetual and will not
be revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on
an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Nadeau et al. Expires October 2001 [Page 13]
