RFC 9929 on IGP Unreachable Prefix Announcement
rfc-editor@rfc-editor.org Fri, 27 February 2026 23:13 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@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 DAEC4C002048; Fri, 27 Feb 2026 15:13:44 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id CAD67C000CC4; Fri, 27 Feb 2026 15:13:44 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9929 on IGP Unreachable Prefix Announcement
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20260227231344.CAD67C000CC4@rfcpa.rfc-editor.org>
Date: Fri, 27 Feb 2026 15:13:44 -0800
Message-ID-Hash: HDOTDG3D63L2TS5PPH6IFHHHXCBMXLLK
X-Message-ID-Hash: HDOTDG3D63L2TS5PPH6IFHHHXCBMXLLK
X-MailFrom: wwwrun@rfcpa.rfc-editor.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: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, lsr@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/ciSoSvKflY8p3S_ZkR5aWxSuT9U>
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>
A new Request for Comments is now available in online RFC libraries.
RFC 9929
Title: IGP Unreachable Prefix Announcement
Author: P. Psenak, Ed.,
C. Filsfils,
D. Voyer,
S. Hegde,
G. Mishra
Status: Standards Track
Stream: IETF
Date: February 2026
Mailbox: ppsenak@cisco.com,
cfilsfil@cisco.com,
davoyer@cisco.com,
shraddha.hegde@hpe.com,
hayabusagsm@gmail.com
Pages: 14
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-lsr-igp-ureach-prefix-announce-11.txt
URL: https://www.rfc-editor.org/info/rfc9929
DOI: 10.17487/RFC9929
Summarization is often used in multi-area or multi-domain networks to
improve network efficiency and scalability. With summarization in
place, there is a need to signal loss of reachability to an
individual prefix covered by the summary. This enables fast
convergence by steering traffic, when applicable, away from the node
which owns the prefix and is no longer reachable.
This document specifies protocol mechanisms in IS-IS and OSPF,
together with two new flags, to advertise such prefix reachability
loss.
The term "OSPF" in this document is used to refer to both OSPFv2 and
OSPFv3.
This document is a product of the Link State 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