draft-ietf-ccamp-mpls-graceful-shutdown-04.txt   draft-ietf-ccamp-mpls-graceful-shutdown-05.txt 
skipping to change at page 1, line 13 skipping to change at page 1, line 13
Networking Working Group Networking Working Group
Internet Draft Internet Draft
Zafar Ali Zafar Ali
Jean-Philippe Vasseur Jean-Philippe Vasseur
Anca Zamfir Anca Zamfir
Cisco Systems, Inc. Cisco Systems, Inc.
Jonathan Newton Jonathan Newton
Cable and Wireless Cable and Wireless
Category: Informational Category: Informational
Expires: July 2008 January 2008
draft-ietf-ccamp-mpls-graceful-shutdown-05.txt
Graceful Shutdown in MPLS and Generalized MPLS Graceful Shutdown in MPLS and Generalized MPLS
Traffic Engineering Networks Traffic Engineering Networks
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that By submitting this Internet-Draft, each author represents that
any applicable patent or other IPR claims of which he or she is any applicable patent or other IPR claims of which he or she is
aware have been or will be disclosed, and any of which he or she aware have been or will be disclosed, and any of which he or she
becomes aware will be disclosed, in accordance with Section 6 of becomes aware will be disclosed, in accordance with Section 6 of
BCP 79. BCP 79.
skipping to change at page 1, line 41 skipping to change at page 1, line 45
documents at any time. It is inappropriate to use Internet- documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as "work Drafts as reference material or to cite them other than as "work
in progress." 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 accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on December 07, 2007. This Internet-Draft will expire on July 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
draft-ietf-ccamp-mpls-graceful-shutdown-04.txt July 07 draft-ietf-ccamp-mpls-graceful-shutdown-05.txt July 07
Abstract Abstract
MPLS-TE Graceful Shutdown is a method for explicitly notifying MPLS-TE Graceful Shutdown is a method for explicitly notifying
the nodes in a Traffic Engineering (TE) enabled network that the the nodes in a Traffic Engineering (TE) enabled network that the
TE capability on a link or on an entire Label Switching Router TE capability on a link or on an entire Label Switching Router
(LSR) is going to be disabled. MPLS-TE graceful shutdown (LSR) is going to be disabled. MPLS-TE graceful shutdown
mechanisms are tailored toward addressing planned outage in the mechanisms are tailored toward addressing planned outage in the
network. network.
skipping to change at page 3, line 4 skipping to change at page 3, line 4
5. Security Considerations.........................................8 5. Security Considerations.........................................8
6. IANA Considerations.............................................9 6. IANA Considerations.............................................9
7. Acknowledgments.................................................9 7. Acknowledgments.................................................9
8. Reference.......................................................9 8. Reference.......................................................9
8.1 Normative Reference............................................9 8.1 Normative Reference............................................9
8.2 Informative Reference..........................................9 8.2 Informative Reference..........................................9
9. Authors' Address:..............................................10 9. Authors' Address:..............................................10
10. Intellectual Property Considerations..........................10 10. Intellectual Property Considerations..........................10
11. Disclaimer of Validity........................................11 11. Disclaimer of Validity........................................11
12. Copyright Statement...........................................11 12. Copyright Statement...........................................11
draft-ietf-ccamp-mpls-graceful-shutdown-04.txt July 07 draft-ietf-ccamp-mpls-graceful-shutdown-05.txt July 07
1. Terminology 1. Terminology
LSR (Label Switching Router): The terms node and LSR are used LSR (Label Switching Router): The terms node and LSR are used
interchangeably in this document. interchangeably in this document.
GMPLS: The term GMPLS is used in this document to refer to GMPLS: The term GMPLS is used in this document to refer to
packet MPLS-TE, as well as GMPLS extensions to MPLS-TE. packet MPLS-TE, as well as GMPLS extensions to MPLS-TE.
LSP: An MPLS-TE/ GMPLS-TE Label Switched Path. LSP: An MPLS-TE/ GMPLS-TE Label Switched Path.
skipping to change at page 4, line 5 skipping to change at page 4, line 5
forwarding. The node initiating the graceful shutdown condition forwarding. The node initiating the graceful shutdown condition
SHOULD introduce a delay between disabling the resource in the SHOULD introduce a delay between disabling the resource in the
control plane and removing the resource for forwarding. This is control plane and removing the resource for forwarding. This is
to allow the control plane to gracefully divert the traffic away to allow the control plane to gracefully divert the traffic away
from the resource being gracefully shutdown. The trigger for the from the resource being gracefully shutdown. The trigger for the
graceful shutdown event is a local matter at the node initiating graceful shutdown event is a local matter at the node initiating
the graceful shutdown. Typically, graceful shutdown is triggered the graceful shutdown. Typically, graceful shutdown is triggered
for administrative reasons, such as link maintenance or for administrative reasons, such as link maintenance or
software/hardware upgrade. software/hardware upgrade.
draft-ietf-ccamp-mpls-graceful-shutdown-04.txt July 07 draft-ietf-ccamp-mpls-graceful-shutdown-05.txt July 07
This document describes the mechanisms that can be used to This document describes the mechanisms that can be used to
gracefully shutdown GMPLS Traffic Engineering on a resource. As gracefully shutdown GMPLS Traffic Engineering on a resource. As
mentioned earlier, the graceful shutdown of the Traffic mentioned earlier, the graceful shutdown of the Traffic
Engineering capability on a resource could be incorporated in the Engineering capability on a resource could be incorporated in the
shutdown operation of an interface, but it is a separate step shutdown operation of an interface, but it is a separate step
that is taken before the IGP on the link is brought down and that is taken before the IGP on the link is brought down and
before the interface is brought down at different layers. This before the interface is brought down at different layers. This
document only addresses TE nodes and TE resources. document only addresses TE nodes and TE resources.
skipping to change at page 5, line 4 skipping to change at page 5, line 4
- Graceful shutdown mechanisms are equally applicable to intra- - Graceful shutdown mechanisms are equally applicable to intra-
domain and TE LSPs spanning multiple domains. Here, a domain is domain and TE LSPs spanning multiple domains. Here, a domain is
defined as either an IGP area or an Autonomous System [RFC4726]. defined as either an IGP area or an Autonomous System [RFC4726].
- Graceful shutdown is equally applicable to GMPLS-TE, as well as - Graceful shutdown is equally applicable to GMPLS-TE, as well as
packet-based (MPLS) TE LSPs. packet-based (MPLS) TE LSPs.
- In order to make rerouting effective, it is required that when - In order to make rerouting effective, it is required that when
a node initiates the graceful shutdown of a resource, it a node initiates the graceful shutdown of a resource, it
draft-ietf-ccamp-mpls-graceful-shutdown-04.txt July 07 draft-ietf-ccamp-mpls-graceful-shutdown-05.txt July 07
identifies to all other network nodes the TE resource under identifies to all other network nodes the TE resource under
graceful shutdown. graceful shutdown.
- Depending on switching technology, it may be possible to - Depending on switching technology, it may be possible to
shutdown a label resource, e.g., shutting down a lambda in a shutdown a label resource, e.g., shutting down a lambda in a
Lambda Switch Capable (LSC) node. Lambda Switch Capable (LSC) node.
4. Mechanisms for Graceful Shutdown 4. Mechanisms for Graceful Shutdown
An IGP only based solution is not applicable when dealing with An IGP only based solution is not applicable when dealing with
skipping to change at page 6, line 4 skipping to change at page 6, line 4
bandwidth which is greater than the available bandwidth. This bandwidth which is greater than the available bandwidth. This
would discourage new LSP establishment through the link under would discourage new LSP establishment through the link under
graceful shutdown. graceful shutdown.
Neighbors of the node where graceful shutdown procedure is in Neighbors of the node where graceful shutdown procedure is in
progress SHOULD continue to advertise the actual unreserved progress SHOULD continue to advertise the actual unreserved
bandwidth of the TE links from the neighbors to that node, bandwidth of the TE links from the neighbors to that node,
without any routing adjacency change. without any routing adjacency change.
4.1.2 Graceful Shutdown of Component Link(s) in a Bundled TE Link 4.1.2 Graceful Shutdown of Component Link(s) in a Bundled TE Link
draft-ietf-ccamp-mpls-graceful-shutdown-04.txt July 07 draft-ietf-ccamp-mpls-graceful-shutdown-05.txt July 07
If graceful shutdown procedure is performed for a component link If graceful shutdown procedure is performed for a component link
within a TE Link bundle and it is not the last component link within a TE Link bundle and it is not the last component link
available within the TE link, the link attributes associated with available within the TE link, the link attributes associated with
the TE link are recomputed. If the removal of the component link the TE link are recomputed. If the removal of the component link
results in a significant bandwidth change event, a new LSA is results in a significant bandwidth change event, a new LSA is
originated with the new traffic parameters. If the last component originated with the new traffic parameters. If the last component
link is being shutdown, the routing procedure outlined in Section link is being shutdown, the routing procedure outlined in Section
4.2.1 is used. 4.2.1 is used.
skipping to change at page 7, line 5 skipping to change at page 7, line 5
is defined in [RFC4736]. The PathErr message SHOULD include the is defined in [RFC4736]. The PathErr message SHOULD include the
ERROR_SPEC object containing IP address of the TE Link being ERROR_SPEC object containing IP address of the TE Link being
gracefully shutdown. If TE link is unnumbered, the PathErr gracefully shutdown. If TE link is unnumbered, the PathErr
message SHOULD include the ERROR_SPEC object containing message SHOULD include the ERROR_SPEC object containing
unnumbered ID and TE router ID for the TE Link being gracefully unnumbered ID and TE router ID for the TE Link being gracefully
shutdown. If available, and where notify requests were included shutdown. If available, and where notify requests were included
when the LSPs were initially setup, Notify message (as defined in when the LSPs were initially setup, Notify message (as defined in
RFC 3471, RFC 3473) MAY also be used for delivery of this RFC 3471, RFC 3473) MAY also be used for delivery of this
information to the head-end node, border node or PCE. information to the head-end node, border node or PCE.
draft-ietf-ccamp-mpls-graceful-shutdown-04.txt July 07 draft-ietf-ccamp-mpls-graceful-shutdown-05.txt July 07
When a graceful shutdown operation is performed along the path of When a graceful shutdown operation is performed along the path of
a protected LSP, based on a local decision, the PLR or branch a protected LSP, based on a local decision, the PLR or branch
node MAY redirect the traffic onto the local detour or protecting node MAY redirect the traffic onto the local detour or protecting
segment. In all cases, the PLR or branch node MUST forward the segment. In all cases, the PLR or branch node MUST forward the
PathErr to the head-end node, border node, or PCE. PathErr to the head-end node, border node, or PCE.
When a head-end node, border node, or PCE receives a PathErr (or When a head-end node, border node, or PCE receives a PathErr (or
Notify) message with error value of " Local link maintenance Notify) message with error value of " Local link maintenance
required", it MAY trigger a make-before-break procedure. When required", it MAY trigger a make-before-break procedure. When
skipping to change at page 8, line 4 skipping to change at page 8, line 4
outlined in Section 4.2.1 is used. outlined in Section 4.2.1 is used.
When a head-end node, border node, or PCE receives an RSVP When a head-end node, border node, or PCE receives an RSVP
PathErr or Notify message with error value "local component link PathErr or Notify message with error value "local component link
maintenance required" Flag set, it MAY immediately perform a maintenance required" Flag set, it MAY immediately perform a
make-before-break to avoid traffic loss. The head-end node, make-before-break to avoid traffic loss. The head-end node,
border node, or PCE MAY still use the IP address contained in the border node, or PCE MAY still use the IP address contained in the
PathErr or Notify message in performing path computation for PathErr or Notify message in performing path computation for
rerouting the LSP. This is because, this address is an IP address rerouting the LSP. This is because, this address is an IP address
of the TE link and the flag is an implicit indication that the TE of the TE link and the flag is an implicit indication that the TE
draft-ietf-ccamp-mpls-graceful-shutdown-04.txt July 07 draft-ietf-ccamp-mpls-graceful-shutdown-05.txt July 07
link may still have capacity to admit new LSPs. However, if the link may still have capacity to admit new LSPs. However, if the
ERO is computed such that it also provides details of the ERO is computed such that it also provides details of the
component link selection(s) along the Path, the component link component link selection(s) along the Path, the component link
previously selected MAY be avoided. previously selected MAY be avoided.
4.2.3 Graceful Shutdown of TE Node 4.2.3 Graceful Shutdown of TE Node
The node that is being gracefully shutdown MUST trigger a PathErr The node that is being gracefully shutdown MUST trigger a PathErr
message with the error code "Notify" and an error value of "Local message with the error code "Notify" and an error value of "Local
skipping to change at page 9, line 5 skipping to change at page 9, line 5
link may still have capacity to admit new LSPs. link may still have capacity to admit new LSPs.
5. Security Considerations 5. Security Considerations
This document introduces no new security considerations beyond This document introduces no new security considerations beyond
those already addressed for existing RSVP PathErr or Notify those already addressed for existing RSVP PathErr or Notify
messages, or advertisement of TE LSA/LSP containing Link TLV. In messages, or advertisement of TE LSA/LSP containing Link TLV. In
this regard, the security considerations specified in [RFC2205], this regard, the security considerations specified in [RFC2205],
[RFC3209] and [MPLS-GMPLS-SECURITY] remain relevant. [RFC3209] and [MPLS-GMPLS-SECURITY] remain relevant.
draft-ietf-ccamp-mpls-graceful-shutdown-04.txt July 07 draft-ietf-ccamp-mpls-graceful-shutdown-05.txt July 07
6. IANA Considerations 6. IANA Considerations
The following assignment is required in the "Notify" subsection The following assignment is required in the "Notify" subsection
of "Error Codes and Values" section of the "RSVP PARAMETERS" of "Error Codes and Values" section of the "RSVP PARAMETERS"
registry (located at http://www.iana.org/assignments/rsvp- registry (located at http://www.iana.org/assignments/rsvp-
parameters): parameters):
12 (TBA) - "Local component link maintenance required" flag. 12 (TBA) - "Local component link maintenance required" flag.
13 (TBA) Local label resource maintenance required. 13 (TBA) Local label resource maintenance required.
7. Acknowledgments 7. Acknowledgments
skipping to change at page 10, line 5 skipping to change at page 10, line 5
in MPLS Traffic Engineering", RFC 4201. in MPLS Traffic Engineering", RFC 4201.
[RFC4206] Label Switched Paths (LSP) Hierarchy with Generalized [RFC4206] Label Switched Paths (LSP) Hierarchy with Generalized
Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE), Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE),
RFC 4206. RFC 4206.
[MPLS-GMPLS-SECURITY] Fang, et al, "Security Framework for MPLS [MPLS-GMPLS-SECURITY] Fang, et al, "Security Framework for MPLS
and GMPLS Networks", draft-fang-mpls-gmpls-security-framework- and GMPLS Networks", draft-fang-mpls-gmpls-security-framework-
00.txt, work in progress. 00.txt, work in progress.
draft-ietf-ccamp-mpls-graceful-shutdown-04.txt July 07 draft-ietf-ccamp-mpls-graceful-shutdown-05.txt July 07
9. Authors' Address: 9. Authors' Address:
Zafar Ali Zafar Ali
Cisco systems, Inc., Cisco systems, Inc.,
2000 Innovation Drive 2000 Innovation Drive
Kanata, Ontario, K2K 3E8 Kanata, Ontario, K2K 3E8
Canada. Canada.
Email: zali@cisco.com Email: zali@cisco.com
skipping to change at page 11, line 5 skipping to change at page 11, line 5
use of such proprietary rights by implementers or users of this use of such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR specification can be obtained from the IETF on-line IPR
repository at http://www.ietf.org/ipr. repository at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention The IETF invites any interested party to bring to its attention
any copyrights, patents or patent applications, or other any copyrights, patents or patent applications, or other
proprietary rights that may cover technology that may be required proprietary rights that may cover technology that may be required
to implement this standard. Please address the information to to implement this standard. Please address the information to
the IETF at ietf-ipr@ietf.org. the IETF at ietf-ipr@ietf.org.
draft-ietf-ccamp-mpls-graceful-shutdown-04.txt July 07 draft-ietf-ccamp-mpls-graceful-shutdown-05.txt July 07
11. Disclaimer of Validity 11. Disclaimer of Validity
This document and the information contained herein are provided This document and the information contained herein are provided
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE
ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
 End of changes. 13 change blocks. 
12 lines changed or deleted 16 lines changed or added

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