SRv6 Compatibility with Legacy Devices
draft-peng-spring-srv6-compatibility-01

Document Type Active Internet-Draft (individual)
Last updated 2019-07-08
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)
SPRING Working Group                                             S. Peng
Internet-Draft                                                     Z. Li
Intended status: Informational                       Huawei Technologies
Expires: January 9, 2020                                          C. Xie
                                                                   C. Li
                                                           China Telecom
                                                            July 8, 2019

                 SRv6 Compatibility with Legacy Devices
                draft-peng-spring-srv6-compatibility-01

Abstract

   When deploying SRv6 on legacy devices, there are some compatibility
   challenges such as the support of SRH processing.

   This document identifies some of the major challenges, and provides
   solutions that are able to mitigate those challenges and smooth the
   migration towards SRv6 deployment.

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 January 9, 2020.

Peng, et al.             Expires January 9, 2020                [Page 1]
Internet-Draft             SRv6 Compatibility                  July 2019

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
   (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.  Compatibility challenges  . . . . . . . . . . . . . . . . . .   3
     2.1.  Fast Reroute (FRR)  . . . . . . . . . . . . . . . . . . .   3
     2.2.  Traffic Engineering (TE)  . . . . . . . . . . . . . . . .   4
     2.3.  Service Function Chaining (SFC) . . . . . . . . . . . . .   4
     2.4.  IOAM  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Solutions . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  TE  . . . . . . . . . . . . . . . . . . . . . . . . . . .   5
       3.1.1.  Binding SID (BSID)  . . . . . . . . . . . . . . . . .   6
       3.1.2.  PCEP FlowSpec . . . . . . . . . . . . . . . . . . . .   6
     3.2.  SFC . . . . . . . . . . . . . . . . . . . . . . . . . . .   6
       3.2.1.  Stateless SFC . . . . . . . . . . . . . . . . . . . .   6
       3.2.2.  Stateful SFC  . . . . . . . . . . . . . . . . . . . .   7
     3.3.  Light Weight IOAM . . . . . . . . . . . . . . . . . . . .   7
   4.  Summary . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   Segment Routing (SR) is a source routing paradigm, which allows a
   headend node to steer the packets through an ordered list of
   instructions, i.e. segments [RFC8402].  A segment can either be
   topological or service based.  SR over IPv6 (SRv6)
   [I-D.filsfils-spring-srv6-network-programming] is the SR instantiated
   on the IPv6 data plane with a new type of routing extension header,
   i.e. SR Header (SRH) [I-D.ietf-6man-segment-routing-header].  An SRv6
   segment, also called SRv6 SID, is a 128-bit value, represented as

Peng, et al.             Expires January 9, 2020                [Page 2]
Internet-Draft             SRv6 Compatibility                  July 2019

   LOC:FUNCT:ARGS (ARGS is optional), and encoded as an IPv6 address.
Show full document text