Unified Identifier in IPv6 Segment Routing Networks
draft-mirsky-6man-unified-id-sr-07

Document Type Active Internet-Draft (individual)
Last updated 2020-07-02
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) 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                                                      C. Weiqiang
Internet-Draft                                              China Mobile
Intended status: Standards Track                               G. Mirsky
Expires: January 3, 2021                                       ZTE Corp.
                                                               P. Shaofu
                                                                L. Aihua
                                                         ZTE Corporation
                                                               G. Mishra
                                                            Verizon Inc.
                                                            July 2, 2020

          Unified Identifier in IPv6 Segment Routing Networks
                   draft-mirsky-6man-unified-id-sr-07

Abstract

   Segment Routing architecture 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. segments.  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 segments in the MPLS label stack.  It also can
   be applied to IPv6 data plane by encoding a list of segment
   identifiers in IPv6 Segment Routing Extension Header (SRH).  This
   document extends the use of the SRH to unified segment identifiers
   encoded, for example, as MPLS label or IPv4 address, to compress the
   SRH, and support more detailed network programming and interworking
   between SR-MPLS and SRv6 domains.

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 3, 2021.

Weiqiang, et al.         Expires January 3, 2021                [Page 1]
Internet-Draft           Unified Identifier SRv6               July 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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Conventions used in this document . . . . . . . . . . . .   3
       1.1.1.  Acronyms  . . . . . . . . . . . . . . . . . . . . . .   3
       1.1.2.  Requirements Language . . . . . . . . . . . . . . . .   4
   2.  Segment Routing Extension Header: Benefits and Challenges . .   4
   3.  Unified SIDs in IPv6 Segment Routing Extension Header . . . .   4
   4.  The Use Case of Unified Segment Identifier  . . . . . . . . .   6
     4.1.  Interworking Between SR-MPLS and SRv6 Using U-SID . . . .   6
   5.  Operations with Unified Segment Identifier  . . . . . . . . .   9
     5.1.  Procedures of SR-MPLS over IP . . . . . . . . . . . . . .  10
     5.2.  Packet Forwarding . . . . . . . . . . . . . . . . . . . .  10
   6.  Interworking Between Different UET domain Considerations  . .  12
     6.1.  Interworking Using Binding SID  . . . . . . . . . . . . .  12
     6.2.  Interworking Using Mixing U-SID . . . . . . . . . . . . .  12
       6.2.1.  UET capability Advertisement  . . . . . . . . . . . .  13
       6.2.2.  SRv6 SID Allocated per UET  . . . . . . . . . . . . .  13
       6.2.3.  Packets Forwarding Procedures . . . . . . . . . . . .  15
       6.2.4.  SRH with mixing elements Pseudo-code  . . . . . . . .  18
   7.  Control Plane in Support of Unified SID . . . . . . . . . . .  19
   8.  U-SID supporting SRv6 programming . . . . . . . . . . . . . .  20
   9.  Implementation Considerations . . . . . . . . . . . . . . . .  20
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  20
   11. Security Considerations . . . . . . . . . . . . . . . . . . .  21
   12. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  21
Show full document text