Re: Copying conditions

Francis Dupont <Francis.Dupont@enst-bretagne.fr> Thu, 07 October 2004 18:21 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 OAA08930; Thu, 7 Oct 2004 14:21:21 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFcLm-0003i2-0h; Thu, 07 Oct 2004 13:46:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFc4W-0006Xs-IA; Thu, 07 Oct 2004 13:28:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFby9-0005Bd-R9 for ietf@megatron.ietf.org; Thu, 07 Oct 2004 13:22:22 -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 NAA06520 for <ietf@ietf.org>; Thu, 7 Oct 2004 13:22:18 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFc7r-0002tm-CI for ietf@ietf.org; Thu, 07 Oct 2004 13:32:26 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194]) by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with ESMTP id i97HLV326245; Thu, 7 Oct 2004 19:21:31 +0200
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1]) by givry.rennes.enst-bretagne.fr (8.12.3/8.12.3) with ESMTP id i97HLTSj030678; Thu, 7 Oct 2004 19:21:29 +0200 (CEST) (envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200410071721.i97HLTSj030678@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Simon Josefsson <jas@extundo.com>
In-reply-to: Your message of Thu, 07 Oct 2004 11:42:01 +0200. <ilu7jq26f12.fsf@latte.josefsson.org>
Date: Thu, 07 Oct 2004 19:21:29 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
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: b19722fc8d3865b147c75ae2495625f2

 In your previous mail you wrote:

   > => 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.
   
=> RFC 3667 style for copyright statements says nearly nothing about
the rights the ISOC grants to us... IMHO you're right and there is a real
issue even any restriction has to be written down to exist (the only
condition is to keep the original copyright).

   > 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".
   
=> RFC 3667 7.1e seems the right answer.

Thanks

Francis.Dupont@enst-bretagne.fr

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