RFC 7938 on Use of BGP for Routing in Large-Scale Data Centers
rfc-editor@rfc-editor.org Wed, 10 August 2016 16:05 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B16212D526; Wed, 10 Aug 2016 09:05:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.849
X-Spam-Level:
X-Spam-Status: No, score=-103.849 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.247, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0mZ7DeoXgQw0; Wed, 10 Aug 2016 09:05:29 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11C2A12B036; Wed, 10 Aug 2016 09:05:29 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 026F0B80FC9; Wed, 10 Aug 2016 09:05:28 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7938 on Use of BGP for Routing in Large-Scale Data Centers
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160810160529.026F0B80FC9@rfc-editor.org>
Date: Wed, 10 Aug 2016 09:05:28 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/EG2lqLF29HkRqtnEDR7CvQ6UxuE>
Cc: drafts-update-ref@iana.org, rtgwg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2016 16:05:30 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7938
Title: Use of BGP for Routing
in Large-Scale Data Centers
Author: P. Lapukhov, A. Premji,
J. Mitchell, Ed.
Status: Informational
Stream: IETF
Date: August 2016
Mailbox: petr@fb.com,
ariff@arista.com,
jrmitche@puck.nether.net
Pages: 35
Characters: 89682
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-rtgwg-bgp-routing-large-dc-11.txt
URL: https://www.rfc-editor.org/info/rfc7938
DOI: http://dx.doi.org/10.17487/RFC7938
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.
This document is a product of the Routing Area Working Group Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC