[Idr] RFC 9351 on Border Gateway Protocol - Link State (BGP-LS) Extensions for Flexible Algorithm Advertisement
rfc-editor@rfc-editor.org Wed, 22 February 2023 19:21 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5A7CC15270B; Wed, 22 Feb 2023 11:21:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.648
X-Spam-Level:
X-Spam-Status: No, score=-6.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RAdnde3rxR4X; Wed, 22 Feb 2023 11:21:41 -0800 (PST)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B766CC1595E5; Wed, 22 Feb 2023 11:19:35 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id A86C755E8B; Wed, 22 Feb 2023 11:19:35 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, idr@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230222191935.A86C755E8B@rfcpa.amsl.com>
Date: Wed, 22 Feb 2023 11:19:35 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/FTcgnN245x7Y1ujijEPAqVoDS5E>
Subject: [Idr] RFC 9351 on Border Gateway Protocol - Link State (BGP-LS) Extensions for Flexible Algorithm Advertisement
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2023 19:21:45 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9351
Title: Border Gateway Protocol - Link
State (BGP-LS) Extensions for Flexible Algorithm
Advertisement
Author: K. Talaulikar, Ed.,
P. Psenak,
S. Zandi,
G. Dawra
Status: Standards Track
Stream: IETF
Date: February 2023
Mailbox: ketant.ietf@gmail.com,
ppsenak@cisco.com,
szandi@linkedin.com,
gdawra.ietf@gmail.com
Pages: 14
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-idr-bgp-ls-flex-algo-12.txt
URL: https://www.rfc-editor.org/info/rfc9351
DOI: 10.17487/RFC9351
Flexible Algorithm is a solution that allows some routing protocols
(e.g., OSPF and IS-IS) to compute paths over a network based on
user-defined (and hence, flexible) constraints and metrics. The
computation is performed by routers participating in the specific
network in a distributed manner using a Flexible Algorithm Definition
(FAD). This definition is provisioned on one or more routers and
propagated through the network by OSPF and IS-IS flooding.
Border Gateway Protocol - Link State (BGP-LS) enables the collection
of various topology information from the network. This document
defines extensions to the BGP-LS address family to advertise the FAD
as a part of the topology information from the network.
This document is a product of the Inter-Domain Routing 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