Service Function Chaining (SFC) Control Plane Components & Requirements
draft-ietf-sfc-control-plane-08
| Document | Type |
Expired Internet-Draft
(sfc WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Mohamed Boucadair | ||
| Last updated | 2017-04-26 (Latest revision 2016-10-23) | ||
| Replaces | draft-ww-sfc-control-plane | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Informational | ||
| Formats | |||
| Reviews |
RTGDIR Early review
by Jonathan Hardwick
Not ready
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | Martin Stiemerling | ||
| Shepherd write-up | Show Last changed 2016-06-08 | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Yes | ||
| Telechat date | (None) | ||
| Responsible AD | Alia Atlas | ||
| Send notices to | "Martin Stiemerling" <mls.ietf@gmail.com> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes requirements for conveying information between Service Function Chaining (SFC) control elements and SFC data plane functional elements. Also, this document identifies a set of control interfaces to interact with SFC-aware elements to establish, maintain or recover service function chains. This document does not specify protocols nor extensions to existing protocols. This document exclusively focuses on SFC deployments that are under the responsibility of a single administrative entity. Inter-domain considerations are out of scope.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)