SFC Use Cases on Recursive Services
draft-huang-sfc-use-case-recursive-service-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Changcheng Huang , Jiafeng Zhu , Peng He | ||
| Last updated | 2015-07-20 (Latest revision 2015-01-13) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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. Alternatively, a client may also choose to ask its service provider to provide a structured service for its user groups. This document describes some exemplary use cases that show the usage of recursive (e.g. nested) or structured 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.)