Service Function Simple Offloads
draft-kumar-sfc-offloads-03

Document Type Active Internet-Draft (individual)
Last updated 2016-10-20
Replaces draft-kumar-sfc-sfp-optimization
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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)
Service Function Chaining                                       S. Kumar
Internet-Draft                                               J. Guichard
Intended status: Standards Track                                P. Quinn
Expires: April 23, 2017                              Cisco Systems, Inc.
                                                              J. Halpern
                                                                Ericsson
                                                                S. Majee
                                                             F5 Networks
                                                        October 20, 2016

                    Service Function Simple Offloads
                      draft-kumar-sfc-offloads-03

Abstract

   Service Function Chaining (SFC) enables services to be delivered by
   selective traffic steering through an ordered set of service
   functions.  Once classified into an SFC, the traffic for a given flow
   is steered through all the service functions of the SFC for the life
   of the traffic flow even though this is often not necessary.
   Steering traffic to service functions only while required and not
   otherwise, leads to shorter SFC forwarding paths with improved
   latencies, reduced resource consumption and better user experience.

   This document describes the rationale, techniques and necessary
   protocol extensions to achieve such optimization, with focus on one
   such technique termed "simple offloads".

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 http://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 April 23, 2017.

Kumar, et al.            Expires April 23, 2017                 [Page 1]
Internet-Draft               SFC SF Offloads                October 2016

Copyright Notice

   Copyright (c) 2016 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
   (http://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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Definition Of Terms . . . . . . . . . . . . . . . . . . . . .   3
   3.  Service Function Path Reduction . . . . . . . . . . . . . . .   4
     3.1.  Bypass  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Simple Offload  . . . . . . . . . . . . . . . . . . . . .   5
       3.2.1.  Stateful SFF  . . . . . . . . . . . . . . . . . . . .   7
       3.2.2.  Packet Re-ordering  . . . . . . . . . . . . . . . . .   7
       3.2.3.  Race Conditions . . . . . . . . . . . . . . . . . . .   8
       3.2.4.  Policy Implications . . . . . . . . . . . . . . . . .   8
       3.2.5.  Capabilities Exchange . . . . . . . . . . . . . . . .   8
   4.  Methods For SFP Reduction . . . . . . . . . . . . . . . . . .   9
     4.1.  SFP In-band Offload . . . . . . . . . . . . . . . . . . .   9
       4.1.1.  Progression Of SFP Reduction  . . . . . . . . . . . .  11
     4.2.  Service Controller Offload  . . . . . . . . . . . . . . .  12
   5.  Simple Offload Data-plane Signaling . . . . . . . . . . . . .  13
     5.1.  Offload Flags Definition  . . . . . . . . . . . . . . . .  14
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  15
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
     7.1.  Standard Class Registry . . . . . . . . . . . . . . . . .  15
       7.1.1.  Simple Offloads TLV . . . . . . . . . . . . . . . . .  15
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  16
Show full document text