Re: Editors vs Authors vs Contributors, was: ANNOUNCEMENT: The IETF Trustees invite your review and comments on a proposed Work-Around to the Pre-5378 Problem

Simon Josefsson <simon@josefsson.org> Fri, 23 January 2009 10:20 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5593B28C0FC; Fri, 23 Jan 2009 02:20:51 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A06743A6974; Fri, 23 Jan 2009 02:20:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.582
X-Spam-Level:
X-Spam-Status: No, score=-2.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A1iDjEPYPp+f; Fri, 23 Jan 2009 02:20:49 -0800 (PST)
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by core3.amsl.com (Postfix) with ESMTP id AAE253A6874; Fri, 23 Jan 2009 02:20:48 -0800 (PST)
Received: from c80-216-29-127.bredband.comhem.se ([80.216.29.127] helo=mocca.josefsson.org) by yxa-v.extundo.com with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from <simon@josefsson.org>) id 1LQJ9H-0000V3-6Z; Fri, 23 Jan 2009 11:20:27 +0100
From: Simon Josefsson <simon@josefsson.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Editors vs Authors vs Contributors, was: ANNOUNCEMENT: The IETF Trustees invite your review and comments on a proposed Work-Around to the Pre-5378 Problem
References: <70873A2B7F744826B0507D4B84903E60@noisy> <54974382E5FF41D3A40EFDF758DB8C49@DGBP7M81> <20090112211809.515993A67EA@core3.amsl.com> <A2460A3CBF9453B10BC02375@PST.jck.com> <20090112221608.5659A3A67EA@core3.amsl.com> <7FCA5612-AACD-404A-A454-E72AB9A5F51E@softarmor.com> <6.1.2.0.2.20090121100156.02670878@boreas.isi.edu> <BE12AE47-BC5C-495C-BBE1-EA16D6442DB1@gbiv.com> <4978A171.6030904@gmx.de> <4978DA6B.7000409@gmail.com> <20090122213012.GK14966@mit.edu> <4978E9CD.9000901@gmail.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090123:trustees@ietf.org::HWCbYjqPw69LS1Oa:2E64
X-Hashcash: 1:22:090123:ietf@ietf.org::VCSmfmrLeWl7fw8h:401j
X-Hashcash: 1:22:090123:brian.e.carpenter@gmail.com::ne4aIMpKxXEKBUyz:4GHU
X-Hashcash: 1:22:090123:tytso@mit.edu::vxyQXtdag1MHyc09:IqkN
X-Hashcash: 1:22:090123:julian.reschke@gmx.de::OaTaRWLJb6XuMRMF:Exgu
Date: Fri, 23 Jan 2009 11:20:25 +0100
In-Reply-To: <4978E9CD.9000901@gmail.com> (Brian E. Carpenter's message of "Fri, 23 Jan 2009 10:49:01 +1300")
Message-ID: <87eiyugw7q.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.60 (gnu/linux)
MIME-Version: 1.0
Cc: Julian Reschke <julian.reschke@gmx.de>, trustees@ietf.org, Theodore Tso <tytso@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.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://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org Brian E Carpenter <brian.e.carpenter@gmail.com> writes:

> Ted,
>
> On 2009-01-23 10:30, Theodore Tso wrote:
> ...
>> Ultimately, I suspect the list of contributors is a good and polite
>> thing to do out of courtesy, but it's not all that useful from an IPR
>> point of view.  Even if there was code that you wanted to use from a
>> pre-RFC5378 text, you wouldn't need or want to contact *all* the
>> contributors; you would want to know who contributed the portion of
>> the RFC containing the code that you wanted to use in an
>> implementation (either proprietary or open source).
>
> To be clear about the case of code: the right to use code was already
> granted under the old rules; it's the right to use non-code text in
> non-IETF derivative works that is made possible by the new rules.
>
> RFC3978 and RFC3667 include:
>       "(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..."

Those right are not granted to "third parties", only to the ISOC/IETF.
The section before the paragraph you quote from RFC 3978 begins with:

   a. To the extent that a Contribution or any portion thereof is
      protected by copyright and other rights of authorship, the
      Contributor, and each named co-Contributor, and the organization
      he or she represents or is sponsored by (if any) grant a
      perpetual, irrevocable, non-exclusive, royalty-free, world-wide
      right and license to the ISOC and the IETF under all intellectual
                --------------------------------
      property rights in the Contribution:

So I disagree that the right to use code was already granted under RFC
3978.  In fact, I believe this was one of the main flaws with RFC 3978.

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