Unified Identifier in IPv6 Segment Routing Networks
draft-wmsaxw-6man-usid-id-use-00

Document Type Active Internet-Draft (individual)
Last updated 2019-11-04
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
On Agenda spring at IETF-106
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: Informational                                 P. Shaofu
Expires: May 6, 2020                                            L. Aihua
                                                         ZTE Corporation
                                                               G. Mirsky
                                                               ZTE Corp.
                                                              W. Xiaolan
                                            New H3C Technologies Co. Ltd
                                                                  C. Wei
                                                                  Centec
                                                                S. Zadok
                                                                Broadcom
                                                        November 3, 2019

          Unified Identifier in IPv6 Segment Routing Networks
                    draft-wmsaxw-6man-usid-id-use-00

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 the MPLS
   data plane by encoding segments in an MPLS label stack.  It also can
   be applied to the IPv6 data plane by encoding a list of segment
   identifiers in IPv6 Segment Routing Extension Header (SRH).  In this
   document is described the use of unified segment identifiers in use
   cases where interworking between SR-MPLS and SRv6 is required.

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 May 6, 2020.

Weiqiang, et al.           Expires May 6, 2020                  [Page 1]
Internet-Draft           Unified Identifier SRv6           November 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
     1.1.  Conventions used in this document . . . . . . . . . . . .   3
       1.1.1.  Terminology . . . . . . . . . . . . . . . . . . . . .   3
       1.1.2.  Requirements Language . . . . . . . . . . . . . . . .   3
   2.  Requirements for Using SRv6 in Backhaul . . . . . . . . . . .   4
   3.  Using SRv6 U-SID in Backhaul  . . . . . . . . . . . . . . . .   4
     3.1.  Smoothly Upgrading to SRv6 from SR-MPLS . . . . . . . . .   4
     3.2.  Interworking Between SRv6 and SR-MPLS . . . . . . . . . .   5
     3.3.  Compressing SRv6 Header Effectively . . . . . . . . . . .   6
     3.4.  Support a Super-large-scale Networking and Flexibility in
           Assigning Addresses . . . . . . . . . . . . . . . . . . .   6
   4.  Operations with Unified Segment Identifier  . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Many functions related to Operation, Administration and Maintenance
   (OAM) require identification of the SR tunnel ingress and the path,
   constructed by segments, between the ingress and the egress SR nodes.
   Combination of IPv6 encapsulation [RFC8200] and the Source Routing
   Extension Header (SRH) [I-D.ietf-6man-segment-routing-header],
Show full document text