Re: Copying conditions

Simon Josefsson <jas@extundo.com> Thu, 07 October 2004 09:56 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28895; Thu, 7 Oct 2004 05:56:30 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFVAO-00082T-Cy; Thu, 07 Oct 2004 06:06:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFUsQ-0005jO-Mh; Thu, 07 Oct 2004 05:47:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFUnN-0004uG-De for ietf@megatron.ietf.org; Thu, 07 Oct 2004 05:42:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27888 for <ietf@ietf.org>; Thu, 7 Oct 2004 05:42:42 -0400 (EDT)
Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178] helo=yxa.extundo.com ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFUx1-00076k-0i for ietf@ietf.org; Thu, 07 Oct 2004 05:52:45 -0400
Received: from latte.josefsson.org (c494102a.s-bi.bostream.se [217.215.27.65]) (authenticated bits=0) by yxa.extundo.com (8.13.1/8.13.1/Debian-14) with ESMTP id i979gRe6025286 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK); Thu, 7 Oct 2004 11:42:30 +0200
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
References: <200410070931.i979VhSj028954@givry.rennes.enst-bretagne.fr>
From: Simon Josefsson <jas@extundo.com>
X-Hashcash: 1:22:041007:francis.dupont@enst-bretagne.fr::bf6e1125dbbc2e84:247a31
X-Hashcash: 1:22:041007:sob@harvard.edu::2615ffabfb58adf9:7da45d
X-Hashcash: 1:22:041007:esr@thyrsus.com::06338e62a5791194:13c73f
X-Hashcash: 1:22:041007:ietf@ietf.org::b1b13a3d05ac209d:7b6120
Date: Thu, 07 Oct 2004 11:42:01 +0200
In-Reply-To: <200410070931.i979VhSj028954@givry.rennes.enst-bretagne.fr> (Francis Dupont's message of "Thu, 07 Oct 2004 11:31:43 +0200")
Message-ID: <ilu7jq26f12.fsf@latte.josefsson.org>
User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.64
X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on yxa-iv
X-Virus-Scanned: clamd / ClamAV version 0.75-1, clamav-milter version 0.75c on yxa-iv
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: esr@thyrsus.com, scott bradner <sob@harvard.edu>, ietf@ietf.org
Subject: Re: Copying conditions
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1

Francis Dupont <Francis.Dupont@enst-bretagne.fr> writes:

>  In your previous mail you wrote:
>
>    > i.e. the rights under 3667 are the same as under 2026 its just stated
>    > more clearly
>    
>    Even if that is true, it would not change that the current copying
>    conditions are a problem for the free software community, and in my
>    opinion, consequently the IETF.
>    
> => I can't understand why the copyright about a text is a problem
> for software when the documentation is explicitely "without
> restriction of any kind".

Where does it say this?  Note that the quote I sent earlier was the
old RFC 2026 copying condition, which I agree with you is OK.  The new
text is in RFC 3667, which seem murkier to me.  I cannot find "without
restriction" in it, for example.

However, Scott Bradner suggested that the old RFC 2026 text may not be
permissive enough to allow for derivative works.  I have asked lawyers
to look at this now, to be certain.

> Perhaps we don't share the meaning of "derivative works" (for me,
> this can't be code itself)?

If you extract, say, a C header file, or an ASN.1 schema, from an RFC
into an application, I believe that may be regard as a "derivative
work".

Thanks,
Simon

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf