Service Function Chaining Problem Statement
draft-quinn-sfc-problem-statement-02

Document Type Replaced Internet-Draft (individual)
Last updated 2014-01-29 (latest revision 2013-12-09)
Replaces draft-quinn-nsc-problem-statement
Replaced by draft-ietf-sfc-problem-statement
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-sfc-problem-statement
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-quinn-sfc-problem-statement-02.txt

Abstract

This document provides an overview of the issues associated with the deployment of service functions (such as firewalls, load balancers) in large-scale environments. The term service function chaining is used to describe the definition and instantiation of an ordered set of such service functions, and the subsequent "steering" of traffic flows through those service functions. The set of enabled service function chains reflect operator service offerings and is designed in conjunction with application delivery and service and network policy.

Authors

Paul Quinn (paulq@cisco.com)
Thomas Nadeau (tnadeau@juniper.net)

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