*****IMPORTANT***** Updated 2026/05/21
RFC Author(s): -------------- Your document has now entered Final Review (formerly called 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/AUTH48-rfc9988 Please do the following: a) accept your invitations to join the repo as collaborators. Henk, please provide your GitHub username so we can send you an invite; we already sent an invite to Carsten. b) see the README for details on the Final Review process: https://github.com/rfc-editor/AUTH48-rfc9988/blob/Approved/README.md c) review and resolve the issues: https://github.com/rfc-editor/AUTH48-rfc9988/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 available as listed in the FAQ (https://www.rfc-editor.org/faq/). Please let us know if you have any questions. Thank you for your cooperation, RFC Editor -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
