RFC 9125 on Gateway Auto-Discovery and Route Advertisement for Site Interconnection Using Segment Routing
rfc-editor@rfc-editor.org Sat, 28 August 2021 17:12 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B3293A0D35; Sat, 28 Aug 2021 10:12:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rh_JxqyTL73C; Sat, 28 Aug 2021 10:12:47 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A98713A0D32; Sat, 28 Aug 2021 10:12:47 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 35658F40744; Sat, 28 Aug 2021 10:12:30 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9125 on Gateway Auto-Discovery and Route Advertisement for Site Interconnection Using Segment Routing
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, bess@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210828171230.35658F40744@rfc-editor.org>
Date: Sat, 28 Aug 2021 10:12:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/XvF1bgOClVTnIcuZs0bwgqVg80A>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Aug 2021 17:12:56 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9125
Title: Gateway Auto-Discovery and Route Advertisement
for Site Interconnection Using Segment Routing
Author: A. Farrel,
J. Drake,
E. Rosen,
K. Patel,
L. Jalil
Status: Standards Track
Stream: IETF
Date: August 2021
Mailbox: adrian@olddog.co.uk,
jdrake@juniper.net,
erosen52@gmail.com,
keyur@arrcus.com,
luay.jalil@verizon.com
Pages: 12
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-bess-datacenter-gateway-13.txt
URL: https://www.rfc-editor.org/info/rfc9125
DOI: 10.17487/RFC9125
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.
This document is a product of the BGP Enabled Services Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC