draft-ietf-ccamp-gmpls-overlay-03.txt   draft-ietf-ccamp-gmpls-overlay-04.txt 
Network Working Group G. Swallow Network Working Group G. Swallow
Internet Draft Cisco Systems, Inc Internet Draft Cisco Systems, Inc
Category: Standards Track Category: Standards Track
Expiration Date: August 2004 Expiration Date: October 2004
J. Drake J. Drake
Calient Networks, Inc Calient Networks, Inc
H. Ishimatsu H. Ishimatsu
Japan Telecom Japan Telecom
Y. Rekhter Y. Rekhter
Juniper Networks, Inc Juniper Networks, Inc
February 2004 April 2004
GMPLS UNI: RSVP Support for the Overlay Model GMPLS UNI: RSVP Support for the Overlay Model
draft-ietf-ccamp-gmpls-overlay-03.txt draft-ietf-ccamp-gmpls-overlay-04.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet-Drafts are working all provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 2, line 15 skipping to change at page 2, line 12
be used to support a number of deployment scenarios. This memo be used to support a number of deployment scenarios. This memo
addresses the application of GMPLS to the overlay model. addresses the application of GMPLS to the overlay model.
Contents Contents
1 Introduction ........................................... 3 1 Introduction ........................................... 3
1.1 GMPLS User-Network Interface (GMPLS UNI) ............... 4 1.1 GMPLS User-Network Interface (GMPLS UNI) ............... 4
2 Addressing ............................................. 5 2 Addressing ............................................. 5
3 ERO Processing ......................................... 6 3 ERO Processing ......................................... 6
3.1 Path Message without ERO ............................... 6 3.1 Path Message without ERO ............................... 6
3.2 Path Message with ERO .................................. 7 3.2 Path Message with ERO .................................. 6
3.3 Explicit Label Control ................................. 7 3.3 Explicit Label Control ................................. 6
4 RRO Processing ......................................... 7 4 RRO Processing ......................................... 7
5 Notification ........................................... 7 5 Notification ........................................... 7
6 Connection Deletion .................................... 8 6 Connection Deletion .................................... 7
6.1 Alarm-Free Connection Deletion ......................... 8 6.1 Alarm-Free Connection Deletion ......................... 7
6.2 Connection Deletion with PathErr ....................... 8 6.2 Connection Deletion with PathErr ....................... 8
7 VPN Connections ........................................ 9 7 VPN Connections ........................................ 8
8 Security Considerations ................................ 10 8 Security Considerations ................................ 9
9 Acknowledgments ........................................ 10 9 Acknowledgments ........................................ 9
10 References ............................................. 10 10 References ............................................. 9
10.1 Normative References ................................... 10 10.1 Normative References ................................... 9
10.2 Informative References ................................. 10 10.2 Informative References ................................. 10
11 Authors' Addresses ..................................... 11 11 Authors' Addresses ..................................... 10
12 Intellectual Property Notice ........................... 11 12 Intellectual Property Notice ........................... 11
12.1 IPR Disclosure Acknowledgement ......................... 11
13 Full Copyright Statement ............................... 12 13 Full Copyright Statement ............................... 12
1. Introduction 1. Introduction
Generalized Multiprotocol Label Switching (GMPLS) defines both Generalized Multiprotocol Label Switching (GMPLS) defines both
routing and signaling protocols for the creation of Label Switched routing and signaling protocols for the creation of Label Switched
Paths (LSPs) in various transport technologies. These protocols can Paths (LSPs) in various transport technologies. These protocols can
be used to support a number of deployment scenarios. In a peer be used to support a number of deployment scenarios. In a peer
model, edge-nodes support both a routing and a signaling protocol. model, edge-nodes support both a routing and a signaling protocol.
The protocol interactions between an edge-node and a core node are The protocol interactions between an edge-node and a core node are
skipping to change at page 7, line 23 skipping to change at page 6, line 50
3.3. Explicit Label Control 3.3. Explicit Label Control
In order to support explicit label control and full identification of In order to support explicit label control and full identification of
the egress link an ingress edge-node may include an ERO that consists the egress link an ingress edge-node may include an ERO that consists
of only the last hop. This is signaled by setting the first of only the last hop. This is signaled by setting the first
subobject of the ERO to the node-ID of the egress core-node with the subobject of the ERO to the node-ID of the egress core-node with the
L-bit set. Following this subobject are all other subobjects L-bit set. Following this subobject are all other subobjects
necessary to identify the link and labels as they would normally necessary to identify the link and labels as they would normally
appear. appear.
This process is described in [RFC3473] and [EXPLICIT].
4. RRO Processing 4. RRO Processing
An edge-node MAY include an RRO. A core-node MAY remove the RRO from An edge-node MAY include an RRO. A core-node MAY remove the RRO from
the Path message before forwarding it. Further the core-node may the Path message before forwarding it. Further the core-node may
remove the RRO from a Resv message before forwarding it to the edge- remove the RRO from a Resv message before forwarding it to the edge-
node. Such behavior is controlled by (hopefully consistent) node. Such behavior is controlled by (hopefully consistent)
configuration. configuration.
Further a core-node MAY edit the RRO in a Resv message such that it Further a core-node MAY edit the RRO in a Resv message such that it
includes only the subobjects from the egress core-node through the includes only the subobjects from the egress core-node through the
skipping to change at page 10, line 32 skipping to change at page 9, line 47
[RFC3471] Berger, L., "Generalized MPLS Signaling Functional [RFC3471] Berger, L., "Generalized MPLS Signaling Functional
Description", RFC 3471, January 2003. Description", RFC 3471, January 2003.
[RFC3473] Berger, L., "Generalized MPLS Signaling RSVP-TE [RFC3473] Berger, L., "Generalized MPLS Signaling RSVP-TE
Extensions", RFC 3473, January 2003. Extensions", RFC 3473, January 2003.
[RFC3209] Awduche, et al, "RSVP-TE: Extensions to RSVP for [RFC3209] Awduche, et al, "RSVP-TE: Extensions to RSVP for
LSP Tunnels", RFC 3209, December 2001. LSP Tunnels", RFC 3209, December 2001.
[RFC3667] Bradner, S., "IETF Rights in Contributions", BCP 78,
RFC 3667, February 2004.
[RFC3668] Bradner, S., Ed., "Intellectual Property Rights in IETF
Technology", BCP 79, RFC 3668, February 2004.
10.2. Informative References 10.2. Informative References
[GMPLS-ARCH] Mannie, E, et al., "Generalized Multi-Protocol [GMPLS-ARCH] Mannie, E, et al., "Generalized Multi-Protocol
Label Switching (GMPLS) Architecture", Internet Draft, Label Switching (GMPLS) Architecture", draft-ietf-ccamp-
draft-ietf-ccamp-gmpls-architecture-04.txt, Feb., 2003. gmpls-architecture-04.txt, February 2003, work in
progress.
[MPLS-HIER] Kompella, K., and Rekhter, Y., "LSP Hierarchy with [MPLS-HIER] Kompella, K., and Rekhter, Y., "LSP Hierarchy with
MPLS TE", Internet Draft, MPLS TE", draft-ietf-mpls-lsp-hierarchy-08.txt,
draft-ietf-mpls-lsp-hierarchy-08.txt, Sep., 2001. September 2001, work in progress.
[BUNDLE] Kompella, K., Rekhter, Y., and Berger, L., "Link [BUNDLE] Kompella, K., Rekhter, Y., and Berger, L., "Link
Bundling in MPLS Traffic Engineering", Internet Draft, Bundling in MPLS Traffic Engineering", draft-ietf-mpls-
draft-ietf-mpls-bundle-04.txt, July, 2002. bundle-04.txt, July 2002, work in progress.
[RFC3477] Kompella, K., and Rekhter, Y., "Signaling Unnumbered [RFC3477] Kompella, K., and Rekhter, Y., "Signaling Unnumbered
Links in RSVP-TE", RFC 3477, January 2003. Links in RSVP-TE", RFC 3477, January 2003.
[G.8080] ITU-T Rec. G.8080/Y.1304, "Architecture for the [G.8080] ITU-T Rec. G.8080/Y.1304, "Architecture for the
Automatically Switched Optical Network (ASON)," Automatically Switched Optical Network (ASON),"
November 2001 (and Revision, January 2003). November 2001 (and Revision, January 2003).
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels," RFC 2119. Requirement Levels," RFC 2119.
[EXPLICIT] Berger, L., "GMPLS Signaling Procedure For Egress
Control", draft-ccamp-gmpls-egress-control-00.txt,
March 2004, work in progress.
11. Authors' Addresses 11. Authors' Addresses
John Drake John Drake
Calient Networks Calient Networks
5853 Rue Ferrari 5853 Rue Ferrari
San Jose, CA 95138 San Jose, CA 95138
Phone: +1 408 972 3720 Phone: +1 408 972 3720
Email: jdrake@calient.net Email: jdrake@calient.net
Hirokazu Ishimatsu Hirokazu Ishimatsu
skipping to change at page 11, line 41 skipping to change at page 11, line 14
George Swallow George Swallow
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Ave, 1414 Massachusetts Ave,
Boxborough, MA 01719 Boxborough, MA 01719
Phone: +1 978 936 1398 Phone: +1 978 936 1398
Email: swallow@cisco.com Email: swallow@cisco.com
12. Intellectual Property Notice 12. Intellectual Property Notice
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed
pertain to the implementation or use of the technology described in to pertain to the implementation or use of the technology
this document or the extent to which any license under such rights described in this document or the extent to which any license
might or might not be available; neither does it represent that it under such rights might or might not be available; nor does it
has made any effort to identify any such rights. Information on the represent that it has made any independent effort to identify any
IETF's procedures with respect to rights in standards-track and such rights. Information on the procedures with respect to rights
standards-related documentation can be found in BCP-11 [RFC2028]. in RFC documents can be found in BCP 78 and BCP 79.
Copies of claims of rights made available for publication and any
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an 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 attempt made to obtain a general license or permission for the use
such proprietary rights by implementors or users of this of such proprietary rights by implementers or users of this
specification can be obtained from the IETF Secretariat. The IETF specification can be obtained from the IETF on-line IPR repository
invites any interested party to bring to its attention any at http://www.ietf.org/ipr.
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.
13. Full Copyright Statement 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 implement this standard. Please address the information to the
IETF at ietf-ipr@ietf.org.
Copyright (C) The Internet Society (2004). All Rights Reserved. 12.1 IPR Disclosure Acknowledgement
This document and translations of it may be copied and furnished to By submitting this Internet-Draft, I certify that any applicable
others, and derivative works that comment on or otherwise explain it patent or other IPR claims of which I am aware have been disclosed,
or assist in its implementation may be prepared, copied, published and any of which I become aware will be disclosed, in accordance with
and distributed, in whole or in part, without restriction of any RFC 3668.
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 be 13. Full Copyright Statement
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an Copyright (C) The Internet Society (2004). This document is
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING subject to the rights, licenses and restrictions contained in BCP
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 78, and except as set forth therein, the authors retain all their
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION rights.
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. This document and the information contained herein are provided
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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/