Re: Copying conditions

Francis Dupont <Francis.Dupont@enst-bretagne.fr> Thu, 07 October 2004 19:34 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 PAA15766; Thu, 7 Oct 2004 15:34:25 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFeBk-0004iJ-QN; Thu, 07 Oct 2004 15:44:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFdwW-0005Cr-KS; Thu, 07 Oct 2004 15:28:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFdkD-0006V4-CE for ietf@megatron.ietf.org; Thu, 07 Oct 2004 15:16:06 -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 PAA13575 for <ietf@ietf.org>; Thu, 7 Oct 2004 15:16:03 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFdtv-0003XY-Ik for ietf@ietf.org; Thu, 07 Oct 2004 15:26:10 -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 i97JFQa06650; Thu, 7 Oct 2004 21:15:26 +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 i97JFQSj031115; Thu, 7 Oct 2004 21:15:26 +0200 (CEST) (envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200410071915.i97JFQSj031115@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: sob@harvard.edu
In-reply-to: Your message of Thu, 07 Oct 2004 07:08:23 EDT. <20041007110823.29441CBDD3@newdev.harvard.edu>
Date: Thu, 07 Oct 2004 21:15:26 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: esr@thyrsus.com, ietf@ietf.org, jas@extundo.com
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: 8abaac9e10c826e8252866cbe6766464

 In your previous mail you wrote:

   > 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".
   
   see RFC 3667 Section 3.3 (a) (E)
   
         (E)  to extract, copy, publish, display, distribute, modify and
              incorporate into other works, for any purpose (and not 
              limited to use within the IETF Standards Process) any
              executable code or code fragments that are included in any
              IETF Document (such as MIB and PIB modules), subject to the
              requirements of Section 5 (it also being understood that the
              licenses granted under this paragraph (E) shall not be deemed
              to grant any right under any patent, patent application or
              other similar intellectual property right disclosed by the
              Contributor under [IETF IPR]).
   
=> the issue is this right is granted to the ISOC and the IETF, not
to third parties. In fact the whole RFC 3667 is about rights granted
by authors to the ISOC and the IETF *only*...
At the limit one can say that 7.1c and 7.1e are not provided by RFC 3667!

Thanks

Francis.Dupont@enst-bretagne.fr

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