Use of BGP for routing in large-scale data centers
draft-lapukhov-bgp-routing-large-dc-07
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Petr Lapukhov , Ariff Premji , Jon Mitchell | ||
Last updated | 2015-10-14 (Latest revision 2014-02-06) | ||
Replaced by | draft-ietf-rtgwg-bgp-routing-large-dc | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Informational | ||
Formats | |||
Stream | WG state | (None) | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-rtgwg-bgp-routing-large-dc | |
Action Holders |
(None)
|
||
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | Alia Atlas | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Some network operators build and operate data centers that support over one hundred thousand servers. In this document, such data centers are referred to as "large-scale" to differentiate them from smaller infrastructures. Environments of this scale have a unique set of network requirements with an emphasis on operational simplicity and network stability. This document summarizes operational experience in designing and operating large-scale data centers using BGP as the only routing protocol. The intent is to report on a proven and stable routing design that could be leveraged by others in the industry.
Authors
Petr Lapukhov
Ariff Premji
Jon Mitchell
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)