*****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-rfc10032 Please do the following: a) accept your invitations to join the repo as collaborators. Note that we sent invitations to both authors. We can also send an invitation to the document shepherd (Stanislav Smyshlyaev) if provided with a GitHub username. b) see the README for details on the Final Review process: https://github.com/rfc-editor-drafts/FinalReview-rfc10032/blob/Approved/README.md c) review the edits in the RPC-edits pull request: https://github.com/rfc-editor-drafts/FinalReview-rfc10032/pulls d) address the issues: https://github.com/rfc-editor-drafts/FinalReview-rfc10032/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/rfc10032/ 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]
