metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 9125: Gateway Auto-Discovery and Route Advertisement for Site Interconnection Using Segment Routing

In plain English — editorial summary, not part of the RFC

Data centers are attached to the Internet or a backbone network by gateway routers. One data center typically has more than one gateway for commercial, load-balancing, and resiliency reasons. Other sites, such as access networks, also need to be connected across backbone networks through gateways. This document defines a mechanism using the BGP Tunnel Encapsulation attribute to allow data center gateway routers to advertise routes to the prefixes reachable in the site, including advertising them on behalf of other gateways at the same site. This allows segment routing to be used to identify multiple paths across the Internet or backbone network between different gateways. The paths can be selected for load-balancing, resilience, and quality purposes.

Document record

Document ID
RFC9125
Published
August 2021
Authors
A. Farrel; J. Drake; E. Rosen; K. Patel; L. Jalil
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
12
Also known as
—

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/9125-gateway-auto-discovery-and-route-advertisement-for-site-interconnection-using-se