Harald Alvestrand | 15 Aug 2008 10:39
Picon

Re: Last Call for Comments on " Legal Provisions Related to IETF Documents"

Bill Fenner wrote:
> On Aug 10, 2008, at 11:58 PM, Ed Juskevicius wrote:
>> On behalf of the IETF Trustees, we invite your
>> review and final comments and suggestions on this
>> policy.
>
> Here's part of an email that I posted last week on the ipr wg list, 
> which hasn't received much comment but I would like the trustees to 
> consider:
>
> When I was updating section 4 [of 1id-guidelines]
> (which talks about the optional
> restrictions in 6b.) I ran across a minor hiccough -- 3978 allows the
> 6.b.ii. statement, "This document may not be modified, and derivative
> works of it may not be created, and it may not be published except as
> an Internet-Draft.", to be split into two: "This document may not be
> modified, and derivative works of it may not be created." and "This
> document may only be posted in an Internet-Draft." are in different
> sections of 3978.  The section of 3978 that mentions this also
> mentions optionally giving extra permissions for MIBs/PIBs published
> with this restriction: "other than to extract section XX as-is for
> separate use."
>
> -incoming only mentions that there are instructions in the Legend
> Instructions, which I assume are the same as the IETF Trust's Legal
> Provisions Relating to IETF Documents, so I can't really tell from
> that whether the wg intentionally removed these options; the trust
> intentionally removed these options; the trust unintentionally removed
> these options; or other. 
As far as I understand it, the WG desired the ability for these code 
pieces to be "code licensed", just as for all other code, but the "extra 
permissions" stuff was never discussed, AFAIK.

So seen from the WG's perspective, I think having an optional ", other 
than to extract code components under the Code License" would be a Good 
Thing; it seems to me that people who post restricted I-Ds (for whatever 
reason) would be surprised if we started licensing their code pieces, so 
it's better to get them to be explicit and allow us to do so.

My opinion.

                 Harald

Gmane