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

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 23 January 2009 21:56 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 5551428C186; Fri, 23 Jan 2009 13:56:28 -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 02C033A6B3A; Fri, 23 Jan 2009 13:56:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.565
X-Spam-Level:
X-Spam-Status: No, score=-2.565 tagged_above=-999 required=5 tests=[AWL=0.034, 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 8eb0KjIOKBBx; Fri, 23 Jan 2009 13:56:26 -0800 (PST)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175]) by core3.amsl.com (Postfix) with ESMTP id 193363A6B56; Fri, 23 Jan 2009 13:56:25 -0800 (PST)
Received: by wf-out-1314.google.com with SMTP id 27so5661237wfd.31 for <multiple recipients>; Fri, 23 Jan 2009 13:56:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=8TW1w7Y7OS10pBc0pZZ0tOMzRbAOLC+ey6kAK3m7w8Q=; b=B61KQxGCXpD5fuGoEg23TXI8uvcYdvBHFD5twGU0BmuJdALQ293r1pnpmQ/BdLUcFB TediA0NG2Agw0KP2R9q1UU4MWupc3CN8tcf8yDLb+AVJFyGoPj43b/tZQWpFAH1NyMtB oYaS05u0pRo8OhOkw4ttkDws257kKtC+qwqeI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=etD/0cdyVKSxd+v4xjYkVHPE2RUGVTsvRsAPSJ9FF+kg6pDwUYbUn//ssnszycb7mv FEPO4MdXSJDzqJv//9X96yFgLMDZHBPxb/vaSAxAMI41z3bnykw+P4Ia6NhvWX3m4Vsc 2xjJx1iC1k0CAjDtDUmxWNoAitUBySH+xMn6M=
Received: by 10.142.161.13 with SMTP id j13mr2906820wfe.270.1232747767942; Fri, 23 Jan 2009 13:56:07 -0800 (PST)
Received: from ?10.1.1.4? (118-92-203-108.dsl.dyn.ihug.co.nz [118.92.203.108]) by mx.google.com with ESMTPS id 30sm23540803wff.52.2009.01.23.13.56.04 (version=SSLv3 cipher=RC4-MD5); Fri, 23 Jan 2009 13:56:07 -0800 (PST)
Message-ID: <497A3CF2.8060806@gmail.com>
Date: Sat, 24 Jan 2009 10:56:02 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Simon Josefsson <simon@josefsson.org>
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> <87eiyugw7q.fsf@mocca.josefsson.org>
In-Reply-To: <87eiyugw7q.fsf@mocca.josefsson.org>
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

Simon,

My recollection, without doing an archive search, is that our counsel
took the opposite view, i.e. that the parenthesis expanded the scope
beyond "ISOC and the IETF". IANAL and YMMV.

    Brian

On 2009-01-23 23:20, Simon Josefsson wrote:
> 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