Re: [License-discuss] For Discussion: Cryptographic Autonomy License (CAL) Beta 2

2019-08-15 Thread Henrik Ingo
> > > Also: > On Thu, Aug 15, 2019 at 9:54 AM Henrik Ingo > wrote: > >> [snip] >> - I don't support the underlying goal of making money and attacking >> competing implementations. >> > > For the record, this is not the goal. The goal is to create a platform > that is resistant to attempts to unde

Re: [License-discuss] For Discussion: Cryptographic Autonomy License (CAL) Beta 2

2019-08-15 Thread VanL
Hi Henrik, There is a catch-22 here. I am trying to represent the law as I understand it. When I was explicit about my understanding of the consequences of the law, I was criticized for expressing it. Now, you criticize me for vagueness. But if there is vagueness, it is because the law is vague.

Re: [License-discuss] For Discussion: Cryptographic Autonomy License (CAL) Beta 2

2019-08-15 Thread Henrik Ingo
On Thu, Aug 15, 2019 at 3:00 PM VanL wrote: > Hi Henrik, > > On Thu, Aug 15, 2019, 6:16 AM Henrik Ingo > wrote: > >> >> Forgive me, but that is just a redundant statement that is legal weasel >> wording. You're essentially still saying that if an API could be protected >> by copyright, in some j

Re: [License-discuss] For Discussion: Cryptographic Autonomy License (CAL) Beta 2

2019-08-15 Thread VanL
Hi Henrik, On Thu, Aug 15, 2019, 6:16 AM Henrik Ingo wrote: > > Forgive me, but that is just a redundant statement that is legal weasel > wording. You're essentially still saying that if an API could be protected > by copyright, in some jurisdiction, then the CAL would still claim those > rights

Re: [License-discuss] For Discussion: Cryptographic Autonomy License (CAL) Beta 2

2019-08-15 Thread VanL
Hi Bruce, > > Haven't you just very clearly characterized this term as a use > restriction? And doesn't this way of stating it make it very clear it's in > contravention of OSD #6? It would certainly be a field of endeavor to run > the program for anyone but yourself, or for anything but a private

Re: [License-discuss] For Discussion: Cryptographic Autonomy License (CAL) Beta 2

2019-08-15 Thread VanL
Hi Roger, Thanks for creating a specific hypothetical. On Wed, Aug 14, 2019, 10:56 PM Roger Fujii wrote: > > *So, let's concoct an example. I have an authentication db which has > username/passwords. I have another separate db that has all sorts of data > on the username. To get a username/pass

Re: [License-discuss] For Discussion: Cryptographic Autonomy License (CAL) Beta 2

2019-08-15 Thread Henrik Ingo
On Wed, Aug 14, 2019 at 5:55 PM VanL wrote: > Hi Lukas, > > Thanks for your comments.In general, the patent termination provision was > crafted to deal with the actual types of patent attacks I most usually see > around open source - a company, frequently an NPE, will assert a patent > against a

Re: [License-discuss] For Discussion: Cryptographic Autonomy License (CAL) Beta 2

2019-08-15 Thread Henrik Ingo
On Wed, Aug 14, 2019 at 5:35 PM VanL wrote: > On Wed, Aug 14, 2019 at 8:02 AM Henrik Ingo > wrote: > >> Data autonomy >> >> Wrt the discussion of not encumbering mere use / private use with any >> obligations, I notice there's first of all a very explicit carve out for >> "your private purposes"

Re: [License-discuss] Discussion: AGPL and Open Source Definition conflict

2019-08-15 Thread Kevin P. Fleming
In my previous job we had a similar discussion related to software which provides connectivity to clients using SIP (Session Initiation Protocol). Even though it would be possible to provide an indication of the AGPL license and URL to obtain the source code during SIP session negotiation, no SIP c