Connection-oriented Path in SRv6 Network
draft-du-spring-connection-oriented-srv6-00

Document Type Active Internet-Draft (individual)
Last updated 2020-03-09
Stream (None)
Intended RFC status (None)
Formats plain text 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)
Network Working Group                                              Z. Du
Internet-Draft                                                    P. Liu
Intended status: Standards Track                                 L. Geng
Expires: September 10, 2020                                 China Mobile
                                                           March 9, 2020

                Connection-oriented Path in SRv6 Network
              draft-du-spring-connection-oriented-srv6-00

Abstract

   This document proposes a method to support connection-oriented path
   in the SRv6 network.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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 September 10, 2020.

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
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect

Du, et al.             Expires September 10, 2020               [Page 1]
Internet-Draft      Connection-oriented Path in SRv6          March 2020

   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
   2.  Data Plane for Connection-oriented Path . . . . . . . . . . .   3
   3.  Control Plane for Connection-oriented Path  . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   SRv6 Network Programming concept is introduced in
   [I-D.ietf-spring-srv6-network-programming] and
   [I-D.filsfils-spring-srv6-net-pgm-illustration], which enables a data
   plane based network programming mechanism that goes beyond mere
   packet routing.

   According to [I-D.ietf-spring-srv6-network-programming], an SRv6 SID
   is defined as the format of LOC:FUNCT:ARG, where the LOC stands for a
   locater, the FUNCT stands for a function, and the ARG stands for the
   arguments of the function.  The locater is usually used to route the
   packet to the node who generates the SID.  The basic functions of
   SRv6 are End (related to a node) and End.X (related to a link/
   adjacency), and many other functions are also defined, including some
   VPN related ones and some binding SIDs.  In addition, it is said that
   even a local VM or container which can apply any complex processing
   on the packet can be defined as a function.  The functions may or may
   not include arguments.

   Based on SRv6, a node in the network can initiate a SID list <SID1,
   SID2, SID3> for a flow, so that a packet of the flow would be routed
   to the first node where the function1 related to SID1 would be
   implemented, then be routed to the second node where function2
   related to SID2 would be implemented, and trigger similar operations
   according to SID3.

   In fact, both MPLS and SRv6 are some kind of languages that support
   network programming.  By using a label to represent a VPN instance,
   MPLS provides a good support to the VPN services in the network.

Du, et al.             Expires September 10, 2020               [Page 2]
Internet-Draft      Connection-oriented Path in SRv6          March 2020

   SRv6 now shows a much powerful capability in network programming.
   Perhaps in future, a lot of new network characteristics would be
Show full document text