On 2021-06-04, at 10:41, Hassan Habibi Gharakheili <[email protected]> wrote: > > 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?
Licenses are like crypto algorithms: They are better developed by specialized individuals and heavily cross-checked before being employed. I would go for OSI-approved licenses only. > 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? 3.7. systeminfo This is a textual UTF-8 description of the Thing to be connected. The intent is for administrators to be able to see a brief displayable description of the Thing. It SHOULD NOT exceed 60 characters worth of display space. I don’t think the admins want to be bothered with this in the place where they expect info about the Thing. That’s exactly why I suggested adding something to MUD. For now, as Eliot said, an SPDX-Identifier is the easiest way to reference a license. Choose between heavily used and sufficiently permissive licenses, e.g., 0BSD, MIT, BSD-3-Clause. Licenses that require the copier to copy the copyright as well are currently a bit icky, as that copyright cannot be reasonably put into the MUD file yet. 0BSD and especially MIT-0 look quite good from this perspective. https://spdx.org/licenses/ TL;DR: Just copy the text at https://spdx.org/licenses/MIT-0.html (after filling in the variables) and place it (the whole text) on https://iotanalytics.unsw.edu.au/mudprofiles for now. Grüße, Carsten > > Regards, > Hassan > > > From: Carsten Bormann <[email protected]> > Date: Friday, 4 June 2021 at 5:04 pm > To: Hassan Habibi Gharakheili <[email protected]> > Cc: Eliot Lear <[email protected]>, [email protected] <[email protected]> > Subject: Re: [OPSAWG] Source attribution in MUD files (RFC 8520) > > On 2021-05-22, at 03:00, Hassan Habibi Gharakheili <[email protected]> > 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 [email protected] https://www.ietf.org/mailman/listinfo/opsawg
