Hi Med, Thank you for your reply! The markdown looks great.
Sincerely, Sarah Tarrant RFC Production Center > On Apr 13, 2026, at 11:12 PM, [email protected] wrote: > > Hi Sarah, all, > > Please see inline. > > Cheers, > Med (as Editor) > >> -----Message d'origine----- >> De : Sarah Tarrant <[email protected]> >> Envoyé : lundi 13 avril 2026 22:19 >> À : [email protected]; [email protected]; BOUCADAIR Mohamed >> INNOV/NET <[email protected]>; >> [email protected]; [email protected] >> Cc : [email protected]; [email protected]; rfc- >> [email protected]; [email protected] >> Objet : Document intake questions about <draft-ietf-cats- >> framework-24> >> >> Author(s), >> >> Congratulations, your document has been successfully added to the >> RFC Editor queue! >> The team at the RFC Production Center (RPC) is looking forward to >> working with you as your document moves forward toward >> publication. To help reduce processing time and improve editing >> accuracy, please respond to the questions below. Please confer >> with your coauthors (or authors of other documents if your >> document is in a >> cluster) as necessary prior to taking action in order to >> streamline communication. >> If your document has multiple authors, only one author needs to >> reply to this message. >> >> As you read through the rest of this email: >> >> * If you need/want to make updates to your document, we encourage >> you to make those changes and resubmit to the Datatracker. This >> allows for the easy creation of diffs, which facilitates review by >> interested parties (e.g., authors, ADs, doc shepherds). >> * If you feel no updates to the document are necessary, please >> reply with any applicable rationale/comments. >> >> >> Please note that the RPC team will not work on your document until >> we hear from you (that is, your document will remain in AUTH state >> until we receive a reply). Even if you don't have guidance or >> don't feel that you need to make any updates to the document, you >> need to let us know. After we hear from you, your document will >> start moving through the queue. You will be able to review and >> approve our updates during AUTH48. >> >> Please feel free to contact us with any questions you may have at >> [email protected]. >> >> Thank you! >> The RPC Team >> >> -- >> >> 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? >> > > [Med] All is 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, >> WG style guide, etc.? If so, please provide a pointer to that >> information >> (e.g., "This document's terminology should match DNS terminology >> in >> RFC 9499." or "This document uses the style info at >> <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 >> Fhttpwg.org%2Fadmin%2Feditors%2Fstyle- >> guide&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Ccb1623fa86ee >> 4e71389508de9999f06c%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C >> 639117083599424029%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWU >> sIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D >> %3D%7C0%7C%7C%7C&sdata=zAEJkWDGUPhsSNl6gPNq3G2QUZ4WFxH6%2FyRoSJETl >> bw%3D&reserved=0>."). >> * Is there a general pattern of capitalization or formatting of >> terms that >> editors can follow (e.g., "Field names should have initial >> capitalization." >> or "Parameter names should be in double quotes." or "<tt/> should >> be used >> for token names." etc.)? >> > > [Med] The document is self-contained. The document was edited to be > internally consistent. > >> >> 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). >> >> * 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. >> > > [Med] ACK. > >> >> >> 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? > > [Med] There is no specific text that requires special handling. > >> >> >> 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 **) >> >> > > [Med] ACK > >> 6) This document contains SVG. What tool did you use to make the >> svg? >> >> The RPC cannot update SVG diagrams, so please ensure that: >> >> * the SVG figures match the ASCII art used in the text output as >> closely as >> possible, and >> * the figures fit on the pages of the PDF output. >> > > [Med] AASVG was used. > >> >> 7) Would you like to participate in the RPC Pilot Test for editing >> in kramdown-rfc? >> If so, please let us know and provide a self-contained kramdown- >> rfc file. For more >> information about this experiment, see: >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Frpc%2Fwiki%2Fdoku.php%3Fid%3Dpilot_test_kramdown_rfc& >> data=05%7C02%7Cmohamed.boucadair%40orange.com%7Ccb1623fa86ee4e7138 >> 9508de9999f06c%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639117 >> 083599461159%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiO >> iIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C >> 0%7C%7C%7C&sdata=JDQuoZ0ATIXraQmFIHGSY5tCeHy0i6OXKvXJa%2FRsZDw%3D& >> reserved=0. > > [Med] Yes. The source file can be found here: > https://github.com/ietf-wg-cats/draft-ietf-cats-framework/blob/main/draft-ietf-cats-framework.md > > >> >> >> 8) Would you like to participate in the RPC Pilot Test for >> completing AUTH48 in >> GitHub? If so, please let us know and provide all author, AD, >> and/or document >> shepherd GitHub usernames. For more information about this >> experiment, see: >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Frpc%2Fwiki%2Fdoku.php%3Fid%3Drpc-github- >> phase-0-pilot- >> test&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Ccb1623fa86ee4 >> e71389508de9999f06c%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6 >> 39117083599473413%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUs >> IlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D% >> 3D%7C0%7C%7C%7C&sdata=SNnKJl68ohFrF5NDKYA0bSQKGOAUlK5ULP%2FR5m%2F% >> 2BaW0%3D&reserved=0. >> > > [Med] Not this time :-) > >> >> 9) Is there anything else that the RPC should be aware of while >> editing this >> document? > > [Med] Nothing special to call out. > >> >>> On Apr 13, 2026, at 3:15 PM, [email protected] wrote: >>> >>> Author(s), >>> >>> Your document draft-ietf-cats-framework-24, which has been >> approved for publication as >>> an RFC, has been added to the RFC Editor queue >>> >> <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 >> Fwww.rfc- >> editor.org%2Fcurrent_queue.php&data=05%7C02%7Cmohamed.boucadair%40 >> orange.com%7Ccb1623fa86ee4e71389508de9999f06c%7C90c7a20af34b40bfbc >> 48b9253b6f5d20%7C0%7C0%7C639117083599486093%7CUnknown%7CTWFpbGZsb3 >> d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFO >> IjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=9yFnIua9vtSr4Qkf%2 >> F5rquial7LUPOC7p%2BtLbgTzTMPs%3D&reserved=0>. >>> >>> If your XML file was submitted using the I-D submission tool >>> >> <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 >> Fdatatracker.ietf.org%2Fsubmit%2F&data=05%7C02%7Cmohamed.boucadair >> %40orange.com%7Ccb1623fa86ee4e71389508de9999f06c%7C90c7a20af34b40b >> fbc48b9253b6f5d20%7C0%7C0%7C639117083599496456%7CUnknown%7CTWFpbGZ >> sb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsI >> kFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Q6rC%2FDtZswwLJ >> GWcMit1P3VaoahXeC8hV5bB%2FaGt%2F7Q%3D&reserved=0>, we have already >> retrieved it >>> and have started working on it. >>> >>> If you did not submit the file via the I-D submission tool, or >>> if you have an updated version (e.g., updated contact >> information), >>> please send us the file at this time by attaching it >>> in your reply to this message and specifying any differences >>> between the approved I-D and the file that you are providing. >>> >>> You will receive a separate message from us asking for style >> input. >>> Please respond to that message. When we have received your >> response, >>> your document will then move through the queue. The first step >> that >>> we take as your document moves through the queue is converting >> it to >>> RFCXML (if it is not already in RFCXML) and applying the >> formatting >>> steps listed at >> <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 >> Fwww.rfc-editor.org%2Fpubprocess%2Fhow-we- >> update%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Ccb1623fa >> 86ee4e71389508de9999f06c%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C >> 0%7C639117083599506456%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR >> ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf >> Q%3D%3D%7C0%7C%7C%7C&sdata=zN89ppz7a4M77oV2loqlq%2BArr3tVOWlnB6cTp >> gi4y%2F0%3D&reserved=0>. >>> Next, we will edit for clarity and apply the style guide >>> >> (<https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F% >> 2Fwww.rfc- >> editor.org%2Fstyleguide%2F&data=05%7C02%7Cmohamed.boucadair%40oran >> ge.com%7Ccb1623fa86ee4e71389508de9999f06c%7C90c7a20af34b40bfbc48b9 >> 253b6f5d20%7C0%7C0%7C639117083599516381%7CUnknown%7CTWFpbGZsb3d8ey >> JFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoi >> TWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=KtndKB2gpYhrm0IUdibfju >> oNudJtB0wpZKQApfP2mwQ%3D&reserved=0>). >>> >>> You can check the status of your document at >>> >> <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 >> Fwww.rfc- >> editor.org%2Fcurrent_queue.php&data=05%7C02%7Cmohamed.boucadair%40 >> orange.com%7Ccb1623fa86ee4e71389508de9999f06c%7C90c7a20af34b40bfbc >> 48b9253b6f5d20%7C0%7C0%7C639117083599525895%7CUnknown%7CTWFpbGZsb3 >> d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFO >> IjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=5ayyT4GtRijx4ZNvsj >> u5%2F3ihdticIjETdMeGHfaxZLs%3D&reserved=0>. >>> >>> You will receive automatic notifications as your document >> changes >>> queue state (for more information about these states, please see >>> >> <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 >> Fwww.rfc- >> editor.org%2Fabout%2Fqueue%2F&data=05%7C02%7Cmohamed.boucadair%40o >> range.com%7Ccb1623fa86ee4e71389508de9999f06c%7C90c7a20af34b40bfbc4 >> 8b9253b6f5d20%7C0%7C0%7C639117083599535548%7CUnknown%7CTWFpbGZsb3d >> 8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOI >> joiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=lv3yAowSteEptTIhgsC >> lR1%2BL0dw5Z%2FGTXqsjaMNs%2FMQ%3D&reserved=0>). When we have >> completed >>> our edits, we will move your document to AUTH48 state and ask >> you >>> to perform a final review of the document. >>> >>> Please let us know if you have any questions. >>> >>> Thank you. >>> >>> The RFC Editor Team >>> > > ____________________________________________________________________________________________________________ > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
