Architecture and application scenario for fused service function chain
draft-dai-sfc-fused-architecture-and-scenario-01
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
---|---|---|---|
Authors | Jinyou Dai , Xueshun Wang , Jun Gao | ||
Last updated | 2021-12-29 (Latest revision 2021-06-27) | ||
RFC stream | (None) | ||
Formats | |||
Additional resources | |||
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
This document discusses the architecture and application scenarios of fused service function chain. Fused service function chain means that two or more service function chains are fused to become a single service function chain from the view of data plane and control plane. Fused service function chain is a expansion for service function chain. Anyhow, some mechanism or methods need to be used when two or more service function chains are fused to be a single service function chain.
Authors
Jinyou Dai
Xueshun Wang
Jun Gao
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)