Service Function Chaining with Stitched Tunnels
draft-hegde-spring-sfc-stitched-tunnel-00

Document Type Active Internet-Draft (individual)
Authors Shraddha Hegde  , Colby Barth 
Last updated 2021-01-07
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                                                          S. Hegde
Internet-Draft                                                  C. Barth
Intended status: Informational                     Juniper Networks Inc.
Expires: July 11, 2021                                   January 7, 2021

            Service Function Chaining with Stitched Tunnels
               draft-hegde-spring-sfc-stitched-tunnel-00

Abstract

   The term "service function chaining" is used to describe the
   definition and instantiation of an ordered list of instances of such
   service functions, and the subsequent "steering" of traffic flows
   through those service functions.This document describes transport
   mechanisms that use stitched tunnels to achieve end-to-end service
   chaining.  This document specifies two different types of transport
   encodings, one based on SR-MPLS and another based on IP tunnels.

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 11, 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 & Barth             Expires July 11, 2021                 [Page 1]
Internet-Draft   Service Chaining with Stitched Tunnels     January 2021

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Concept of Stitched Tunnel  . . . . . . . . . . . . . . . . .   3
   4.  SR-MPLS based Tunnels . . . . . . . . . . . . . . . . . . . .   6
   5.  IP Tunnels  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Backward Compatibility  . . . . . . . . . . . . . . . . . . .   7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   10. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   7
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   7
     11.2.  Informative References . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Service function chaining requires an ordered set of service
   functions to be executed on the traffic.  The set of service
   functions could be virtualized functions or physical appliance based
   functions or in some cases a mix of both.  Traffic needs to be
   steered to the set of service functions in an ordered manner.  Based
   on the the type of traffic, the order of the service functions and
   the type of service functions that need to be executed may differ.
   Service functions may not be aware of the transport encodings and
   hence the transport encodings may have to be removed before passing
   the packet(s) to the service functions.

   Section Section 3 describes basic concepts of using stitched tunnels
   to steer the traffic through the service functions.
   Section Section 4 describes the transport encodings using SR-MPLS
   based tunnels [RFC8402].  Section Section 5 describes the transport
   encodings using IP Tunnels [I-D.saad-teas-rsvpte-ip-tunnels].

   This document uses terminology defined in [RFC7665].

2.  Terminology

Hegde & Barth             Expires July 11, 2021                 [Page 2]
Internet-Draft   Service Chaining with Stitched Tunnels     January 2021

 This document uses the following terminology

   o  Service Function Orchestrator (SFO): Service Function Orchestrator is
      responsible for defining the Service Function Chains and the traffic
      types where the particular service function chains are applicable.
Show full document text