Begin forwarded message:
From: [email protected]
Subject: AUTH48: RFC-to-be 9929
<draft-ietf-lsr-igp-ureach-prefix-announce-11> for your review
Date: February 16, 2026 at 4:28:08 PM PST
To: [email protected], [email protected], [email protected],
[email protected], [email protected]
Cc: [email protected], [email protected], [email protected],
[email protected], [email protected],
[email protected]
*****IMPORTANT*****
Updated 2026/02/16
RFC Author(s):
--------------
Instructions for Completing AUTH48
Your document has now entered AUTH48. Once it has been reviewed and
approved by you and all coauthors, it will be published as an RFC.
If an author is no longer available, there are several remedies
available as listed in the FAQ
(https://urldefense.com/v3/__https://www.rfc-editor.org/faq/__;!!NpxR!kUe9vZ5eEJZ-xcMBPIlkPDUu84G4rddQJUovgr0YdlTue7o4WkxjGygOR7FUsiSLsOrAlLuRJS-2uak82vs$
).
You and you coauthors are responsible for engaging other parties
(e.g., Contributors or Working Group) as necessary before providing
your approval.
Planning your review
---------------------
Please review the following aspects of your document:
* RFC Editor questions
Please review and resolve any questions raised by the RFC Editor
that have been included in the XML file as comments marked as
follows:
<!-- [rfced] ... -->
These questions will also be sent in a subsequent email.
* Changes submitted by coauthors
Please ensure that you review any changes submitted by your
coauthors. We assume that if you do not speak up that you agree to
changes submitted by your coauthors.
* Content
Please review the full content of the document, as this cannot
change once the RFC is published. Please pay particular attention to:
- IANA considerations updates (if applicable)
- contact information
- references
* Copyright notices and legends
Please review the copyright notice and legends as defined in RFC
5378 and the Trust Legal Provisions (TLP –
https://urldefense.com/v3/__https://trustee.ietf.org/license-info__;!!NpxR!kUe9vZ5eEJZ-xcMBPIlkPDUu84G4rddQJUovgr0YdlTue7o4WkxjGygOR7FUsiSLsOrAlLuRJS-2kV3eNVk$
).
* Semantic markup
Please review the markup in the XML file to ensure that elements of
content are correctly tagged. For example, ensure that <sourcecode>
and <artwork> are set correctly. See details at
<https://urldefense.com/v3/__https://authors.ietf.org/rfcxml-vocabulary__;!!NpxR!kUe9vZ5eEJZ-xcMBPIlkPDUu84G4rddQJUovgr0YdlTue7o4WkxjGygOR7FUsiSLsOrAlLuRJS-2e_CgA54$
>.
* Formatted output
Please review the PDF, HTML, and TXT files to ensure that the
formatted output, as generated from the markup in the XML file, is
reasonable. Please note that the TXT will have formatting
limitations compared to the PDF and HTML.
Submitting changes
------------------
To submit changes, please reply to this email using ‘REPLY ALL’ as
all the parties CCed on this message need to see your changes. The
parties
include:
* your coauthors
* [email protected] (the RPC team)
* other document participants, depending on the stream (e.g.,
IETF Stream participants are your working group chairs, the
responsible ADs, and the document shepherd).
* [email protected], which is a new archival mailing list
to preserve AUTH48 conversations; it is not an active discussion
list:
* More info:
https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/iet
f-announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc__;!!NpxR!kUe9vZ5eEJZ-xcMBPIlkP
DUu84G4rddQJUovgr0YdlTue7o4WkxjGygOR7FUsiSLsOrAlLuRJS-2mcX7YfI$
* The archive itself:
https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/browse/
auth48archive/__;!!NpxR!kUe9vZ5eEJZ-xcMBPIlkPDUu84G4rddQJUovgr0YdlTue
7o4WkxjGygOR7FUsiSLsOrAlLuRJS-2x1Arw8w$
* Note: If only absolutely necessary, you may temporarily opt out
of the archiving of messages (e.g., to discuss a sensitive matter).
If needed, please add a note at the top of the message that you
have dropped the address. When the discussion is concluded,
[email protected] will be re-added to the CC list and
its addition will be noted at the top of the message.
You may submit your changes in one of two ways:
An update to the provided XML file
— OR —
An explicit list of changes in this format
Section # (or indicate Global)
OLD:
old text
NEW:
new text
You do not need to reply with both an updated XML file and an
explicit list of changes, as either form is sufficient.
We will ask a stream manager to review and approve any changes that
seem beyond editorial in nature, e.g., addition of new text, deletion
of text, and technical changes. Information about stream managers
can be found in the FAQ. Editorial changes do not require approval from a
stream manager.
Approving for publication
--------------------------
To approve your RFC for publication, please reply to this email
stating that you approve this RFC for publication. Please use ‘REPLY
ALL’, as all the parties CCed on this message need to see your approval.
Files
-----
The files are available here:
https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc992
9.xml__;!!NpxR!kUe9vZ5eEJZ-xcMBPIlkPDUu84G4rddQJUovgr0YdlTue7o4WkxjGy
gOR7FUsiSLsOrAlLuRJS-2Y9OO7xg$
https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc992
9.html__;!!NpxR!kUe9vZ5eEJZ-xcMBPIlkPDUu84G4rddQJUovgr0YdlTue7o4WkxjG
ygOR7FUsiSLsOrAlLuRJS-2LM81rA4$
https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc992
9.pdf__;!!NpxR!kUe9vZ5eEJZ-xcMBPIlkPDUu84G4rddQJUovgr0YdlTue7o4WkxjGy
gOR7FUsiSLsOrAlLuRJS-21Zc9Pd0$
https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc992
9.txt__;!!NpxR!kUe9vZ5eEJZ-xcMBPIlkPDUu84G4rddQJUovgr0YdlTue7o4WkxjGy
gOR7FUsiSLsOrAlLuRJS-2R7ha60I$
Diff file of the text:
https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc992
9-diff.html__;!!NpxR!kUe9vZ5eEJZ-xcMBPIlkPDUu84G4rddQJUovgr0YdlTue7o4
WkxjGygOR7FUsiSLsOrAlLuRJS-22oeYZm4$
https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc992
9-rfcdiff.html__;!!NpxR!kUe9vZ5eEJZ-xcMBPIlkPDUu84G4rddQJUovgr0YdlTue
7o4WkxjGygOR7FUsiSLsOrAlLuRJS-2no9HyKE$ (side by side)
Diff of the XML:
https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc992
9-xmldiff1.html__;!!NpxR!kUe9vZ5eEJZ-xcMBPIlkPDUu84G4rddQJUovgr0YdlTu
e7o4WkxjGygOR7FUsiSLsOrAlLuRJS-2_xABOQo$
Tracking progress
-----------------
The details of the AUTH48 status of your document are here:
https://urldefense.com/v3/__https://www.rfc-editor.org/auth48/rfc9929
__;!!NpxR!kUe9vZ5eEJZ-xcMBPIlkPDUu84G4rddQJUovgr0YdlTue7o4WkxjGygOR7F
UsiSLsOrAlLuRJS-2ohYmvIQ$
Please let us know if you have any questions.
Thank you for your cooperation,
RFC Editor
--------------------------------------
RFC9929 (draft-ietf-lsr-igp-ureach-prefix-announce-11)
Title : IGP Unreachable Prefix Announcement
Author(s) : P. Psenak, Ed., C. Filsfils, D. Voyer, S. Hegde, G. Mishra
WG Chair(s) : Acee Lindem, Christian Hopps, Yingzhen Qu
Area Director(s) : Jim Guichard, Ketan Talaulikar, Gunter Van de
Velde
