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

Document Type Active Internet-Draft (individual)
Last updated 2018-10-10
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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                                                        G. Mirsky
Internet-Draft                                                 ZTE Corp.
Intended status: Standards Track                               P. Shaofu
Expires: April 13, 2019                                  ZTE Corporation
                                                        October 10, 2018

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

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 MPLS label stack.  It also can be
   applied to IPv6 data plane by encoding list of segment identifiers in
   IPv6 Segment Routing Extension Header (SRH).  This document extends
   the use of the SRH to segment identifiers encoded as MPLS label and
   IPv4 address.

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 April 13, 2019.

Copyright Notice

   Copyright (c) 2018 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

Mirsky & Shaofu          Expires April 13, 2019                 [Page 1]
Internet-Draft           Unified Identifier SRv6            October 2018

   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.  Segment Routing Extension Header: Benefits and Challenges . .   3
   3.  Support of Multiple SID Lengths in IPv6 Segment Routing
       Extension Header  . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Theory of Operation . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Egress SR Tunnel Node . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

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 [I-D.ietf-spring-segment-routing-mpls].  It also can
   be applied to IPv6 data plane by encoding list of 128-bits SIDs in
   IPv6 Segment Routing Extension Header (SRH)
   [I-D.ietf-6man-segment-routing-header].  Applicability of 32-bits SID
   that may represent an IPv4 address has not been defined.

   SR extensions to Interior Gateway Protocols (IGP), IS-IS
   [I-D.ietf-isis-segment-routing-extensions], OSPF
   [I-D.ietf-ospf-segment-routing-extensions], and OSPFv3
   [I-D.ietf-ospf-ospfv3-segment-routing-extensions], defined how
   20-bits and 32-bits SIDs advertised and bound to SR objects and/or
   instructions.  Extensions to BGP link-state address family
   [I-D.ietf-idr-bgp-ls-segment-routing-ext] enabled propagation of
   segment information of variable length via BGP.

Show full document text