The SRv6 END.DTM Segment Type
draft-bonica-spring-srv6-end-dtm-00

Document Type Active Internet-Draft (individual)
Authors Shraddha Hegde  , Kaliraj Vairavakkalai  , Ron Bonica 
Last updated 2021-01-08
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)
SPRING Working Group                                            S. Hegde
Internet-Draft                                          K. Vairavakkalai
Intended status: Standards Track                               R. Bonica
Expires: July 12, 2021                                  Juniper Networks
                                                         January 8, 2021

                     The SRv6 END.DTM Segment Type
                  draft-bonica-spring-srv6-end-dtm-00

Abstract

   This document describes a new SRv6 segment type, called END.DTM.  The
   END.DTM segment type supports inter-working between SRv6 and SR-MPLS.
   Like any segment type, END.DTM contains a function and arguments.
   The function causes the processing SRv6 node to remove an SRv6 header
   and impose an SR-MPLS label stack.  The arguments determine MPLS-
   label stack contents.

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 July 12, 2021.

Copyright Notice

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

Hegde, et al.             Expires July 12, 2021                 [Page 1]
Internet-Draft                   END.DTM                    January 2021

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   2
   3.  Use-case  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Processing  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Overview

   Segment Routing (SR) [RFC8402] allows source nodes to steer packets
   through SR paths.  It can be implemented over IPv6 [RFC8200] or MPLS
   [RFC3031].  When SR is implemented over IPv6, it is called SRv6
   [I-D.ietf-spring-srv6-network-programming].  When SR is implemented
   over MPLS, it is called SR-MPLS [RFC8660].

   This document describes a new SRv6 segment type, called END.DTM.  The
   END.DTM segment type supports inter-working between SRv6 and SR-MPLS.
   Like any segment type, END.DTM contains a function and arguments.
   The function causes the processing SRv6 node to:

   o  Remove an SRv6 header (i.e., an IPv6 header and its extensions).

   o  Impose an SR-MPLS label stack.

   The arguments determine MPLS-label stack contents and Transport Class
   of the MPLS Tunnel.

2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Hegde, et al.             Expires July 12, 2021                 [Page 2]
Internet-Draft                   END.DTM                    January 2021

3.  Use-case

        ------       ------       ------       ------       ------
       |Node 1| --- |Node 2| --- |Node 3| --- |Node 4| --- |Node 5|
        ------       ------       ------       ------       ------

                       Seg. A     Seg. B       Seg. C       Seg. D

        <-----------SRv6 Part ----------><-------SR-MPLS Part------>

                        Figure 1: END.DTM Use-case

   Figure 1 depicts an inter-working SR path.  The SR path originates on
Show full document text