draft-ietf-ccamp-gmpls-tc-mib-00.txt   draft-ietf-ccamp-gmpls-tc-mib-01.txt 
Network Working Group Thomas D. Nadeau Network Working Group Thomas D. Nadeau
Internet Draft Cisco Systems, Inc. Internet Draft Cisco Systems, Inc.
Expires: December 2002 Expires: February 2004
Cheenu Srinivasan Cheenu Srinivasan
Parama Networks, Inc. Bloomberg L.P.
Adrian Farrel Adrian Farrel
Movaz Networks, Inc. Old Dog Consulting
Edward Harrison
Tim Hall Tim Hall
Ed Harrison
Data Connection Ltd. Data Connection Ltd.
June 2002 August 2003
Definition of Textual Conventions and OBJECT-IDENTITIES for Definitions of Textual Conventions for Generalized Multi-Protocol
Generalized Multiprotocol Label Switching (GMPLS) Management Label Switching (GMPLS) Management
draft-ietf-ccamp-gmpls-tc-mib-00.txt draft-ietf-ccamp-gmpls-tc-mib-01.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
conformance with all provisions of Section 10 of RFC 2026 all provisions of Section 10 of RFC 2026.
[RFC2026].
Internet-Drafts are working documents of the Internet Internet-Drafts are working documents of the Internet Engineering
Engineering Task Force (IETF), its areas, and its working Task Force (IETF), its areas, and its working groups. Note that
groups. Note that other groups may also distribute other groups may also distribute working documents as Internet-
working documents as Internet-Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum Internet-Drafts are draft documents valid for a maximum of six months
of six months and may be updated, replaced, or obsoleted and may be updated, replaced, or obsoleted by other documents at any
by other documents at any time. It is inappropriate to time. It is inappropriate to use Internet-Drafts as reference
use Internet- Drafts as reference material or to cite material or to cite them other than as "work in progress."
them other 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 http://www.ietf.org/shadow.html.
Abstract Abstract
This memo describes Textual Conventions and OBJECT- This document defines a Management Information Base (MIB) module
IDENTITIES common to the Management Information Bases which contains Textual Conventions to represent commonly used
(MIBs) for managing Generalized Multiprotocol Label Generalized Multi-Protocol Label Switching (GMPLS) management
Switching (GMPLS) networks. information. The intent is that these TEXTUAL CONVENTIONS (TCs) will
be imported and used in GMPLS related MIB modules that would
It supplements [TCMIB] which describes Textual otherwise define their own representations.
Conventions and OBJECT-IDENTITIES common to the
Management Information Bases (MIBs) for managing
Multiprotocol Label Switching (MPLS) networks.
Nadeau, et al. [Page 1 ]
Table of Contents Table of Contents
1. Changes and Pending Work 2 1. Introduction 2
1.1. Changes Since the Last Version 2 2. The SNMP Management Framework 2
1.2. Pending Work 2 3. GMPLS Textual Conventions MIB Definitions 3
2. Introduction 2 4. Security Considerations 5
3. The SNMP Management Framework 3 5. IANA Considerations 5
4. GMPLS TC MIB Definitions 4 6. References 5
5. Security Considerations 6 6.1. NORMATIVE REFERENCES 5
6. References 7 6.2. INFORMATIONAL REFERENCES 6
6.1. Normative References 7 7. Authors' Addresses 7
6.2. Informational References 7 8. Full Copyright Statement 7
7. Authors' Addresses 10 9. Intellectual Property Notice 8
8. Full Copyright Statement 11
1. Changes and Pending Work
This section must be removed before the draft progresses
to RFC.
1.1. Changes Since the Last Version
This is the first version of this draft.
1.2. Pending Work
- Update reference to latest versions of drafts.
- Check compilation of MIB.
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 GMPLS and GMPLS-related
MIBs.
This document supplements [TCMIB] that defines Textual
Conventions and OBJECT-IDENTITIES for Multiprotocol Label
Switching (MPLS) Management. [TCMIB] may continue to be
used without this MIB in networks that support only MPLS.
Comments should be made directly to the CCAMP mailing
list at ccamp@ops.ietf.org.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
"SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",
"MAY", and "OPTIONAL" in this document are to be
Nadeau, et al. [Page 2 ]
interpreted as described in RFC 2119, reference
[RFC2119].
For an introduction to the concepts of GMPLS, see
[GMPLSArch].
3. The SNMP Management Framework
The SNMP Management Framework presently consists of five
major components:
- An overall architecture, described in RFC 2571 1. Introduction
[RFC2571].
- Mechanisms for describing and naming objects and This document defines a MIB module which contains Textual Conventions
events for the purpose of management. The first for Generalized Multi-Protocol Label Switching (GMPLS) networks.
version of this Structure of Management Information These Textual Conventions should be imported by MIB modules which
(SMI) is called SMIv1 and described in STD 16, RFC manage GMPLS networks.
1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and STD 16,
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].
- Message protocols for transferring management This MIB module supplements the MIB module in [TCMIB] that defines
information. The first version of the SNMP message Textual Conventions for Multiprotocol Label Switching (MPLS)
protocol is called SNMPv1 and described in STD 15, RFC Management. [TCMIB] may continue to be used without this MIB module
1157 [RFC1157]. A second version of the SNMP message in networks that support only MPLS.
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].
- Protocol operations for accessing management The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
information. The first set of protocol operations and "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
associated PDU formats is described in STD 15, RFC document are to be interpreted as described in RFC 2119 [RFC2119].
1157 [RFC1157]. A second set of protocol operations
and associated PDU formats is described in RFC 1905
[RFC1905].
- A set of fundamental applications described in RFC Comments should be made directly to the CCAMP mailing list at
2573 [RFC2573] and the view-based access control ccamp@ops.ietf.org.
mechanism described in RFC 2575 [RFC2575].
A more detailed introduction to the current SNMP For an introduction to the concepts of GMPLS, see [GMPLSArch].
Management Framework can be found in RFC 2570 [RFC2570].
Managed objects are accessed via a virtual information 2. The SNMP Management Framework
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 For a detailed overview of the documents that describe the current
SMIv2. A MIB conforming to the SMIv1 can be produced Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Nadeau, et al. [Page 3 ] Managed objects are accessed via a virtual information store, termed
through the appropriate translations. The resulting the Management Information Base or MIB. MIB objects are generally
translated MIB must be semantically equivalent, except accessed through the Simple Network Management Protocol (SNMP).
where objects or events are omitted because no Objects in the MIB are defined using the mechanisms defined in the
translation is possible (use of Counter64). Some machine Structure of Management Information (SMI). This memo specifies a MIB
readable information in SMIv2 will be converted into module that is compliant to the SMIv2, which is described in STD 58,
textual descriptions in SMIv1 during the translation RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
process. However, this loss of machine readable [RFC2580].
information is not considered to change the semantics of
the MIB.
4. GMPLS TC MIB Definitions 3. GMPLS Textual Conventions MIB Definitions
GMPLS-TC-MIB DEFINITIONS ::= BEGIN GMPLS-TC-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, Unsigned32, Integer32 MODULE-IDENTITY, Unsigned32, Integer32
FROM SNMPv2-SMI FROM SNMPv2-SMI
transmission
FROM RFC1213-MIB
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
; ;
gmplsTCMIB MODULE-IDENTITY gmplsTCStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"200224060900Z" -- 24 June 2002 9:00:00 GMT "200308190900Z " -- 19 August 2003 9:00:00 GMT"
ORGANIZATION ORGANIZATION "Common Control And Management Protocols (CCAMP)
"Common Control And Management Protocols (CCAMP)
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
Postal: Cisco Systems, Inc. Cisco Systems, Inc.
250 Apollo Drive
Chelmsford, MA 01824
Tel: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Cheenu Srinivasan Cheenu Srinivasan
Postal: Parama Networks, Inc. Bloomberg L.P.
1030 Broad Street Email: cheenu@bloomberg.net
Shrewsbury, NJ 07702
Tel: +1-732-544-9120 x731
Email: cheenu@paramanet.com
Tel: +1-732-544-9120x731
Adrian Farrel Adrian Farrel
Postal: Movaz Networks, Inc. Old Dog Consulting
7926 Jones Branch Drive Email: adrian@olddog.co.uk
McLean, VA 22102
Tel: +1-703-847-1867
Email: afarrel@movaz.com
Edward Harrison
Postal: Data Connection Ltd.
100 Church Street
Enfield, Middlesex
EN2 6BQ, United Kingdom
Nadeau, et al. [Page 4 ] Ed Harrison
Tel: +44-20-8366-1177 Data Connection Ltd.
Email: eph@dataconnection.com Email: ed.harrison@dataconnection.com
Tim Hall Tim Hall
Postal: Data Connection Ltd. Data Connection Ltd.
100 Church Street
Enfield, Middlesex
EN2 6BQ, United Kingdom
Tel: +44-20-8366-1177
Email: timhall@dataconnection.com Email: timhall@dataconnection.com
Email comments to the CCAMP WG Mailing List at Comments about this document should be emailed direct to the
ccamp@ops.ietf.org." CCAMP working group mailing list at ccamp@ops.ietf.org"
DESCRIPTION DESCRIPTION
"This MIB module defines Textual Conventions "Copyright (C) The Internet Society (2003). This version of this
and OBJECT-IDENTITIES for use in documents MIB module is part of RFCXXX; see the RFC itself for full legal
defining management information bases notices.
(MIBs) for managing GMPLS networks."
This MIB module defines Textual Conventions for concepts used in
Generalized Multi-Protocol Label Switching (GMPLS) networks."
-- Revision history. -- Revision history.
REVISION REVISION
"200224060900Z" -- 24 June 2002 09:00:00 GMT "2003080190900Z" -- 19 August 2003 09:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial version." "Initial version published as part of RFC XXXX."
-- Above revision history to be replaced as below. -- Please see the IANA Considerations Section.
-- REVISION -- The requested gmplsStdMIB subId is xx, i.e.
-- "yyyymmddhhmmZ"-- DESCRIPTION "Initial version, published as RFC xxxx" ::= { gmplsStdMIB xx }
-- xxxx to be assigned by RFC Editor gmplsStdMIB OBJECT IDENTIFIER
::= { gmplsMIB 1 }
-- This object identifier needs to be assigned by IANA. -- This object identifier needs to be assigned by IANA.
-- Note that MPLS has been assigned an ifType of 166 and that an OID -- Since mpls has been assigned an ifType of 166 we recommend
-- of 166 has been suggested for the MPLS MIBs. -- that this OID be 166 as well, i.e.
gmplsMIB OBJECT IDENTIFIER ::= { transmission xxx } ::= { transmission XXX }
-- Textual Conventions (sorted alphabetically). -- Textual Conventions (sorted alphabetically).
GmplsFreeformLabel ::= TEXTUAL-CONVENTION GmplsFreeformLabel ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents a freeform "This value represents a freeform generalized MPLS Label. This
generalized MPLS Label. This can be used can be used to represent label types which are not standard
to represent label types which are not in the drafts. It may also be used by systems that do not
standard in the drafts." wish to represent the labels using the specific label types."
SYNTAX OCTET STRING (SIZE (0..64)) SYNTAX OCTET STRING (SIZE (0..64))
GmplsGeneralizedLabelSubtypes ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Determines the interpretation that should
be applied to a label given its label type
as specified by
GmplsGeneralizedLabelTypes."
SYNTAX INTEGER {
mplsLabel(1),
Nadeau, et al. [Page 5 ]
portWavelengthLabel(2),
freeformGeneralizedLabel(3),
sonetLabel(4),
sdhLabel(5),
wavebandLabel(6)
}
GmplsGeneralizedLabelTypes ::= TEXTUAL-CONVENTION GmplsGeneralizedLabelTypes ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The label types that are defined for "Determines the interpretation that should be applied to a
Generalized MPLS." label."
SYNTAX INTEGER {
mplsLabel(1),
generalizedLabel(2)
}
GmplsHopUnnumAddrTypes ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Identifies whether a hop of an explicit or
reported route uses unnumbered addresses
and, if so, the type of unnumbered
address."
SYNTAX INTEGER { SYNTAX INTEGER {
numbered(1), gmplsMplsLabel(1),
unnumberedIfIpV4(2), gmplsPortWavelengthLabel(2),
unnumberedIfIpV6(3) gmplsFreeformGeneralizedLabel(3),
gmplsSonetLabel(4),
gmplsSdhLabel(5),
gmplsWavebandLabel(6)
} }
GmplsSegmentDirection ::= TEXTUAL-CONVENTION GmplsSegmentDirection ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The direction of data flow on an LSP "The direction of data flow on an LSP segment with respect to the
segment with respect to the head of the head of the LSP.
LSP.
Where an LSP is signaled using a Where an LSP is signaled using a conventional signaling
conventional signaling protocol, the 'head' protocol, the 'head' of the LSP is the source of the signaling
of the LSP is the source of the signaling (also known as the ingress) and the 'tail' is the destination
(also known as the ingress) and the 'tail' (also known as the egress).
is the destination (also known as the
egress).
For manually configured LSPs an arbitrary For manually configured LSPs an arbitrary decision must be made
decision must be made about which LER is about which LER is the 'head'."
the 'head'."
SYNTAX INTEGER { SYNTAX INTEGER {
forward(1), forward(1),
reverse(2) reverse(2)
} }
END END
Nadeau, et al. [Page 6 ] 4. Security Considerations
5. Security Considerations
This memo defines textual conventions and object
identities for use in GMPLS MIB modules. Security issues
for these MIB modules are addressed in the memos defining
those modules.
6. References
6.1. Normative References
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and
J. Davin, "Simple Network Management
Protocol", RFC 1157, May 1990.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB
Definitions", RFC 1212, March 1991.
[RFC2119] Bradner, S., "Key words for use in RFCs to
Indicate Requirement Levels", BCP 14, RFC
2119, March 1997.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder,
J., Case, J., Rose, M., and S. Waldbusser,
"Textual Conventions for SMIv2", STD 58,
RFC 2579, April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholtz, "The
Interfaces Group MIB", RFC 2863, June 2000.
[GMPLSArch] Ashwood-Smith, P., Awduche, D., Banerjee,
A., Basak, D, Berger, L., Bernstein, G.,
Drake, J., Fan, Y., Fedyk, D., Grammel, D.,
Kompella, K., Kullberg, A., Lang, J., Liaw,
F., Papadimitriou, D., Pendarakis, D.,
Rajagopalan, B., Rekhter, Y., Saha, D.,
Sandick, H., Sharma, V., Swallow, G., Tang,
Z., Yu, J., Zinin, A., Nadeau, T., Mannie,
E., Generalized Multiprotocol Label
Switching (GMPLS) Architecture, Internet
Draft <draft-many-gmpls-architecture-
01.txt>, March 2001, work in progress.
6.2. Informational References
[RFC1155] Rose, M., and K. McCloghrie, "Structure and This module does not define any management objects. Instead, it
Identification of Management Information defines a set of textual conventions which may be used by other GMPLS
for TCP/IP-based Internets", RFC 1155, May MIB modules to define management objects.
1990.
[RFC1213] McCloghrie, K, and M. Rose, "Management Meaningful security considerations can only be written in the MIB
Information Base for Network Management of modules that define management objects. Therefore, this document has
TCP/IP Based Internets", RFC 1213, March no impact on the security of the Internet.
Nadeau, et al. [Page 7 ] 5. IANA Considerations
1991.
[RFC1215] M. Rose, "A Convention for Defining Traps IANA is requested to make a MIB OID assignment under the transmission
for use with the SNMP", RFC 1215, March branch, that is, assign the gmplsStdMIB under { transmission 166 }.
1991.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. This sub-id is requested because 166 is the ifType for mpls(166) and
Waldbusser, "Introduction to Community- is available under transmission.
based SNMPv2", RFC 1901, January 1996.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. In the future, GMPLS related standards track MIB modules should be
Waldbusser, "Protocol Operations for rooted under the mplsStdMIB (sic) subtree. IANA is requested to
Version 2 of the Simple Network Management manage that namespace. New assignments can only be made via a
Protocol (SNMPv2)", RFC 1905, January 1996. Standards Action as specified in [RFC2434].
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. This document also requests IANA to assign { gmplsStdMIB xx } to the
Waldbusser, "Transport Mappings for Version GMPLS-TC-STD-MIB specified in this document.
2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1906, January 1996.
[RFC2514] Noto, et. al., "Definitions of Textual 6. References
Conventions and OBJECT-IDENTITIES for ATM
Management", RFC 2514, Feb. 1999
[RFC2570] Case, J., Mundy, R., Partain, D., and B. 6.1. Normative References
Stewart, "Introduction to Version 3 of the
Internet-standard Network Management
Framework", RFC 2570, April 1999.
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
"An Architecture for Describing SNMP Requirement Levels", BCP 14, RFC 2119, March 1997.
Management Frameworks", RFC 2571, April
1999.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
Wijnen, "Message Processing and Dispatching Case, J., Rose, M. and S. Waldbusser, "Structure of
for the Simple Network Management Protocol Management Information Version 2 (SMIv2)", STD 58,
(SNMP)", RFC 2572, April 1999. RFC 2578, April 1999.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
"SNMPv3 Applications", RFC 2573, April Case, J., Rose, M. and S. Waldbusser, "Textual
Conventions for SMIv2", STD 58, RFC 2579, April
1999. 1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
Security Model (USM) for version 3 of the Case, J., Rose, M. and S. Waldbusser, "Conformance
Simple Network Management Protocol Statements for SMIv2", STD 58, RFC 2580, April 1999.
(SNMPv3)", RFC 2574, 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.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder,
J., Case, J., Rose, M., and S. Waldbusser,
"Structure of Management Information
Nadeau, et al. [Page 8 ]
Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, [GMPLS-ARCH] Mannie, E., (editor), et. al. "Generalized Multi-
J., Case, J., Rose, M., and S. Waldbusser, Protocol Label Switching (GMPLS) Architecture",
"Conformance Statements for SMIv2", STD 58, draft-ietf-ccamp-gmpls-architecture-07.txt, May
RFC 2580, April 1999. 2003.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 6.2. Informational References
"Multiprotocol Label Switching
Architecture", RFC 3031, August 1999.
[RFC3032] Rosen, E., Rekhter, Y., Tappan, D., [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for
Farinacci, D., Federokow, G., Li, T., and Writing an IANA Considerations Section in RFCs",
A. Conta, "MPLS Label Stack Encoding", RFC BCP: 26, RFC 2434, October 1998.
3032, January 2001.
[RFC3034] Conta, A., Doolan, P., Malis, A., "Use of [RFC3031] Rosen, E., Viswananthan, A., and R. Callon,
Label Switching on Frame Relay Networks Multiprotocol Label Switching Architecture",
Specification", RFC 3034, January 2001. RFC 3031, January 2001.
[RFC3035] Davie, B., Lawrence, J., McCloghrie, K., [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T.,
Rosen, E., Swallow, G., Rekhter, Y., and P. Srinivasan, V., Swallow, G., "RSVP-TE: Extensions to
Doolan, "MPLS using LDP and ATM VC RSVP for LSP Tunnels", RFC 3209, December 2001.
switching", RFC 3035, January 2001.
[RFC3036] Anderson, L., Doolan, P., Feldman, N., [RFC3212] Jamoussi, B., (editor), et. al. "Constraint-Based
Fredette, A., and B. Thomas, "LDP LSP Setup using LDP", RFC 3212, January 2002.
Specification", RFC 3036, January 2001.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
Srinivasan, V., and G. Swallow, "RSVP-TE: "Introduction and Applicability Statements for
Extensions to RSVP for LSP Tunnels", Internet-Standard Management Framework", RFC 3410,
RFC3209, December 2001. December 2002.
[CRLDP] Jamoussi, B., Aboul-Magd, O., Andersson, [RFC3471] Berger, L. (Editor), "Generalized Multi-Protocol
L., Ashwood-Smith, P., Hellstrand, F., Label Switching (GMPLS) Signaling Functional
Sundell, K., Callon, R., Dantu, R., Wu, L., Description", RFC 3471, January 2003.
Doolan, P., Worster, T., Feldman, N.,
Fredette, A., Girish, M., Gray, E.,
Halpern, J., Heinanen, J., Kilty, T.,
Malis, A., and P. Vaananen, "Constraint-
Based LSP Setup using LDP", draft-ietf-mpls-
cr-ldp-05.txt, February 2001, work in
progress.
[GMPLSSig] Ashwood-Smith, P., Awduche, D., Banerjee, [RFC3472] Ashwood-Smith, P., Berger, L. (Editors),
A., Basak, D, Berger, L., Bernstein, G., "Generalized MPLS Signaling - CR-LDP Extensions",
Drake, J., Fan, Y., Fedyk, D., Grammel, D., RFC 3472, January 2003.
Kompella, K., Kullberg, A., Lang,
Rajagopalan, B., Rekhter, Y., Saha, D.,
Sharma, V., Swallow, G., Bo Tang, Z.,
Generalized MPLS - Signaling Functional
Description, <draft-ietf-mpls-generalized-
signaling-04.txt>, May 2001, work in
progress.
Nadeau, et al. [Page 9 ] [RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling -
[GMPLSCRLDP] Ashwood-Smith, P., Awduche, D., Banerjee, RSVP-TE Extensions", RFC 3473 January 2003.
A., Basak, D, Berger, L., Bernstein, G.,
Drake, J., Fan, Y., Fedyk, D., Grammel, D.,
Kompella, K., Kullberg, A., Lang,
Rajagopalan, B., Rekhter, Y., Saha, D.,
Sharma, V., Swallow, G., Bo Tang, Z.,
Generalized MPLS Signaling - CR-LDP
Extensions, Internet Draft <draft-ietf-mpls-
generalized-cr-ldp-03.txt>, May 2001, work
in progress.
[GMPLSRSVPTE] Ashwood-Smith, P., Awduche, D., Banerjee, [GMPLSSonetSDH] Mannie, E., Papadimitriou, D. (Editors),
A., Basak, D, Berger, L., Bernstein, G., "Generalized Multi-Protocol Label Switching
Drake, J., Fan, Y., Fedyk, D., Grammel, D., Extensions for SONET and SDH Control", Internet
Kompella, K., Kullberg, A., Lang, Draft <draft-ietf-ccamp-gmpls-sonet-sdh-08.txt>,
Rajagopalan, B., Rekhter, Y., Saha, D., February 2003, work in progress.
Sharma, V., Swallow, G., Bo Tang, Z.,
Generalized MPLS Signaling - RSVP-TE
Extensions, Internet Draft <draft-ietf-mpls-
generalized-rsvp-te-03.txt>, May 2001, work
in progress.
[GMPLSSonetSDH] Mannie, E., Ansorge, S., Ashwood-Smith, [TCMIB] Nadeau, T., Cucchiara, J. (Editors) "Definitions
P., Banerjee, A., Berger, L., Bernstein, of Textual Conventions for Multiprotocol Label
G., Chiu, A., Drake, J., Fan, Y., Fontana, Switching (MPLS) Management", Internet Draft
M., Grammel, G., Heiles, J., Katukam, S., <draft-ietf-mpls-tc-mib-09.txt>, August 2003,
Kompella, K., Lang, J. P., Liaw, F., Lin, work in progress.
Z., Mack-Crane, B., Papadimitriou, D.,
Pendarakis, D., Raftelis, M., Rajagopalan,
B., Rekhter, Y., Saha, D., Sharma, V.,
Swallow, G., Bo Tang, Z., Varma, E.,
Vissers, M., Xu, Y., GMPLS Extensions for
SONET and SDH Control, Internet Draft
<draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>,
May 2001, work in progress.
[TCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C, [GMPLSLSRMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T.,
Viswanathan, A. and H. Sjostrand, and Harrison, E., " Generalized Multiprotocol Label
"Definition of Textual Conventions and Switching (GMPLS) Label Switching Router (LSR)
OBJECT-IDENTITIES for Multiprotocol Label Management Information Base", draft-ietf-ccamp-
Switching (MPLS) Management", Internet gmpls-lsr-mib-01.txt, August 2003, work in progress.
Draft <draft-ietf-mpls-tc-mib-03.txt>,
January 2002, work in progress.
[GMPLSTEMIB] Nadeau, T., Srinivasan, C., Farrel, A., [GMPLSTEMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T.,
Hall, T., and Harrison, E., "Extensions to and Harrison, E., "Generalized Multiprotocol Label
the MPLS Traffic Engineering Management Switching (GMPLS) Traffic Engineering Management
Information Base in Support of Generalized Information Base", draft-ietf-ccamp-gmpls-te-mib-
Multiprotocol Label Switching", draft- 01.txt, August 2003, work in progress.
nadeau-ccamp-gmpls-te-mib-01.txt, January
2002, work in progress.
7. Authors' Addresses 7. Authors' Addresses
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
300 Apollo Drive 300 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
Cheenu Srinivasan Cheenu Srinivasan
Parama Networks, Inc. Bloomberg L.P.
1030 Broad Street 499 Park Ave.,
Shrewsbury, NJ 07702 New York, NY 10022
Phone: +1-732-544-9120 x731 Phone: +1-212-893-3682
Email: cheenu@paramanet.com Email: cheenu@bloomberg.net
Adrian Farrel Adrian Farrel
Movaz Networks, Inc. Old Dog Consulting
7926 Jones Branch Drive, Suite 615 Phone: +44-(0)-1978-860944
McLean VA, 22102USA Email: adrian@olddog.co.uk
Phone: +1-703-847-1867
Email: afarrel@movaz.com
Tim Hall Tim Hall
Data Connection Ltd. Data Connection Ltd.
100 Church Street 100 Church Street
Enfield, Middlesex Enfield, Middlesex
EN2 6BQ, UK EN2 6BQ, UK
Phone: +44 20 8366 1177 Phone: +44 20 8366 1177
Email: timhall@dataconnection.com Email: timhall@dataconnection.com
Edward Harrison Ed Harrison
Data Connection Ltd. Data Connection Ltd.
100 Church Street 100 Church Street
Enfield, Middlesex Enfield, Middlesex
EN2 6BQ, UK EN2 6BQ, UK
Phone: +44 20 8366 1177 Phone: +44 20 8366 1177
Email: eph@dataconnection.com Email: ed.harrison@dataconnection.com
8. Full Copyright Statement 8. Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Copyright (C) The Internet Society (2003). All Rights Reserved.
Reserved.
This document and translations of it may be copied and This document and translations of it may be copied and furnished
furnished to others, and derivative works that comment on to others, and derivative works that comment on or otherwise explain
or otherwise explain it or assist in its implementation it or assist in its implementation may be prepared, copied, published
may be prepared, copied, published and distributed, in and distributed, in whole or in part, without restriction of any
whole or in part, without restriction of any kind, kind, provided that the above copyright notice and this paragraph are
provided that the above copyright notice and this included on all such copies and derivative works. However, this
paragraph are included on all such copies and derivative document itself may not be modified in any way, such as by removing
works. However, this document itself may not be modified the copyright notice or references to the Internet Society or other
in any way, such as by removing the copyright notice or Internet organizations, except as needed for the purpose of
references to the Internet Society or other Internet developing Internet standards in which case the procedures for
organizations, except as needed for the purpose of copyrights defined in the Internet Standards process must be
developing Internet standards in which case the followed, or as required to translate it into languages other than
procedures for copyrights defined in the Internet English.
Standards process must be followed, or as required to
translate it into languages other than English.
The limited permissions granted above are perpetual and The limited permissions granted above are perpetual and will not be
will not be revoked by the Internet Society or its revoked by the Internet Society or its successors or assigns. This
successors or assigns. This document and the information document and the information contained herein is provided on an "AS
contained herein is provided on an "AS IS" basis and THE IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY OR FITNESS FOR A PARTICULAR PURPOSE.
IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. 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 implementers 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.
 End of changes. 

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