Hi Sarrah, all, Please see inline.
Cheers, Med (as author) > -----Message d'origine----- > De : Sarah Tarrant <[email protected]> > Envoyé : vendredi 3 avril 2026 22:16 > À : [email protected]; [email protected]; BOUCADAIR Mohamed > INNOV/NET <[email protected]>; [email protected] > Cc : [email protected]; [email protected]; rfc- > [email protected]; [email protected] > Objet : Document intake questions about <draft-ietf-opsawg-ucl- > acl-15> > > > 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%7C5af36deb3bb0 > 4913716e08de91bdef59%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C > 639108442150366745%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWU > sIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D > %3D%7C0%7C%7C%7C&sdata=3NcPPBc59QLJLqPV6K%2F%2BaO8VLYUj7YULMfGpQzK > K0Ys%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] Nothing special to flag other than we would like to keep consistency with RFC8519, RFC9922, and RFC6929. > > > 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] Nothing that is worth to call out specifically here. > > > 5) This document contains sourcecode: > > * Does the sourcecode validate? [Med] Yes (YANG and JSON Examples). > * Some sourcecode types (e.g., YANG) require certain references > and/or text > in the Security Considerations section. Is this information > correct? [Med] ACK. > * Is the sourcecode type indicated in the XML? [Med] Yes. code is marked "yang" or "json" in the doc. (See information > about > types: > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc-editor.org%2Frpc%2Fwiki%2Fdoku.php%3Fid%3Dsourcecode- > types&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C5af36deb3bb0 > 4913716e08de91bdef59%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C > 639108442150409644%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWU > sIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D > %3D%7C0%7C%7C%7C&sdata=6B%2BhF8jP0luy8zlqpEOoYK0ojosCJKCFfp3Sv0mjL > 8Y%3D&reserved=0.) > > > 6) This document contains SVG. What tool did you use to make the > svg? [Med] We used aasvg (integrated with markdown tooling). > > 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. > > > 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%7C5af36deb3bb0491371 > 6e08de91bdef59%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639108 > 442150421836%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiO > iIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C > 0%7C%7C%7C&sdata=CaR6ZZdJ8rS%2Fz8myQRyw8usuZOlySPo72yL9FH8Bqac%3D& > reserved=0. > [Med] No this time. FWIW, our source can be seen at https://github.com/IETF-OPSAWG-WG/policy-based-network-acl/blob/main/draft-ietf-opsawg-ucl-acl.md, but the file is not self-contained (as it points to external files for authors convenience). > > 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%7C5af36deb3bb04 > 913716e08de91bdef59%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6 > 39108442150432983%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUs > IlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D% > 3D%7C0%7C%7C%7C&sdata=XLGHx%2BmPpx5I3t8IPIdYLsxWlm92%2F40Umbckbnv8 > zZs%3D&reserved=0. > [Med] No this time. > > 9) Is there anything else that the RPC should be aware of while > editing this > document? [Med] Nothing worth to report here. > > > On Apr 3, 2026, at 3:11 PM, [email protected] wrote: > > > > Author(s), > > > > Your document draft-ietf-opsawg-ucl-acl-15, 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%7C5af36deb3bb04913716e08de91bdef59%7C90c7a20af34b40bfbc > 48b9253b6f5d20%7C0%7C0%7C639108442150443368%7CUnknown%7CTWFpbGZsb3 > d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFO > IjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ZfceUMseBEeMOy%2BX > tySmvPXSfTmvrWzFyKxwbmRjylQ%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%7C5af36deb3bb04913716e08de91bdef59%7C90c7a20af34b40b > fbc48b9253b6f5d20%7C0%7C0%7C639108442150455392%7CUnknown%7CTWFpbGZ > sb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsI > kFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=y4hvUspFsd2DM8x > %2BZ0%2FK%2FWBTACQ2DcWPE5Ldd6wkNnY%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%7C5af36deb > 3bb04913716e08de91bdef59%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C > 0%7C639108442150466874%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR > ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf > Q%3D%3D%7C0%7C%7C%7C&sdata=W22XuAhVRJzTTraRr5gpueJbB9TWHUUAyQYkGTz > XeQE%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%7C5af36deb3bb04913716e08de91bdef59%7C90c7a20af34b40bfbc48b9 > 253b6f5d20%7C0%7C0%7C639108442150478385%7CUnknown%7CTWFpbGZsb3d8ey > JFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoi > TWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=mfFgNtv7NHKcTdECycyAi2 > lwYw5sVlIh5mbpuiyu08Y%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%7C5af36deb3bb04913716e08de91bdef59%7C90c7a20af34b40bfbc > 48b9253b6f5d20%7C0%7C0%7C639108442150490269%7CUnknown%7CTWFpbGZsb3 > d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFO > IjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Dnde9wtnYRo%2Fx73D > P4XbHitHbRqJT5f%2FeqBh%2Fg%2F3lJM%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%7C5af36deb3bb04913716e08de91bdef59%7C90c7a20af34b40bfbc4 > 8b9253b6f5d20%7C0%7C0%7C639108442150504523%7CUnknown%7CTWFpbGZsb3d > 8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOI > joiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=8DwwvswAH3blXZJvrgk > 2x3MG3U%2FS4IEUfjzmExZqYUI%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]
