[Idr] Last Call: <draft-ietf-idr-bgp-optimal-route-reflection-23.txt> (BGP Optimal Route Reflection (BGP-ORR)) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Fri, 21 May 2021 19:36 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 78F5E3A1E13; Fri, 21 May 2021 12:36:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.30.0
Auto-Submitted: auto-generated
Precedence: bulk
CC: John Scudder <jgs@juniper.net>, Susan Hares <shares@ndzh.com>, aretana.ietf@gmail.com, draft-ietf-idr-bgp-optimal-route-reflection@ietf.org, idr-chairs@ietf.org, idr@ietf.org, shares@ndzh.com
Reply-To: last-call@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <162162580140.12804.4057428587485376506@ietfa.amsl.com>
Date: Fri, 21 May 2021 12:36:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/bN3KU__wSVfBn_0UVQlQ21GFoL4>
Subject: [Idr] Last Call: <draft-ietf-idr-bgp-optimal-route-reflection-23.txt> (BGP Optimal Route Reflection (BGP-ORR)) to Proposed Standard
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 May 2021 19:36:42 -0000

The IESG has received a request from the Inter-Domain Routing WG (idr) to
consider the following document: - 'BGP Optimal Route Reflection (BGP-ORR)'
  <draft-ietf-idr-bgp-optimal-route-reflection-23.txt> as Proposed Standard

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
last-call@ietf.org mailing lists by 2021-06-07. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.


   This document defines an extension to BGP route reflectors.  On route
   reflectors, BGP route selection is modified in order to choose the
   best route from the standpoint of their clients, rather than from the
   standpoint of the route reflectors.  Depending on the scaling and
   precision requirements, route selection can be specific for one
   client, common for a set of clients or common for all clients of a
   route reflector.  This solution is particularly applicable in
   deployments using centralized route reflectors, where choosing the
   best route based on the route reflector's IGP location is suboptimal.
   This facilitates, for example, best exit point policy (hot potato

   The solution relies upon all route reflectors learning all paths
   which are eligible for consideration.  BGP Route Selection is
   performed in the route reflectors based on the IGP cost from
   configured locations in the link state IGP.

The file can be obtained via

The following IPR Declarations may be related to this I-D: