SRv6 Midpoint Protection
draft-chen-rtgwg-srv6-midpoint-protection-03

Document Type Active Internet-Draft (individual)
Authors Huanan Chen  , Zhibo Hu , Huaimo Chen  , Xuesong Geng 
Last updated 2020-10-15
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) 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)
Network Working Group                                            H. Chen
Internet-Draft                                             China Telecom
Intended status: Experimental                                      Z. Hu
Expires: April 18, 2021                              Huawei Technologies
                                                                 H. Chen
                                                               Futurewei
                                                                 X. Geng
                                                     Huawei Technologies
                                                        October 15, 2020

                        SRv6 Midpoint Protection
              draft-chen-rtgwg-srv6-midpoint-protection-03

Abstract

   The current local repair mechanism, e.g., TI-LFA, allows local repair
   actions on the direct neighbors of the failed node to temporarily
   route traffic to the destination.  This mechanism could not work
   properly when the failure happens in the destination point or the
   link connected to the destination.  In SRv6 TE, the IPv6 destination
   address in the outer IPv6 header could be the dedicated endpoint of
   the TE path rather than the destination of the TE path.  When the
   endpoint fails, local repair couldn't work on the direct neighbor of
   the failed endpoint either.  This document defines midpoint
   protection, which enables the direct neighbor of the failed endpoint
   to do the function of the endpoint, replace the IPv6 destination
   address to the other endpoint, and choose the next hop based on the
   new destination address.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any

Chen, et al.             Expires April 18, 2021                 [Page 1]
Internet-Draft          SRv6 Midpoint Protection            October 2020

   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 18, 2021.

Copyright Notice

   Copyright (c) 2020 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.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  SRv6 Midpoint Protection Mechanism  . . . . . . . . . . . . .   3
   3.  SRv6 Midpoint Protection Example  . . . . . . . . . . . . . .   3
   4.  SRv6 Midpoint Protection Behavior . . . . . . . . . . . . . .   5
     4.1.  Transit Node as Repair Node . . . . . . . . . . . . . . .   5
     4.2.  Endpoint Node as Repair Node  . . . . . . . . . . . . . .   5
     4.3.  Endpoint x Node as Repair Node  . . . . . . . . . . . . .   6
   5.  Determining whether the Endpoint could Be Bypassed  . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   The current mechanism, e.g., TI-LFA
   ([I-D.ietf-rtgwg-segment-routing-ti-lfa]), allows local repair
   actions on the direct neighbors of the failed node to temporarily
   route traffic to the destination.  This mechanism could not work
   properly when the failure happens in the destination point or the
   link connected to the destination.  In SRv6 TE, the IPv6 destination
   address in the outer IPv6 header could be the dedicated endpoint of
Show full document text