Sure. We are happy to put up a LICENSE file in our repository (https://iotanalytics.unsw.edu.au/mudprofiles). It would be great if you could provide us with a simple template of such license, or we should develop one?
Once we put up the license, we can also augment the “systeminfo” field of every MUD profile with the URL of the license. For example, · systeminfo: "lifxbulb", becomes something like this: · systeminfo: "lifxbulb (https://iotanalytics.unsw.edu.au/mud/license.txt)", Your thoughts? Regards, Hassan From: Carsten Bormann <c...@tzi.org> Date: Friday, 4 June 2021 at 5:04 pm To: Hassan Habibi Gharakheili <h.hab...@unsw.edu.au> Cc: Eliot Lear <l...@lear.ch>, opsawg@ietf.org <opsawg@ietf.org> Subject: Re: [OPSAWG] Source attribution in MUD files (RFC 8520) On 2021-05-22, at 03:00, Hassan Habibi Gharakheili <h.hab...@unsw.edu.au> wrote: > > If I understood correctly, the two statements (you mentioned below) are > expected to be included in every published MUD profile. Right? > > That makes sense to me -- happy to help. Please do — even if you can’t put this into the files before the detailed YANG syntax is agreed, please put up a LICENSE file or some such now so that we can use your files in our curated repo. Grüße, Carsten
_______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
