The use case in Edge Datacenter network
draft-aoch-nvo3-edge-datacenter-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ting Ao , Zhonghua Chen | ||
| 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
This document introduces the Edge Datacentet network, and describe some use cases about Edge Datacenter, discusses an important component in the Edge Datacenter:Service Gateway and its functions, elaborates the requirements on Service Gateway. Service Gateway works as a Flow Split Device(FSD) in the Edge DC network, it needs to not only play a gateway of the edge Datacenter network, implementing coordination with existing technology, but also meets many new requirements. For example, to make sure the packets goes into Edge DC or Metro network, SDN forwarding, and as a leaf in the leaf-spin architecture.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)