Analysis of the SFC scalability
draft-ao-sfc-scalability-analysis-00
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
---|---|---|---|
Author | Ting Ao | ||
Last updated | 2016-01-08 (Latest revision 2015-07-07) | ||
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
SFC as a chain of a set of service function, should be scalable to meet all kinds of requirements. The scalability of SFC means the SFC could be elastic to accomodate one or more SFs join the SFC , or leave the SFC. The document present four cases of the scalability, and analysis the data plane and the control plane to implement the scalable SFC.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)