Interworking SFC network and Overlay network
draft-ao-sfc-overlay-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ting Ao , Greg Mirsky | ||
| Last updated | 2018-01-04 (Latest revision 2017-07-03) | ||
| 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 Chain (SFC) network presents a distinct network layer. As such, it is carried over by an underlay network. The document reviews two interworking scenarios between the SFC domain and its underlay network - co-located and stand-alone. The document also defines necessary interworking between stand-alone Network Virtual Edge and Service Forwarding Function entities to ensure proper handling of SFC traffic by the underlay network.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)