Hi Kehan, Thank you for your reply!
Sincerely, Sarah Tarrant RFC Production Center > On Feb 4, 2026, at 4:39 AM, Yao Kehan <[email protected]> wrote: > > Dear Sarah, > > I've copied previous questions here. Please see reply inline. > > Thank you so much for your help. > > Best regards, > Kehan > > --- > 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? > * Are the Authors' Addresses, Contributors, and Acknowledgments > sections current? > > [KY] The Abstract is accurate, and the Authors' Addresses, Contributors, and > Acknowledgments sections are up-to-date. > > 2) Please share any style information that could help us with editing your > document. For example: > > * Is your document's format or its terminology based on another document? > If so, please provide a pointer to that document (e.g., this document's > terminology should match DNS terminology in RFC 9499). > * Is there a pattern of capitalization or formatting of terms? (e.g., field > names > should have initial capitalization; parameter names should be in double > quotes; > should be used for token names; etc.) > > [KY] As mentioned in previous emails, the terminology in this document is > referenced from the CATS framework document, so they should form a cluster. > There are capitalization requirements for the terms, please follow the > definitions within this document. > > > 3) Please review the entries in the References section carefully 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). > > * 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. > > Note: To check for outdated RFC and I-D references, you can use > idnits . You can also help the > IETF Tools Team by testing idnits3 > with your document and reporting any issues to them. > > [KY]Okay, please proceed as you have outlined. > > 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)). > *Are there any instances of repeated text/sections that should be edited > the same way? > > [KY]There are no contentious sections, no sections requiring further removal, > and no instances of repeated text/sections that need uniform editing. > > 5) Is there anything else that the RPC should be aware of while editing this > document? > [KY]There are no other matters. Please feel free to contact us if you have > any questions. > > > > > ----邮件原文---- > 发件人：Sarah Tarrant <[email protected]> > 收件人：Yao Kehan <[email protected]> > 抄 送: "luismiguel.contreras" > <[email protected]>,shihang9 > <[email protected]>,zhangs366 <[email protected]>,"anqing.aq" > <[email protected]>,"huang.guangping" > <[email protected]>,"james.n.guichard" > <[email protected]>,rfc-editor > <[email protected]>,auth48archive > <[email protected]>,cats-chairs <[email protected]> > 发送时间：2026-02-03 22:15:41 > 主题：Re: Document intakequestionsabout<draft-ietf-cats-usecases-requirements-13> > > Hi Kehan, > > Thank you for the update! I've included you on the email to the AD regarding > version approval. > > In the meantime, feel free to answer that questions we had on the intake form > (see previous email thread) so we can record those for processing. > > Sincerely, > Sarah Tarrant > RFC Production Center > > > On Feb 3, 2026, at 1:59AM, Yao Kehan wrote: > > > > Dear Sarah, > > > > I've just uploaded a new version onto datatracker. > > > > A diff from the previous version is available at: > > https://author-tools.ietf.org/iddiff?url2=draft-ietf-cats-usecases-requirements-14 > > Please help proceed this document. Thank you. > > > > Best regards, > > Kehan > > > > ----邮件原文---- > > 发件人：Sarah Tarrant > > 收件人：Yao Kehan > > 抄 送: "luismiguel.contreras" ,shihang9 ,zhangs366 ,"anqing.aq" > > ,"huang.guangping" ,"james.n.guichard" ,rfc-editor ,auth48archive > > ,cats-chairs > > 发送时间：2026-02-02 22:11:20 > > 主题：Re: Document intake questionsabout > > > > Hi Kehan, > > > > Since that is a change that is above editorial, we would need you to submit > > a new version to the datatracker so that it is clear where that change > > originated and we can more easily get AD approval. > > > > Let me know if I can be of further assistance! > > > > Sincerely, > > Sarah Tarrant > > RFC Production Center > > > > > On Feb 1, 2026, at 10:24PM, Yao Kehan wrote: > > > > > > Kehan > > > > > > > > -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
