RSVP-TE Extensions in Support of Proactive Protection
draft-lin-ccamp-gmpls-proactive-protection-00

Document Type Active Internet-Draft (individual)
Last updated 2019-11-03
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
CCAMP Working Group                                              Yi Lin 
Internet Draft                                      Huawei Technologies 
Intended status: Standards Track                       November 3, 2019 
Expires: May 2020 
                                   
 
 
                                      
           RSVP-TE Extensions in Support of Proactive Protection 
             draft-lin-ccamp-gmpls-proactive-protection-00.txt 

Status of this Memo 

   This Internet-Draft is submitted in full conformance with the 
   provisions of BCP 78 and BCP 79.  

   Internet-Drafts are working documents of the Internet Engineering 
   Task Force (IETF), its areas, and its working groups.  Note that 
   other groups may also distribute working documents as Internet-
   Drafts. 

   Internet-Drafts are draft documents valid for a maximum of six 
   months and may be updated, replaced, or obsoleted by other documents 
   at any time.  It is inappropriate to use Internet-Drafts as 
   reference material or to cite them other than as "work in progress." 

   The list of current Internet-Drafts can be accessed at 
   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 

   This Internet-Draft will expire on May 3, 2020. 

Copyright Notice 

   Copyright (c) 2019 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. Code Components extracted from this 
   document must include Simplified BSD License text as described in 

 
 
 
Yi Lin                  Expires May 3, 2020                   [Page 1] 


Internet-Draft          GMPLS Proactive Protection       November 2019 
    

   Section 4.e of the Trust Legal Provisions and are provided without 
   warranty as described in the Simplified BSD License. 

Abstract 

   This document describes protocol-specific procedures and extensions 
   for Generalized Multi-Protocol Label Switching (GMPLS) Resource 
   ReSerVation Protocol - Traffic Engineering (RSVP-TE) signaling to 
   support Label Switched Path (LSP) Proactive Protection, which create 
   the protection LSP after a failure is predicted and before it 
   becomes a real failure. 

Table of Contents 

   1. Introduction .................................................. 2 
   2. Conventions used in this document ............................. 3 
   3. Overview of Predicted Failure and Related Recovery Methods .... 3 
      3.1. Predicted Failure ........................................ 3 
      3.2. Proactive Protection ..................................... 4 
   4. Modified PROTECTION Object Format ............................. 5 
   5. Extension to ERROR_SPEC Object ................................ 6 
      5.1. New Error Code / Sub-code ................................ 6 
      5.2. New TLV in ERROR_SPEC Object ............................. 6 
   6. End-to-end Proactive Protection ............................... 7 
      6.1. Creation of the Protected LSP ............................ 7 
      6.2. Notification of Predicted Failure Event .................. 7 
      6.3. Tearing Down of the Protection LSP ....................... 8 
   7. Proactive Segment Protection .................................. 8 
      7.1. Creation of the Protected LSP ............................ 8 
      7.2. Notification of Predicted Failure Event .................. 9 
      7.3. Tearing Down of the Segment Recovery LSP ................. 9 
      7.4. Priority and Resource Pre-emption ....................... 10 
   8. Consideration of Backward Compatibility ...................... 11 
   9. Security Considerations ...................................... 11 
   10. IANA Considerations ......................................... 11 
   11. References .................................................. 12 
      11.1. Normative References ................................... 12 
      11.2. Informative References ................................. 12 
   12. Authors' Addresses .......................................... 12 
    
    

1. Introduction 

   [RFC4872] and [RFC4873] describe protocol-specific procedures and 
   extensions for GMPLS RSVP-TE signaling to support end-to-end LSP 

 
 
Yi Lin                  Expires May 3, 2020                   [Page 2] 


Internet-Draft          GMPLS Proactive Protection       November 2019 
    

   recovery (including protection and restoration) and segment LSP 
   recovery, respectively. 

   Traditional protection solution (e.g., 1+1 or 1:1 protection) could 
Show full document text