RFC 9107: BGP Optimal Route Reflection (BGP ORR)
In plain English — editorial summary, not part of the RFC
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 themselves. 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, a "best exit point" policy ("hot potato routing"). The solution relies upon all route reflectors learning all paths that 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.
Document record
- Document ID
- RFC9107
- Published
- August 2021
- Authors
- R. Raszuk; B. Decraene; C. Cassar; E. Åman; K. Wang
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9072Extended Optional Parameters Length for BGP OPEN MessageCurrent
July 2021
- RFC 8810Revision to Capability Codes Registration ProceduresCurrent
August 2020
- RFC 8538Notification Message Support for BGP Graceful RestartCurrent
March 2019
- RFC 9815BGP Link State (BGP-LS) Shortest Path First (SPF) RoutingCurrent
July 2025
- RFC 7947Internet Exchange BGP Route ServerCurrent
September 2016
- RFC 7705Autonomous System Migration Mechanisms and Their Effects on the BGP AS_PATH AttributeCurrent
November 2015
- RFC 5575Dissemination of Flow Specification RulesObsoleted
August 2009
- RFC 5492Capabilities Advertisement with BGP-4Updated
February 2009
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?