[Idr] RFC 9514 on Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6)
rfc-editor@rfc-editor.org Wed, 06 December 2023 00:39 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 DE18AC14CEE3; Tue, 5 Dec 2023 16:39:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level:
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 f_AcofYWsYMK; Tue, 5 Dec 2023 16:39:01 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [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 C4DB1C14CE2C; Tue, 5 Dec 2023 16:37:02 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id B89E6AB8AC; Tue, 5 Dec 2023 16:37:02 -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: <20231206003702.B89E6AB8AC@rfcpa.amsl.com>
Date: Tue, 05 Dec 2023 16:37:02 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Ax9xiLdXjkIQ8TlebFCBjb0Mh9o>
Subject: [Idr] RFC 9514 on Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6)
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, 06 Dec 2023 00:39:06 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9514
Title: Border Gateway Protocol - Link
State (BGP-LS) Extensions for Segment Routing
over IPv6 (SRv6)
Author: G. Dawra,
C. Filsfils,
K. Talaulikar, Ed.,
M. Chen,
D. Bernier,
B. Decraene
Status: Standards Track
Stream: IETF
Date: December 2023
Mailbox: gdawra.ietf@gmail.com,
cfilsfil@cisco.com,
ketant.ietf@gmail.com,
mach.chen@huawei.com,
daniel.bernier@bell.ca,
bruno.decraene@orange.com
Pages: 23
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-idr-bgpls-srv6-ext-14.txt
URL: https://www.rfc-editor.org/info/rfc9514
DOI: 10.17487/RFC9514
Segment Routing over IPv6 (SRv6) allows for a flexible definition of
end-to-end paths within various topologies by encoding paths as
sequences of topological or functional sub-paths called "segments".
These segments are advertised by various protocols such as BGP,
IS-IS, and OSPFv3.
This document defines extensions to BGP - Link State (BGP-LS) to
advertise SRv6 segments along with their behaviors and other
attributes via BGP. The BGP-LS address-family solution for SRv6
described in this document is similar to BGP-LS for SR for the MPLS
data plane, which is defined in RFC 9085.
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