Hi Eliot, Thank you for addressing these. Please find some additional comments:
1. I created a PR for some minor points: https://github.com/elear/opsawg-ol/pull/3/files: TLP + follow the guidance for the list names. 2. I know that you don’t use the security template in 8520, but given that you are introducing a reusable module I think that you should include it this time. In particular, please see the template of the reusable grouping here: https://datatracker.ietf.org/doc/html/draft-ietf-netmod-rfc8407bis-11#name-security-considerations-sect (see the last two para). 3. From a YANG standpoint, I think that defining an “ol” feature would be cleaner than the current use of “extensions”. I know that this is inherited from 8520, but a clarification is needed here, especially that the grouping is a reusable one. 4. You may check with netmod whether they have any preference about keeping the ol grouping as part of the mud extension or be defined as a separate module. Cheers, Med De : Eliot Lear <l...@lear.ch> Envoyé : samedi 27 avril 2024 13:22 À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com>; Michael Richardson <mcr+i...@sandelman.ca>; opsawg@ietf.org; m...@ietf.org Objet : Re: [Mud] [OPSAWG] I-D Action: draft-ietf-opsawg-ol-05.txt Hi Med, I attempted to whack your changes into the draft. Carsten's merged the copy, so for ease of reading (and diffing) I'll post an update for your consideration. Michael, I don't think it's necessary in this case to update 8520 because we are indeed creating a new namespace. However, this wasn't properly indicated in the draft. Eliot On 23.04.2024 08:40, mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com> wrote: Hi all, Like Michael, I'm puzzled about the development of this draft. I raised comments back in 05/2021 that I reiterated during the call for adoption: https://mailarchive.ietf.org/arch/msg/opsawg/OlkjFOk55hB-29UG4FQaNbunXTY/ but still see the same issues in 2024. Putting aside the list/leaf-list thing, the other points are straightforward such as fixing a json example. Cheers, Med -----Message d'origine----- De : OPSAWG <opsawg-boun...@ietf.org><mailto:opsawg-boun...@ietf.org> De la part de Eliot Lear Envoyé : lundi 22 avril 2024 20:02 À : Michael Richardson <mcr+i...@sandelman.ca><mailto:mcr+i...@sandelman.ca>; opsawg@ietf.org<mailto:opsawg@ietf.org>; m...@ietf.org<mailto:m...@ietf.org> Objet : Re: [OPSAWG] [Mud] I-D Action: draft-ietf-opsawg-ol- 05.txt On 22.04.2024 19:29, Michael Richardson wrote: 0) Why is this document still kicking around the WG? (Too bad it doesn't have the word "mud" in the filename.) 1) I find the title confusing. 2) I don't think that AUGMENT does what you want, because YANG is not extensible in the way we are used to doing with IANA. 3) I think that you have to revise the MUD specification itself. internet-dra...@ietf.org<mailto:internet-dra...@ietf.org> wrote: > Internet-Draft draft-ietf-opsawg-ol-05.txt is now available. It is a work item > of the Operations and Management Area Working Group (OPSAWG) WG of the IETF. > Title: Ownership and licensing statements in YANG > Authors: Eliot Lear > Carsten Bormann > Name: draft-ietf-opsawg-ol-05.txt > Pages: 8 > Dates: 2024-04-18 > Abstract: > This memo provides for an extension to RFC 8520 that allows MUD file > authors to specify ownership and licensing of MUD files themselves. > This memo updates RFC 8520. However, it can also be used for > purposes outside of MUD, and the grouping is structured as such. > The IETF datatracker status page for this Internet-Draft is: > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%252> Fdata tracker.ietf.org%2Fdoc%2Fdraft-ietf-opsawg- ol%2F&data=05%7C02%7Cmohame d.boucadair%40orange.com%7C92093d31adb04e54433408dc62f660b8%7C90c 7a20a f34b40bfbc48b9253b6f5d20%7C0%7C0%7C638494057558027066%7CUnknown%7 CTWFp bGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXV CI6Mn 0%3D%7C0%7C%7C%7C&sdata=evbyUZ0QB67LVPRNDJMok1EDqirGGX3LRl5lcZBXY %2FA% 3D&reserved=0 > There is also an HTML version available at: > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%252> Fwww. ietf.org%2Farchive%2Fid%2Fdraft-ietf-opsawg-ol- 05.html&data=05%7C02%7C mohamed.boucadair%40orange.com%7C92093d31adb04e54433408dc62f660b8 %7C90 c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638494057558035784%7CUnk nown% 7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWw iLCJX VCI6Mn0%3D%7C0%7C%7C%7C&sdata=ALyUu59W4HpqkNgltW2MR3tMIP0Oy7g2lx0 eMO2B WFw%3D&reserved=0 > A diff from the previous version is available at: > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%252> Fauth or-tools.ietf.org%2Fiddiff%3Furl2%3Ddraft-ietf-opsawg-ol- 05&data=05%7C 02%7Cmohamed.boucadair%40orange.com%7C92093d31adb04e54433408dc62f 660b8 %7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638494057558042269% 7CUnk nown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik 1haWw iLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=AuV0M7yp48hbdOAfzjyMxgo8hTJruD g7ijp dwVJhrCY%3D&reserved=0 > Internet-Drafts are also available by rsync at: > rsync.ietf.org::internet-drafts > _______________________________________________ > OPSAWG mailing list > OPSAWG@ietf.org<mailto:OPSAWG@ietf.org> > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%252> Fwww. ietf.org%2Fmailman%2Flistinfo%2Fopsawg&data=05%7C02%7Cmohamed.bou cadai r%40orange.com%7C92093d31adb04e54433408dc62f660b8%7C90c7a20af34b4 0bfbc 48b9253b6f5d20%7C0%7C0%7C638494057558048845%7CUnknown%7CTWFpbGZsb 3d8ey JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D% 7C0%7 C%7C%7C&sdata=dMV04fnfSh7yh8zTnekcIFHOpK5FAVqp8aKEMh0U8bQ%3D&rese rved= 0 -- Michael Richardson <mcr+i...@sandelman.ca><mailto:mcr+i...@sandelman.ca> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide ____________________________________________________________________________________________________________ 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.
_______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
