Last Call: <draft-ietf-pim-mofrr-tilfa-09.txt> (Multicast-only Fast Reroute Based on Topology Independent Loop-free Alternate Fast Reroute) to Informational RFC
The IESG <iesg-secretary@ietf.org> Tue, 04 February 2025 15:59 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from mail.ietf.org (ietfa.amsl.com [50.223.129.194]) (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 ietfa.amsl.com (Postfix) with ESMTPSA id 467A4C180B7C; Tue, 4 Feb 2025 07:59:35 -0800 (PST)
Received: from [10.244.8.188] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id C176DC180B61; Tue, 4 Feb 2025 07:59:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-pim-mofrr-tilfa-09.txt> (Multicast-only Fast Reroute Based on Topology Independent Loop-free Alternate Fast Reroute) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 12.34.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <173868477437.287792.6344255395872068825@dt-datatracker-6f7f8bdd64-25rl2>
Date: Tue, 04 Feb 2025 07:59:34 -0800
Message-ID-Hash: LD6TJGE5YPAIGBEZPFAE32MAB6YQPVZ7
X-Message-ID-Hash: LD6TJGE5YPAIGBEZPFAE32MAB6YQPVZ7
X-MailFrom: iesg-secretary@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-pim-mofrr-tilfa@ietf.org, gunter@vandevelde.cc, pim-chairs@ietf.org, pim@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: last-call@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/JC0wcAbq95CCSxt1xEPncZ-GHow>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
The IESG has received a request from the Protocols for IP Multicast WG (pim) to consider the following document: - 'Multicast-only Fast Reroute Based on Topology Independent Loop-free Alternate Fast Reroute' <draft-ietf-pim-mofrr-tilfa-09.txt> as Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the last-call@ietf.org mailing lists by 2025-02-18. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document specifies the use of Topology Independent Loop-Free Alternate (TI-LFA) mechanisms with Multicast Only Fast ReRoute (MoFRR) for Protocol Independent Multicast (PIM). The TI-LFA mechanism is designed for standard link-state Interior Gateway Protocol (IGP) shortest path and Segment Routing (SR) scenarios. TI- LFA provides fast reroute protection for unicast traffic in IP networks by precomputing backup paths that avoid potential failures. By integrating TI-LFA with MoFRR, this document extends the benefits of fast reroute mechanisms to multicast traffic, enabling enhanced resilience and minimized packet loss in multicast networks. The document outlines the necessary protocol extensions and operational considerations to implement TI-LFA in conjunction with MoFRR for PIM, ensuring that multicast traffic is rapidly rerouted in the event of a failure. This document uses the backup path computed by TI-LFA through IGP as a secondary Upstream Multicast Hop (UMH) for PIM. By using the TI-LFA backup path to send PIM secondary join messages hop- by-hop, it achieves the generation of a fast reroute backup path for PIM multicast. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-pim-mofrr-tilfa/ The following IPR Declarations may be related to this I-D: https://datatracker.ietf.org/ipr/5730/