Hi Megan, Mahesh, all # Sections 4.30.3.1./4.30.3.2.
CURRENT: This template ends with a section labeled "Optional". I would revert the change (my preference) or delete the remaining sentence as this sentence does not add much now. The initial intent of the full para (agreed with IANA) was to explain the customization. A relevant comment was added to the template itself to prevent blind copy/paste. Yes, some may not read the preamble. # Section 3.9 That new text was added to address a comment both Mahesh and myself discussed with the RFC editor team and which was echoed in this question: 20) <!--[rfced] Would you like to add examples of "reference" substatements? The RPC and OPS ADs discussed this topic during IETF 123. The examples would show that the RFC title does not need to be included. (The exception is in the "revision" statement, where the title is typically included.) For example: reference (with section) "RFC 8665, Section 5 RFC 8666, Section 6"; reference (just RFC number) "RFC 8665 RFC 8666"; --> If I remember well, this is also to simplify the required reference checks/overload for the RFC Editor team (?). BTW, this practice is already followed by authors, see for example a recent document that went IESG review: https://datatracker.ietf.org/doc/draft-ietf-teas-yang-te/. Removing that new text does not imply that practice is not allowed. Cheers, Med > -----Message d'origine----- > De : Megan Ferguson <[email protected]> > Envoyé : vendredi 13 février 2026 01:12 > À : Mahesh Jethanandani <[email protected]> > Cc : BOUCADAIR Mohamed INNOV/NET <[email protected]>; > [email protected]; RFC Editor <[email protected]>; Andy > Bierman <[email protected]>; [email protected]; netmod- > [email protected]; [email protected]; auth48archive@rfc- > editor.org; [email protected] > Objet : Re: [AD] [IANA] AUTH48: RFC-to-be 9907 <draft-ietf-netmod- > rfc8407bis-28> for your review > > > Mahesh, > > Sounds good. We have incorporated the change to “Optional”. We > believe that closes out Issues 2 and 4 from our previous mail. > > So we will wait to hear back: > > -from the authors regarding Issue 1 (the added text to Section > 3.9) > -that the wiki page has been updated (Issue 3) > > prior to moving this document forward. > > 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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C639065383593201970%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=XzDxvhwMgGnkim > EwjLmuFREy3kuOrrAYiEwDwWz92fc%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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C639065383593249793%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=YB0GmN63BQyIvU > lD4FtgoG2iuWGS0ZKmZ%2BOkQvdSm0A%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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b4 > 0bfbc48b9253b6f5d20%7C0%7C0%7C639065383593274720%7CUnknown%7CTWFpb > GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiI > sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=0Fya%2FWYRmji > eYpnJMW%2B1m0UCeF1GbESb1gDoUQKC7Kk%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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C639065383593293346%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=dnbk4Uu3c8uioc > 2Ou4qfdanIwG3CiT1STwaMRm0qj%2Bg%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%7C39078eca > 2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C > 0%7C639065383593309641%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR > ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf > Q%3D%3D%7C0%7C%7C%7C&sdata=i3O%2BosKZfuca%2FzegQ3bDhw%2F8sf0SgNwjc > 3bTnx3k50Y%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%7C39078 > eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0 > %7C0%7C639065383593325317%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGki > OnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIj > oyfQ%3D%3D%7C0%7C%7C%7C&sdata=nIKN0RP6sC4Xj0CQ8wcD9VILPLf%2BL9fF7s > pIFIhl%2B%2FE%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%7C39 > 078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20% > 7C0%7C0%7C639065383593339902%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hc > GkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIld > UIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=NNcSLrnnoxPTN8n1ccBovDx5ytuO7ZLmA > 1VkKGAg1Hw%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 > C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d > 20%7C0%7C0%7C639065383593356748%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU > 1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIs > IldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=OoRQTCumFYk1vcSIONq2vmUvK18FL2 > nh9K9h%2BsqWcaw%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%7C3907 > 8eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C > 0%7C0%7C639065383593372347%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGk > iOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUI > joyfQ%3D%3D%7C0%7C%7C%7C&sdata=YQbsLMtdmWQ%2BnVebXSONmPa%2FG3E0CL9 > 6NQ9IvBhc%2FIQ%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%7C3 > 9078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20 > %7C0%7C0%7C639065383593386173%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1h > cGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIl > dUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ITOmCFbAum6uB1RMldW7P69L9ei7y9qC > lalgNtQJM1k%3D&reserved=0 (last version side by side) > > The AUTH48 status page is viewable 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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc4 > 8b9253b6f5d20%7C0%7C0%7C639065383593402654%7CUnknown%7CTWFpbGZsb3d > 8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOI > joiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=EXFse1gLrCaf1aBzovW > od0pb8y%2BXmccfd2EKn%2BbRvhY%3D&reserved=0 > > Thank you. > > Megan Ferguson > RFC Production Center > > > On Feb 12, 2026, at 4:32 PM, Mahesh Jethanandani > <[email protected]> wrote: > > > > Hi Megan, > > > >> On Feb 12, 2026, at 2:54 PM, Megan Ferguson > <[email protected]> wrote: > >> > >> Hi Mahesh, > >> > >> Thanks for the quick reply! > >> > >> Some follow-ups below marked with [rfced]. > >> > >> Thank you. > >> > >> Megan Ferguson > >> RFC Production Center > >> > >>>> > >>>> > >>>> Issue #2: Redundant text in Section 4.30.3.1: > >>>> > >>>> We have updated to remove the text from the first paragraph > in this section as Mahesh suggested. > >>>> > >>>> Out of curiosity, is this a BCP 14 OPTIONAL? Or is this all > caps just to call attention to it? > >>>> > >>>> Current: > >>>> This template ends with a section labeled "OPTIONAL”. > >>> > >>> My take is that it is not. It just happens to be all caps, and > it just happens to be one of the keywords from BCP 14. If we want > to disambiguate, we could call it TEMPLATE. > >> > >> [rfced] Could we simply have this appear as “Optional” (as it > is inside a template)? > >> > >> Note that this would include a change in multiple places (twice > in both Sections 4.30.3.1 and 4.30.3.2). > >> > >> Current: > >> This template ends with a section labeled "OPTIONAL”. > >> … > >> -- OPTIONAL: > >> > >> Perhaps: > >> This template ends with a section labeled "Optional”. > >> … > >> --Optional: > > > > I am ok with that > > > >> > >> > >> > >> Further related clean up: > >> a) This discussion made me realize that we had not updated the > <CODE BEGINS> and <CODE ENDS> tags used in Sections 4.30.3.1 and > 4.30.3.2 to instead use <BEGIN TEMPLATE TEXT> and <END TEMPLATE > TEXT> (as we had done in the security considerations template > section (see discussion with Med below)). This change has now been > incorporated (please refresh links to view). > >> > >> Note also that we made the following related change to the > change log: > >> > >> Original: > >> * Added code markers for the security template. > >> > >> Current: > >> * Added template markers for the security template. > > > > I do agree that it is not code, and using code markers would be > odd. Thanks for updating them to use template markers. > > > >> > >> b) Note also that we have removed the following text from > Section 4.30.3.2 (to match its removal in 4.30.3.1). > >> > >> Original: > >> > >> 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 section. > >> > >> Current: > >> This template ends with a section labeled "OPTIONAL”. > > > > Thanks for catching that. > > > > Cheers. > > > >> > >> > >> > >>>>> b) In contrast, regarding your note (about Section 3.7.1): > >>>>> * Added code markers for the security template. > >>>>> > >>>>> Why are the code markers being used for the security > >>>>> considerations > >>>>> template? It seems odd because it is prose, not code. > >>>> > >>>> [Med] This one was requested by the trust. Please see > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > datatracker.ietf.org%2Fmeeting%2F116%2Fmaterials%2Fslides-116- > netmod-05-security-considerations-template-for-yang-module- > documents- > 00&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C39078eca2c854aa > b7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639 > 065383593420259%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIl > YiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D > %7C0%7C%7C%7C&sdata=Wfgbm9Hm%2FJ%2Bswg3TibMopgJW32ku7dniR2ktJ0dZZS > 0%3D&reserved=0 or > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > mailarchive.ietf.org%2Farch%2Fmsg%2Fnetmod%2FgBEuz3mgOuyghmeQk7T4s > o_ZxF8%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C39078eca > 2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C > 0%7C639065383593436342%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR > ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf > Q%3D%3D%7C0%7C%7C%7C&sdata=ePsoWXIhj8LSchGe3ErP17HRlYaC2GXkbwOgxWS > eG4o%3D&reserved=0. > >>>> > >>>>> > >>>>> c) Similarly, why are code markers used for the templates > >>>>> in Sections 4.30.3.1 and 4.30.3.2? > >>>> > >>>> [Med] For the same reasons as above. > >>> > >>> Might it be possible to update to <BEGIN TEMPLATE TEXT> and > <END TEMPLATE TEXT> instead? Additionally, should the following > paragraph from the TLP should be included? > >>> > >>> From > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > trustee.ietf.org%2Fdocuments%2Ftrust-legal-provisions%2Ftlp- > 5%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C39078eca2c854 > aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6 > 39065383593452621%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUs > IlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D% > 3D%7C0%7C%7C%7C&sdata=cGpUlA6lI88Uric7AwV3NFHflA17tEV5MW%2FR8NZXu9 > A%3D&reserved=0 (which is linked to from > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > datatracker.ietf.org%2Fmeeting%2F116%2Fmaterials%2Fslides-116- > netmod-05-security-considerations-template-for-yang-module- > documents- > 00&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C39078eca2c854aa > b7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C639 > 065383593470383%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIl > YiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D > %7C0%7C%7C%7C&sdata=2FYg88rBxgu1DmocUfP6dw9DepNJBf%2BpsMKzROuaYzM% > 3D&reserved=0): > >>> > >>> Section 9. Template Text > >>> a. Certain RFCs may contain text designated as “Template Text” > by the inclusion of the following legend in the introduction to > the RFC: > >>> > >>> “This RFC contains text intended for use as a template as > designated below by the markers <BEGIN TEMPLATE TEXT> and <END > TEMPLATE TEXT> or other clear designation. Such Template Text is > subject to the provisions of Section 9(b) of the Trust Legal > Provisions.” > >> > >>> [Med] Works for me. Thanks > >> > >> > >>> > >>>> > >>>> > >>>> > >>>> Issue #3: The wiki page update to make > 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%7C39078ec > a2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7 > C0%7C639065383593489275%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOn > RydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoy > fQ%3D%3D%7C0%7C%7C%7C&sdata=25g1CfGTw6%2Fi0cLX%2FH6Fei6ffGP1Q8j2nb > EZpAZGX%2FI%3D&reserved=0? match the template in the document: > >>>> > >>>> Note that we have added this as an “approver” on the AUTH48 > status page at > 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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc4 > 8b9253b6f5d20%7C0%7C0%7C639065383593508067%7CUnknown%7CTWFpbGZsb3d > 8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOI > joiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=fdtWkF1cWK9sIHCtcm1 > %2FHiQZecSZN4%2BKFRpMRcyWQ20%3D&reserved=0 to ensure we match up > differences between the doc and that page prior to publication. > >>>> > >>>> In addition to updating to point to this document’s RFC > number (once it is published), we think the following still need > to be updated on the wiki page prior to publication (also viewable > in the diff at > https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > www.rfc-editor.org%2Fauthors%2Frfc9907-wiki- > diff.html&data=05%7C02%7Cmohamed.boucadair%40orange.com%7C39078eca > 2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C > 0%7C639065383593524187%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR > ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf > Q%3D%3D%7C0%7C%7C%7C&sdata=ntLH%2FlvomLtImePwD6JlsCjFkYTuSD%2FjfgT > ubLxZU%2BY%3D&reserved=0): > >>>> > >>>> Current (at wiki): > >>>> The Network Configuration Access Control Model (NACM) > [RFC8341] provides the means to restrict access for particular > NETCONF or... > >>>> > >>>> Perhaps (to match document): > >>>> The Network Configuration Access Control Model (NACM) > [RFC8341] provides the means to restrict access for particular > Network Configuration Protocol (NETCONF) or... > >>>> > >>>> Current (at wiki): > >>>> All writable data nodes are likely to be sensitive... > >>>> > >>>> Perhaps (to match document): > >>>> All writable data nodes are likely to be reasonably > sensitive… > >>>> > >>>> Current (at wiki): > >>>> ...e.g., ones that might be protected by a "nacm:default- > deny-write”... > >>>> > >>>> Perhaps (to match document): > >>>> ...e.g., ones that might be protected by a "nacm:default- > deny-write”… > >>> > >>> Hmm. I am not sure if I am seeing a difference. > >> > >> [rfced] Sorry - copy and paste error: > >> > >> Perhaps: > >> ...e.g., ones that are protected by a "nacm:default-deny- > write”… > >> > >>> > >>>> > >>>> Current (at wiki): > >>>> ...or get-config) are particularly sensitive or vulnerable… > >>>> > >>>> Perhaps (to match document): > >>>> ...or get-config) that are particularly sensitive or > vulnerable… > >>>> > >>>> Current (at wiki): > >>>> ...readable data nodes are ones that might be protected by a… > >>>> > >>>> Perhaps (to match document): > >>>> ...readable data nodes are ones that are protected by a… > >>>> > >>>> Current (at wiki): > >>>> ...then add this text to remind the specific sensitivity… > >>>> > >>>> Perhaps (to match document): > >>>> ...then add this text as a reminder of the specific > sensitivity… > >>>> > >>>> > >>>> > >>>> Issue #4: Our request for AD approval of Med’s suggestion. > >>>> > >>>> *Mahesh - please review and approve the following change: > >>>> > >>>> OLD: > >>>> The IANA Considerations Section MAY also provide the > following > >>>> information if a default action is expected: > >>>> > >>>> NEW: > >>>> The IANA Considerations Section MAY also provide the > following > >>>> information if a default action is to be overridden: > >>> > >>> I am ok with this change. > >>> > >>> Thanks for checking. > >> > >> [rfced] No problem. We have recorded your approval of this > change in the Notes field of the AUTH48 status page, but have left > your “Approval” field blank until the issue with the text in > Section 3.9 issue is resolved (we believe we’ve heard back from > you approving all other changes we requested - thank you!). > >>> > >>>> > >>>> Please review our updates carefully as we do not make changes > once the document is published as an RFC. > >>>> Please contact us with any further changes you may have. > >>>> > >>>> 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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C639065383593542855%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=xLceZBOSxIjIs6 > yPOwP%2Fah82rG6%2FemSyhusvyTuZZJE%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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C639065383593592063%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=jdyllRVcvqTta1 > qm2aHVxeu43CJeL3d3yD5P6V%2F42g8%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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b4 > 0bfbc48b9253b6f5d20%7C0%7C0%7C639065383593634108%7CUnknown%7CTWFpb > GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiI > sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=GuVNdBFpDleIu > lO0ws%2Blup2t%2Bi3c2S%2BQauHFviFABSY%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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C639065383593655966%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=IzZcmDQpKPFZ8L > 2kf%2Bdph3%2FWhpcr3EoqLjFsSEDRPf4%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%7C39078eca > 2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C > 0%7C639065383593674421%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR > ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf > Q%3D%3D%7C0%7C%7C%7C&sdata=SvN5dyltTFtAXMXFgGI1KQyWUkOdmdPCWYjF2Nl > NkK4%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%7C39078 > eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0 > %7C0%7C639065383593691732%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGki > OnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIj > oyfQ%3D%3D%7C0%7C%7C%7C&sdata=Ka0ATGu3ipl0Qwb6DnnrLjJdXkHrzV8o%2BQ > vQT8AlqmY%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%7C39 > 078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20% > 7C0%7C0%7C639065383593711381%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hc > GkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIld > UIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=tVAmhyJRnR9kj5eeZrRT1Aja9iW%2BrD4 > LXLb7xJTDPMs%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 > C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d > 20%7C0%7C0%7C639065383593728764%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU > 1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIs > IldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2FDAuMCBgT2Z3celwIQSdf3bqXtPS > otUdup3daKnNfF4%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%7C3907 > 8eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C > 0%7C0%7C639065383593747290%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGk > iOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUI > joyfQ%3D%3D%7C0%7C%7C%7C&sdata=npnNXeqH035aaIi7wCi909iHwzZ5ER7ftvA > 5IQ0o8zE%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%7C3 > 9078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20 > %7C0%7C0%7C639065383593764878%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1h > cGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIl > dUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=GpkgHfWr6BgtmInKA3uFz%2BYbPauq2Z > IqnDbqtSb7JLw%3D&reserved=0 (last version side by side) > >>>> > >>>> The AUTH48 status page is viewable 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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc4 > 8b9253b6f5d20%7C0%7C0%7C639065383593783733%7CUnknown%7CTWFpbGZsb3d > 8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOI > joiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=l4dXdw8k9IMMMTPcz4A > JpuUCDmu6QoqrrLD3ziM7dBg%3D&reserved=0 > >>>> > >>>> Thank you. > >>>> > >>>> Megan Ferguson > >>>> RFC Production Center > >>>> > >>>> > >>>>> On Feb 10, 2026, at 8:39 PM, Mahesh Jethanandani > <[email protected]> wrote: > >>>>> > >>>>> Hi Megan, > >>>>> > >>>>>> On Jan 26, 2026, at 12:13 PM, Megan Ferguson > <[email protected]> wrote: > >>>>>> > >>>>>> 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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc4 > 8b9253b6f5d20%7C0%7C0%7C639065383593802739%7CUnknown%7CTWFpbGZsb3d > 8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOI > joiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=goNOcdvIJsH8qxzKN3% > 2F48fupkQ0P7C3uaByyLL4Mkn8%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%7C39 > 078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20% > 7C0%7C0%7C639065383593821376%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hc > GkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIld > UIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=RNqyrb0weRmD4LM90uu0yif058d5BIRlv > lrhMtIvHfs%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%7Cmohamed.boucadair%40orange.com%7 > C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d > 20%7C0%7C0%7C639065383594176291%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU > 1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIs > IldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=SYN9rGisKXmnxIoNRO%2BJ8ElzKJdV > sca3tp157BA18XI%3D&reserved=0 (AUTH48 side by side) > >>>>>> > >>>>>> We have also attached a screenshot of the piece in question > for your convenience. > >>>>>> > >>>>>> <Screen Shot 2026-01-16 at 10.25.54 AM.png> > >>>>> > >>>>> Thanks for sharing the screenshot of the set of changes. I > went and looked at all the revisions of the document including - > 25, the version approved by IESG. This whole text is a completely > new addition, and was never approved by the WG or by IESG. As > such, this cannot be approved, unless we poll the WG regarding the > change. Alternatively, we can just drop this new text. I will also > note that in later in the document, when it comes to IANA modules, > we insist that the reference statement contain the title of the > RFC. As such, these guidances are contradicting each other. > >>>>> > >>>>> Separately, I will note that in Section 4.30.3.1 this text > is repeated twice. The first time in the first paragraph: > >>>>> > >>>>> 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 section. > >>>>> > >>>>> and later in the “OPTIONAL” section: > >>>>> > >>>>> -- Include only text that needs to be customized for the > module. > >>>>> -- Text that does not require customization should be > >>>>> -- omitted. > >>>>> > >>>>> Do we need it twice? Maybe remove the new text in the first > paragraph?? > >>>>> > >>>>>> > >>>>>> 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%7C39078ec > a2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7 > C0%7C639065383594220833%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOn > RydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoy > fQ%3D%3D%7C0%7C%7C%7C&sdata=m2USeL1ZnTi4ZRRFf6bHxvHiDGBOa5a3fQaibl > %2BOL8o%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%7Cmohamed.boucadair%40orange.com%7C39078eca > 2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C > 0%7C639065383594245668%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR > ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf > Q%3D%3D%7C0%7C%7C%7C&sdata=9XkYk4kseO%2FMVwfuEtJuf8OVmTp9SZdqSBXfy > UuS0t4%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. > >>>>> > >>>>> Ok. > >>>>> > >>>>>> > >>>>>> > >>>>>> 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%7C39078eca2c > 854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0% > 7C639065383594264027%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRyd > WUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ% > 3D%3D%7C0%7C%7C%7C&sdata=g4kDPofY2hB6Y65KlD8TrYSlCuT%2Bj3onxdMpw9U > K6Ds%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%7C39078eca2c854 > aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6 > 39065383594282565%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUs > IlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D% > 3D%7C0%7C%7C%7C&sdata=DXvubJrq1TEjILMi%2BKE8uquJq5c0csZJtpcWrT8asu > c%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. > >>>>> > >>>>> Ok. > >>>>> > >>>>>> > >>>>>> > >>>>>> 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). > >>>>> > >>>>> I have reviewed these changes and approve of them. > >>>>> > >>>>> Thanks > >>>>> > >>>>>> > >>>>>> 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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C639065383594301458%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=UyrSC8DZXOXO6T > UGZ5kjqBeYiycZoXS6v8C4G5oQOI0%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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C639065383594320389%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=pPGd%2FYJNA6%2 > BV0lvFFYczNuvWYKRvM%2F1pF0hX094xI0A%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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b4 > 0bfbc48b9253b6f5d20%7C0%7C0%7C639065383594338959%7CUnknown%7CTWFpb > GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiI > sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Grolthrh%2FIH > r%2Bj%2Fq8%2Fw9yvkbSHva7zs3RhUej7YIMFE%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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C639065383594357990%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=th25jjUeCxTPpn > 1RQDNPP6xP%2FAHR1WHPOY9e9NZfXQc%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%7C39078eca > 2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C > 0%7C639065383594375184%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR > ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf > Q%3D%3D%7C0%7C%7C%7C&sdata=ThJJ3XSsU0v6vFbY%2Bh8FaUKEqgfe9HOKo78BL > 6XVVzA%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%7C39078 > eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0 > %7C0%7C639065383594392286%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGki > OnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIj > oyfQ%3D%3D%7C0%7C%7C%7C&sdata=UHZGwDeczNT4rQVQgGR5hQxLuT8q6hQwuBtC > 5cILnNE%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%7C39 > 078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20% > 7C0%7C0%7C639065383594410012%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hc > GkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIld > UIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=b5UduzpVDzFeZ8l2cgR7sXJsZr3Egy8U1 > zZiPnycswY%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 > C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d > 20%7C0%7C0%7C639065383594426071%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU > 1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIs > IldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=4kJwSj%2F2G2easNW4aYElwdRxWZJp > sKZSrLbhJLZgr3s%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%7C3907 > 8eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C > 0%7C0%7C639065383594441481%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGk > iOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUI > joyfQ%3D%3D%7C0%7C%7C%7C&sdata=APHhyWDXWuhNA2U6lLEnR2i4X2Rixr9mPlF > YmXzE%2Bsw%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%7C3 > 9078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20 > %7C0%7C0%7C639065383594456542%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1h > cGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIl > dUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=PD9inrxJTcW7mhfnSfP0wXnVNVVsGDE1 > pdJz7I5LUWs%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. > >>>>>>> > >>>>>>>> > >>>>>>>> 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”. > >>>>>> > >>>>>> -Should any quotes be added here? > >>>>>> "YANG module namespace statement" (see also namespace > statement without YANG module before). > >>>>>> > >>>>>> -Should “definition” be double-quoted in the following or > other instances of “data definition statement"? > >>>>>> “...all top-level data definition statements…" > >>>>>> > >>>>>> -We see this use of “extensions statement”; should double > quotes be used? > >>>>>> “…or a “nacm:default-deny-all” extensions statement, then > those…" > >>>>>> > >>>>>> -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? > >>>>>> > >>>>>> -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 > >>>>>> > >>>>>> -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...” > >>>>>> > >>>>>> > >>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> 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. > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>> > >>>>>>> > >>>>>>>> > >>>>>>>>>> "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. > >>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>>>> 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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C639065383594470826%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=jR0ZQ0HvkB1Ctf > E4yOa5YtRbJmiJcUE2J7mZtw136Vw%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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C639065383594512352%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=4p2Nl6ODb9QL8u > A1SNZ7Qs8fEFTufpNSeMdlTvgPAXM%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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b4 > 0bfbc48b9253b6f5d20%7C0%7C0%7C639065383594544582%7CUnknown%7CTWFpb > GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiI > sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=FTuNHC8KLTpmo > fHu6ZeI7UCa4QGEPfQobAHntRgtdSI%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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C639065383594562126%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2FNXS0GLprfpa > VMy5%2F%2Ff8BYtsWYyZZ7N4rm8dujg8Op0%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%7C39078eca > 2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C > 0%7C639065383594576118%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR > ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf > Q%3D%3D%7C0%7C%7C%7C&sdata=xDBmCoQ7VFBziI3pyrKNosDIjhcri3eqPOTB5C2 > OVpU%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%7C39078 > eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0 > %7C0%7C639065383594590644%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGki > OnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIj > oyfQ%3D%3D%7C0%7C%7C%7C&sdata=O8JD3R5C8MTN4zyAwzFCkcbCesuVkL9xhdQg > JL%2FwQew%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%7C39 > 078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20% > 7C0%7C0%7C639065383594602996%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hc > GkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIld > UIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=t%2BGTYnlAy4TiHkNeMbrwp%2F%2FmbIb > 8pviX5QavxeAvj1I%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 > C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d > 20%7C0%7C0%7C639065383594616786%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU > 1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIs > IldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=13kZcRxmTj992DcX3ee1Wd7WYgnJM2 > rQKfqOA3UluSQ%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%7C3907 > 8eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C > 0%7C0%7C639065383594630649%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGk > iOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUI > joyfQ%3D%3D%7C0%7C%7C%7C&sdata=hjkiF7escsQW5PECxJ8VTYGFGaK5n0AAOCK > RP%2BPD4XQ%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%7C3 > 9078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20 > %7C0%7C0%7C639065383594645038%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1h > cGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIl > dUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=7UqUU5qvgZYC8o%2FQ6xvwAw1bzYzOXZ > E0UVqjv6OPKg4%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. > >>>>>>> > >>>>>>> ========================================== > >>>>>>> > >>>>>>> 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. > >>>>>>> > >>>>>>> ========================================== > >>>>>>> > >>>>>>> 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). > >>>>>>> > >>>>>>> ========================================== > >>>>>>> > >>>>>>> 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). > >>>>>> > >>>>>> 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. > >>>>>> > >>>>>> 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>". > >>>>>> > >>>>>> 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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C639065383594686798%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ZQ26cMp4vsqTAk > Yo2cUvmcaQHDBD6GLwmsMQFLA9Wdw%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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C639065383594706318%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=6jnZL39DF6Scs9 > ARICPdcJ1iVDxIn13pzOGDb34Ra%2Fk%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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b4 > 0bfbc48b9253b6f5d20%7C0%7C0%7C639065383594721821%7CUnknown%7CTWFpb > GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiI > sIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=r%2BPa5ehEend > uIkCEicv6isnlIKc8FTkkGsszsKWLs0M%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%7C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40 > bfbc48b9253b6f5d20%7C0%7C0%7C639065383594739029%7CUnknown%7CTWFpbG > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=GieBy8LQf4qgnM > AS6pseoQx%2BS1rwrF6u9v7w502dOSg%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%7C39078eca > 2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C > 0%7C639065383594756045%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR > ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf > Q%3D%3D%7C0%7C%7C%7C&sdata=yvy4uC8zvsuO68zzKOABsXotWANBCH86TkfMvRg > A1fM%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%7C39078 > eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0 > %7C0%7C639065383594773074%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGki > OnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIj > oyfQ%3D%3D%7C0%7C%7C%7C&sdata=997lfj8v2eut8F4Dn8enEUikLEH6LR%2Fc0N > ly1fqhw6w%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%7C39 > 078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20% > 7C0%7C0%7C639065383594789466%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hc > GkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIld > UIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=URSXNzH%2Be%2FEB2MuqTG4SsxLKqUC6S > 7uNZu3uSb0SDSM%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 > C39078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d > 20%7C0%7C0%7C639065383594806894%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU > 1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIs > IldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=xFWE9d5DZhiee8VUDe3kGcA0uIR3ef > foyaDmMt%2FKCkU%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%7C3907 > 8eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20%7C > 0%7C0%7C639065383594824201%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGk > iOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUI > joyfQ%3D%3D%7C0%7C%7C%7C&sdata=GkPCn8rgB7sd4CaOJhEMgFK9fhuEk5bE8QN > f8ddnBA0%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%7C3 > 9078eca2c854aab7f8e08de6a948313%7C90c7a20af34b40bfbc48b9253b6f5d20 > %7C0%7C0%7C639065383594841426%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1h > cGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIl > dUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=KgzAw%2BVG9MoJYWB5hzCbciX8i9PBxY > MjTP0Z0jl1vjA%3D&reserved=0 (last version side by side) > >>>>>> > >>>>>> Thank you. > >>>>>> > >>>>>> Megan Ferguson > >>>>>> RFC Production Center > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>> > >>>>> > >>>>> Mahesh Jethanandani > >>>>> [email protected] > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>> > >>> > >>> > >>> Mahesh Jethanandani > >>> [email protected] > >> > > > > > > Mahesh Jethanandani > > [email protected] > > > > > > > > > > > > > ____________________________________________________________________________________________________________ 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]
