Service Function Simple Offloads
draft-ietf-sfc-offloads-00
Document | Type |
Expired Internet-Draft
(sfc WG)
Expired & archived
|
|
---|---|---|---|
Authors | Surendra Kumar , Jim Guichard , Paul Quinn , Joel M. Halpern , Sumandra Majee | ||
Last updated | 2017-10-04 (Latest revision 2017-04-02) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Jim Guichard
Paul Quinn
Joel M. Halpern
Sumandra Majee
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)