The use case in Edge Datacenter network
draft-aoch-nvo3-edge-datacenter-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Ting Ao , Zhonghua Chen | ||
| Last updated | 2017-05-01 (Latest revision 2016-10-28) | ||
| 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
This document introduce the Edge Datacentet network, and describe some use cases about Edge Datacenter, discuss an important component in the Edge Datacenter:Service Gateway and its functions. Service Gateway as a flow distribution device 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, acts as a traffic distributor 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.)