Looks good, approved from my side! Tommy
> On Aug 10, 2026, at 6:23 PM, Martin Thomson <[email protected]> wrote: > > LGTM, thanks! > > On Tue, Aug 11, 2026, at 04:31, Rebecca VanRheenen wrote: >> Hello authors, >> >> We have merged the updates and converted the kramdown-rfc file to RFCXML. >> >> Please review the XML file and its TXT, HTML, and PDF outputs, and let >> us know if any changes are required or if you approve the RFC for >> publication. We consider this your final assent that the document is >> ready for publication. To request changes or approve your RFC for >> publication, please reply to this email. Please use ‘REPLY ALL’, as all >> the parties CCed on this message need to see your approval. >> >> Notes: >> >> 1) We made two small updates: fixed typo in the Acknowledgments section >> and updated “is” to “has been” in the second paragraph of the IANA >> Considerations section (to align with similar text in the previous >> paragraph). >> >> 2) We will only make changes in the XML file from this point on. >> >> >> XML file: >> https://www.rfc-editor.org/authors/rfc10036.xml >> >> Output files: >> https://www.rfc-editor.org/authors/rfc10036.txt >> https://www.rfc-editor.org/authors/rfc10036.pdf >> https://www.rfc-editor.org/authors/rfc10036.html >> >> Comprehensive diff file of the text: >> https://www.rfc-editor.org/authors/rfc10036-diff.html >> https://www.rfc-editor.org/authors/rfc10036-rfcdiff.html (side by side) >> >> For the Final Review status of this document, please see: >> https://queue.rfc-editor.org/final-review/rfc10036 >> >> Thank you, >> >> Rebecca VanRheenen >> RFC Production Center >> >> >> >>> On Aug 6, 2026, at 5:37 PM, [email protected] wrote: >>> >>> *****IMPORTANT***** >>> >>> RFC Author(s): >>> -------------- >>> >>> Your document has now entered Final Review (previously AUTH48). >>> >>> The document was edited in kramdown-rfc as part of the RPC pilot test (see >>> https://www.rfc-editor.org/rpc/wiki/doku.php?id=pilot_test_kramdown_rfc). >>> >>> Final Review is being handled in GitHub as part of the GitHub pilot test >>> (see >>> https://www.rfc-editor.org/rpc/wiki/doku.php?id=rpc-github-phase-0-pilot-test). >>> >>> Your document is available for review at: >>> https://github.com/rfc-editor-drafts/FinalReview-rfc10036 >>> >>> Please do the following: >>> >>> a) accept your invitations to join the repo as collaborators. >>> >>> b) see the README for details on the Final Review process: >>> https://github.com/rfc-editor-drafts/FinalReview-rfc10036/blob/Approved/README.md >>> >>> c) review the edits in the RPC-edits pull request: >>> https://github.com/rfc-editor-drafts/FinalReview-rfc10036/pulls >>> >>> In particular, we recommend reviewing the diffs in the md file: >>> https://github.com/rfc-editor-drafts/FinalReview-rfc10036/pull/1/changes#diff-3512a1a99f77536ee6703d499677d0f2e932ad49498e46fcac6bde88313f32f1 >>> >>> >>> d) address the issues: >>> https://github.com/rfc-editor-drafts/FinalReview-rfc10036/issues >>> >>> Once the content of the .md file is stable, we will convert it to .xml >>> and provide the .html, .pdf, .txt, and .xml files for review. >>> >>> You and your coauthors are responsible for engaging other parties >>> (e.g., Contributors or Working Group) as necessary before providing >>> your approval. >>> >>> Once the document has been reviewed and approved by all of the authors, >>> it will be published as an RFC. If an author is no longer available, >>> there are several remedies; see the Unavailable Authors section >>> (https://authors.ietf.org/rfc-publication-process#unavailable-authors). >>> >>> Details on the status of your Final Review are here: >>> https://queue.rfc-editor.org/final-review/rfc10036/ >>> >>> Please let us know if you have any questions. >>> >>> Thank you for your cooperation, >>> >>> RFC Production Center >>> -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
