Hello authors, Please reply with your GitHub usernames so that we can add you as collaborations to the GitHub repo. Of the five authors, we only have a GitHub username for Mahesh.
We can also add the Document Shepherd and WG Chairs (Reshad Rahman and Jeffrey Haas) if they provide GitHub usernames. We have already added Mahesh (author), Ketan (AD), and the editors who will be working with you during AUTH48. Also, please make sure to review the README for details on this pilot AUTH48 process: https://github.com/rfc-editor/AUTH48-rfc9978/blob/Approved/README.md Let us know if you have any questions, and thank you for participating in the GitHub pilot for AUTH48! Best regards, Rebecca VanRheenen RFC Production Center > On May 11, 2026, at 2:23 PM, [email protected] wrote: > > Please disregard the previous AUTH48 message. This message contains the > correct information for the GitHub pilot test for AUTH48. > > Note that the previous message containing the questions is correct, but the > questions also appear as issues at > https://github.com/rfc-editor/AUTH48-rfc9978/issues. > > > *****IMPORTANT***** > > Updated 2026/05/11 > > RFC Author(s): > -------------- > > Your document has now entered AUTH48. > > AUTH48 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-rfc9978 > > Please see the README for details on the AUTH48 process: > https://github.com/rfc-editor/AUTH48-rfc9978/blob/Approved/README.md > > Please review and resolve the issues: > https://github.com/rfc-editor/AUTH48-rfc9978/issues > > Once the content is stable in GitHub, we will provide the updated XML file > and the output files for review and approval. The final approvals will be > handled via email. > > 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]
