RFC 7938: Use of BGP for Routing in Large-Scale Data Centers
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7938
- Published
- August 2016
- Authors
- P. Lapukhov; A. Premji; J. Mitchell
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 35
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7899Multicast VPN State DampingCurrent
June 2016
- RFC 8092BGP Large Communities AttributeCurrent
February 2017
- RFC 7752North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGPObsoleted
March 2016
- RFC 7705Autonomous System Migration Mechanisms and Their Effects on the BGP AS_PATH AttributeCurrent
November 2015
- RFC 7674Clarification of the Flowspec Redirect Extended CommunityObsoleted
October 2015
- RFC 8203BGP Administrative Shutdown CommunicationObsoleted
July 2017
- RFC 8205BGPsec Protocol SpecificationUpdated
September 2017
- RFC 8207BGPsec Operational ConsiderationsCurrent
September 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?