Segment Routing Proxy Forwarding
draft-hu-spring-segment-routing-proxy-forwarding-00

Document Type Active Internet-Draft (individual)
Last updated 2018-10-22
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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                                              Z. Hu
Internet-Draft                                                   H. Chen
Intended status: Standards Track                                  J. Yao
Expires: April 25, 2019                              Huawei Technologies
                                                        October 22, 2018

                    Segment Routing Proxy Forwarding
          draft-hu-spring-segment-routing-proxy-forwarding-00

Abstract

   Segment Routing Traffic Engineering (SR-TE) supports the creation of
   explicit paths using adjacency-sids, node-sids, and binding-sids.  In
   the SR-TE path, by providing proxy forwarding to the neighbor nodes
   of the faulty node, it is ensured that the traffic can reach the
   neighbor node of the faulty node normally in the case of the SR-TE of
   the loose path or strict path.  If the failed node is a node that
   provides the Binding-sids service, the neighbor node can perform the
   binding-sids forwarding behavior to swap the corresponding label
   stack through the proxy forwarding of the neighbor node.
   [I-D.bashandy-rtgwg-segment-routing-ti-lfa] defines the usecase of
   protecting the node failure of segment list.  This document describes
   how to implement the proxy forwarding mechanism of a faulty node at
   the neighbor node of the faulty node on the SR-TE path .

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
   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 25, 2019.

Hu, et al.               Expires April 25, 2019                 [Page 1]
Internet-Draft      Segment Routing Proxy Forwarding        October 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.  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.  IGP extended for proxy forwarding . . . . . . . . . . . . . .   3
     2.1.  ISIS proxy forwarding Prefix-SID  . . . . . . . . . . . .   3
     2.2.  ISIS Path Binding TLV . . . . . . . . . . . . . . . . . .   4
   3.  Building proxy forwarding table . . . . . . . . . . . . . . .   5
     3.1.  Advertise proxy forwarding TLV  . . . . . . . . . . . . .   7
     3.2.  Calculate the proxy forwarding table  . . . . . . . . . .   7
   4.  Node Protection for Segment List  . . . . . . . . . . . . . .   8
     4.1.  Next segment is an adjacency segment  . . . . . . . . . .   9
     4.2.  Next segment is a node segment  . . . . . . . . . . . . .  11
     4.3.  Next segment is a binding segment . . . . . . . . . . . .  13
   5.  Other scenario considerations . . . . . . . . . . . . . . . .  15
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  16
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  16
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   Segment Routing Traffic Engineering (SR-TE) is a technology that
   implements traffic engineering using Segment Routing.  Segment
   Routing-Traffic Engineering supports the creation of explicit paths
   using adjacency-sids, node-sids, and binding-sids.  After a node
Show full document text