Internet Engineering Task Force (IETF)                      H. Chen, Ed.
Request for Comments: 8424                           Huawei Technologies
Category: Experimental                                     R. Torvi, Ed.
ISSN: 2070-1721                                         Juniper Networks
                                                             August 2018


          Extensions to RSVP-TE for Label Switched Path (LSP)
                 Ingress Fast Reroute (FRR) Protection

Abstract

   This document describes extensions to Resource Reservation Protocol -
   Traffic Engineering (RSVP-TE) for locally protecting the ingress node
   of a Point-to-Point (P2P) or Point-to-Multipoint (P2MP) Traffic
   Engineered (TE) Label Switched Path (LSP).  It extends the Fast
   Reroute (FRR) protection for transit nodes of an LSP to the ingress
   node of the LSP.  The procedures described in this document are
   experimental.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for examination, experimental implementation, and
   evaluation.

   This document defines an Experimental Protocol for the Internet
   community.  This document is a product of the Internet Engineering
   Task Force (IETF).  It represents the consensus of the IETF
   community.  It has received public review and has been approved for
   publication by the Internet Engineering Steering Group (IESG).  Not
   all documents approved by the IESG are candidates for any level of
   Internet Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8424.














Chen & Torvi                  Experimental                      [Page 1]

RFC 8424                 LSP Ingress Protection              August 2018


Copyright Notice

   Copyright (c) 2018 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
   (https://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.








































Chen & Torvi                  Experimental                      [Page 2]

RFC 8424                 LSP Ingress Protection              August 2018


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.1.  Ingress Local Protection Example  . . . . . . . . . . . .   5
     1.2.  Ingress Local Protection Overview . . . . . . . . . . . .   6
   2.  Conventions Used in This Document . . . . . . . . . . . . . .   7
   3.  Ingress Failure Detection . . . . . . . . . . . . . . . . . .   7
     3.1.  Source Detects Failure  . . . . . . . . . . . . . . . . .   7
     3.2.  Backup and Source Detect Failure  . . . . . . . . . . . .   8
   4.  Backup Forwarding State . . . . . . . . . . . . . . . . . . .   9
     4.1.  Forwarding State for Backup LSP . . . . . . . . . . . . .   9
   5.  Protocol Extensions . . . . . . . . . . . . . . . . . . . . .   9
     5.1.  INGRESS_PROTECTION Object . . . . . . . . . . . . . . . .  10
       5.1.1.  Class Number and Class Type . . . . . . . . . . . . .  10
       5.1.2.  Object Format . . . . . . . . . . . . . . . . . . . .  11
       5.1.3.  Subobject: Backup Ingress IPv4 Address  . . . . . . .  12
       5.1.4.  Subobject: Backup Ingress IPv6 Address  . . . . . . .  13
       5.1.5.  Subobject: Ingress IPv4 Address . . . . . . . . . . .  13
       5.1.6.  Subobject: Ingress IPv6 Address . . . . . . . . . . .  13
       5.1.7.  Subobject: TRAFFIC_DESCRIPTOR . . . . . . . . . . . .  14
       5.1.8.  Subobject: Label-Routes . . . . . . . . . . . . . . .  15
   6.  Behavior of Ingress Protection  . . . . . . . . . . . . . . .  15
     6.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .  15
       6.1.1.  Relay-Message Method  . . . . . . . . . . . . . . . .  15
       6.1.2.  Proxy-Ingress Method  . . . . . . . . . . . . . . . .  16
     6.2.  Ingress Behavior  . . . . . . . . . . . . . . . . . . . .  17
       6.2.1.  Relay-Message Method  . . . . . . . . . . . . . . . .  17
       6.2.2.  Proxy-Ingress Method  . . . . . . . . . . . . . . . .  18
     6.3.  Backup Ingress Behavior . . . . . . . . . . . . . . . . .  19
       6.3.1.  Backup Ingress Behavior in the Off-Path Case  . . . .  20
       6.3.2.  Backup Ingress Behavior in the On-Path Case . . . . .  22
       6.3.3.  Failure Detection and Refresh PATH Messages . . . . .  23
     6.4.  Revertive Behavior  . . . . . . . . . . . . . . . . . . .  23
       6.4.1.  Revert to Primary Ingress . . . . . . . . . . . . . .  24
       6.4.2.  Global Repair by Backup Ingress . . . . . . . . . . .  24
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .