draft-ietf-mpls-tc-mib-00.txt   draft-ietf-mpls-tc-mib-01.txt 
Network Working Group Thomas D. Nadeau Network Working Group Thomas D. Nadeau
Cisco Systems, Inc. Internet Draft Cisco Systems, Inc.
Expires: October 2001 Expires: January 2002
Joan Cucchiara Joan Cucchiara
Crescent Networks
Cheenu Srinivasan Cheenu Srinivasan
Tachion Networks, Inc. Alphion Corp.
Arun Viswanathan Arun Viswanathan
Force10 Networks, Inc. Force10 Networks, Inc.
Hans Sjostrand Hans Sjostrand
ipUnplugged ipUnplugged
April 2001 August 16, 2001
Definitions of Textual Conventions and OBJECT-IDENTITIES Definition of Textual Conventions and OBJECT-IDENTITIES for
for Multi-Protocol Label Switching Management Multi-Protocol Label Switching (MPLS) Management
draft-nadeau-mpls-tc-mib-00.txt draft-ietf-mpls-tc-mib-01.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
all provisions of Section 10 of RFC 2026. conformance with all provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet
Task Force (IETF), its areas, and its working groups. Note that Engineering Task Force (IETF), its areas, and its working
other groups may also distribute working documents as Internet- groups. Note that other groups may also distribute working
Drafts. documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of
months and may be updated, replaced, or obsoleted by other six months and may be updated, replaced, or obsoleted by
documents at any time. It is inappropriate to use Internet- other documents at any time. It is inappropriate to use
Drafts as reference material or to cite them other than as "work Internet-Drafts as reference material or to cite them other
in progress." than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
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
http://www.ietf.org/shadow.html. accessed at http://www.ietf.org/shadow.html.
Table of Contents Table of Contents
1. Abstract............................................2 1. Abstract 2
2. Introduction........................................2 2. Introduction 2
3. Terminology.........................................2 3. The SNMP Management Framework 2
4. The SNMP Management Framework.......................3 4. MPLS TC MIB Definitions 3
5. Definitions.........................................3 5. Security Considerations 10
6. Security Considerations.............................9 6. References 10
7. References..........................................9
8. Authors' Addresses.................................12 IETF Draft MPLS TC MIB August 2001
9. Full Copyright Statement...........................12
7. Authors' Addresses 12
8. Full Copyright Statement 12
1. Abstract 1. Abstract
This memo describes Textual Conventions and OBJECT-IDENTITIES used
for managing MPLS networks. This memo describes Textual Conventions and OBJECT-
IDENTITIES used for managing MPLS networks.
2. Introduction 2. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information
for use with network management protocols in the Internet community. Base (MIB) for use with network management protocols in the
In particular, it defines Textual Conventions used in IETF MPLS and Internet community. In particular, it defines Textual
MPLS-related MIBs. Conventions used in IETF MPLS and MPLS-related MIBs.
Comments should be made directly to the MPLS mailing list at Comments should be made directly to the MPLS mailing list
mpls@uu.net. at mpls@uu.net.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
"OPTIONAL" in this document are to be interpreted as described in and "OPTIONAL" in this document are to be interpreted as
RFC 2119, reference [BCP14]. described in RFC 2119, reference [RFC2119].
For an introduction to the concepts of MPLS, see [MPLSArch]. For an introduction to the concepts of MPLS, see [RFC3031].
3. Terminology 3. The SNMP Management Framework
This document uses terminology from the document describing the The SNMP Management Framework presently consists of five
MPLS architecture [MPLSArch]. major components:
4. The SNMP Management Framework - An overall architecture, described in RFC 2571
[RFC2571].
The SNMP Management Framework presently consists of five major - Mechanisms for describing and naming objects and events
components: 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 An overall architecture, described in RFC 2571 [RFC2571]. - 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
o Mechanisms for describing and naming objects and events for the IETF Draft MPLS TC MIB August 2001
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 protocol, which is not an Internet standards track
first version of the SNMP message protocol is called SNMPv1 and protocol, is called SNMPv2c and described in RFC 1901
described in STD 15, RFC 1157 [RFC1157]. A second version of [RFC1901] and RFC 1906 [RFC1906]. The third version of
the SNMP message protocol, which is not an Internet standards the message protocol is called SNMPv3 and described in
track protocol, is called SNMPv2c and described in RFC 1901 RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574
[RFC1901] and RFC 1906 [RFC1906]. The third version of the [RFC2574].
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 - Protocol operations for accessing management
first set of protocol operations and associated PDU formats is information. The first set of protocol operations and
described in STD 15, RFC 1157 [RFC1157]. A second set of associated PDU formats is described in STD 15, RFC 1157
protocol operations and associated PDU formats is described in [RFC1157]. A second set of protocol operations and
RFC 1905 [RFC1905]. associated PDU formats is described in RFC 1905
[RFC1905].
o A set of fundamental applications described in RFC 2573 - A set of fundamental applications described in RFC 2573
[RFC2573] and the view-based access control mechanism described [RFC2573] and the view-based access control mechanism
in RFC 2575 [RFC2575]. described in RFC 2575 [RFC2575].
A more detailed introduction to the current SNMP Management Framework A more detailed introduction to the current SNMP Management
can be found in RFC 2570 [RFC2570]. Framework can be found in RFC 2570 [RFC2570].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information
the Management Information Base or MIB. Objects in the MIB are store, termed the Management Information Base or MIB.
defined using the mechanisms defined in the SMI. 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 This memo specifies a MIB module that is compliant to the
MIB conforming to the SMIv1 can be produced through the appropriate SMIv2. A MIB conforming to the SMIv1 can be produced
translations. The resulting translated MIB must be semantically through the appropriate translations. The resulting
equivalent, except where objects or events are omitted because no translated MIB must be semantically equivalent, except
translation is possible (use of Counter64). Some machine readable where objects or events are omitted because no translation
information in SMIv2 will be converted into textual descriptions in is possible (use of Counter64). Some machine readable
SMIv1 during the translation process. However, this loss of machine information in SMIv2 will be converted into textual
readable information is not considered to change the semantics of the descriptions in SMIv1 during the translation process.
MIB. However, this loss of machine readable information is not
considered to change the semantics of the MIB.
5. Definitions 4. MPLS TC MIB Definitions
MPLS-TC-MIB DEFINITIONS ::= BEGIN MPLS-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, Integer32, Unsigned32, transmission MODULE-IDENTITY, Unsigned32, Integer32
FROM SNMPv2-SMI FROM SNMPv2-SMI
transmission
FROM RFC1213-MIB
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; FROM SNMPv2-TC;
IETF Draft MPLS TC MIB August 2001
mplsTCMIB MODULE-IDENTITY mplsTCMIB MODULE-IDENTITY
LAST-UPDATED "200104101200Z" -- 10 April 2001 12:00:00 GMT LAST-UPDATED
ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" "200108161200Z" -- 16 August 2001 12:00:00 GMT
ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working 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
jcucchiara@mindspring.com Crescent Networks
jcucchiara@crescentnetworks.com
Cheenu Srinivasan Cheenu Srinivasan
Tachion Networks, Inc. Alphion Corp.
cheenu@tachion.com cheenu@alphion.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
Working Group Mailing List: mpls@uu.net" Email comments to the MPLS WG Mailing List at
mpls@uu.net."
DESCRIPTION DESCRIPTION
"This MIB Module provides Textual Conventions "This MIB module defines Textual Conventions and
and OBJECT-IDENTITY Objects to be used by OBJECT-IDENTITIES for use in documents defining
management information bases (MIBs) for managing
MPLS networks." MPLS networks."
-- Revision history. -- Revision history.
REVISION "200104101200Z" -- 10 April 2001 12:00:00 GMT
REVISION
"200108161200Z" -- 16 August 2001 12:00:00 GMT
DESCRIPTION
"Updates based on IESG review."
REVISION
"200104101200Z" -- 10 April 2001 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial version." "Initial version."
::= { mplsMIB 1 } -- mplsMIB To Be Assigned by IANA
::= { mplsMIB 1 }
-- This object identifier needs to be assigned by IANA.
-- Since mpls has been assigned an ifType of 166 we recommend
-- that this OID be 166 as well.
IETF Draft MPLS TC MIB August 2001
mplsMIB OBJECT IDENTIFIER mplsMIB OBJECT IDENTIFIER
::= { transmission xxx } -- To be assigned by IANA ::= { transmission xxx }
-- Since mpls is ifType: 166
-- we recommend xxx to be 166
-- Textual Conventions.
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 "An estimate of bandwidth in units of 1,000 bits per
second. If this object reports a value of 'n' then second. If this object reports a value of 'n' then
the rate of the object is somewhere in the range of the rate of the object is somewhere in the range of
'n-500' to 'n+499'. For objects which do not vary in 'n-500' to 'n+499'. For objects which do not vary
bit rate, or for those where no accurate estimation in bit rate, or for those where no accurate
can be made, this object should contain the nominal estimation can be made, this object should contain
bit rate." the nominal bit rate."
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
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."
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MplsPortAddr ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A TCP or UDP port number. Along with an IP address
identifies a stream of IP traffic uniquely."
SYNTAX INTEGER (0..65535)
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 LSR for the tunnel. This value is derived from the
the Extended Tunnel Id in RSVP or the Ingress Extended Tunnel Id in RSVP or the Ingress Router ID
Router ID for CR-LDP." for CR-LDP."
SYNTAX Unsigned32
REFERENCE REFERENCE
"1. Awduche, D., et al., RSVP-TE: Extensions to RSVP "1. Awduche, D., et al., RSVP-TE: Extensions to RSVP
for LSP Tunnels, for LSP Tunnels, draft-ietf-mpls-rsvp-lsp-tunnel-
draft-ietf-mpls-rsvp-lsp-tunnel-08.txt, 08.txt, February 2001.
February 2001.
2. Constraint-Based LSP Setup using LDP, Jamoussi, 2. Constraint-Based LSP Setup using LDP, Jamoussi,
B., et al., draft-ietf-mpls-cr-ldp-05.txt, B., et al., draft-ietf-mpls-cr-ldp-05.txt, February
February 2001." 2001."
IETF Draft MPLS TC MIB August 2001
SYNTAX Unsigned32
MplsLabel ::= TEXTUAL-CONVENTION MplsLabel ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents an MPLS label. "This value represents an MPLS label as defined in
The label contents are specific to [RFC3031], [RFC3032], [RFC3034] and [RFC3035]."
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
bits MUST be zero."
REFERENCE REFERENCE
"1. MPLS Label Stack Encoding, Rosen et al, RFC 3032, "1. Multiprotocol Label Switching Architecture, Rosen
et al, RFC 3031, August 1999.
2. MPLS Label Stack Encoding, Rosen et al, RFC 3032,
January 2001. January 2001.
2. Use of Label Switching on Frame Relay Networks, 3. Use of Label Switching on Frame Relay Networks,
Conta et al, RFC 3034, January 2001. Conta et al, RFC 3034, January 2001.
3. MPLS using LDP and ATM VC switching, Davie et al, 4. MPLS using LDP and ATM VC switching, Davie et al,
RFC 3035, January 2001." RFC 3035, January 2001."
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
MplsLdpGenAddr ::= TEXTUAL-CONVENTION MplsLdpGenAddr ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of an network layer or data link "The value of an network layer or data link layer
layer address." address."
SYNTAX OCTET STRING (SIZE (0..64)) SYNTAX OCTET STRING (SIZE (0..64))
MplsLdpIdentifier ::= TEXTUAL-CONVENTION MplsLdpIdentifier ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The LDP identifier is a six octet quantity "The LDP identifier is a six octet quantity which is
which is used to identify an Label Switch Router used to identify an Label Switch Router (LSR) label
(LSR) label space. space.
The first four octets encode an IP address 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 assigned to the LSR, and the last two octets
identify a specific label space within the LSR." identify a specific label space within the LSR."
SYNTAX OCTET STRING (SIZE (6)) SYNTAX OCTET STRING (SIZE (6))
MplsLdpLabelTypes ::= TEXTUAL-CONVENTION MplsLdpLabelTypes ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Layer 2 label types which are defined for "The Layer 2 label types which are defined for MPLS
MPLS LDP/CRLDP are generic(1), atm(2), or LDP/CRLDP are generic(1), atm(2), or
frameRelay(3)." frameRelay(3)."
SYNTAX INTEGER { SYNTAX INTEGER {
generic(1), generic(1),
atm(2), atm(2),
frameRelay(3) frameRelay(3)
} }
IETF Draft MPLS TC MIB August 2001
MplsAtmVcIdentifier ::= TEXTUAL-CONVENTION MplsAtmVcIdentifier ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VCI value for a VCL. The maximum VCI value "The VCI value for a VCL. The maximum VCI value
cannot exceed the value allowable by cannot exceed the value allowable by
atmInterfaceMaxVciBits defined in ATM-MIB. atmInterfaceMaxVciBits defined in ATM-MIB. The
The minimum value is 32, values 0 to 31 are minimum value is 32, values 0 to 31 are reserved
reserved for other uses by the ITU and ATM for other uses by the ITU and ATM Forum. 32 is
Forum. 32 is typically the default value typically the default value for the Control VC."
for the Control VC." REFERENCE
"Definitions of Textual Conventions and OBJECT-
IDENTITIES for ATM Management, RFC 2514, Feb.
1999."
SYNTAX Integer32 (32..65535) SYNTAX Integer32 (32..65535)
MplsLSPID ::= TEXTUAL-CONVENTION MplsLSPID ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An identifier that is assigned to each LSP and is "An identifier that is assigned to each LSP and is
used to uniquely identify it. This is assigned at used to uniquely identify it. This is assigned at
the head end of the LSP and can be used by all LSRs the head end of the LSP and can be used by all LSRs
to identify this LSP. This value is piggybacked by to identify this LSP. This value is piggybacked by
the signaling protocol when this LSP is signaled the signaling protocol when this LSP is signaled
within the network. This identifier can then be within the network. This identifier can then be
used at each LSR to identify which labels are being used at each LSR to identify which labels are being
swapped to other labels for this LSP. For IPv4 swapped to other labels for this LSP. For IPv4
addresses this results in a 6-octet long cookie." addresses this results in a 6-octet long cookie."
SYNTAX OCTET STRING (SIZE (0..31)) SYNTAX OCTET STRING (SIZE (0..31))
MplsLsrIdentifier ::= TEXTUAL-CONVENTION MplsLsrIdentifier ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Label Switch Router (LSR) identifier is the "The Label Switch Router (LSR) identifier is the
first 4 bytes or the Router Id component first 4 bytes of the Label Distribution Protocol
of the Label Distribution Protocol (LDP) (LDP) identifier."
identifier."
SYNTAX OCTET STRING (SIZE (4)) SYNTAX OCTET STRING (SIZE (4))
MplsInitialCreationSource ::= TEXTUAL-CONVENTION MplsInitialCreationSource ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The entity that originally created the object in "The entity that originally created the object in
question. The values of this enumeration are question. The values of this enumeration are
defined as follows: defined as follows:
other(1) - This is used when an entity which has not other(1) - This is used when an entity which has not
been enumerated in this textual convention been enumerated in this textual convention but
but which is known by the agent. which is known by the agent.
snmp(2) - The Simple Network Management Protocol was snmp(2) - The Simple Network Management Protocol was
used to configure this object initially. used to configure this object initially.
ldp(3) - The Label Distribution Protocol was used IETF Draft MPLS TC MIB August 2001
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 rsvp(4) - The Resource Reservation Protocol was used
to configure this object initially. to configure this object initially.
crldp(5) - The Constraint-Based Label Distribution crldp(5) - The Constraint-Based Label Distribution
Protocol was used to configure this object Protocol was used to configure this object
initially. initially.
policyAgent(6) - A policy agent (perhaps in combination with policyAgent(6) - A policy agent (perhaps in
one of the above protocols) was used combination with one of the above protocols) was
to configure this object initially. used to configure this object initially.
unknown(7) -- the agent cannot discern which component
created the object."
unknown(7) - the agent cannot discern which
component created the object."
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
snmp(2), snmp(2),
ldp(3), ldp(3),
rsvp(4), rsvp(4),
crldp(5), crldp(5),
policyAgent(6), policyAgent(6),
unknown (7) unknown (7)
} }
skipping to change at page 9, line 15 skipping to change at page 9, line 4
SYNTAX Unsigned32 SYNTAX Unsigned32
MplsTunnelAffinity ::= TEXTUAL-CONVENTION MplsTunnelAffinity ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Include-any, include-all, or exclude-all constraint "Include-any, include-all, or exclude-all constraint
for link selection." for link selection."
SYNTAX Unsigned32 SYNTAX Unsigned32
MplsTunnelIndex ::= TEXTUAL-CONVENTION MplsTunnelIndex ::= TEXTUAL-CONVENTION
IETF Draft MPLS TC MIB August 2001
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Index into mplsTunnelTable." "Index into mplsTunnelTable."
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (1..65535)
MplsTunnelInstanceIndex ::= TEXTUAL-CONVENTION MplsTunnelInstanceIndex ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Instance index into mplsTunnelTable." "Instance index into mplsTunnelTable."
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
MplsFTNIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Index for an FEC-to-NHLFE (FTN) entry."
SYNTAX Integer32(1..2147483647)
MplsFTNIndexOrZero ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Index for an FTN entry or zero."
SYNTAX Integer32(0..2147483647)
END END
6. Security Considerations 5. Security Considerations
This memo defines textual conventions and object identities for use This memo defines textual conventions and object identities
in MPLS MIB modules. Security issues for these MIB modules are for use in MPLS MIB modules. Security issues for these MIB
addressed in the memos defining those modules. modules are addressed in the memos defining those modules.
7. References 6. References
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture [RFC1155] Rose, M., and K. McCloghrie, "Structure and
for Describing SNMP Management Frameworks", RFC 2571, April Identification of Management Information for
1999. TCP/IP-based Internets", STD 16, RFC 1155,
May 1990.
[RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J.
of Management Information for TCP/IP-based Internets", STD Davin, "Simple Network Management Protocol",
16, RFC 1155, May 1990. STD 15, RFC 1157, May 1990.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB
16, RFC 1212, March 1991. Definitions", STD 16, RFC 1212, March 1991.
[RFC1215] M. Rose, "A Convention for Defining Traps for use with the [RFC1215] M. Rose, "A Convention for Defining Traps
SNMP", RFC 1215, March 1991. for use with the SNMP", RFC 1215, March
1991.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., IETF Draft MPLS TC MIB August 2001
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., [RFC1901] Case, J., McCloghrie, K., Rose, M., and S.
Rose, M., and S. Waldbusser, "Textual Conventions for Waldbusser, "Introduction to Community-based
SMIv2", STD 58, RFC 2579, April 1999. SNMPv2", RFC 1901, January 1996.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC1905] Case, J., McCloghrie, K., Rose, M., and S.
Rose, M., and S. Waldbusser, "Conformance Statements for Waldbusser, "Protocol Operations for Version
SMIv2", STD 58, RFC 2580, April 1999. 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1905, January 1996.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple [RFC1906] Case, J., McCloghrie, K., Rose, M., and S.
Network Management Protocol", STD 15, RFC 1157, May 1990. Waldbusser, "Transport Mappings for Version
2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1906, January 1996.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC2119] Bradner, S., "Key words for use in RFCs to
"Introduction to Community-based SNMPv2", RFC 1901, January Indicate Requirement Levels", BCP 14, RFC
1996. 2119, March 1997.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC2514] Noto, et. al., "Definitions of Textual
"Transport Mappings for Version 2 of the Simple Network Conventions and OBJECT-IDENTITIES for ATM
Management Protocol (SNMPv2)", RFC 1906, January 1996. Management", RFC 2514, Feb. 1999
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [RFC2570] Case, J., Mundy, R., Partain, D., and B.
Processing and Dispatching for the Simple Network Management Stewart, "Introduction to Version 3 of the
Protocol (SNMP)", RFC 2572, April 1999. Internet-standard Network Management
Framework", RFC 2570, April 1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen,
(USM) for version 3 of the Simple Network Management "An Architecture for Describing SNMP
Protocol (SNMPv3)", RFC 2574, April 1999. Management Frameworks", RFC 2571, April
1999.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC2572] Case, J., Harrington D., Presuhn R., and B.
"Protocol Operations for Version 2 of the Simple Network Wijnen, "Message Processing and Dispatching
Management Protocol (SNMPv2)", RFC 1905, January 1996. for the Simple Network Management Protocol
(SNMP)", RFC 2572, April 1999.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
RFC 2573, April 1999. Applications", RFC 2573, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC2574] Blumenthal, U., and B. Wijnen, "User-based
Access Control Model (VACM) for the Simple Network Security Model (USM) for version 3 of the
Management Protocol (SNMP)", RFC 2575, April 1999. Simple Network Management Protocol
(SNMPv3)", RFC 2574, April 1999.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie,
"Introduction to Version 3 of the Internet-standard Network "View-based Access Control Model (VACM) for
Management Framework", RFC 2570, April 1999. the Simple Network Management Protocol
(SNMP)", RFC 2575, April 1999.
[MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, IETF Draft MPLS TC MIB August 2001
"Multiprotocol Label Switching Architecture",
RFC 3031, August 1999.
[LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder,
Federokow, G., Li, T., and A. Conta, "MPLS Label J., Case, J., Rose, M., and S. Waldbusser,
Stack Encoding", RFC 3032, January 2001. "Structure of Management Information Version
label-encaps-07.txt>, September 1999. 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[LWFRN] Conta, A., Doolan, P., Malis, A., "Use of Label [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder,
Switching on Frame Relay Networks Specification", J., Case, J., Rose, M., and S. Waldbusser,
RFC 3034, January 2001. "Textual Conventions for SMIv2", STD 58, RFC
2579, April 1999.
[MLDPATM] Davie, B., Lawrence, J., McCloghrie, K., Rosen, E., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder,
Swallow, G., Rekhter, Y., Doolan, P., "MPLS using J., Case, J., Rose, M., and S. Waldbusser,
LDP and ATM VC switching", RFC 3035, January 2001. "Conformance Statements for SMIv2", STD 58,
RFC 2580, April 1999.
[Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", [RFC3031] Rosen, E., Viswanathan, A., and R. Callon,
RFC 1700, October 1994. See also: "Multiprotocol Label Switching
http://www.isi.edu/in-notes/iana/assignments/smi- Architecture", RFC 3031, August 1999.
numbers
[IPSEC] Kent, S., and Atkinson, R., "Security Architecture [RFC3032] Rosen, E., Rekhter, Y., Tappan, D.,
for the Internet Protocol", RFC 2401, November Farinacci, D., Federokow, G., Li, T., and A.
1998. Conta, "MPLS Label Stack Encoding", RFC
3032, January 2001.
[IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces [RFC3034] Conta, A., Doolan, P., Malis, A., "Use of
Group MIB", RFC 2863, June 2000. Label Switching on Frame Relay Networks
Specification", RFC 3034, January 2001.
[ATOMMIBTC] Noto, et. al., "Definitions of Textual Conventions and [RFC3035] Davie, B., Lawrence, J., McCloghrie, K.,
OBJECT-IDENTITIES for ATM Management", RFC 2514, Rosen, E., Swallow, G., Rekhter, Y., and P.
Feb. 1999 Doolan, "MPLS using LDP and ATM VC
switching", RFC 3035, January 2001.
[BCP14] Bradner, S., "Key words for use in RFCs to Indicate [RFC3036] Anderson, L., Doolan, P., Feldman, N.,
Requirement Levels", BCP 14, RFC 2119, March 1997. Fredette, A., and B. Thomas, "LDP
Specification", RFC 3036, January 2001.
[RSVPTE] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, [Assigned] Reynolds, J., and J. Postel, "Assigned
V., Swallow, G., RSVP-TE: Extensions to RSVP Numbers", RFC 1700, October 1994. See also:
for LSP Tunnels, draft-ietf-mpls-rsvp-lsp-tunnel-08.txt, http://www.isi.edu/in-
February 2001. notes/iana/assignments/smi-numbers
[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., [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."
8. Authors' Addresses IETF Draft MPLS TC MIB August 2001
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."
7. Authors' Addresses
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
250 Apollo Drive 250 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
Phone: +1-978-244-3051 Phone: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Joan Cucchiara Joan Cucchiara
Phone: Crescent Networks
Email: jcucchiara@mindspring.com 900 Chelmsford Street
Lowell, MA 01851
Phone: +1-978-275-3183
email: jcucchiara@crescentnetworks.com
Cheenu Srinivasan Cheenu Srinivasan
Tachion Networks, Inc. Alphion Corp.
Monmouth Park Corporate Center I 4 Industrial Way West
Building C, 185 Monmouth Parkway Eatontown, NJ 07724
West Long Branch, NJ 07764 Phone: +1-732-676-7066
Phone: +1-732-542-7750 x1234 Email: cheenu@alphion.com
Email: cheenu@tachion.com
Arun Viswanathan Arun Viswanathan
Force10 Networks, Inc. Force10 Networks, Inc.
1440 McCarthy Blvd 1440 McCarthy Blvd
Milpitas, CA 95035 Milpitas, CA 95035
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
9. Full Copyright Statement 8. Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights
This document and translations of it may be copied and furnished IETF Draft MPLS TC MIB August 2001
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
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 Reserved.
be revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on This document and translations of it may be copied and
an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET furnished to others, and derivative works that comment on
ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR or otherwise explain it or assist in its implementation may
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF be prepared, copied, published and distributed, in whole or
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED in part, without restriction of any kind, provided that the
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 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
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.
 End of changes. 

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