Leading indicators of change for routing in Modern Data Center environments
draft-purkayastha-dcrouting-leading-indicators-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Debashish Purkayastha , Akbar Rahman , Dirk Trossen | ||
| Last updated | 2018-09-02 (Latest revision 2018-03-01) | ||
| 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 describes a few use cases to illustrate the expectations on today's network. Based on those expectations, it describes how the network architecture and network requirements are changing. The new requirements are impacting data center architecture. The way data centers are evolving, such as central data centers to smaller data centers, a single deployment to multiple deployments, is described. With this new data center model, areas such as routing inside the data center and outside the data center is impacted. The document describes this impact and summarizes few features for these new data center model.
Authors
Debashish Purkayastha
Akbar Rahman
Dirk Trossen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)