SRv6 network programming using Unified Identifier
draft-mirsky-spring-unified-id-network-programming-00

Document Type Active Internet-Draft (individual)
Last updated 2020-03-06
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                                                       C. Weiqiang
Internet-Draft                                              China Mobile
Intended status: Informational                                 G. Mirsky
Expires: September 7, 2020                                     ZTE Corp.
                                                                L. Aihua
                                                               P. Shaofu
                                                         ZTE Corporation
                                                           March 6, 2020

           SRv6 network programming using Unified Identifier
         draft-mirsky-spring-unified-id-network-programming-00

Abstract

   This draft describes how Unified Segment Identifier can be used to
   achieve the goals of SRv6 network programming.

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 7, 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

Weiqiang, et al.        Expires September 7, 2020               [Page 1]
Internet-Draft     Unified Identifier SRv6 programming        March 2020

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Conventions used in this document . . . . . . . . . . . .   2
       1.1.1.  Terminology . . . . . . . . . . . . . . . . . . . . .   3
       1.1.2.  Requirements Language . . . . . . . . . . . . . . . .   3
   2.  SRv6 Network Programming using U-SID  . . . . . . . . . . . .   3
     2.1.  SRv6 Network Programming  . . . . . . . . . . . . . . . .   3
     2.2.  SRv6 Network Programming Using 32bit U-SID  . . . . . . .   4
     2.3.  U-SID with MPLS Programming Process . . . . . . . . . . .   5
       2.3.1.  U-SID with MPLS Support Programming using Flavors . .   5
     2.4.  U-SID with SRv6 Programming process . . . . . . . . . . .   6
     2.5.  U-SID Complementary Method  . . . . . . . . . . . . . . .   6
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Segment Routing architecture [RFC8402] leverages the paradigm of
   source routing.  It can be realized in a network data plane by
   prepending the packet with a list of instructions, a.k.a.  Segment
   Identifiers (SIDs).  A segment can be encoded as a Multi-Protocol
   Label Switching (MPLS) label, IPv4 address, or IPv6 address.  Segment
   Routing can be applied in MPLS data plane by encoding 20-bits SIDs in
   MPLS label stack [RFC8660].  It also can be applied to 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].

   Unified SID [I-D.mirsky-6man-unified-id-sr] defines an extension of
   SRH that enables the use of a shorter segment identifier, such as
   32-bits Label format SID or 32-bits IP address format SID.

   SRv6 network programming is defined
   [I-D.ietf-spring-srv6-network-programming].  SRv6 network programming
   can be supported using Unified SID.

1.1.  Conventions used in this document

Weiqiang, et al.        Expires September 7, 2020               [Page 2]
Internet-Draft     Unified Identifier SRv6 programming        March 2020

1.1.1.  Terminology

   SR: Segment Routing

   SRH: Segment Routing Extension Header
Show full document text