Re: [tlp-interest] Request to designate TLP Section 6 as Code Components

[Marshall Eubanks <[e-mail]>]

On Nov 4, 2009, at 11:18 AM, Simon Josefsson wrote:

> Marshall Eubanks <[e-mail]> writes:
>
>> On Nov 4, 2009, at 10:53 AM, Simon Josefsson wrote:
>>
>>> On Wed, 2009-11-04 at 10:46 -0500, Joel M. Halpern wrote:
>>>> I really don't think there is a problem Simon.
>>>> If anyone, anywhere, builds a tool for crafting I-Ds, and in the
>>>> portion
>>>> of the tool for crafting I-Ds for the IETF, they use the words the
>>>> IETF
>>>> wants used, then it is being done for IETF pruposes, and is clearly
>>>> allowed.
>>>>
>>>> Now, if some other standards body needs those exact words  
>>>> (copyright
>>>> applies only to exact words), then they need to talk to the trust.
>>>
>>> What you are saying here implies that there is a problem.  Free OS
>>> distributions needs a legal right to use those exact words, under a
>>> free
>>> license such as the BSD license, otherwise they cannot include the
>>> work.
>>>
>>> Since this has come up many times before, and I apparently have  
>>> failed
>>> to get this point through, please take some time and read these
>>> rules on
>>> what Debian requires for distribution:
>>>
>>> http://www.debian.org/social_contract#guidelines
>>>
>>
>> That link says
>> Example Licenses
>>
>> The GPL, BSD, and Artistic licenses are examples of licenses that we
>> consider free.
>>
>> -----
>> and links to
>>
>> http://www.debian.org/misc/bsd.license
>>
>> which is actually what the OSI calls the "Simplified BSD License,"
>> which is what we adopted
>>
>> http://www.opensource.org/licenses/bsd-license.php
>>
>> So, I think we are OK on this basis.
>
> Did you read the first post in this thread?  This question is about
> boiler plate text in section 6 of the TLP.  The IETF Trust is not  
> using
> the BSD license for that.

Why not ?

The current TLP :

License to Code Components.
a. Definition.  IETF Contributions and IETF Documents often include  
components
intended to be directly processed by a computer (“Code Components”).   
A list of common Code
Components can be found at http://trustee.ietf.org/license-info/.

The TLP is an IETF document. If you need to use the boiler plate text  
in section 6 as or in code, that is text from an IETF
document, it is being used as code and a BSD license certainly is  
available.

Regards
Marshall


>
> /Simon
>
>> Regards
>> Marshall
>>
>>> /Simon
>>>
>>>
>>>> But
>>>> it is almost certain that anyone else would need different words.
>>>>
>>>> So even if Debian were to distribute the xml2rfc tool, there  would
>>>> still be no problem in using IETF boilerplate for producing I-Ds
>>>> for the
>>>> IETF.
>>>>
>>>> Yours,
>>>> Joel
>>>>
>>>> Simon Josefsson wrote:
>>>>> Brian E Carpenter <[e-mail]> writes:
>>>>>
>>>>>> It doesn't need to be marked as code. Just get a mail from the
>>>>>> Trust
>>>>>> telling you it's OK. The IETF is not going to sue itself for  
>>>>>> using
>>>>>> its own property.
>>>>>
>>>>> I think the point is that xml2rfc may be distributed by others
>>>>> (e.g.,
>>>>> Debian), and without a clear license on the material, the IETF has
>>>>> the
>>>>> right to sue others for copyright infringement.  That situation is
>>>>> rarely acceptable for free software distributions, and the
>>>>> alternative
>>>>> is to not distribute xml2rfc at all.
>>>>>
>>>>> /Simon
>>>>>
>>>>>> IANAL, but this is a no brainer.
>>>>>>
>>>>>> Regards
>>>>>> Brian Carpenter
>>>>>>
>>>>>> On 2009-11-04 18:51, Florian Weimer wrote:
>>>>>>> * Russ Housley:
>>>>>>>
>>>>>>>> I do not understand this request.  Section 6 is boilerplate  
>>>>>>>> text,
>>>>>>>> not code.
>>>>>>> It has to be put into xml2rfc, as code, so that xml2rfc can be
>>>>>>> used to
>>>>>>> produce conforming documents.
>>>>>>> _______________________________________________
>>>>>>> tlp-interest mailing list
>>>>>>> [e-mail]
>>>>>>> https://www.ietf.org/mailman/listinfo/tlp-interest
>>>>>>>
>>>>>> _______________________________________________
>>>>>> tlp-interest mailing list
>>>>>> [e-mail]
>>>>>> https://www.ietf.org/mailman/listinfo/tlp-interest
>>>>> _______________________________________________
>>>>> tlp-interest mailing list
>>>>> [e-mail]
>>>>> https://www.ietf.org/mailman/listinfo/tlp-interest
>>>>>
>>>
>>>
>>> _______________________________________________
>>> tlp-interest mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/tlp-interest
>>>
>