List Info

Thread: DISCUSS: Rights normally granted




DISCUSS: Rights normally granted
user name
2006-12-03 18:32:36
Harald Alvestrand wrote:

> can you provide a proposal for text for 5.3 that
creates the
> restrictions you want?

The first  proposal was s/in any way desired//
The second proposal was s/in any way desired/worldwide/

You're probably not asking for a link to "CC BY
SA", and it
wouldn't help with say RFC 4643.   Any restriction
compatible
with the rest of 5.3 (and anything else in the I-D) should
be
possible.  Let the lawyers figure out how to get this right.

For I-D authors it should be (in normal cases, not RFC 4643)
as simple as adding ipr="full3978" in their XML
source.  

There should be some simple choices like
ipr="ietfbysa" for
those who don't like "in any way desired".  The
"ietfby" is
ready as far as I can judge it (= not at all, IANAL), now it
only needs a simple alternative, and probably a procedure
for
tricky cases like 4643 or MD5.

Frank



_______________________________________________
Ipr-wg mailing list
Ipr-wgietf.org
https:/
/www1.ietf.org/mailman/listinfo/ipr-wg
DISCUSS: Rights normally granted
user name
2006-12-03 20:20:05

--On 3. desember 2006 19:32 +0100 Frank Ellermann 
<nobodyxyzzy.claranet.de> wrote:

> Harald Alvestrand wrote:
>
>> can you provide a proposal for text for 5.3 that
creates the
>> restrictions you want?
>
> The first  proposal was s/in any way desired//
> The second proposal was s/in any way desired/worldwide/

how do you see this as limiting the permissions granted to
implementors?

I am very afraid of saying that "the IETF desires to
grant the implementors 
permission to change the code, but there are limits to how
we allow you to 
change it, and we're not going to tell you how the IETF
desires to limit 
implementors' permission to make changes".

> You're probably not asking for a link to "CC BY
SA", and it
> wouldn't help with say RFC 4643.   Any restriction
compatible
> with the rest of 5.3 (and anything else in the I-D)
should be
> possible.  Let the lawyers figure out how to get this
right.
>
> For I-D authors it should be (in normal cases, not RFC
4643)
> as simple as adding ipr="full3978" in their
XML source.
>
> There should be some simple choices like
ipr="ietfbysa" for
> those who don't like "in any way desired". 
The "ietfby" is
> ready as far as I can judge it (= not at all, IANAL),
now it
> only needs a simple alternative, and probably a
procedure for
> tricky cases like 4643 or MD5.

This (mechanisms of specifying relevant rights granted to
the IETF, or 
authors' desire wrt what the IETF should grant to
implementors) is on the 
"incoming side" - later discussion. But only
relevant if we agreee that we 
desire this restriction.

>
> Frank
>
>
>
> _______________________________________________
> Ipr-wg mailing list
> Ipr-wgietf.org
> https:/
/www1.ietf.org/mailman/listinfo/ipr-wg
>
>





_______________________________________________
Ipr-wg mailing list
Ipr-wgietf.org
https:/
/www1.ietf.org/mailman/listinfo/ipr-wg
[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )