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. Stream: Internet Engineering Task Force (IETF) RFC: 9125 Category: Standards Track Published: August 2021 ISSN: 2070-1721 Authors: A. Farrel Old Dog Consulting J. Drake Juniper Networks E. Rosen Juniper Networks K. Patel Arrcus, Inc. L. Jalil Verizon Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at . https://www.rfc-editor.org/info/rfc9125 Copyright Notice Copyright (c) 2021 IETF Trust and the persons identified as the document authors. All rights reserved. Farrel, et al. Standards Track Page 1 This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents ( ) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. https://trustee.ietf.org/license-info Table of
[1]
Clarence Filsfils,et al.
The Segment Routing Architecture
,
2014,
2015 IEEE Global Communications Conference (GLOBECOM).
[2]
Luyuan Fang,et al.
Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs)
,
2006,
RFC.
[3]
Eric C. Rosen,et al.
The BGP Tunnel Encapsulation Attribute
,
2019
.
[4]
Adrian Farrel,et al.
Interconnection of Segment Routing Domains - Problem Statement and Solution Landscape
,
2018
.
[5]
Adrian Farrel,et al.
North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
,
2016,
RFC.
[6]
Enke Chen,et al.
Outbound Route Filtering Capability for BGP-4
,
2008,
RFC.
[7]
Joseph D. Touch,et al.
The TCP Authentication Option
,
2010,
RFC.
[8]
Xian Zhang,et al.
Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered Networks
,
2016,
RFC.
[9]
Yakov Rekhter,et al.
BGP/MPLS IP Virtual Private Networks (VPNs)
,
2006,
RFC.
[10]
Keyur Patel,et al.
Analysis of BGP, LDP, PCEP, and MSDP Issues According to the Keying and Authentication for Routing Protocols (KARP) Design Guide
,
2013,
RFC.
[11]
Ketan Talaulikar,et al.
Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing
,
2021,
RFC.
[12]
Sandra L. Murphy,et al.
BGP Security Vulnerabilities Analysis
,
2006,
RFC.
[13]
Ketan Talaulikar,et al.
BGP-LS extensions for Segment Routing BGP Egress Peer Engineering
,
2019
.
[14]
Thomas Narten,et al.
Guidelines for Writing an IANA Considerations Section in RFCs
,
1998,
RFC.
[15]
Yakov Rekhter,et al.
BGP Extended Communities Attribute
,
2006,
RFC.
[16]
Daniel Walton,et al.
Advertisement of Multiple Paths in BGP
,
2016,
RFC.
[17]
Barry Leiba,et al.
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
,
2017,
RFC.
[18]
Dave Katz,et al.
Multiprotocol Extensions for BGP-4
,
1998,
RFC.