Re: [OPSAWG] [Mud] I-D Action: draft-ietf-opsawg-ol-05.txt

Eliot Lear Tue, 23 Apr 2024 00:02:22 -0700

I'm sorry, Med.  I missed your original note.  We'll apply as suggested.


Eliot

On 23.04.2024 08:40, 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> De la part de Eliot Lear
Envoyé : lundi 22 avril 2024 20:02
À : Michael Richardson <mcr+i...@sandelman.ca>; opsawg@ietf.org;
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 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
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
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
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
      >

https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2
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>   . 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.

OpenPGP_0x87B66B46D9D27A33.asc
Description: OpenPGP public key

OpenPGP_signature.asc
Description: OpenPGP digital signature

_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

Re: [OPSAWG] [Mud] I-D Action: draft-ietf-opsawg-ol-05.txt

Reply via email to