Hi Authors, Jim - Thank you for your comments! I updated the "RPC edits to initiate Final Review" PR accordingly.
As of right now, all of the issues have been addressed aside from #7 and #8, which is inclusive language and RFCXML conversion, respectively. Since our script did not flag any words for inclusive language, no updates are needed here (this was mostly posted as an FYI). Once this is confirmed on your end, we can close issue #7 [1]. At that point, issue #8 [2] only needs one author to comment when all changes shown in the RPC edits PR are okay to merge. At that point, we will convert the file to RFCXML, complete formatting updates on our end, send updated files, and gather all author approvals before proceeding with publication. [1]: https://github.com/rfc-editor-drafts/FinalReview-rfc10033/issues/7 [2]: https://github.com/rfc-editor-drafts/FinalReview-rfc10033/issues/8 Thank you! Madison Church RFC Production Center > On Aug 13, 2026, at 12:38 PM, <[email protected]> <[email protected]> wrote: > > Hello everyone, > > I've gone through and reviewed the issues and am fine > with all of the suggested changes, leaving just a review > for inclusive language outstanding. Based on my quick > re-read of the document I think we're fine on that > front as well but will defer to my other authors who > may have more time to do a more thorough review. > > Take care. > > Jim > > -----Original Message----- > From: Kaveh Bashiri <[email protected]> > Sent: August 13, 2026 1:26 PM > To: Thom Wiggers <[email protected]> > Cc: Madison Church <[email protected]>; Stefan Kölbl > <[email protected]>; Jim Goodman <[email protected]>; Stavros Kousidis > <[email protected]>; Editor RFC <[email protected]>; > [email protected]; [email protected]; > [email protected]; [email protected]; Paul Hoffman > <[email protected]>; [email protected] > Subject: Re: Final Review: RFC-to-be 10033 (draft-ietf-pquip-hbs-state) in > markdown/GitHub > > Dear all, > > I have exactly the same situation and opinion as Thom. Would that be enough > for the process to proceed? > > Best wishes, > Kaveh > > Am 13.08.2026 um 17:52 schrieb Thom Wiggers <[email protected]>: > > Dear Madison, everyone, > > Thanks for the reminder. I very quickly reviewed your suggestions and I don’t > have strong opinions. I’m (almost) on leave so I’m afraid that a more > detailed look would have to wait but if some of my co-authors are willing to > chime in with opinions either way then I will defer to the wisdom of the > collective. > > Cheers, > > Thom > > >> Op 13 aug 2026, om 16:15 heeft Madison Church <[email protected]> >> het volgende geschreven: >> >> Hi Authors, >> >> This is a friendly weekly reminder that we await your response to the issues >> documented here: https://github.com/rfc-editor-drafts/FinalReview-rfc10033. >> Please review the issues using the process instructions listed below and let >> us know if you have any questions. >> >> Thank you! >> Madison Church >> RFC Production Center >> >>> On Aug 6, 2026, at 1:43 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-rfc10033 >>> >>> 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-rfc10033/blob/Approv >>> ed/README.md >>> >>> c) review the edits in the RPC-edits pull request: >>> https://github.com/rfc-editor-drafts/FinalReview-rfc10033/pulls >>> >>> d) address the issues: >>> https://github.com/rfc-editor-drafts/FinalReview-rfc10033/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/rfc10033/ >>> >>> Please let us know if you have any questions. >>> >>> Thank you for your cooperation, >>> >>> Madison Church and Alice Russo >>> RFC Production Center >>> >> > -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
