SRv6 Network Migration
draft-xie-spring-srv6-network-migration-00

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)
Network Working Group                                             C. Xie
Internet-Draft                                                     C. Li
Intended status: Informational                             China Telecom
Expires: January 9, 2020                                         S. Peng
                                                                   Z. Li
                                                                 Y. Xiao
                                                     Huawei Technologies
                                                            July 8, 2019

                         SRv6 Network Migration
               draft-xie-spring-srv6-network-migration-00

Abstract

   SRv6 has significant advantages over SR-MPLS which has attracted more
   and more attentions and interests from operators and verticals.  The
   smooth network migration towards SRv6 is a key focal point for the
   SRv6 deployers.  This document provides network migration guidance
   and recommendations on solutions in various scenarios.

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.

Xie, et al.              Expires January 9, 2020                [Page 1]
Internet-Draft           SRv6 Network Migration                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.  Advantages of SRv6  . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  IP Route Aggregation  . . . . . . . . . . . . . . . . . .   3
     2.2.  End-to-end Service Auto-start . . . . . . . . . . . . . .   4
     2.3.  On-Demand Upgrade . . . . . . . . . . . . . . . . . . . .   5
   3.  Incremental Deployment Guidance for SRv6 Migration  . . . . .   6
   4.  Migration Guidance for SRv6/SR-MPLS Co-existence Scenario . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   SRv6 [I-D.ietf-spring-srv6-network-programming] has significant
   advantages over SR-MPLS and has attracted more and more attentions
   and interests from operators and verticals.  The smooth network
   migration towards SRv6 is a key focal point for the SRv6 deployers.

   SRv6 is the Segment Routing deployed on the IPv6 data plane[RFC8200].
   Therefore, in order to support SRv6, the network needs to support
   IPv6 first.  As being actively promoted all over the world, the
   deployments of IPv6 have been ever-increasing which provides the
   strong base for the deployments of SRv6.

   With the IPv6 as its data plane, for network migration towards SRv6,
   both software and hardware need to be upgraded.  Compared with other
   new protocols, only IGP and BGP need to be extended to support SRv6,
   which significantly simplifies the software upgrade required.  While

Xie, et al.              Expires January 9, 2020                [Page 2]
Internet-Draft           SRv6 Network Migration                July 2019

   in the hardware it needs to support the new SRv6 header
   SRH[I-D.ietf-6man-segment-routing-header], the design of SRv6 assures
Show full document text