Hi Mark, We have marked your approval on the Final Review status page for this document; see https://queue.rfc-editor.org/final-review/rfc9998/.
Once we receive approval from Martin, we can move this document forward in the publication process. Also, that gif is great! Thank you, Rebecca VanRheenen RFC Production Center > On Jun 7, 2026, at 3:04 PM, Mark Nottingham <[email protected]> wrote: > > I think it's ready to go. > > <jodie-foster-contact-2520879837.gif> > > > Cheers, > > > > >> On 5 Jun 2026, at 4:59 am, Rebecca VanRheenen >> <[email protected]> wrote: >> >> Hello Martin and Mark >> >> 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. >> >> Note that we will only make changes in the XML file from this point on. >> >> XML file: >> https://www.rfc-editor.org/authors/rfc9998.xml >> >> Output files: >> https://www.rfc-editor.org/authors/rfc9998.txt >> https://www.rfc-editor.org/authors/rfc9998.html >> https://www.rfc-editor.org/authors/rfc9998.pdf >> >> Comprehensive diff file of the text: >> https://www.rfc-editor.org/authors/rfc9998-diff.html >> https://www.rfc-editor.org/authors/rfc9998-rfcdiff.html (side by side) >> >> For the Final Review status of this document, please see: >> https://queue.rfc-editor.org/final-review/rfc9998 >> (Note: I will update this link to include the current status after a >> database upgrade that should complete in a few hours.) >> >> Thank you, >> >> Rebecca VanRheenen >> RFC Production Center >> >> >>> On Jun 1, 2026, at 7:55 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/FinalReview-rfc9998 >>> >>> 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/FinalReview-rfc9998/blob/Approved/README.md >>> >>> c) review and resolve the issues: >>> https://github.com/rfc-editor/FinalReview-rfc9998/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 >>> >>> >>> -------------------------------------- >>> RFC 9998 (draft-iab-agews-report) >>> >>> Title : Report from the IAB/W3C Workshop on Age-Based >>> Restrictions on Content Access >>> Author(s) : M. Nottingham, >>> M. Thomson >>> WG Chair(s) : Dhruv Dhody >>> Area Director(s) : N/A >>> >> > > -- > Mark Nottingham https://www.mnot.net/ > -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
