Service Function Chaining Problem Statement
draft-quinn-sfc-problem-statement-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Paul Quinn , Thomas Nadeau | ||
| Last updated | 2014-01-29 (Latest revision 2013-12-09) | ||
| Replaces | draft-quinn-nsc-problem-statement | ||
| Replaced by | RFC 7498 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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 | (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
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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)