SFC Use Cases on Recursive Service Function Chaining
draft-huang-sfc-use-case-recursive-service-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Changcheng Huang , Jiafeng Zhu , Peng He | ||
| Last updated | 2015-01-03 (Latest revision 2014-07-02) | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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) provides various services that can be tailored to different requirements from diversified user groups, where each user group forms a collective client that requires similar service. SFC is typically deployed as a service overlay with its own service topology on top of existing network topology. This kind of virtualized structure naturally enables recursive service relationship where a client may become a service provider and resell SFC services to its own user groups. This document describes some exemplary use cases that show the usage of recursive (e.g. nested) service function chaining relationship.
Authors
Changcheng Huang
Jiafeng Zhu
Peng He
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)