[rtgwg] RFC 9855 on Topology Independent Fast Reroute Using Segment Routing
rfc-editor@rfc-editor.org Wed, 29 October 2025 05:24 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: rtgwg@ietf.org
Delivered-To: rtgwg@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 904507DD2A01; Tue, 28 Oct 2025 22:24:12 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 5AB5FC000BCA; Tue, 28 Oct 2025 22:24:12 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20251029052412.5AB5FC000BCA@rfcpa.rfc-editor.org>
Date: Tue, 28 Oct 2025 22:24:12 -0700
Message-ID-Hash: 3DLXN6H4KQTJXXD7CP3KFXFZ6D62HLBE
X-Message-ID-Hash: 3DLXN6H4KQTJXXD7CP3KFXFZ6D62HLBE
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-rtgwg.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rtgwg@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [rtgwg] RFC 9855 on Topology Independent Fast Reroute Using Segment Routing
List-Id: Routing Area Working Group <rtgwg.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/_Cuz94tF-y29FNNoU0mUC_RqjTw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Owner: <mailto:rtgwg-owner@ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Subscribe: <mailto:rtgwg-join@ietf.org>
List-Unsubscribe: <mailto:rtgwg-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9855
Title: Topology Independent Fast Reroute Using
Segment Routing
Author: A. Bashandy,
S. Litkowski,
C. Filsfils,
P. Francois,
B. Decraene,
D. Voyer
Status: Standards Track
Stream: IETF
Date: October 2025
Mailbox: abashandy.ietf@gmail.com,
slitkows@cisco.com,
cfilsfil@cisco.com,
pierre.francois@insa-lyon.fr,
bruno.decraene@orange.com,
daniel.voyer@bell.ca
Pages: 23
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-rtgwg-segment-routing-ti-lfa-21.txt
URL: https://www.rfc-editor.org/info/rfc9855
DOI: 10.17487/RFC9855
This document presents Topology Independent Loop-Free Alternate
(TI-LFA) Fast Reroute (FRR), which is aimed at providing protection
of node and Adjacency segments within the Segment Routing (SR)
framework. This FRR behavior builds on proven IP FRR concepts being
LFAs, Remote LFAs (RLFAs), and Directed Loop-Free Alternates (DLFAs).
It extends these concepts to provide guaranteed coverage in any
two-connected networks using a link-state IGP. An important aspect of
TI-LFA is the FRR path selection approach establishing protection
over the expected post-convergence paths from the Point of Local
Repair (PLR), reducing the operational need to control the tie-breaks
among various FRR options.
This document is a product of the Routing Area Working Group 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