Re: Copying conditions

Simon Josefsson <jas@extundo.com> Thu, 07 October 2004 11:15 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 HAA04772; Thu, 7 Oct 2004 07:15:29 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFWOs-0004LG-34; Thu, 07 Oct 2004 07:25:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFW7o-0006kN-NR; Thu, 07 Oct 2004 07:07:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFW5w-00064U-N0 for ietf@megatron.ietf.org; Thu, 07 Oct 2004 07:06:00 -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 HAA04247 for <ietf@ietf.org>; Thu, 7 Oct 2004 07:05:56 -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 1CFWFY-0003rK-44 for ietf@ietf.org; Thu, 07 Oct 2004 07:16:01 -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 i97B5bu3029273 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK); Thu, 7 Oct 2004 13:05:40 +0200
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
References: <200410071030.i97AUlSj029374@givry.rennes.enst-bretagne.fr>
From: Simon Josefsson <jas@extundo.com>
X-Hashcash: 1:22:041007:francis.dupont@enst-bretagne.fr::1330e8a4cc667c91:26edc
X-Hashcash: 1:22:041007:ietf@ietf.org::40d5ec932d35dbe5:4006fa
Date: Thu, 07 Oct 2004 13:05:11 +0200
In-Reply-To: <200410071030.i97AUlSj029374@givry.rennes.enst-bretagne.fr> (Francis Dupont's message of "Thu, 07 Oct 2004 12:30:47 +0200")
Message-ID: <ilupt3u4wm0.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: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: 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: 9ed51c9d1356100bce94f1ae4ec616a9

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

> => I understand better your concern: the problem is about pieces of
> code which can be extracted from an RFC, the cannonical example is
> a MIB. This is covered in RFC 3667 by 5.2, 5.6 and 7.1e which I
> give here:
>
>    e. the right to let third parties extract some logical parts, for
>       example MIB modules
>
> So at least your concern was not forgotten...

I am sorry to continue this, but I think it is valuable to have a
complete discussion in public on record of this.  Especially since
Harald imply IETF hasn't been aware of this before.

I still see two issues:

1) The above does not grant me the right to incorporate text into,
   e.g., my manual.  It seems to me that this should be encouraged and
   promoted.

2) I cannot find anything about "third parties" in the actual license
   text, in section 3.3.  The (E) clause grant the ISOC/IETF the right
   to extract, etc code fragments, but doesn't say anything about
   third parties.  Your quote suggest the intention was to address my
   concern, but to my reading, the intention isn't addressed in the
   more legally phrased rights grant.  Naturally, I may have
   completely missed it, though.

I don't believe this issue is off topic.  I agree with Eric Raymond
that IETF must make an effort to ensure that the standards can be
openly implemented without risking legal consequences.  Copying
conditions is a minor tangent to those larger IPR issues, but if it
cannot be resolved, I see little hope in resolving larger problems.  I
do agree that fleshing out any details should be moved to the IPR WG.

Thanks.

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