Med, IANA (Amanda), and *Mahesh, Thank you for your careful reviews and replies. We have incorporated the changes submitted by Med (on 2 Feb). We have some further queries based on the reply from Mahesh below:
*Mahesh - Thank you for raising the three issues. 1) We believe the items you highlighted from the diff between the document template and the text in the wiki (https://wiki.ietf.org/group/ops/yang-security-guidelines?) require no change to the document (i.e., the document uses RFC 9907 while the wiki page uses [RFCAAAA]). The wiki will need to be updated upon the publication of the document with the RFC number. 2) Section 4.30.3: Thank you for pointing out the missing sentence! And apologies - we don’t think we understood the update the first time around. We have now incorporated the missing sentence into the document as we *believe* was intended. A related note below: **AUTHORS** please review this update as well as the list formation (indentation) we created (we believe this was a new list, not a further embedded list). Having it appear this way may clear Mahesh’s concern about the MAY/SHALL switch(?). If this does not appear as desired, please let us know how to update. If we have it right currently, please let Mahesh know to re-review how it now appears. 3) Section 4.30.3.1: We will await further guidance from the authors on what updates are needed to address Mahesh’s comments. (Please also see related mail from Amanda dated 3 February.) The files have been posted here (please refresh): https://www.rfc-editor.org/authors/rfc9907.txt https://www.rfc-editor.org/authors/rfc9907.pdf https://www.rfc-editor.org/authors/rfc9907.html https://www.rfc-editor.org/authors/rfc9907.xml The related diff files have been posted here (please refresh): https://www.rfc-editor.org/authors/rfc9907-diff.html (comprehensive) https://www.rfc-editor.org/authors/rfc9907-rfcdiff.html (comprehensive side by side) https://www.rfc-editor.org/authors/rfc9907-auth48diff.html (AUTH48 changes to date) https://www.rfc-editor.org/authors/rfc9907-auth48rfcdiff.html (AUTH48 changes side by side) https://www.rfc-editor.org/authors/rfc9907-lastdiff.html (last version to this) https://www.rfc-editor.org/authors/rfc9907-lastrfcdiff.html (last version side by side) The AUTH48 status page is viewable here: https://www.rfc-editor.org/auth48/rfc9907 Thank you. Megan Ferguson RFC Production Center > On Feb 2, 2026, at 1:25 AM, [email protected] wrote: > > Hi Megan, all, > > Thank you for sharing this updated version. Please find below some few > comments: > > # Section 3.9: delete an extra } > > OLD: > } > > 3.10. Validation Tools > > NEW: > > 3.10. Validation Tools > > # Section 3.10/3.11 > > There is inconsistency formatting about how tools are listed, e.g., 'pyang' > vs "yanglint" > > Please change "yangson" / "yanglint" to 'yangson' / 'yanglint' to adhere to > the formatting used in 8407. > > # Please revert back these changes through the document > > "definition" statement > "definition" statements > > to > > definition statement > definition statements > > # Section 4.20: revert this change > > OLD: "yang-data" "extension" statement > > NEW: OLD: "yang-data" extension statement > > Assuming these changes are implemented, I approve the publication of the > document. > > Cheers, > Med > >> -----Message d'origine----- >> De : Megan Ferguson <[email protected]> >> Envoyé : vendredi 30 janvier 2026 19:53 >> À : BOUCADAIR Mohamed INNOV/NET <[email protected]>; >> [email protected]; [email protected] >> Cc : [email protected]; [email protected]; >> [email protected]; [email protected]; [email protected]; >> [email protected]; [email protected] >> Objet : Re: [AD] [IANA] AUTH48: RFC-to-be 9907 <draft-ietf-netmod- >> rfc8407bis-28> for your review >> >> >> Hi Med and Amanda (and *Mahesh), >> >> [*Mahesh - please see our mail sent 26 January regarding AD >> actions.] >> >> We have updated per your replies. We believe Med's reply >> addressed all of our concerns from our previous mail (and have >> recorded this fact in the notes on the AUTH48 status page linked >> below). We will await AD approval from our previous message prior >> to moving forward in the publication process. >> >> Please review carefully and let us know if any further changes are >> necessary. >> >> The files have been posted here (please refresh): >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauthors%2Frfc9907.txt&data=05%7C02%7Cmohamed.boucadai >> r%40orange.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40 >> bfbc48b9253b6f5d20%7C0%7C0%7C639053960376312830%7CUnknown%7CTWFpbG >> Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs >> IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=710lW0XndgdlI% >> 2BBItFNd5u6bisZ9CHx5qghBXRgoqCQ%3D&reserved=0 >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauthors%2Frfc9907.pdf&data=05%7C02%7Cmohamed.boucadai >> r%40orange.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40 >> bfbc48b9253b6f5d20%7C0%7C0%7C639053960376328445%7CUnknown%7CTWFpbG >> Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs >> IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=NkAiahW2SxHO6m >> Go4A%2BsnGAll6GD7X0ePWcDzd5ybAA%3D&reserved=0 >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauthors%2Frfc9907.html&data=05%7C02%7Cmohamed.boucada >> ir%40orange.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b4 >> 0bfbc48b9253b6f5d20%7C0%7C0%7C639053960376338773%7CUnknown%7CTWFpb >> GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiI >> sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=WAvJmWP6%2BO% >> 2B5SsImir0GOKtoLOhblRkt%2FO6ohgy1wSA%3D&reserved=0 >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauthors%2Frfc9907.xml&data=05%7C02%7Cmohamed.boucadai >> r%40orange.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40 >> bfbc48b9253b6f5d20%7C0%7C0%7C639053960376349659%7CUnknown%7CTWFpbG >> Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs >> IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=mkL3bP6y7%2B77 >> sPNFNO67VMEQjwXHVqX%2BbseU7U4YruU%3D&reserved=0 >> >> The related diff files have been posted here (please refresh): >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> diff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C89f3cbb6 >> ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C >> 0%7C639053960376361497%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR >> ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf >> Q%3D%3D%7C0%7C%7C%7C&sdata=ndhXp3NTOHpjlFiw67Ve7j3hxybXvjYn2jicwvY >> HpB8%3D&reserved=0 (comprehensive) >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> rfcdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C89f3c >> bb6ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0 >> %7C0%7C639053960376371900%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGki >> OnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIj >> oyfQ%3D%3D%7C0%7C%7C%7C&sdata=jOvxPNle7NwCMFbmY%2F0x%2BXG6JV1wo8%2 >> FY6jiwjZ70lcw%3D&reserved=0 (comprehensive side by side) >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> auth48diff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C89 >> f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d20% >> 7C0%7C0%7C639053960376381941%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hc >> GkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIld >> UIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=i7AoqZ8laUd6EabYkxxGhUOXFOECX1rMq >> UXa%2BP8tfKU%3D&reserved=0 (AUTH48 changes to date) >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> auth48rfcdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7 >> C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d >> 20%7C0%7C0%7C639053960376393254%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU >> 1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIs >> IldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=1cVek6Dw493S7KJsGsP0GB%2BOjAzF >> wevZMIG3UbqIIEg%3D&reserved=0 (AUTH48 changes side by side) >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> lastdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C89f3 >> cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d20%7C >> 0%7C0%7C639053960376403391%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGk >> iOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUI >> joyfQ%3D%3D%7C0%7C%7C%7C&sdata=VHf%2FDriIH5ZGFlTuLz0J3dVX%2B00qheC >> mcIIQ%2Br24yPY%3D&reserved=0 (last version to this) >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> lastrfcdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C8 >> 9f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d20 >> %7C0%7C0%7C639053960376416862%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1h >> cGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIl >> dUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=SUNBh1KUX1%2FeCUc89rMsXI4IQLC%2B >> DMRRkYZvSAv2STM%3D&reserved=0 (last version side by side) >> >> The AUTH48 status page is available here: >> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauth48%2Frfc9907&data=05%7C02%7Cmohamed.boucadair%40o >> range.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc4 >> 8b9253b6f5d20%7C0%7C0%7C639053960376427203%7CUnknown%7CTWFpbGZsb3d >> 8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOI >> joiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ZTEo89BuVx3GXcApule >> T05DuMJu1PexgBme6TtGrZOE%3D&reserved=0 >> >> Thank you. >> >> Megan Ferguson >> RFC Production Center >> >> >> >>> On Jan 27, 2026, at 12:08 AM, [email protected] >> wrote: >>> >>> Hi Megan, all, >>> >>> Please see inline. >>> >>> Cheers, >>> Med >>> >>> PS: I'm currently travelling so I don't have enough flexibility >> to review more than what is requested below. >>> >>> De : Megan Ferguson <[email protected]> Envoyé : >> lundi 26 >>> janvier 2026 21:13 À : BOUCADAIR Mohamed INNOV/NET >>> <[email protected]>; [email protected] Cc : >>> [email protected]; [email protected]; >> [email protected]; >>> [email protected]; [email protected]; >> [email protected]; >>> [email protected]; [email protected] Objet : Re: [AD] >> [IANA] >>> AUTH48: RFC-to-be 9907 <draft-ietf-netmod-rfc8407bis-28> for >> your >>> review >>> >>> >>> >>> Hi Med, *Mahesh, (and IANA), >>> >>> Thanks for your careful reviews and replies. >>> >>> This message addresses mail from Mahesh, Med, and IANA (the >> changes requested by Amanda on 22 January). For your convenience, >> we have included links to the current versions of files in >> multiple places in this mail (but all point to the same files). >>> >>> Please review all updates carefully and let us know if further >> changes are necessary. We will await approvals from all parties >> (and of all actions) listed at the AUTH48 status page >> (https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 >> Fwww.rfc- >> editor.org%2Fauth48%2Frfc9907&data=05%7C02%7Cmohamed.boucadair%40o >> range.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc4 >> 8b9253b6f5d20%7C0%7C0%7C639053960376438218%7CUnknown%7CTWFpbGZsb3d >> 8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOI >> joiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=p%2BplcwHwFWRMMPRNM >> fof3sI6ZviDZfRbbGehUEUxSh4%3D&reserved=0) prior to moving this >> document forward in the publication process. >>> >>> >>> >>> Addressing Mahesh's reply (and necessary actions): >>> ------------------------------------------------- >>> *Mahesh - the addition of text to Section 3.9 can be viewed in >> the diff files here: >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> auth48diff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C89 >> f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d20% >> 7C0%7C0%7C639053960376448071%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hc >> GkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIld >> UIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=9rr6AYNWOJmMuF8v9CDGSktIutKroBQMl >> %2BITbzk5fng%3D&reserved=0 (AUTH48 changes only) >>> >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www. >>> rfc-editor.org%2Fauthors%2Frfc9907- >> auth48rfcdiff.html&data=05%7C02%7Cm >>> >> ohamed.boucadair%40orange.com%7C89f3cbb6ffca48df781a08de6030d7d2%7 >> C90c >>> >> 7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639053960376457593%7CUnkno >> wn%7 >>> >> CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXa >> W4zM >>> >> iIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Y3hCUjt0NHa >> R1Ce >>> uc8mrsOXESgJ5FFnzOYop8j0g8n8%3D&reserved=0 (AUTH48 side by side) >>> >>> We have also attached a screenshot of the piece in question for >> your convenience. >>> >>> <image001.png> >>> >>> With regard to the possible updates to the wiki page at >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> wiki.ietf.org%2Fgroup%2Fops%2Fyang-security- >> guidelines&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C89f3cbb >> 6ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7 >> C0%7C639053960376466844%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOn >> RydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoy >> fQ%3D%3D%7C0%7C%7C%7C&sdata=azZAHPx14GAycwgLw5elkkt%2BDp0uGQ1%2FKz >> vjDJijfIg%3D&reserved=0?, we have also posted a diff file to >> highlight the current differences between the document (template) >> and the wiki at: >>> >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www. >>> rfc-editor.org%2Fauthors%2Frfc9907-wiki- >> diff.html&data=05%7C02%7Cmoham >>> >> ed.boucadair%40orange.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C90c >> 7a20 >>> >> af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639053960376476582%7CUnknown%7 >> CTWF >>> >> pbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zM >> iIsI >>> >> kFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=5naUX14Gm8NSVQW >> BkdB >>> 6hZdbTRm5lFv%2BP3D5JHFa0o4%3D&reserved=0 >>> >>> Some of the differences highlighted are expected and will likely >> remain (e.g., having an RFC number in brackets or marking with a >> double dash in the RFC itself vs. colored boxes), but there are >> some textual differences remaining that we believe should be >> resolved. >>> >>> >>> Regarding this comment from Mahesh: >>> OLD: >>> "WG Web: >> <https://fra01.safelinks.protection.outlook.com/?url=http%3A%2F%2F >> datatracker.ietf.org%2Fwg%2Fyour-wg- >> name%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C89f3cbb6ff >> ca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0% >> 7C639053960376486772%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRyd >> WUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ% >> 3D%3D%7C0%7C%7C%7C&sdata=oS%2BoSXXFbgoTigBEYm6aOCPM3%2BdDHRXXIHyra >> YmcwY4%3D&reserved=0> >>> WG List: <mailto:[email protected]> >>> >>> NEW: >>> "WG Web: >> https://fra01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fd >> atatracker.ietf.org%2Fwg%2Fyour-wg- >> name&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C89f3cbb6ffca4 >> 8df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6 >> 39053960376495936%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUs >> IlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D% >> 3D%7C0%7C%7C%7C&sdata=6E1OYdT%2FPg%2FIyjOV%2BusBzouCh2lPEijEjI5hW8 >> gUL2k%3D&reserved=0 >>> WG List: YOUR-WG-NAME <mailto:[email protected]> >>> >>> Shouldn't http be changed to https above? >>> >>> [rfced] We have updated as suggested. Calling out here for >> author awareness. >>> >>> >>> For the update to the instructions below: >>> >>> NEW1: >>> >>> // RFC Ed: replace 'date-revision' with the module >> publication date <- Moved "RFC Ed: here >>> // the format is (YYYY-MM-DD) >>> >>> // replace XXXX with actual RFC number and remove >>> // this note >>> >>> revision date-revision { >>> description >>> "What changed in this revision."; >>> reference >>> "RFC XXXX: <Replace With Document Title>"; >>> } >>> >>> // Authors: Replace RFC IIIII with the RFC number and title. >> <- Made the text similar to the note to the RFC Editor. >>> // of the RFC that defined the initial version of >>> // the module and remove this note >>> >>> revision date-initial { >>> description >>> "Initial version"; version."; >>> reference >>> "RFC IIII: <Replace With Document Title>"; >>> } >>> >>> >>> Please review our update to this text and let us know if any >> further changes are necessary. >>> >>> *Mahesh - please also review and approve the following updates >> we have received in the meantime: >>> >>> -the addition of text to the end of the Introduction >>> >>> -the updates captured in the "Addressing the mail exchange with >> IANA" part of this email below (the updates suggested by IANA as >> well as our updates to it) - this includes changes to Sections >> 4.30.3 (added text), 4.30.3.1 (added and changed text), 4.30.3.2 >> (added and changed text), 5.3 (and the reorganization/addition of >> Sections 5.3.1 and 5.3.1). >>> >>> The above are reviewable in the files below: >>> >>> The files have been posted here (please refresh): >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauthors%2Frfc9907.txt&data=05%7C02%7Cmohamed.boucadai >> r%40orange.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40 >> bfbc48b9253b6f5d20%7C0%7C0%7C639053960376505953%7CUnknown%7CTWFpbG >> Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs >> IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ABIjlS%2F8zher >> WGMZFifYvOHG2Vba1To5mulZNIcsZF0%3D&reserved=0 >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauthors%2Frfc9907.pdf&data=05%7C02%7Cmohamed.boucadai >> r%40orange.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40 >> bfbc48b9253b6f5d20%7C0%7C0%7C639053960376516107%7CUnknown%7CTWFpbG >> Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs >> IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=krK2doIOas100% >> 2Fn3Jm%2F5X71pJUtaGMtcupBNfRR7QYU%3D&reserved=0 >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauthors%2Frfc9907.html&data=05%7C02%7Cmohamed.boucada >> ir%40orange.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b4 >> 0bfbc48b9253b6f5d20%7C0%7C0%7C639053960376525956%7CUnknown%7CTWFpb >> GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiI >> sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Yrjfc2MjIoImD >> 54K5yuCMtJasrU288EZxh3ENrs6PwM%3D&reserved=0 >>> >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www. >>> rfc- >> editor.org%2Fauthors%2Frfc9907.xml&data=05%7C02%7Cmohamed.boucadai >>> >> r%40orange.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40 >> bfbc >>> >> 48b9253b6f5d20%7C0%7C0%7C639053960376536234%7CUnknown%7CTWFpbGZsb3 >> d8ey >>> >> JFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoi >> TWFp >>> >> bCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=RN4ldiectbHluhTxuK6CPu%2Bq >> tQS7 >>> 9O%2BfiNRSj1PuRoE%3D&reserved=0 >>> >>> The related diff files have been posted here (please refresh): >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> diff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C89f3cbb6 >> ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C >> 0%7C639053960376546200%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR >> ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf >> Q%3D%3D%7C0%7C%7C%7C&sdata=3oUGoVW0Z4F2z4mv3WMelYTo5jxccrqVaC0LjkL >> Sd%2F0%3D&reserved=0 (comprehensive) >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> rfcdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C89f3c >> bb6ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0 >> %7C0%7C639053960376555860%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGki >> OnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIj >> oyfQ%3D%3D%7C0%7C%7C%7C&sdata=VjpyHqxuFNT3gLt4fy0nVU1re9szbwyQw%2B >> sOOxQ4v%2BY%3D&reserved=0 (comprehensive side by side) >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> auth48diff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C89 >> f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d20% >> 7C0%7C0%7C639053960376566385%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hc >> GkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIld >> UIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=VDISHGNIk%2BPSX%2F%2BcO7OaDzB2Osu >> nt0iIA40FQP%2FTFF0%3D&reserved=0 (AUTH48 changes to date) >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> auth48rfcdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7 >> C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d >> 20%7C0%7C0%7C639053960376581854%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU >> 1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIs >> IldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=06MvJ8y%2Fx8%2Fdz7KYOAFMMPbEdv >> ZkHupl27kI7bo%2B6Pk%3D&reserved=0 (AUTH48 changes side by side) >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> lastdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C89f3 >> cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d20%7C >> 0%7C0%7C639053960376595837%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGk >> iOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUI >> joyfQ%3D%3D%7C0%7C%7C%7C&sdata=K1Kqo8nVkMjp8xcpvfCanSBq1oXfj1PJaet >> aLMtYcP0%3D&reserved=0 (last version to this) >>> >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www. >>> rfc-editor.org%2Fauthors%2Frfc9907- >> lastrfcdiff.html&data=05%7C02%7Cmoh >>> >> amed.boucadair%40orange.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C9 >> 0c7a >>> >> 20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639053960376609138%7CUnknown >> %7CT >>> >> WFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4 >> zMiI >>> >> sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=dbjLi7Jr4p15q >> IXhS >>> vcG%2Faz1b1v5dXMBa8ygNOs5qBo%3D&reserved=0 (last version side by >> side) >>> >>> >>> Addressing Med's mail (all resolved issues snipped): >>> --------------------------------------------------- >>> >>> On Jan 16, 2026, at 12:43 AM, [email protected] >> wrote: >>> >>> >>> >>> 4) For 28d: >>> >>> >>> d) Please review the use of module/model when it appears without >> YANG >>> >>> and confirm that these instances appear as intended. >>> >>> [Med] Will review that separately. >>> >>> Please let us know if any further changes are necessary once you >>> complete your review. >>> >>> [Med] We can update all "model" occurrences in the bullet list >> of 4.23.3 to "module". >>> >>> Also, make a similar change in 4.23.3.1 for two occurrences. >>> [rfced] Please note that we also updated an instance before the >> bulleted list in Section 4.23.3. Please review and let us know if >> this change should be reverted. >>> [Med] ACK >>> >>> >>> 5) 28(e) and 28(f) ask about quotation around terms: >>> >>> >>> e) We note that there may be some inconsistency in the double >> quotes >>> >>> around statement names. For example, these terms are not quoted >> at >>> >>> places in the text: >>> >>> import statement >>> include statement >>> normative reference statement >>> XPath statement >>> extension statement >>> YANG statement >>> YANG extension statement >>> YANG conditional statement >>> reference statement >>> length statement >>> module tag extension statement >>> >>> [Med] Please follow the same convention as in RFC8407 for these. >>> >>> Unfortunately, RFC 8407 has some inconsistencies here. A number >> of >>> the items in the list above appear in both quotes and unquoted, >> with >>> the latter being more prevalent. Other statement names like >>> "description" and "revision" statement are majority quoted. >>> Please let us know if one of the following options should be >>> implemented: >>> a) double quote all statement (and substatement?) names >>> >>> [Med] We can double quote all statements for internal >> consistency then and also with RFC7950. >>> >>> Here is my proposal: >>> >>> "import" statement >>> "include" statement >>> normative "reference" statement >>> "XPath" statement >>> "extension" statement >>> YANG statement >>> YANG "extension" statement >>> YANG conditional statement >>> "reference" statement >>> "length" statement >>> module-tag "extension" statement >>> >>> [rfced] In implementing these suggestions, we had these follow >> up queries: >>> >>> -Should anydata be quoted here? >>> "Added anydata to the list of statements with mandatory". >>> [Med] Yes, please. >>> >>> -Should any quotes be added here? >>> "YANG module namespace statement" (see also namespace statement >> without YANG module before). >>> [Med] This should be changed to "YANG module "namespace" >> statement" to be consistent with 7950. All similar namespace >> statements should be changed (except for templates). >>> >>> -Should "definition" be double-quoted in the following or other >> instances of "data definition statement"? >>> "...all top-level data definition statements." >>> [Med] No. Please revert these changes. >>> Also, please revert "ordered list or leaf-list" to "ordered >> "list" or "leaf-list"" (Section 4.6.2). >>> >>> -We see this use of "extensions statement"; should double quotes >> be used? >>> ".or a "nacm:default-deny-all" extensions statement, then >> those." >>> [Med] We can leave this one unchanged as this will overload the >> template. >>> >>> -We assume these should not be single-quoted in the YANG >> example, please confirm. >>> "Several description and pattern statements have been >> improved.";" >>> Pattern statements; range statement; max-elements statement; >> list statement; YANG constraint statments, and YANG deviation >> statement? >>> [Med] I confirm. >>> >>> -Please advise on how quoting should appear in the following >> titles (i.e., should any of these be double quoted as well?): >>> 4.8. Module Header, Meta, and Revision Statement (quotes only >> on >>> Revision, correct?) 4.19.1. Conditional Augment Statements >> 4.19.2. >>> Conditionally Mandatory Data Definition Statements 4.20. >> Deviation >>> Statements 4.21. Extension Statements [Med] We can leave these >>> unchanges. >>> >>> -We added quotes to "extension" statement, but that makes for >> back-to-back quotes as seen in this example (see Section 4.29 for >> more examples): >>> "...the use of the "structure" "extension" statement..." >>> [Med] For those we can use ""structure" extension" to be >> consistent with rfc8791. >>> >>> >>> f) Further, there are some similar terms that may benefit from >>> quotation review. We see: >>> >>> when expression vs. "when" expression must expression vs. >>> "must" >>> >>> expression >>> >>> [rfced] Note also that we see "when" statement and "must" >>> statement. Should these be updated to expression? >>> >>> [Med] statement is actually more compliant with RFC7950. >>> >>> [rfced] We have updated from "expression" to "statement" per >> this guidance. Please review and let us know if this is in error. >>> [Med] ACK >>> >>> "deprecated" vs. "status deprecated" >>> >>> [rfced] We have added quotation marks where these appears to be >> a >>> setting. Please advise if any changes from simply "deprecated" >> to >>> instead say "status deprecated" are desired. >>> >>> [Med] The 2 uses in the doc are OK. However, when re-reading: >>> >>> CURRENT: >>> The "/interfaces-state" hierarchy has >>> been marked "status deprecated". Models that mark their >> "/foo- >>> state" hierarchy with "status deprecated" will allow >> NMDA- >>> >>> I wonder whether: >>> >>> OLD: been marked "status deprecated". >>> >>> NEW: been marked with "status deprecated". >>> [rfced] We have made this update as requested. As this was >> marked "I wonder", please confirm this appears as desired. >>> [Med] OK >>> >>> 6) We did not see a reply to questions 29(b) and 29(c). Please >> let us >>> know if any action is necessary on these items: >>> >>> >>> b) Please review the use of quotation marks (both single quotes >> and >>> >>> double quotes) with these terms; specifically, should they be >> moved >>> >>> to outside the <tt> tag? >>> >>> For example, we see both: >>> >>> <tt>"<CODE BEGINS>"</tt> tag >>> >>> and >>> >>> <tt><CODE BEGINS></tt> convention >>> >>> c) Please review to ensure the usage of <tt> is consistent. It >>> appears that there may be varying treatment of these terms. >>> >>> >>> [Med] Please use a consistent approach for all similar matters. >>> [rfced] We have updated to include double quotes outside the >> <tt> tags for CODE BEGINS and CODE ENDS throughout. We have added >> <tt> tags and quotation marks around BEGIN TEMPLATE TEXT and END >> TEMPLATE TEXT as well. Please let us know any objections. >>> >>> The above updates (and all the updates related Med's mail are >> reviewable in the most recent postings, again, those are viewable >> at: >>> >>> The files have been posted here (please refresh): >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauthors%2Frfc9907.txt&data=05%7C02%7Cmohamed.boucadai >> r%40orange.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40 >> bfbc48b9253b6f5d20%7C0%7C0%7C639053960376622632%7CUnknown%7CTWFpbG >> Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs >> IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=PI3CT%2B9k0DXw >> D1fcrxwwqqsun1cZgcv3iLH%2Fg15RabE%3D&reserved=0 >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauthors%2Frfc9907.pdf&data=05%7C02%7Cmohamed.boucadai >> r%40orange.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40 >> bfbc48b9253b6f5d20%7C0%7C0%7C639053960376636194%7CUnknown%7CTWFpbG >> Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs >> IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=S0MNrQiC6vqlm3 >> IpAJ6%2BxEtf5%2FYT6vyB8ySeTyUz8is%3D&reserved=0 >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauthors%2Frfc9907.html&data=05%7C02%7Cmohamed.boucada >> ir%40orange.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b4 >> 0bfbc48b9253b6f5d20%7C0%7C0%7C639053960376649995%7CUnknown%7CTWFpb >> GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiI >> sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=MSzqm8%2B8BkG >> 4Ok60MqV4C%2BDBF0F6V2%2F5hQzOJTnddcs%3D&reserved=0 >>> >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www. >>> rfc- >> editor.org%2Fauthors%2Frfc9907.xml&data=05%7C02%7Cmohamed.boucadai >>> >> r%40orange.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40 >> bfbc >>> >> 48b9253b6f5d20%7C0%7C0%7C639053960376663410%7CUnknown%7CTWFpbGZsb3 >> d8ey >>> >> JFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoi >> TWFp >>> >> bCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=DCtyhCwB4oZGt1qoK9gBzUaSXT >> I4cr >>> 8WxWa7OzHKcj0%3D&reserved=0 >>> >>> The related diff files have been posted here (please refresh): >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> diff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C89f3cbb6 >> ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C >> 0%7C639053960376676817%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR >> ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf >> Q%3D%3D%7C0%7C%7C%7C&sdata=NR18f8p9v4HA3HYxFIswBwpkCo90hHQZmEnKXq8 >> eME0%3D&reserved=0 (comprehensive) >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> rfcdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C89f3c >> bb6ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0 >> %7C0%7C639053960376690389%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGki >> OnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIj >> oyfQ%3D%3D%7C0%7C%7C%7C&sdata=PxlJLhCsKvMpnTFQ0iFbt4F3ia%2F5XQrHXy >> AWrb14LOM%3D&reserved=0 (comprehensive side by side) >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> auth48diff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C89 >> f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d20% >> 7C0%7C0%7C639053960376701596%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hc >> GkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIld >> UIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=1AJut3m5Tsr0dd5KmTgJn4sOzhuOZjIVO >> oEMaFVESR0%3D&reserved=0 (AUTH48 changes to date) >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> auth48rfcdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7 >> C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d >> 20%7C0%7C0%7C639053960376711392%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU >> 1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIs >> IldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=3ucr%2BrlXTHTuQg7xVUqIeR59dUKM >> oLOlTnrEzCy%2FKhk%3D&reserved=0 (AUTH48 changes side by side) >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> lastdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C89f3 >> cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d20%7C >> 0%7C0%7C639053960376721442%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGk >> iOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUI >> joyfQ%3D%3D%7C0%7C%7C%7C&sdata=ExLRgjE0A4ujs%2FSrFzkwpbaYJiPLE1m03 >> 4fJqtk2lQ8%3D&reserved=0 (last version to this) >>> >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www. >>> rfc-editor.org%2Fauthors%2Frfc9907- >> lastrfcdiff.html&data=05%7C02%7Cmoh >>> >> amed.boucadair%40orange.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C9 >> 0c7a >>> >> 20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639053960376734540%7CUnknown >> %7CT >>> >> WFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4 >> zMiI >>> >> sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Dk5wZqXjDdCwO >> qZY5 >>> ypqRGN5qTApk9UHEkL03L3wvI8%3D&reserved=0 (last version side by >> side) >>> >>> Addressing the mail exchange with IANA: >>> --------------------------------------- >>> >>> RFC Editor: >>> >>> Hi! Med has asked us to coordinate four sets of changes to >> draft-ietf-netmod-rfc8407bis with you. He approved the proposed >> text for 4.30.3.1, 4.30.3.2, and 5.3 this morning, with a change >> that's been applied below (s/5.3/5.3.2/), and he provided the >> updated 4.30.3 text in a message from January 17th. >>> >>> thanks, >>> Amanda >>> >>> ========================================== >>> >>> 1) Make this change to 4.30.3: >>> >>> OLD: >>> >>> * A note that unassigned or reserved values must not be present >> in the IANA-maintained module. >>> >>> * An instruction whether experimental values should be included >> in the IANA-maintained module. If no instruction is provided, >> experimental values MUST NOT be listed in the IANA-maintained >> module. >>> >>> * An instruction about how to generate the "revision" statement. >>> >>> NEW: >>> >>> The IANA Considerations Section MAY also provide the following >>> information if a default action is expected: >>> >>> * A note whether unassigned or reserved values should be >> present in >>> the IANA-maintained module. If no instruction is provided, >>> unassigned or reserved values must not be present in >>> the IANA-maintained module. >>> >>> * An instruction whether experimental values should be included >> in >>> the IANA-maintained module. If no instruction is provided, >>> experimental values MUST NOT be listed in the IANA-maintained >>> module. >>> >>> * An instruction about how to generate the "revision" >> statement. >>> If not present, default actions provided in Section 5.3 will >> be followed. >>> >>> [rfced] Note that we updated the last bullet point to read as >> "If no instruction is provided" instead of "If not present" to be >> consistent with the two previous points. Please let us know any >> objections. >>> [Med] Works for me. I see that the reference in the last bullet >> was >>> changed to 4.30 >>> >>> CURRENT: >>> * An instruction about how to generate the "revision" >> statement. If >>> no instruction is provided, default actions provided in >>> Section 4.30 will be followed. >>> >>> While this should be Section 5.3. Can we please fix that? >>> >>> ========================================== >>> >>> 2) Update Section 4.30.3.1 to read as follows: >>> >>> 4.30.3.1. Template for IANA-Maintained Modules with Identities >>> >>> This template ends with a section labeled "OPTIONAL." Any text >> in this section that needs to be customized should be included in >> the template. Text that does not require customization should be >> omitted. >>> >>> <CODE BEGINS> >>> >>> This document defines the initial version of the IANA-maintained >>> "iana-foo" YANG module. The most recent version of the YANG >> module is >>> available from the "YANG Parameters" registry group >>> [IANA-YANG-PARAMETERS]. >>> >>> IANA is requested to add this note to the registry: >>> >>> New values must not be directly added to the "iana-foo" YANG >> module. >>> They must instead be added to the "foo" registry. >>> >>> IANA is requested to add this note to [reference-to-the-iana- >> foo- >>> registry]: >>> >>> When this registry is modified, the YANG module "iana-foo" >>> [IANA_FOO_URL] must be updated as defined in RFC IIII. >>> >>> When a value is added to the "foo" registry, a new "identity" >>> statement needs to be added to the "iana-foo" YANG module. The >> name of >>> the "identity" MUST be the name as provided in the registry. >>> The "identity" statement should have the following sub- >> statements >>> defined: >>> >>> "base": Contains 'name-base-identity-defined-in-foo'. >>> >>> "status": Include only if a registration has been >> deprecated or >>> obsoleted. IANA "deprecated" maps to YANG status >>> "deprecated", and IANA "obsolete" maps to YANG >> status >>> "obsolete". >>> >>> "description": Replicates the description from the registry. >>> >>> "reference": Replicates the reference(s) from the registry. >>> References to documents should also include >> titles. >>> >>> -- OPTIONAL: >>> >>> -- Include only text that needs to be customized for the module. >>> -- Text that does not require customization should be >>> -- omitted. >>> >>> -- Notes tagged with "--" include instructions for authors. >> These >>> notes >>> -- must not be copied. >>> >>> Unassigned and Reserved Values: >>> >>> -- To be completed only if unassigned and/or reserved values >>> -- (which may include experimental values) should be included >>> -- in the module. These values are typically not included. >>> >>> Description Substatements: >>> >>> -- To be completed only if the default actions described in >>> -- Section 5.3.2 are to be overridden. >>> -- Specify whether instructions apply to "revision" statements, >> "identity" statements, or both. >>> >>> Reference Substatements: >>> >>> -- To be completed only if the default actions described in >>> -- Section 5.3.2 are to be overridden. >>> -- Specify whether instructions apply to "revision" statements, >> "identity" statements, or both. >>> >>> Naming Considerations: >>> >>> -- If a name in the IANA registry does not comply with the >>> -- YANG naming conventions, add details how IANA can generate >>> -- legal identifiers. For example, if the name begins with >>> -- a number, indicate a preference to spell out the number when >>> -- used as an identifier. >>> >>> <CODE ENDS> >>> >>> [rfced] We made a slight further update to use "Section 5.3.2 of >> RFC 9907" in the text under both "Description Substatements" and >> "Reference Substatements". We also updated the introductory text >> to more closely match the text proposed for Section 4.30.3.2 >> (below). Please review and let us know any concerns. >>> [Med] ACK. Thank you >>> >>> ========================================== >>> >>> 3) Update Section 4.30.3.2 to read as follows (same text as >> above, aside from references to enums instead of identities): >>> >>> 4.30.3.2. Template for IANA-Maintained Modules with Enumerations >>> >>> This template ends with a section labeled "OPTIONAL." Any text >> in this section that needs to be customized should be included in >> the template. Text that does not require customization should be >> omitted from the IANA Considerations. >>> >>> <CODE BEGINS> >>> >>> This document defines the initial version of the IANA-maintained >>> "iana-foo" YANG module. The most recent version of the YANG >> module is >>> available from the "YANG Parameters" registry group >>> [IANA-YANG-PARAMETERS]. >>> >>> IANA is requested to add this note to the registry: >>> >>> New values must not be directly added to the "iana-foo" YANG >> module. >>> They must instead be added to the "foo" registry. >>> >>> IANA is requested to add this note to [reference-to-the-iana- >> foo- >>> registry]: >>> >>> When this registry is modified, the YANG module "iana-foo" >>> [IANA_FOO_URL] must be updated as defined in RFC IIII. >>> >>> When a value is added to the "foo" registry, a new "enum" >> statement >>> must be added to the "iana-foo" YANG module. The "enum" >> statement, and >>> sub-statements thereof, should be defined: >>> >>> "enum": Replicates a name from the registry. >>> >>> "value": Contains the decimal value of the IANA-assigned value. >>> >>> "status": Is included only if a registration has been deprecated >> or >>> obsoleted. IANA "deprecated" maps to YANG status "deprecated", >> and >>> IANA "obsolete" >>> maps to YANG status "obsolete". >>> >>> "description": Replicates the description from the registry. >>> >>> "reference": Replicates the reference(s) from the registry. >> References to documents should also include titles. >>> >>> -- OPTIONAL: >>> >>> -- Include only text that needs to be customized for the module. >>> -- Text that does not require customization should be >>> -- omitted. >>> >>> -- Notes tagged with "--" include instructions for authors. >> These >>> notes >>> -- must not be copied. >>> >>> Unassigned and Reserved Values: >>> >>> -- To be completed only if unassigned and/or reserved values >>> -- (which may include experimental values) should be included >>> -- in the module. These values are typically not included. >>> >>> Description Substatements: >>> >>> -- To be completed only if the default actions described in >>> -- Section 5.3.2 are to be overridden. >>> -- Specify whether instructions apply to "revision" statements, >> "enum" statements, or both. >>> >>> Reference Substatements: >>> >>> -- To be completed only if the default actions described in >>> -- Section 5.3.2 are to be overridden. >>> -- Specify whether instructions apply to "revision" statements, >> "enum" statements, or both. >>> >>> Naming Considerations: >>> >>> -- If a name in the IANA registry does not comply with the >>> -- YANG naming conventions, add details how IANA can generate >>> -- legal identifiers. For example, if the name begins with >>> -- a number, indicate a preference to spell out the number when >>> -- used as an identifier. >>> >>> <CODE ENDS> >>> [rfced] We have made similar updates as mentioned above (added >> RFC 9907 to section mentions). >>> [Med] ACK >>> >>> ========================================== >>> >>> 4) Replace Section 5.3 with the following: >>> >>> 5.3. IANA-Maintained Modules >>> >>> IANA should refer to Section 4.30.3 for information necessary to >> populate "revision" statements and "identity" and "enum" >> substatements in IANA-maintained modules. >>> >>> These considerations cover both the creation and maintenance of >> an IANA-maintained module, and they include both instructions >> applicable to all IANA-maintained modules and instructions that >> can be customized by module creators. >>> >>> 5.3.1. Requirements for All Modules >>> >>> In particular, the following instructions should apply to all >> modules: >>> >>> * When an underlying registration is deprecated or obsoleted, a >> corresponding "status" substatement should be added to the >> identity or enumeration statement. >>> >>> * The "reference" substatement in the revision statement should >> point specifically to the published module (i.e., >> IANA_FOO_URL_With_REV). When the registration is triggered by an >> RFC, that RFC must also be included in the "reference" >> substatement. It may also point to an authoritative event >> triggering the update to the YANG module. In all cases, the event >> is cited from the underlying IANA registry. >>> >>> * References to documents should include titles. >>> >>> In addition, when the module is published, IANA must add the >> following notes to: >>> >>> The YANG Module Names registry: >>> New values must not be directly added to the "iana-foo" YANG >> module. They must instead be added to the "foo" registry. >>> >>> The underlying registry: >>> When this registry is modified, the YANG module "iana-foo" >> [IANA_FOO_URL] must be updated as defined in RFC IIII. >>> >>> 5.3.2. Requirements Subject to Customization >>> >>> Unless the creators of an IANA-maintained module specify >> otherwise in their document's IANA Considerations section, the >> following instructions will apply: >>> >>> * Unassigned and reserved values (including experimental values) >> will be omitted from the module. >>> >>> * The "reference" statement in an "identity" or "enum" >> substatement should mirror the underlying registry. It may point >> to contact names as well as documents. >>> >>> * In a revision statement, the "description" substatement >> captures >>> what changed in the revised version. Typically, the description >>> enumerates changes such as updates to existing entries (e.g., >> update a >>> description or a reference) or notes which identities were added >> or >>> had their status changed (e.g., deprecated, discouraged, or >> obsoleted). >>> >>> When such a description is not feasible, the description varies >> in accordance with the trigger for the update. >>> >>> If the update is triggered by an RFC, the "description" >> substatement should include or consist of this text: >>> "Applied updates as specified by RFC XXXX." >>> >>> If the registration policy for the registry does not require RFC >> publication (Section 4 of [RFC8126]), insert this text: >>> >>> "Applied updates as specified by the registration policy >>> <Some_IANA_policy>". >>> >>> [rfced] A few points: >>> >>> 1) Please review the following text: >>> >>> * When an underlying registration is deprecated or obsoleted, a >> corresponding "status" substatement should be added to the >> identity or enumeration statement. >>> >>> Should double quotes be added to make this "identity" or >> "enumeration" statements (double quotes and plural statement)? We >> also note that "identity" and "enum" substatements used in the >> text preceding this. Please confirm that these should not match >> (i.e., the lead in text is about substatements and the text above >> is about statements). >>> [Med] Please update to: >>> >>> NEW: >>> "identity" or "enum" statement. >>> >>> 2) We have updated to use "revision" statement (in quotes) or >> "description" etc. Please review any addition of quotation marks >> and let us know if these were general uses instead of statement >> names and we can revert if necessary. >>> [Med] ACK. >>> >>> 3) Should the following text be in double quotes in the >> template? Other parts of the template are not quoted... >>> >>> "Applied updates as specified by RFC XXXX." >>> >>> >>> and >>> >>> "Applied updates as specified by the registration policy >>> <Some_IANA_policy>". >>> >>> [Med] We can get rid of the double quotes here. >>> >>> The incorporation of the updates requested by IANA are >> reviewable in the most recent postings, which (again) are located >> at: >>> >>> The files have been posted here (please refresh): >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauthors%2Frfc9907.txt&data=05%7C02%7Cmohamed.boucadai >> r%40orange.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40 >> bfbc48b9253b6f5d20%7C0%7C0%7C639053960376744311%7CUnknown%7CTWFpbG >> Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs >> IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=cMyTtYIkdssVi5 >> PAAlmd62C7eyF5nYJyncByxw0z1wI%3D&reserved=0 >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauthors%2Frfc9907.pdf&data=05%7C02%7Cmohamed.boucadai >> r%40orange.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40 >> bfbc48b9253b6f5d20%7C0%7C0%7C639053960376753952%7CUnknown%7CTWFpbG >> Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs >> IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ToPrLdGHT3nFJj >> vFpcklCXIzRNppbPmcAv1MTwbosXE%3D&reserved=0 >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc- >> editor.org%2Fauthors%2Frfc9907.html&data=05%7C02%7Cmohamed.boucada >> ir%40orange.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b4 >> 0bfbc48b9253b6f5d20%7C0%7C0%7C639053960376763093%7CUnknown%7CTWFpb >> GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiI >> sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=z0SVmx%2F032y >> Rk8DVxSBCY7lyRDnH6qZ3gbiiW9MgX48%3D&reserved=0 >>> >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www. >>> rfc- >> editor.org%2Fauthors%2Frfc9907.xml&data=05%7C02%7Cmohamed.boucadai >>> >> r%40orange.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40 >> bfbc >>> >> 48b9253b6f5d20%7C0%7C0%7C639053960376772434%7CUnknown%7CTWFpbGZsb3 >> d8ey >>> >> JFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoi >> TWFp >>> >> bCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=6lneGDp8gzLZcInKWFRwWxgjsh >> bM73 >>> Wtnltn0q4Ggx8%3D&reserved=0 >>> >>> The related diff files have been posted here (please refresh): >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> diff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C89f3cbb6 >> ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C >> 0%7C639053960376781930%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR >> ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf >> Q%3D%3D%7C0%7C%7C%7C&sdata=mu2A1Nf4fTuoaRmN3%2FlsKaDLXMXoJ8moporjI >> 8EIDQQ%3D&reserved=0 (comprehensive) >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> rfcdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C89f3c >> bb6ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0 >> %7C0%7C639053960376791207%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGki >> OnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIj >> oyfQ%3D%3D%7C0%7C%7C%7C&sdata=7I%2BiPhKvO%2B%2FDcIx76WitWktrjnbPzG >> kxi24EH19KUkw%3D&reserved=0 (comprehensive side by side) >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> auth48diff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C89 >> f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d20% >> 7C0%7C0%7C639053960376800611%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hc >> GkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIld >> UIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=t9qDftn%2FprRozw2uDWazZfIPsgKsCw3 >> %2B5aYxMoeG9Wc%3D&reserved=0 (AUTH48 changes to date) >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> auth48rfcdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7 >> C89f3cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d >> 20%7C0%7C0%7C639053960376810248%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU >> 1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIs >> IldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=71Tt5ulaxNo6hZyyl531oN%2B522Mv >> lIqTHGDgVrMGzfk%3D&reserved=0 (AUTH48 changes side by side) >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www.rfc-editor.org%2Fauthors%2Frfc9907- >> lastdiff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C89f3 >> cbb6ffca48df781a08de6030d7d2%7C90c7a20af34b40bfbc48b9253b6f5d20%7C >> 0%7C0%7C639053960376819620%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGk >> iOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUI >> joyfQ%3D%3D%7C0%7C%7C%7C&sdata=cVP7FhAHdqomIjN5Bt%2FE%2Fq04MAnSLAq >> s0Pkg4dFuuxE%3D&reserved=0 (last version to this) >>> >>> >> https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F >> www. >>> rfc-editor.org%2Fauthors%2Frfc9907- >> lastrfcdiff.html&data=05%7C02%7Cmoh >>> >> amed.boucadair%40orange.com%7C89f3cbb6ffca48df781a08de6030d7d2%7C9 >> 0c7a >>> >> 20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639053960376828772%7CUnknown >> %7CT >>> >> WFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4 >> zMiI >>> >> sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=f8HnoOMGG7uCC >> dXkA >>> I5nqiKYl9o2IdPpNh4Zo6ikKXY%3D&reserved=0 (last version side by >> side) >>> >>> Thank you. >>> >>> Megan Ferguson >>> RFC Production Center >>> >>> >>> >>> >>> >> __________________________________________________________________ >> ____ >>> _____________________________________ >>> _ >>> 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. >>> > > ____________________________________________________________________________________________________________ > 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]
