Re: Review of outbound-03: Major issues

Below...

On 2007-07-24 23:43, Simon Josefsson wrote:
> Harald Tveit Alvestrand <haraldalvestrand.no> writes:
> 
>>> * Permit additional license notes
>>>   and additional copyright notices (section
6.5)
>>>
>>>   I believe the current text goes beyond RFC
2026, RFC 3978 and the
>>>   running code of the IETF.  Several code
examples have been included
>>>   into IETF documents with special license
notes.  RFC 2026 and RFC 3978
>>>   permits additional license notes (but not
additional copyright
>>>   notices).
>>>
>>>   A lot of source code that is useful to
include in RFCs are available
>>>   under liberal licenses, such as the BSD
license.  That license
>>>   requires that the license notices are
preserved.  It is helpful for
>>>   technical documents to include such source
code.  I believe the
>>>   outbound document should not stand in the way
here.
>>>
>>>   There also doesn't seem to be a good
justification for the text.  What
>>>   problem is it aiming to solve?
>> Please identify exactly which section you mean. I
do not know if this
>> is a duplicate of #1282 or not.
> 
> #1282 appear to be about multiple copyright notices,
section 6.5 is
> about multiple license statements.  That is not the
same thing.  Section
> 6.5 currently reads:
> 
> 6.5.  Additional Licenses for IETF Contributions
> 
>    There have been contexts where the material in an
IETF contribution
>    is also available under other license terms.  The
IETF wishes to be
>    able to include content which is available under
such licenses.  It
>    is desirable to indicate in the IETF contribution
that other licenses
>    are available.  It would be inappropriate and
confusing if such
>    additional licenses restricted the rights the IETF
intends to grant
>    in the content of RFCS.
> 
>    However, the IETF does not wish to have IETF
Contributions contain
>    additional copyright notices and licenses, as that
introduces a
>    number of additional difficulties.  Specifically,
additional text in
>    the document, and any additional license referred to
by permitted
>    additional text MUST NOT in any way restrict the
rights the IETF
>    intends to grant to others for using the contents of
IETF
>    contributions.
> 
>    Authors of contributions retain all rights in their
contributions.
>    As such, an author may directly grant any rights
they wish separately
>    from what the IETF grants.  However, a reader
wishing to determine or
>    make use of such grants will need to consult
external sources of
>    information, including possibly open source code and
documents, or
>    contact the author directly.
> 
> The first sentence of the second paragraph is
incompatible with the
> stated intention in the first paragraph, at least the
way I read it.
> 
> Specifically, you cannot include content available
under, e.g., the BSD
> or GPL license, without conforming to the license
requirements, and
> those include retaining the copyright notice and the
license statement.

We know that. I thought the solution we reached was for the
original
copyright holder to re-license (in parallel to the open
source
license) by submitting the code as a direct contribution to
the IETF.

     Brian
> 
> Thus, if, e.g., BSD/GPL code should be acceptable in
contributions,
> which I believe is a useful thing that promotes the
goal of the IETF,
> and is also the running code (there are many RFCs with
example code
> under various licenses), the IETF must accept that this
leads to having
> additional license notices.
> 
> /Simon
> 
> _______________________________________________
> 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