Shorter SRv6 SID Requirements
draft-cheng-shorter-srv6-sid-requirement-00

Document Type Active Internet-Draft (individual)
Last updated 2020-02-19
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 WG                                                       W. Cheng
Internet-Draft                                              China Mobile
Intended status: Standards Track                                 R. Chen
Expires: August 19, 2020                                          A. Liu
                                                                G. Mirsk
                                                         ZTE Corporation
                                                       February 16, 2020

                     Shorter SRv6 SID Requirements
              draft-cheng-shorter-srv6-sid-requirement-00

Abstract

   This document describes a list of requirement for Shorter SRv6 SID.

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 August 19, 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.

Cheng, et al.            Expires August 19, 2020                [Page 1]
Internet-Draft        Shorter SRv6 SID Requirements        February 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements: . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  The proposal solutions of shorter SRv6 SID  . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Segment Routing [RFC8402]leverages the source routing paradigm.  An
   ingress node steers a packet through an ordered list of instructions,
   called segments.

   A segment can be encoded as a Multi-Protocol Label Switching (MPLS)
   label, IPv4 address, or IPv6 address.  Segment Routing can be
   deployed on MPLS data plane by encoding 20-bits SIDs in MPLS label
   stack [I-D.ietf-spring-segment-routing-mpls].  It also can be
   deployed on the IPv6 data plane by encoding a list of 128-bits SIDs
   in IPv6 Segment Routing Extension Header
   (SRH)[I-D.ietf-6man-segment-routing-header].

   The SRv6 Network Programming
   [I-D.ietf-spring-srv6-network-programming]specifies the base set of
   SRv6 behaviors that enables the creation of interoperable overlays
   with underlay optimization.

   However, the size of the IPv6 segment identifier (SID) presents a
   scaling challenge to use topological instructions that define a
   strict explicitly routed path in combination with service-based
   instructions.  At the same time, the size of the SRH/SID may be a
   challenge for some data plane processors and traffic overhead.
   Meanwhile, SR-MPLS currently, more often than SRv6, is used in metro
   networks.  With the gradual deployment of SRv6 in the core networks,
   it becomes necessary to support interworking between SR-MPLS and SRv6
   and upgrading to SRv6 from SR-MPLS.It requires some solutions to
   resolve these problems.

2.  Requirements:

   This section list the suggested requirements for Shorter SRv6 SID,
   which have been used to help the WG evaluate against the proposed
   solutions:

Cheng, et al.            Expires August 19, 2020                [Page 2]
Internet-Draft        Shorter SRv6 SID Requirements        February 2020

   REQ#1:The Shorter SRv6 solution MUST align with the basic SRv6.
   There are three basic Segment Routing over the IPv6 data-plane (SRv6)
   documents:

   o  The Segment Routing (SR) architecture is defined [RFC8402].

   o  The IPv6 Segment Routing Header (SRH) is defined
      [I-D.ietf-6man-segment-routing-header].

   o  SRv6 Network Programming is defined
      [I-D.ietf-spring-srv6-network-programming].
Show full document text