Skip to main content

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

Revision differences

Document history

Date By Action
2022-03-31
Gunter Van de Velde Closed request for Last Call review by OPSDIR with state 'Overtaken by Events'
2021-08-28
(System)
Received changes through RFC Editor sync (created alias RFC 9125, changed title to 'Gateway Auto-Discovery and Route Advertisement for Site Interconnection Using Segment Routing', …
Received changes through RFC Editor sync (created alias RFC 9125, changed title to 'Gateway Auto-Discovery and Route Advertisement for Site Interconnection Using Segment Routing', changed abstract to '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.', changed pages to 12, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2021-08-28, changed IESG state to RFC Published)
2021-08-28
(System) RFC published