Shorter SRv6 SID Requirements
draft-cheng-spring-shorter-srv6-sid-requirement-01

Document Type Active Internet-Draft (individual)
Last updated 2020-03-09
Stream (None)
Intended RFC status (None)
Formats plain text xml 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: Informational                                    C. Xie
Expires: September 9, 2020                                 China Telecom
                                                                 R. Pang
                                                            China Unicom
                                                                   Z. Li
                                                     Huawei Technologies
                                                                 R. Chen
                                                         ZTE Corporation
                                                                   L. Zu
                                                                Unionpay
                                                                 X. Duan
                                                            China Mobile
                                                               G. Mirsky
                                                         ZTE Corporation
                                                           March 8, 2020

                     Shorter SRv6 SID Requirements
           draft-cheng-spring-shorter-srv6-sid-requirement-01

Abstract

   This document describes a list of requirements for the use of a
   shortened identifier in a segment routing network with the IPv6 data
   plane.

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

Cheng, et al.           Expires September 9, 2020               [Page 1]
Internet-Draft        Shorter SRv6 SID Requirements           March 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.  Conventions used in this document . . . . . . . . . . . . . .   3
     2.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Keywords  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Typical Application Scenarios . . . . . . . . . . . . . . . .   3
   4.  Analysis of SRH Overhead  . . . . . . . . . . . . . . . . . .   5
   5.  Gap Analysis of Existing Solutions  . . . . . . . . . . . . .   6
     5.1.  Binding SID . . . . . . . . . . . . . . . . . . . . . . .   6
     5.2.  Loose Path TE . . . . . . . . . . . . . . . . . . . . . .   7
   6.  Requirements: . . . . . . . . . . . . . . . . . . . . . . . .   8
   7.  The proposal solutions of shorter SRv6 SID  . . . . . . . . .  11
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  12
     10.2.  Informative References . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   Segment routing (SR) [RFC8402] is a source routing paradigm that
   explicitly indicates the forwarding path for packets at the ingress
   node by inserting 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 the MPLS data plane by
   encoding 32-bits SIDs in MPLS label stack [RFC8660].  It also can be
   deployed on the IPv6 data plane by encoding a list of 128-bits SRv6
   SIDs in IPv6 Segment Routing Extension Header
   (SRH)[I-D.ietf-6man-segment-routing-header].
Show full document text