Hi! Thank you for your edit work. I approve publication.
Kind regards, Job > On 13 May 2026, at 01:30, Megan Ferguson <[email protected]> > wrote: > > Hi Tom, > > Thanks for your prompt response. We have updated the document as suggested > and updated our database to include your recommended keywords as well as > Job’s new email address (also CC’d on this message). > > Your message seemed to indicate that you approved of the document in this > form, so we have updated your status to “Approved” at the AUTH48 status page > (see link below). (If this is in error, please let us know.) We will assume > your approval stands even if coauthors submit changes unless we hear > otherwise at that time. Once we have approvals from each party listed at the > AUTH48 status page, we will be ready to move the document forward in the > publication process. > > Note that we do not make changes once a document is published as an RFC, so > please review carefully. > > The files have been posted here (please refresh): > https://www.rfc-editor.org/authors/rfc9981.txt > https://www.rfc-editor.org/authors/rfc9981.pdf > https://www.rfc-editor.org/authors/rfc9981.html > https://www.rfc-editor.org/authors/rfc9981.xml > > The diff files have been posted here (please refresh): > https://www.rfc-editor.org/authors/rfc9981-diff.html (comprehensive) > https://www.rfc-editor.org/authors/rfc9981-rfcdiff.html (side by side) > > https://www.rfc-editor.org/authors/rfc9981-auth48diff.html (AUTH48 changes > only) > https://www.rfc-editor.org/authors/rfc9981-auth48rfcdiff.html (side by side) > > The AUTH48 status page is available here: > https://www.rfc-editor.org/auth48/rfc9981 > > Thank you. > > Megan Ferguson > RFC Production Center > >> On May 12, 2026, at 2:10 PM, Tom Harrison <[email protected]> wrote: >> >> Hi Megan, >> >> Thanks for your work on this document. >> >>> On Fri, May 08, 2026 at 07:42:58PM -0700, [email protected] wrote: >>> 1) <!-- [rfced] Please insert any keywords (beyond those that appear >>> in the title) for use on https://www.rfc-editor.org/search. --> >> >> RPKI >> Routing Security >> X.509 >> >>> 2) <!-- [rfced] Please review the Acknowledgments for mention of >>> Ines Robles. We see a "Maria Ines Robles" as an author of >>> RFC 9008. Perhaps these names should be made uniform. --> >> >> I had a look through previous acknowledgments sections that referred >> to her, and they varied as to the form used, so I asked her about this >> directly, and she said she would prefer "Maria Ines Robles". >> >>> 3) <!-- [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. >> >> I've reviewed the document per the above, and can't see any other >> changes that are needed. >> >>> * 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 >> >> Just one change, in "Authors' Addresses": >> >> OLD: >> >> <author fullname="Job Snijders" initials="J." surname="Snijders"> >> <organization/> >> <address> >> <postal> >> <city>Amsterdam</city> >> <country>Netherlands</country> >> </postal> >> <email>[email protected]</email> >> </address> >> </author> >> >> NEW: >> >> <author fullname="Job Snijders" initials="J." surname="Snijders"> >> <organization abbrev="BSD">BSD Software Development</organization> >> <address> >> <postal> >> <postalLine>Amsterdam</postalLine> >> <postalLine>The Netherlands</postalLine> >> </postal> >> <email>[email protected]</email> >> <uri>https://www.bsd.nl</uri> >> </address> >> </author> >> >>> * 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. >> >> Each of the above points is fine, thanks. >> >> -Tom >> > -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
