Anycast SID for Flexible and Robust Service in SRv6
draft-li-spring-anycast-sid-service-01

Document Type Active Internet-Draft (individual)
Last updated 2020-05-15
Stream (None)
Intended RFC status (None)
Formats plain text 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                                              T. Li
Internet-Draft                                                   Z. Chen
Intended status: Standards Track                     Huawei Technologies
Expires: November 16, 2020                                  May 15, 2020
 

          Anycast SID for Flexible and Robust Service in SRv6
                 draft-li-spring-anycast-sid-service-01

Abstract

   Segment Routing enables an operator or an application to specify a
   packet processing program. When Segment Routing is applied to IPv6
   data plane, the list of IPv6 SIDs in SRH can specify a series of
   execution endpoints that hold service functions that process the
   packet. However, steering traffic dynamically to the different
   execution endpoints requires a specific "re-encapsulating". This
   procedure may be complex and take time.

   This document proposes A-SID (Anycast-SID) based on SRv6 to achieve
   flexible and robust service provision. It uses anycast SID to
   identify service functions and locates the service functions based on
   anycast routing. The proposed solution can stay compatibility with
   the existing SRv6.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED","MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

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."

Li & Chen              Expires November 16, 2020                [Page 1]
Internet-Draft         Anycast SID Service in SRv6              May 2020

   This Internet-Draft will expire on November 16, 2020.

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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Anycast SID (A-SID) . . . . . . . . . . . . . . . . . . . . .   3
   4.  Control Plane . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Data Plane  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Illustration  . . . . . . . . . . . . . . . . . . . . . . . .   6
     6.1.  Usecase1 migration of service function  . . . . . . . . .   6
     6.2.  Usecase2 failover of service function . . . . . . . . . .   7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     10.2.  Informative References . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   Segment Routing [RFC8402] enables an operator or an application to
   specify a packet processing program. SRv6 applies Segment Routing to
   IPv6 data plane. A new routing header for IPv6, which is called
   Segment Routing Header (SRH) [RFC8754] is defined to carry 128-bit
   SIDs. The list of IPv6 SIDs in SRH can specify not only a TE path,
   but also a series of execution endpoints that hold service functions
   that process the packet. In this way, a service function chain
   [RFC7665] is formed based on SRv6.

   However, more and more functions, such as firewall and DPI, are
   deployed in cloud technology and Network Function Virtualization,

Li & Chen              Expires November 16, 2020                [Page 2]
Show full document text