Last Call: <draft-ietf-rtgwg-bgp-routing-large-dc-10.txt> (Use of BGP for routing in large-scale data centers) to Informational RFC

The IESG <> Mon, 23 May 2016 22:51 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 3989612DC0B; Mon, 23 May 2016 15:51:25 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: "IETF-Announce" <>
Subject: Last Call: <draft-ietf-rtgwg-bgp-routing-large-dc-10.txt> (Use of BGP for routing in large-scale data centers) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 6.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <>
Message-ID: <>
Date: Mon, 23 May 2016 15:51:25 -0700
Archived-At: <>
X-Mailman-Version: 2.1.17
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 23 May 2016 22:51:25 -0000

The IESG has received a request from the Routing Area Working Group WG
(rtgwg) to consider the following document:
- 'Use of BGP for routing in large-scale data centers'
  <draft-ietf-rtgwg-bgp-routing-large-dc-10.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the mailing lists by 2016-06-06. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   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.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.