Send kea-dev mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/kea-dev
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of kea-dev digest..."


Today's Topics:

   1. Re:  Licensing of Yang models (Tomek Mrugalski)
   2.  This list has become obsolete.... (Victoria Risk)


----------------------------------------------------------------------

Message: 1
Date: Thu, 20 Jan 2022 14:55:56 +0100
From: Tomek Mrugalski <[email protected]>
To: [email protected]
Subject: Re: [kea-dev] Licensing of Yang models
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8

On 07.01.2022 15:53, Roman Mashak wrote:
> KEA Dhcp comes with Netconf support and a handful of Yang modules in
> https://gitlab.isc.org/isc-projects/kea/-/tree/master/src/share/yang/modules
All my responses below apply to kea YANG modules.

There's also a handful of IETF modules. IIRC Kea can support
ietf-dhcpv6-server to some degree. They are coming from an earlier
version of the IETF draft. Link to the latest is:
https://datatracker.ietf.org/doc/html/draft-ietf-dhc-dhcpv6-yang-24.
According to its Copyright Notice on the first page, they're distributed
under Simplified BSD License with the copyright owner being IETF.

> However, I could not find under what license the Yang modules are
> distributed. Is it the same as the KEA-Dhcp package (i.e. Mozilla
> Public License v2.0)?
Yes. MPL 2.0.

> What happens if I modify the shipped Yang modules, 
Github has a good quick overview of the MPL2.0 license:
https://github.com/isc-projects/stork/blob/master/LICENSE
(Kea's LICENSE file has some extra text on it, so gitlab doesn't
recognize it, hence the link to Stork).

If in doubt, please do read the MPL 2.0 text. It's not that long.
In particular, see Sections 3.1 and 3.2.

> or add a new one,
> am I supposed to return the changes in the open source community?
MPL is file-based license. If you add a new file, it's up to you to
decide the license.

Obviously, this is not a legal advice. I'm not a lawyer.

Out of curiosity, what did you change or added in the YANG modules? We
gotten very little feedback for NETCONF implementation. Either it's
perfect or very few people use it. I'm a bit too old to believe in the
former ;)

Tomek


------------------------------

Message: 2
Date: Thu, 20 Jan 2022 17:33:23 -0500
From: Victoria Risk <[email protected]>
To: [email protected]
Subject: [kea-dev] This list has become obsolete....
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"

Hello folks,

We at ISC would like to shut down this list, and consolidate what little 
traffic there is with our other lists.

We have kea-users, and kea-announce, and our development environment, 
https://gitlab.isc.org/isc-projects/kea 
<https://gitlab.isc.org/isc-projects/kea> is completely open, so this list 
seems redundant.  There are 172 people subscribed, but only a handful actually 
post here and most months there is no traffic.

We will put the list into moderation, and plan to shut it down in about a 
month. If anyone has a strong objection, speak up! Otherwise, if you haven?t, 
go subscribe to [email protected] <mailto:[email protected]>, or, 
if you plan to submit patches to Kea, create an account at 
https://gitlab.isc.org/isc-projects/kea 
<https://gitlab.isc.org/isc-projects/kea>.

Regards,

Vicky Risk, ISC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://lists.isc.org/pipermail/kea-dev/attachments/20220120/3910291a/attachment-0001.htm>

------------------------------

Subject: Digest Footer

_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev


------------------------------

End of kea-dev Digest, Vol 76, Issue 3
**************************************

Reply via email to