Hi Kris, That is correct! The RFC Editor will work with version -04, and then once the editing is done, you and your coauthors will receive the AUTH48 email where you will review the suggested updates.
For a more in-depth explanation of what the AUTH48 process looks like, see https://www.rfc-editor.org/pubprocess/auth48/. If we have any questions before AUTH48, we'll reach out. But, in the meantime, we have everything we need. Thank you, Sarah Tarrant RFC Production Center > On Feb 27, 2026, at 2:28 AM, Kris Kwiatkowski <[email protected]> wrote: > > Hi Sarah, > > I just wanted to make sure if there is something else we need to do for the > draft > to smoothly go thru the RFC queue? My understanding is that from now on RFC > editor > will take care of the draft and will apply any changes on top of -04 version > if > needed. > Please let me know if I'm wrong or if there is anything else we can do to > help. It > is my first RFC, so I'm not 100% sure how the process works (in practice). > > Kind regards, > Kris > On 2/13/26 21:55, Kris Kwiatkowski wrote: >> Hello RPC Team, >> >> Thank you for contacting us. Please find the answers to all the questions >> below and let us >> know in case anything more is needed. >> >> > 1) As there may have been multiple updates made to the document during >> > Last Call, >> > please review the current version of the document: >> > * Is the text in the Abstract still accurate? >> >> Yes, the abstract was recently updated and it is accurate. >> >> > * Are the Authors' Addresses, Contributors, and Acknowledgments >> > sections current? >> We would like to change the name of one of the authors from >> "Kris Kwiatkowski" to "Krzysztof Kwiatkowski" (change of the first name) >> >> >> > 2) Please share any style information that could help us with editing your >> > document. For example: >> >> The document is based on the other document in the same cluster, namely the >> draft-ietf-tls-hybrid-design-16. I believe both documents match the style. >> >> > 3) Please carefully review the entries and their URLs in the >> > References section with the following in mind. Note that we will >> > update as follows unless we hear otherwise at this time: >> >> > * References to obsoleted RFCs will be updated to point to the current >> > RFC on the topic in accordance with Section 4.8.6 of RFC 7322 >> > (RFC Style Guide). >> >> * The document uses reference [hybrid] to refer to the >> draft-ietf-tls-hybrid-design-16. We will need to change >> it to the RFC number once [hybrid] gets RFC assigned. >> >> > * References to I-Ds that have been replaced by another I-D will be >> > updated to point to the replacement I-D. >> > >> > * References to documents from other organizations that have been >> > superseded will be updated to their superseding version. >> >> Checked. Nothing to comment on. >> >> > 4) Is there any text that requires special handling? For example: >> > *Are there any sections that were contentious when the document was >> > drafted? >> > *Are any sections that need to be removed before publication marked as >> > such >> > (e.g., Implementation Status sections (per RFC 7942)). >> >> Yes, "Appendix A. Change log" needs to be removed >> >> > *Are there any instances of repeated text/sections that should be edited >> > the same way? >> No >> >> > 5) This document uses one or more of the following text styles. >> > Are these elements used consistently? >> > >> > * fixed width font (<tt/> or `) >> > * italics (<em/> or *) >> > * bold (<strong/> or **) >> >> Styles are used consequently. >> >> >> > 6) This document is part of Cluster 553: >> > https://www.rfc-editor.org/cluster_info.php?cid=C553 >> >> > * To help the reader understand the content of the cluster, is there a >> > document in the cluster that should be read first? Next? If so, please >> > provide >> > the order and we will provide RFC numbers for the documents accordingly. >> > If order is not important, please let us know. >> > * Is there any text that has been repeated within the cluster document >> > that >> > should be edited in the same way (for instance, parallel introductory text >> > or >> > Security Considerations)? >> >> >> > * For more information about clusters, see >> > https://www.rfc-editor.org/about/clusters/ >> > * For a list of all current clusters, see: >> > http://www.rfc-editor.org/all_clusters.php >> >> The draft-ietf-tls-hybrid-design-16 should be read before. >> >> >> > 7) Is there anything else that the RPC should be aware of while editing >> > this >> > document? >> >> No. >> >> >> Kind regards, >> Kris Kwiatkowski >> -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
