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

Document Type Expired Internet-Draft (individual)
Last updated 2017-04-23 (latest revision 2016-10-20)
Replaces draft-kumar-sfc-sfp-optimization
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-kumar-sfc-offloads-03.txt

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".

Authors

Surendra Kumar (smkumar@cisco.com)
Jim Guichard (jguichar@cisco.com)
Paul Quinn (paulq@cisco.com)
Joel Halpern (joel.halpern@ericsson.com)
Sumandra Majee (s.majee@f5.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)