draft-ietf-mpls-gmpls-lsp-reroute-03.txt   draft-ietf-mpls-gmpls-lsp-reroute-04.txt 
Internet Draft Lou Berger (LabN) Internet Draft Lou Berger (LabN)
Updates: 3209 Dimitri Papadimitriou (Alcatel Lucent) Updates: 3209 Dimitri Papadimitriou (Alcatel Lucent)
Category: Standards Track JP. Vasseur (Cisco) Category: Standards Track JP. Vasseur (Cisco)
Expiration Date: May 25, 2009 Expiration Date: July 30, 2009
November 25, 2008 January 30, 2009
PathErr Message Triggered MPLS and GMPLS LSP Reroute PathErr Message Triggered MPLS and GMPLS LSP Reroute
draft-ietf-mpls-gmpls-lsp-reroute-03.txt draft-ietf-mpls-gmpls-lsp-reroute-04.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. 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
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite 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/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on May 25, 2009. This Internet-Draft will expire on July 30, 2009.
Copyright Notice Copyright and License Notice
Copyright (C) The IETF Trust (2008). Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
Abstract Abstract
This document describes how Resource ReserVation Protocol (RSVP) This document describes how Resource ReserVation Protocol (RSVP)
PathErr Messages may be used to trigger rerouting of Multi-Protocol PathErr Messages may be used to trigger rerouting of Multi-Protocol
Label Switching (MPLS) and Generalized MPLS (GMPLS) point-to-point Label Switching (MPLS) and Generalized MPLS (GMPLS) point-to-point
Traffic Engineering (TE) Label Switched Paths (LSPs) without first Traffic Engineering (TE) Label Switched Paths (LSPs) without first
removing LSP state or resources. Such LSP rerouting may be desirable removing LSP state or resources. Such LSP rerouting may be desirable
in a number of cases including, for example, soft-preemption and in a number of cases including, for example, soft-preemption and
graceful shutdown. This document describes the usage of existing graceful shutdown. This document describes the usage of existing
skipping to change at page 2, line 27 skipping to change at page 3, line 4
3.2 Interface Reroute Request ................................. 7 3.2 Interface Reroute Request ................................. 7
3.3 Component Reroute Request ................................. 8 3.3 Component Reroute Request ................................. 8
3.4 Label Reroute Request ..................................... 9 3.4 Label Reroute Request ..................................... 9
4 IANA Considerations ....................................... 9 4 IANA Considerations ....................................... 9
5 Security Considerations ................................... 10 5 Security Considerations ................................... 10
6 References ................................................ 10 6 References ................................................ 10
6.1 Normative References ...................................... 10 6.1 Normative References ...................................... 10
6.2 Informative References .................................... 11 6.2 Informative References .................................... 11
7 Acknowledgments ........................................... 12 7 Acknowledgments ........................................... 12
8 Author's Addresses ........................................ 12 8 Author's Addresses ........................................ 12
9 Full Copyright Statement .................................. 12
10 Intellectual Property ..................................... 13
1. Introduction 1. Introduction
Resource ReserVation Protocol (RSVP), see [RFC2205], has been Resource ReserVation Protocol (RSVP), see [RFC2205], has been
extended to support the control of Traffic Engineering (TE) Label extended to support the control of Traffic Engineering (TE) Label
Switched Paths (LSPs) for both Multi-Protocol Label Switching (MPLS) Switched Paths (LSPs) for both Multi-Protocol Label Switching (MPLS)
and Generalized MPLS (GMPLS) in, respectively, [RFC3209] and and Generalized MPLS (GMPLS) in, respectively, [RFC3209] and
[RFC3473]. In all cases, a PathErr message is used to report errors [RFC3473]. In all cases, a PathErr message is used to report errors
to nodes upstream of the error detecting node. As defined in to nodes upstream of the error detecting node. As defined in
[RFC2205], and left unmodified by [RFC3209], PathErr messages "do not [RFC2205], and left unmodified by [RFC3209], PathErr messages "do not
skipping to change at page 12, line 32 skipping to change at line 507
Email: Dimitri.Papadimitriou@alcatel-lucent.be Email: Dimitri.Papadimitriou@alcatel-lucent.be
JP Vasseur JP Vasseur
Cisco Systems, Inc Cisco Systems, Inc
11, Rue Camille Desmoulins 11, Rue Camille Desmoulins
L'Atlantis L'Atlantis
92782 Issy Les Moulineaux 92782 Issy Les Moulineaux
France France
Email: jpv@cisco.com Email: jpv@cisco.com
9. Full Copyright Statement Generated on: Fri Jan 30 15:42:58 EST 2009
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
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, THE IETF TRUST 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.
10. Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights 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; nor does it
represent that it has made any independent effort to identify any
such rights. Information on the procedures with respect to rights
in RFC documents can be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat 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 on-line IPR repository
at http://www.ietf.org/ipr.
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.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Generated on: Tue Nov 25 09:47:22 EST 2008
 End of changes. 9 change blocks. 
12 lines changed or deleted 16 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/