Authors and AD*, While reviewing this document during AUTH48, please resolve (as necessary) the following questions, which are also in the XML file.
*AD, please see question #7 below. 1) <!-- [rfced] We note that most of the recently published RFCs containing YANG modules format their titles as "A YANG Data Model for...", for example: RFC 9094 - A YANG Data Model for Wavelength Switched Optical Networks (WSONs) RFC 9093 - A YANG Data Model for Layer 0 Types RFC 9067 - A YANG Data Model for Routing Policy Please consider whether the title of this document should be updated. Current: Extensions to OSPF for Advertising Prefix Administrative Tags Perhaps: A Yang Data Model for Extensions to OSPF for Advertising Prefix Administrative Tags --> 2) <!-- [rfced] Please insert any keywords (beyond those that appear in the title) for use on https://www.rfc-editor.org/search. --> 3) <!-- [rfced] FYI - We updated "OSPFv2 Extended Prefix LSA" to "OSPFv2 Extended Prefix Opaque LSA" to match RFC 7684. Please let us know of any objections. --> 4) <!-- [rfced] FYI - We have added line breaks to the YANG tree diagram as well as a note and reference to RFC 8792 for the '\' line wrapping. Please review. --> 5) <!--[rfced] FYI - As the RFC 2119 and RFC 8174 keywords are not used within the YANG module, we have removed the keywords boilerplate paragraph from the module. --> 6) <!--[rfced] Note that the YANG module has been updated per the formatting option of pyang. Please let us know of any concerns. --> 7) <!--[rfced] *AD - We note that the first paragraph in the Security Considerations section does not match what appears at <https://wiki.ietf.org/group/ops/yang-security-guidelines>. Additionally, we have made some updates in this section to closer reflect the boilerplate. Please review this section and let us know if any further updates are necessary. --> 8) <!-- [rfced] Throughout the text, the following terminology appears to be used interchangeably. Please review these occurrences and let us know if/how they may be made consistent. Administrative Tag vs. admin tag vs. administrative tag Administrative Tag sub-TLV vs. Administrative Tag TLV vs. administrative tag TLV E-Inter-Area-Prefix-LSA vs. E-Inter-Area-Prefix LSA E-Intra-Area-Prefix-LSA vs. E-Intra-Area-Prefix LSA Extended Prefix TLV vs. extended prefix TLV Prefix Administrative Tag sub-TLV vs. prefix admin tag sub-TLV --> 9) <!-- [rfced] FYI - We have added expansions for the following abbreviations per Section 3.6 of RFC 7322 ("RFC Style Guide"). Please review each expansion in the document carefully to ensure correctness. Border Gateway Protocol - Link State (BGP-LS) Network Configuration Protocol (NETCONF) --> 10) <!-- [rfced] Please review the "Inclusive Language" portion of the online Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language> and let us know if any changes are needed. Updates of this nature typically result in more precise language, which is helpful for readers. Note that our script did not flag any words in particular, but this should still be reviewed as a best practice. --> Thank you. RFC Editor/st/ap On Jul 17, 2025, at 2:09 PM, rfc-edi...@rfc-editor.org wrote: *****IMPORTANT***** Updated 2025/07/17 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://www.rfc-editor.org/faq/). 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://trustee.ietf.org/license-info). * 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://authors.ietf.org/rfcxml-vocabulary>. * 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 * rfc-edi...@rfc-editor.org (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). * auth48archive@rfc-editor.org, which is a new archival mailing list to preserve AUTH48 conversations; it is not an active discussion list: * More info: https://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc * The archive itself: https://mailarchive.ietf.org/arch/browse/auth48archive/ * 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, auth48archive@rfc-editor.org 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://www.rfc-editor.org/authors/rfc9825.xml https://www.rfc-editor.org/authors/rfc9825.html https://www.rfc-editor.org/authors/rfc9825.pdf https://www.rfc-editor.org/authors/rfc9825.txt Diff file of the text: https://www.rfc-editor.org/authors/rfc9825-diff.html https://www.rfc-editor.org/authors/rfc9825-rfcdiff.html (side by side) Diff of the XML: https://www.rfc-editor.org/authors/rfc9825-xmldiff1.html Tracking progress ----------------- The details of the AUTH48 status of your document are here: https://www.rfc-editor.org/auth48/rfc9825 Please let us know if you have any questions. Thank you for your cooperation, RFC Editor -------------------------------------- RFC9825 (draft-ietf-lsr-ospf-admin-tags-29) Title : Extensions to OSPF for Advertising Prefix Administrative Tags Author(s) : A. Lindem, Ed., P. Psenak, Y. Qu WG Chair(s) : Acee Lindem, Christian Hopps, Yingzhen Qu Area Director(s) : Jim Guichard, Ketan Talaulikar, Gunter Van de Velde -- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
