Hi Med, Thank you for your reply!
Sincerely, Sarah Tarrant RFC Production Center > On Sep 23, 2025, at 12:47 AM, [email protected] wrote: > > Hi Sarah, > > Please see inline. > > Cheers, > Med > >> -----Message d'origine----- >> De : Sarah Tarrant <[email protected]> >> Envoyé : lundi 22 septembre 2025 22:36 >> À : BOUCADAIR Mohamed INNOV/NET <[email protected]> >> Cc : [email protected]; [email protected]; rfc- >> [email protected]; [email protected] >> Objet : Document intake questions about <draft-ietf-netconf-port- >> numbers-07> >> >> >> 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 is still accurate? >> * Are the References, Authors' Addresses, Contributors, and >> Acknowledgments sections current? >> >> > > [Med] All is OK. > >> 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; >> <tt/> should be used for token names; etc.) >> > > [Med] Nothing special to call out here. > >> >> 3) Is there any text that should be handled extra cautiously? For >> example, are >> there any sections that were contentious when the document was >> drafted? >> > > [Med] No. > >> >> 4) Is there anything else that the RPC should be aware of while >> editing this >> document? >> > > [Med] FWIW, the source md can be found at: > https://github.com/boucadair/netconf-port-numbers/blob/main/draft-ietf-netconf-port-numbers.md > > >> >>> On Sep 22, 2025, at 3:32 PM, [email protected] wrote: >>> >>> Author(s), >>> >>> Your document draft-ietf-netconf-port-numbers-07, 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%7C1306b434ed1b4cd2a4e008ddfa17a2e7%7C90c7a20af34b40bfbc >> 48b9253b6f5d20%7C0%7C0%7C638941701614462026%7CUnknown%7CTWFpbGZsb3 >> d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFO >> IjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=SRDjPbPeZn9gMbwE5B >> KvVhcdaJZN1aN8v2ECtA%2BVkYY%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%7C1306b434ed1b4cd2a4e008ddfa17a2e7%7C90c7a20af34b40b >> fbc48b9253b6f5d20%7C0%7C0%7C638941701614482195%7CUnknown%7CTWFpbGZ >> sb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsI >> kFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=STUGZgZCYICL5b9 >> PYomxlrLJgkMmsI2Yoj6cTrjizBo%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%7C1306b434 >> ed1b4cd2a4e008ddfa17a2e7%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C >> 0%7C638941701614495681%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR >> ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf >> Q%3D%3D%7C0%7C%7C%7C&sdata=Cp3BHoE8lZIJENE911Zh%2FRdkN7ikE2dns9gaQ >> 3dP0KU%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%7C1306b434ed1b4cd2a4e008ddfa17a2e7%7C90c7a20af34b40bfbc48b9 >> 253b6f5d20%7C0%7C0%7C638941701614509565%7CUnknown%7CTWFpbGZsb3d8ey >> JFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoi >> TWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=48v98UlWlr7aNGO6lNvtD5 >> qpB0GsT1jvKHdKk43%2Bm1E%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%7C1306b434ed1b4cd2a4e008ddfa17a2e7%7C90c7a20af34b40bfbc >> 48b9253b6f5d20%7C0%7C0%7C638941701614524058%7CUnknown%7CTWFpbGZsb3 >> d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFO >> IjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=U5%2BOy02j6vBXYlQ5 >> KknZT4t46SKaKIrJR%2BZVxTzDOKw%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%7C1306b434ed1b4cd2a4e008ddfa17a2e7%7C90c7a20af34b40bfbc4 >> 8b9253b6f5d20%7C0%7C0%7C638941701614537352%7CUnknown%7CTWFpbGZsb3d >> 8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOI >> joiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=1rvA1FNSVI%2BHW8ch3 >> WMIBbRgZ3qZEDe%2FmWytiXF0DT4%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]
