Encapsulation of Path Segment in SRv6
draft-li-6man-srv6-path-segment-encap-04

Document Type Active Internet-Draft (individual)
Authors Cheng Li  , Weiqiang Cheng  , Zhenbin Li  , Dhruv Dhody 
Last updated 2020-10-30
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)
6man Working Group                                                 C. Li
Internet-Draft                                       Huawei Technologies
Intended status: Standards Track                                W. Cheng
Expires: May 4, 2021                                        China Mobile
                                                                   Z. Li
                                                                D. Dhody
                                                     Huawei Technologies
                                                        October 31, 2020

                 Encapsulation of Path Segment in SRv6
                draft-li-6man-srv6-path-segment-encap-04

Abstract

   Segment Routing (SR) allows for a flexible definition of end-to-end
   paths by encoding an ordered list of instructions, called "segments".
   The SR architecture can be implemented over an IPv6 data plane,
   called SRv6.  In some use-cases such as end-to-end SR Path Protection
   and Performance Measurement (PM), an SRv6 path needs to be
   identified.  This document defines the encoding of Path Segment in
   SRv6 networks.

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

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

Li, et al.                 Expires May 4, 2021                  [Page 1]
Internet-Draft               SRv6 PSID Encap                October 2020

   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.  Encoding of an SRv6 Path Segment  . . . . . . . . . . . . . .   3
     2.1.  Encapsulation of SRv6 Path Segment  . . . . . . . . . . .   3
   3.  Processing of SRv6 Path Segment . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

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 an IPv6 data plane, it is called
   SRv6, and it uses a new IPv6 [RFC8200] Routing Header (EH) called the
   IPv6 Segment Routing Header (SRH) [RFC8754] to construct an SRv6
   path.  As per [I-D.ietf-spring-srv6-network-programming], an SRv6
   segment identifier is a 128-bit value, which can be represented as
   LOC:FUNCT, where LOC is the L most significant bits and FUNCT is the
   128-L least significant bits.  Most often the LOC part of the SID is
   routable and leads to the node which instantiates that SID.  The
   FUNCT part of the SID is an opaque identification of a local function
   bound to the SID.

   In several use cases, such as binding bidirectional path
   [I-D.ietf-pce-sr-bidir-path] and end-to-end performance measurement
   [I-D.gandhi-spring-twamp-srpm], the ability to implement path
   identification is a pre-requisite.  In SRv6, it is possible to
   identify a path by the content of the segment list.  However, the
   segment list may not be a good key, since the length of the segment
   list may be too long and flexible according to the number of SIDs.
Show full document text