Path Segment for SRv6 (Segment Routing in IPv6)
draft-li-spring-srv6-path-segment-03

Document Type Active Internet-Draft (individual)
Last updated 2019-08-13
Replaces draft-li-spring-passive-pm-for-srv6-np
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 Working Group                                               C. Li
Internet-Draft                                       Huawei Technologies
Intended status: Standards Track                                W. Cheng
Expires: February 14, 2020                                  China Mobile
                                                                 M. Chen
                                                                D. Dhody
                                                                   Z. Li
                                                                 J. Dong
                                                     Huawei Technologies
                                                               R. Gandhi
                                                     Cisco Systems, Inc.
                                                         August 13, 2019

            Path Segment for SRv6 (Segment Routing in IPv6)
                  draft-li-spring-srv6-path-segment-03

Abstract

   Segment Routing (SR) allows for a flexible definition of end-to-end
   paths by encoding paths as sequences of sub-paths, called "segments".
   Segment routing architecture can be implemented over an MPLS data
   plane as well as an IPv6 data plane.

   Further, Path Segment has been defined in order to identify an SR
   path in SR-MPLS networks, and used for various use-cases such as end-
   to-end SR Path Protection and Performance Measurement (PM) of an SR
   path.  Similar to SR-MPLS, this document defines the Path Segment in
   SRv6 networks in order to identify an SRv6 path.

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 February 14, 2020.

Li, et al.              Expires February 14, 2020               [Page 1]
Internet-Draft              SRv6 Path Segment                August 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.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Use Cases of SRv6 Path Segment  . . . . . . . . . . . . . . .   4
   3.  SRv6 Path Segment . . . . . . . . . . . . . . . . . . . . . .   5
   4.  SRv6 Path Segment Allocation  . . . . . . . . . . . . . . . .   6
   5.  Operations  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

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.

   When segment routing is deployed on MPLS dataplane, called SR-MPLS
   [I-D.ietf-spring-segment-routing-mpls], a segment is an MPLS label.
   When segment routing is deployed on IPv6 dataplane, called SRv6
   [I-D.ietf-6man-segment-routing-header], a segment is a 128 bit value,
   and it can be an IPv6 address of a local interface but it does not
   have to.  For supporting SR, an extended header called Segment
   Routing Header (SRH), which contains a list of SIDs and several
   needed information such as Segments Left, has been defined in
   [I-D.ietf-6man-segment-routing-header].
Show full document text