Med, Thank you for your reply. The revised files are here (please refresh): https://www.rfc-editor.org/authors/rfc9900.html https://www.rfc-editor.org/authors/rfc9900.txt https://www.rfc-editor.org/authors/rfc9900.pdf https://www.rfc-editor.org/authors/rfc9900.xml
This diff file shows all changes from the approved I-D: https://www.rfc-editor.org/authors/rfc9900-diff.html https://www.rfc-editor.org/authors/rfc9900-rfcdiff.html (side by side) This diff file shows the changes made during AUTH48 thus far: https://www.rfc-editor.org/authors/rfc9900-auth48diff.html https://www.rfc-editor.org/authors/rfc9900-auth48rfcdiff.html (side by side) Re: > Assuming the pending change is implemented, I approve the publication of the > document. We have recorded your approval on the AUTH48 status page (https://www.rfc-editor.org/auth48/rfc9900) and will continue with the publication process. Thank you. Alice Russo RFC Production Center > On Dec 3, 2025, at 10:05 PM, [email protected] wrote: > > Hi Alice, > > Thank you for preparing this edited version. > > Please see inline. > > Cheers, > Med > >> -----Message d'origine----- >> De : [email protected] <[email protected]> >> Envoyé : jeudi 4 décembre 2025 02:50 >> À : BOUCADAIR Mohamed INNOV/NET <[email protected]> >> Cc : [email protected]; [email protected]; netconf- >> [email protected]; [email protected]; [email protected]; >> [email protected] >> Objet : Re: AUTH48: RFC-to-be 9900 <draft-ietf-netconf-port- >> numbers-07> for your review >> >> >> Greetings, >> >> While reviewing this document during AUTH48, please resolve (as >> necessary) the following questions, which are also in the source >> file. >> >> 1) <!--[rfced] May we update the abstract as follows or otherwise >> so that NETCONF is expanded? >> >> Original: >> This document releases NETCONF-related port number IANA >> assignments >> for services that have not been in use in production networks. >> >> Perhaps: >> This document releases IANA-assigned port numbers for services >> related to the Network Configuration Protocol (NETCONF) that >> have not >> been in use in production networks. >> --> > > [Med] OK for me. > >> >> >> 2) <!-- [rfced] Please review the "Inclusive Language" portion of >> the online Style Guide >> <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 >> Fwww.rfc- >> editor.org%2Fstyleguide%2Fpart2%2F%23inclusive_language&data=05%7C >> 02%7Cmohamed.boucadair%40orange.com%7C1983051a7b024c0dd99908de32d7 >> 6ffa%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6390040980494376 >> 34%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDA >> wMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C >> &sdata=AxwcgI5dDeY8ncbhwOmld0R2C%2F2sB1cSXbB4rWTuhiE%3D&reserved=0 >>> >> and let us know if any changes are needed. Updates of this nature >> typically result in more precise language, which is helpful for >> readers. >> >> Note that our script did not flag any words in particular, but >> this should still be reviewed as a best practice. >> --> > > [Med] I confirm as well. > > Assuming the pending change is implemented, I approve the publication of the > document. Thank you. > >> >> >> Thank you. >> >> Alice Russo >> RFC Production Center >> >> On Dec 3, 2025, [email protected] wrote: >> >> *****IMPORTANT***** >> >> Updated 2025/12/03 >> >> RFC Author(s): >> -------------- >> >> Instructions for Completing AUTH48 >> >> Your document has now entered AUTH48. Once it has been reviewed >> and approved by you and all coauthors, it will be published as an >> RFC. >> If an author is no longer available, there are several remedies >> available as listed in the FAQ >> (https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 >> Fwww.rfc- >> editor.org%2Ffaq%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com% >> 7C1983051a7b024c0dd99908de32d76ffa%7C90c7a20af34b40bfbc48b9253b6f5 >> d20%7C0%7C0%7C639004098049467047%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0e >> U1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCI >> sIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=gus3nq5RvJmkLIAfLIvlDyMgfbsDe >> ZyZVWGrMt0OIpg%3D&reserved=0). >> >> You and you coauthors are responsible for engaging other parties >> (e.g., Contributors or Working Group) as necessary before >> providing your approval. >> >> Planning your review >> --------------------- >> >> Please review the following aspects of your document: >> >> * RFC Editor questions >> >> Please review and resolve any questions raised by the RFC Editor >> that have been included in the XML file as comments marked as >> follows: >> >> <!-- [rfced] ... --> >> >> These questions will also be sent in a subsequent email. >> >> * Changes submitted by coauthors >> >> Please ensure that you review any changes submitted by your >> coauthors. We assume that if you do not speak up that you >> agree to changes submitted by your coauthors. >> >> * Content >> >> Please review the full content of the document, as this cannot >> change once the RFC is published. Please pay particular >> attention to: >> - IANA considerations updates (if applicable) >> - contact information >> - references >> >> * Copyright notices and legends >> >> Please review the copyright notice and legends as defined in >> RFC 5378 and the Trust Legal Provisions >> (TLP - >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> trustee.ietf.org%2Flicense- >> info&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C1983051a7b024 >> c0dd99908de32d76ffa%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6 >> 39004098049490622%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUs >> IlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D% >> 3D%7C0%7C%7C%7C&sdata=dtUv%2FQJh8u2Yu%2BHn5kRIvinDGEItTbK9%2BUehCU >> vULoY%3D&reserved=0). >> >> * Semantic markup >> >> Please review the markup in the XML file to ensure that elements >> of >> content are correctly tagged. For example, ensure that >> <sourcecode> >> and <artwork> are set correctly. See details at >> >> <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 >> Fauthors.ietf.org%2Frfcxml- >> vocabulary&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C1983051 >> a7b024c0dd99908de32d76ffa%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7 >> C0%7C639004098049505467%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOn >> RydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoy >> fQ%3D%3D%7C0%7C%7C%7C&sdata=cTmP0ZdnvQzW4wAvJuF4T7dzJltNdu0K%2B3XN >> 4ZLnFWw%3D&reserved=0>. >> >> * Formatted output >> >> Please review the PDF, HTML, and TXT files to ensure that the >> formatted output, as generated from the markup in the XML file, >> is >> reasonable. Please note that the TXT will have formatting >> limitations compared to the PDF and HTML. >> >> >> Submitting changes >> ------------------ >> >> To submit changes, please reply to this email using 'REPLY ALL' as >> all the parties CCed on this message need to see your changes. The >> parties >> include: >> >> * your coauthors >> >> * [email protected] (the RPC team) >> >> * other document participants, depending on the stream (e.g., >> IETF Stream participants are your working group chairs, the >> responsible ADs, and the document shepherd). >> >> * [email protected], which is a new archival mailing >> list >> to preserve AUTH48 conversations; it is not an active >> discussion >> list: >> >> * More info: >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> mailarchive.ietf.org%2Farch%2Fmsg%2Fietf-announce%2Fyb6lpIGh- >> 4Q9l2USxIAe6P8O4Zc&data=05%7C02%7Cmohamed.boucadair%40orange.com%7 >> C1983051a7b024c0dd99908de32d76ffa%7C90c7a20af34b40bfbc48b9253b6f5d >> 20%7C0%7C0%7C639004098049517757%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU >> 1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIs >> IldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=w4r6AYqEr%2BDBsN38yCkJ6lYpdebh >> fXDLruUozv7PmKE%3D&reserved=0 >> >> * The archive itself: >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> mailarchive.ietf.org%2Farch%2Fbrowse%2Fauth48archive%2F&data=05%7C >> 02%7Cmohamed.boucadair%40orange.com%7C1983051a7b024c0dd99908de32d7 >> 6ffa%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6390040980495285 >> 42%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDA >> wMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C >> &sdata=XsxJ%2B0nIccHMvrnJNq3qC%2FH1PwATJrviflrMpe65sJs%3D&reserved >> =0 >> >> * Note: If only absolutely necessary, you may temporarily opt >> out >> of the archiving of messages (e.g., to discuss a sensitive >> matter). >> If needed, please add a note at the top of the message that >> you >> have dropped the address. When the discussion is concluded, >> [email protected] will be re-added to the CC >> list and >> its addition will be noted at the top of the message. >> >> You may submit your changes in one of two ways: >> >> An update to the provided XML file >> - OR - >> An explicit list of changes in this format >> >> Section # (or indicate Global) >> >> OLD: >> old text >> >> NEW: >> new text >> >> You do not need to reply with both an updated XML file and an >> explicit list of changes, as either form is sufficient. >> >> We will ask a stream manager to review and approve any changes >> that seem beyond editorial in nature, e.g., addition of new text, >> deletion of text, and technical changes. Information about stream >> managers can be found in the FAQ. Editorial changes do not >> require approval from a stream manager. >> >> >> Approving for publication >> -------------------------- >> >> To approve your RFC for publication, please reply to this email >> stating that you approve this RFC for publication. Please use >> 'REPLY ALL', as all the parties CCed on this message need to see >> your approval. >> >> >> Files >> ----- >> >> The files are available here: >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauthors%2Frfc9900.xml&data=05%7C02%7Cmohamed.boucadai >> r%40orange.com%7C1983051a7b024c0dd99908de32d76ffa%7C90c7a20af34b40 >> bfbc48b9253b6f5d20%7C0%7C0%7C639004098049538034%7CUnknown%7CTWFpbG >> Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs >> IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=YVSmUgI669CCYs >> v1gIu1ghAzGSL8NjgbcE2CyU3q%2BjE%3D&reserved=0 >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauthors%2Frfc9900.html&data=05%7C02%7Cmohamed.boucada >> ir%40orange.com%7C1983051a7b024c0dd99908de32d76ffa%7C90c7a20af34b4 >> 0bfbc48b9253b6f5d20%7C0%7C0%7C639004098049547616%7CUnknown%7CTWFpb >> GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiI >> sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=wY%2BdHKpFsFf >> wp974pVKIz7kMkbxtUcpsmiHuegv6lCc%3D&reserved=0 >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauthors%2Frfc9900.pdf&data=05%7C02%7Cmohamed.boucadai >> r%40orange.com%7C1983051a7b024c0dd99908de32d76ffa%7C90c7a20af34b40 >> bfbc48b9253b6f5d20%7C0%7C0%7C639004098049558014%7CUnknown%7CTWFpbG >> Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs >> IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=mvvaz%2B8QCBdS >> IFfiNc%2B1uzePGgHaV1fTJOdQ7rxn7ug%3D&reserved=0 >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauthors%2Frfc9900.txt&data=05%7C02%7Cmohamed.boucadai >> r%40orange.com%7C1983051a7b024c0dd99908de32d76ffa%7C90c7a20af34b40 >> bfbc48b9253b6f5d20%7C0%7C0%7C639004098049573406%7CUnknown%7CTWFpbG >> Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs >> IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2F4HyizRuLOxe >> IiwSMpMT%2F6nPq%2FfTBsDisODfDWqEMyo%3D&reserved=0 >> >> Diff file of the text: >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9900- >> diff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C1983051a >> 7b024c0dd99908de32d76ffa%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C >> 0%7C639004098049587111%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR >> ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf >> Q%3D%3D%7C0%7C%7C%7C&sdata=53VdC6y0V7wFP9RzmoTLixz1Te1PeYSCDKCIme2 >> K7S4%3D&reserved=0 >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9900- >> rfcdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C19830 >> 51a7b024c0dd99908de32d76ffa%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0 >> %7C0%7C639004098049601702%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGki >> OnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIj >> oyfQ%3D%3D%7C0%7C%7C%7C&sdata=XM2MR9NZd19IUGslIKKQizRMnxuL4r220Udt >> K4t1fpg%3D&reserved=0 (side by side) >> >> Diff of the XML: >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9900- >> xmldiff1.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C1983 >> 051a7b024c0dd99908de32d76ffa%7C90c7a20af34b40bfbc48b9253b6f5d20%7C >> 0%7C0%7C639004098049615869%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGk >> iOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUI >> joyfQ%3D%3D%7C0%7C%7C%7C&sdata=ujWteIaqb%2FlVeqYl5lTIbkbPxiediLcb5 >> xmuEqVpYMo%3D&reserved=0 >> >> >> Tracking progress >> ----------------- >> >> The details of the AUTH48 status of your document are here: >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauth48%2Frfc9900&data=05%7C02%7Cmohamed.boucadair%40o >> range.com%7C1983051a7b024c0dd99908de32d76ffa%7C90c7a20af34b40bfbc4 >> 8b9253b6f5d20%7C0%7C0%7C639004098049629549%7CUnknown%7CTWFpbGZsb3d >> 8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOI >> joiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=px5f%2FpH%2B94jlC6p >> Jpi3LGg3Kx3jVsub6L%2F6vOvhC%2Fa8%3D&reserved=0 >> >> Please let us know if you have any questions. >> >> Thank you for your cooperation, >> >> RFC Editor >> >> -------------------------------------- >> RFC9900 (draft-ietf-netconf-port-numbers-07) >> >> Title : Updates to NETCONF Transport Port Numbers >> Author(s) : M. Boucadair >> WG Chair(s) : Kent Watsen, Per Andersson >> Area Director(s) : Mohamed Boucadair, Mahesh Jethanandani > ____________________________________________________________________________________________________________ > 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]
