draft-ietf-mpls-tc-mib-01.txt   draft-ietf-mpls-tc-mib-02.txt 
Network Working Group Thomas D. Nadeau Network Working Group Thomas D. Nadeau
Internet Draft Cisco Systems, Inc. Internet Draft Cisco Systems, Inc.
Expires: January 2002 Expires: February 2002
Joan Cucchiara Joan Cucchiara
Crescent Networks Crescent Networks
Cheenu Srinivasan Cheenu Srinivasan
Alphion Corp. Alphion Corp.
Arun Viswanathan Arun Viswanathan
Force10 Networks, Inc. Force10 Networks, Inc.
Hans Sjostrand Hans Sjostrand
ipUnplugged ipUnplugged
August 16, 2001 August 2001
Definition of Textual Conventions and OBJECT-IDENTITIES for Definition of Textual Conventions and OBJECT-IDENTITIES for
Multi-Protocol Label Switching (MPLS) Management Multi-Protocol Label Switching (MPLS) Management
draft-ietf-mpls-tc-mib-01.txt draft-ietf-mpls-tc-mib-02.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full This document is an Internet-Draft and is in full
conformance with 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 Internet-Drafts are working documents of the Internet
Engineering Task Force (IETF), its areas, and its working Engineering Task Force (IETF), its areas, and its working
groups. Note that other groups may also distribute working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
skipping to change at page 1, line 52 skipping to change at page 1, line 52
The list of Internet-Draft Shadow Directories can be The list of Internet-Draft Shadow Directories can be
accessed at 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. The SNMP Management Framework 2 3. The SNMP Management Framework 2
4. MPLS TC MIB Definitions 3 4. MPLS TC MIB Definitions 3
5. Security Considerations 10 5. Security Considerations 9
6. References 10 6. References 9
IETF Draft MPLS TC MIB August 2001
7. Authors' Addresses 12 7. Authors' Addresses 12
8. Full Copyright Statement 12 8. Full Copyright Statement 13
1. Abstract 1. Abstract
This memo describes Textual Conventions and OBJECT- This memo describes Textual Conventions and OBJECT-
IDENTITIES used for managing MPLS networks. IDENTITIES used for managing MPLS networks.
2. Introduction 2. Introduction
This memo defines a portion of the Management Information This memo defines a portion of the Management Information
Base (MIB) for use with network management protocols in the Base (MIB) for use with network management protocols in the
skipping to change at page 3, line 4 skipping to change at page 3, line 4
called SMIv1 and described in STD 16, RFC 1155 called SMIv1 and described in STD 16, RFC 1155
[RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215
[RFC1215]. The second version, called SMIv2, is [RFC1215]. The second version, called SMIv2, is
described in STD 58, RFC 2578 [RFC2578], STD 58, RFC described in STD 58, RFC 2578 [RFC2578], STD 58, RFC
2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
- Message protocols for transferring management - Message protocols for transferring management
information. The first version of the SNMP message information. The first version of the SNMP message
protocol is called SNMPv1 and described in STD 15, RFC protocol is called SNMPv1 and described in STD 15, RFC
1157 [RFC1157]. A second version of the SNMP message 1157 [RFC1157]. A second version of the SNMP message
IETF Draft MPLS TC MIB August 2001
protocol, which is not an Internet standards track protocol, which is not an Internet standards track
protocol, is called SNMPv2c and described in RFC 1901 protocol, is called SNMPv2c and described in RFC 1901
[RFC1901] and RFC 1906 [RFC1906]. The third version of [RFC1901] and RFC 1906 [RFC1906]. The third version of
the message protocol is called SNMPv3 and described in the message protocol is called SNMPv3 and described in
RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574
[RFC2574]. [RFC2574].
- Protocol operations for accessing management - Protocol operations for accessing management
information. The first set of protocol operations and information. The first set of protocol operations and
associated PDU formats is described in STD 15, RFC 1157 associated PDU formats is described in STD 15, RFC 1157
skipping to change at page 4, line 5 skipping to change at page 4, line 5
MPLS-TC-MIB DEFINITIONS ::= BEGIN MPLS-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, Unsigned32, Integer32 MODULE-IDENTITY, Unsigned32, Integer32
FROM SNMPv2-SMI FROM SNMPv2-SMI
transmission transmission
FROM RFC1213-MIB 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 LAST-UPDATED
"200108161200Z" -- 16 August 2001 12:00:00 GMT "200108211200Z" -- 21 August 2001 12:00:00 GMT
ORGANIZATION ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group" "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
Crescent Networks Crescent Networks
jcucchiara@crescentnetworks.com jcucchiara@crescentnetworks.com
skipping to change at page 4, line 44 skipping to change at page 4, line 42
mpls@uu.net." mpls@uu.net."
DESCRIPTION DESCRIPTION
"This MIB module defines Textual Conventions and "This MIB module defines Textual Conventions and
OBJECT-IDENTITIES for use in documents defining OBJECT-IDENTITIES for use in documents defining
management information bases (MIBs) for managing management information bases (MIBs) for managing
MPLS networks." MPLS networks."
-- Revision history. -- Revision history.
REVISION REVISION
"200108211200Z" -- 21 August 2001 12:00:00 GMT
DESCRIPTION
"Reordered TCs alphabetically. Changed MplsPortAddr
to MplsPortNumber and redefined it to use Integer32
instead of INTEGER."
REVISION
"200108161200Z" -- 16 August 2001 12:00:00 GMT "200108161200Z" -- 16 August 2001 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Updates based on IESG review." "Updates based on IESG review."
REVISION REVISION
"200104101200Z" -- 10 April 2001 12:00:00 GMT "200104101200Z" -- 10 April 2001 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial version." "Initial version."
::= { 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.
IETF Draft MPLS TC MIB August 2001
mplsMIB OBJECT IDENTIFIER mplsMIB OBJECT IDENTIFIER
::= { transmission xxx } ::= { transmission xxx }
-- Textual Conventions (sorted alphabetically).
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."
REFERENCE
"Definitions of Textual Conventions and OBJECT-
IDENTITIES for ATM Management, RFC 2514, Feb.
1999."
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 "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 'n-500' to 'n+499'. For objects which do not vary
in bit rate, or for those where no accurate in bit rate, or for those where no accurate
skipping to change at page 5, line 34 skipping to change at page 5, line 52
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 may send back-to-back without concern for
policing." 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 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
"1. Awduche, D., et al., RSVP-TE: Extensions to RSVP "1. Awduche, D., et al., RSVP-TE: Extensions to RSVP
for LSP Tunnels, draft-ietf-mpls-rsvp-lsp-tunnel- for LSP Tunnels, draft-ietf-mpls-rsvp-lsp-tunnel-
08.txt, February 2001. 08.txt, 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, February B., et al., draft-ietf-mpls-cr-ldp-05.txt, February
2001." 2001."
SYNTAX Unsigned32
IETF Draft MPLS TC MIB August 2001 MplsFTNIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Index for a FEC-to-NHLFE (FTN) entry."
SYNTAX Integer32(1..2147483647)
SYNTAX Unsigned32 MplsFTNIndexOrZero ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Index for a FTN entry or zero."
SYNTAX Integer32(0..2147483647)
MplsInitialCreationSource ::= 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."
SYNTAX INTEGER {
other(1),
snmp(2),
ldp(3),
rsvp(4),
crldp(5),
policyAgent(6),
unknown (7)
}
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))
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] and [RFC3035]." [RFC3031], [RFC3032], [RFC3034] and [RFC3035]."
REFERENCE REFERENCE
"1. Multiprotocol Label Switching Architecture, Rosen "1. Multiprotocol Label Switching Architecture, Rosen
et al, RFC 3031, August 1999. et al, RFC 3031, August 1999.
2. MPLS Label Stack Encoding, Rosen et al, RFC 3032, 2. MPLS Label Stack Encoding, Rosen et al, RFC 3032,
skipping to change at page 7, line 5 skipping to change at page 8, line 34
DESCRIPTION DESCRIPTION
"The Layer 2 label types which are defined for MPLS "The Layer 2 label types which are defined for 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
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."
REFERENCE
"Definitions of Textual Conventions and OBJECT-
IDENTITIES for ATM Management, RFC 2514, Feb.
1999."
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 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 of the Label Distribution Protocol first 4 bytes of the Label Distribution Protocol
(LDP) identifier." (LDP) identifier."
SYNTAX OCTET STRING (SIZE (4)) 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
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.
IETF Draft MPLS TC MIB August 2001
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 MplsPathIndex ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A unique identifier used to identify a specific path "A unique identifier used to identify a specific path
used by a tunnel." used by a tunnel."
SYNTAX Unsigned32 SYNTAX Unsigned32
MplsPathIndexOrZero ::= TEXTUAL-CONVENTION MplsPathIndexOrZero ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A unique identifier used to identify a specific path "A unique identifier used to identify a specific path
used by a tunnel. If this value is set to 0, it used by a tunnel. If this value is set to 0, it
indicates that no path is in use." indicates that no path is in use."
SYNTAX Unsigned32 SYNTAX Unsigned32
MplsPortNumber ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A TCP or UDP port number. Along with an IP address
identifies a stream of IP traffic uniquely."
SYNTAX Integer32 (0..65535)
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
5. Security Considerations 5. Security Considerations
This memo defines textual conventions and object identities This memo defines textual conventions and object identities
for use in MPLS MIB modules. Security issues for these MIB for use in MPLS MIB modules. Security issues for these MIB
modules are addressed in the memos defining those modules. modules are addressed in the memos defining those modules.
6. References 6. References
skipping to change at page 10, line 5 skipping to change at page 10, line 12
Davin, "Simple Network Management Protocol", Davin, "Simple Network Management Protocol",
STD 15, RFC 1157, May 1990. STD 15, RFC 1157, May 1990.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB
Definitions", STD 16, RFC 1212, March 1991. Definitions", STD 16, RFC 1212, March 1991.
[RFC1215] M. Rose, "A Convention for Defining Traps [RFC1215] M. Rose, "A Convention for Defining Traps
for use with the SNMP", RFC 1215, March for use with the SNMP", RFC 1215, March
1991. 1991.
IETF Draft MPLS TC MIB August 2001
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. [RFC1901] Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Introduction to Community-based Waldbusser, "Introduction to Community-based
SNMPv2", RFC 1901, January 1996. SNMPv2", RFC 1901, January 1996.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. [RFC1905] Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Protocol Operations for Version Waldbusser, "Protocol Operations for Version
2 of the Simple Network Management Protocol 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1905, January 1996. (SNMPv2)", RFC 1905, January 1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. [RFC1906] Case, J., McCloghrie, K., Rose, M., and S.
skipping to change at page 11, line 5 skipping to change at page 11, line 11
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based [RFC2574] Blumenthal, U., and B. Wijnen, "User-based
Security Model (USM) for version 3 of the Security Model (USM) for version 3 of the
Simple Network Management Protocol Simple Network Management Protocol
(SNMPv3)", RFC 2574, April 1999. (SNMPv3)", RFC 2574, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie,
"View-based Access Control Model (VACM) for "View-based Access Control Model (VACM) for
the Simple Network Management Protocol the Simple Network Management Protocol
(SNMP)", RFC 2575, April 1999. (SNMP)", RFC 2575, April 1999.
IETF Draft MPLS TC MIB August 2001
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder,
J., Case, J., Rose, M., and S. Waldbusser, J., Case, J., Rose, M., and S. Waldbusser,
"Structure of Management Information Version "Structure of Management Information Version
2 (SMIv2)", STD 58, RFC 2578, April 1999. 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder,
J., Case, J., Rose, M., and S. Waldbusser, J., Case, J., Rose, M., and S. Waldbusser,
"Textual Conventions for SMIv2", STD 58, RFC "Textual Conventions for SMIv2", STD 58, RFC
2579, April 1999. 2579, April 1999.
skipping to change at page 11, line 50 skipping to change at page 12, line 4
[RFC3036] Anderson, L., Doolan, P., Feldman, N., [RFC3036] Anderson, L., Doolan, P., Feldman, N.,
Fredette, A., and B. Thomas, "LDP Fredette, A., and B. Thomas, "LDP
Specification", RFC 3036, January 2001. Specification", RFC 3036, January 2001.
[Assigned] Reynolds, J., and J. Postel, "Assigned [Assigned] Reynolds, J., and J. Postel, "Assigned
Numbers", RFC 1700, October 1994. See also: Numbers", RFC 1700, October 1994. See also:
http://www.isi.edu/in- http://www.isi.edu/in-
notes/iana/assignments/smi-numbers notes/iana/assignments/smi-numbers
[RSVPTE] Awduche, D., Berger, L., Gan, D., Li, T., [RSVPTE] Awduche, D., Berger, L., Gan, D., Li, T.,
Srinivasan, V., Swallow, G., RSVP-TE: Srinivasan, V., and G. Swallow, "RSVP-TE:
Extensions to RSVP for LSP Tunnels, draft- Extensions to RSVP for LSP Tunnels", draft-
ietf-mpls-rsvp-lsp-tunnel-08.txt, February ietf-mpls-rsvp-lsp-tunnel-08.txt, February
2001. 2001.
[CRLDP] Jamoussi, B., Aboul-Magd, O., Andersson, L., [CRLDP] Jamoussi, B., Aboul-Magd, O., Andersson, L.,
IETF Draft MPLS TC MIB August 2001
Ashwood-Smith, P., Hellstrand, F., Sundell, Ashwood-Smith, P., Hellstrand, F., Sundell,
K., Callon, R., Dantu, R., Wu, L., Doolan, K., Callon, R., Dantu, R., Wu, L., Doolan,
P., Worster, T., Feldman, N., Fredette, A., P., Worster, T., Feldman, N., Fredette, A.,
Girish, M., Gray, E., Halpern, J., Heinanen, Girish, M., Gray, E., Halpern, J., Heinanen,
J., Kilty, T., Malis, A., Vaananen, P., J., Kilty, T., Malis, A., and P. Vaananen,
Constraint-Based LSP Setup using LDP, draft- "Constraint-Based LSP Setup using LDP",
ietf-mpls-cr-ldp-05.txt, February 2001." draft-ietf-mpls-cr-ldp-05.txt, February
2001."
7. Authors' Addresses 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
skipping to change at page 13, line 4 skipping to change at page 13, line 10
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
8. Full Copyright Statement 8. Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Copyright (C) The Internet Society (2001). All Rights
IETF Draft MPLS TC MIB August 2001
Reserved. Reserved.
This document and translations of it may be copied and This document and translations of it may be copied and
furnished to others, and derivative works that comment on furnished to others, and derivative works that comment on
or otherwise explain it or assist in its implementation may or otherwise explain it or assist in its implementation may
be prepared, copied, published and distributed, in whole or be prepared, copied, published and distributed, in whole or
in part, without restriction of any kind, provided that the in part, without restriction of any kind, provided that the
above copyright notice and this paragraph are included on above copyright notice and this paragraph are included on
all such copies and derivative works. However, this all such copies and derivative works. However, this
document itself may not be modified in any way, such as by document itself may not be modified in any way, such as by
 End of changes. 

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