RFC 9125

Gateway Auto-Discovery and Route Advertisement for Site Interconnection Using Segment Routing, August 2021

File formats:

icon for HTML icon for text file icon for v3pdf icon for XML
Status:
PROPOSED STANDARD
Authors:
A. Farrel
J. Drake
E. Rosen
K. Patel
L. Jalil
Stream:
IETF
Source:
bess (rtg)

Cite this RFC: TXT  |  XML

DOI:  10.17487/RFC9125

Discuss this RFC: Send questions or comments to bess@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 9125


Abstract

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.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.