Re: [tao-discuss] Misleading text on copyright

Joel Halpern <jmh@joelhalpern.com> Wed, 14 September 2022 14:56 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: tao-discuss@ietfa.amsl.com
Delivered-To: tao-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63A08C14F748 for <tao-discuss@ietfa.amsl.com>; Wed, 14 Sep 2022 07:56:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.812
X-Spam-Level:
X-Spam-Status: No, score=-2.812 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ppSEGpU3gBPp for <tao-discuss@ietfa.amsl.com>; Wed, 14 Sep 2022 07:56:29 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 552DBC14F6EC for <tao-discuss@ietf.org>; Wed, 14 Sep 2022 07:56:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4MSNhF0KVYz6GZ2F; Wed, 14 Sep 2022 07:56:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1663167389; bh=Rp18EzratxATqnn2JP8EDuRoRWN0UIFzzLdguFV5nDk=; h=Date:Subject:To:References:From:In-Reply-To:From; b=YifICwoHP8jsjOeqMH93BCUHiVeRjnDywV3M4VkTafzkZeo3636Bnh5rPJLveiCmb cC+Zkxt0NvasobQQmLk56KN5XLTzIQfimejUTJiUDfeLjjJ2hVc6irnr6DiaUAsydi QP5qivxaU5djS7oYm/lcU7MMQxlZnu88kj2cGZMg=
X-Quarantine-ID: <lVl-jPZfa7bh>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.23.73] (unknown [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4MSNhD2X9Pz6G9w8; Wed, 14 Sep 2022 07:56:26 -0700 (PDT)
Message-ID: <7ba3388d-4a56-d883-d317-8488bbd13203@joelhalpern.com>
Date: Wed, 14 Sep 2022 10:56:13 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2
Content-Language: en-US
To: Niels ten Oever <mail@nielstenoever.net>, tao-discuss@ietf.org
References: <130e7c3d-852e-cf9a-ec81-74373cad876f@joelhalpern.com> <11234513-64fc-3cc0-b1b5-eef65a93fdeb@nielstenoever.net>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <11234513-64fc-3cc0-b1b5-eef65a93fdeb@nielstenoever.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tao-discuss/t5tLyeuH2iepbUPFP20QxmWOQ30>
Subject: Re: [tao-discuss] Misleading text on copyright
X-BeenThere: tao-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion of the Tao of the IETF <tao-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tao-discuss>, <mailto:tao-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tao-discuss/>
List-Post: <mailto:tao-discuss@ietf.org>
List-Help: <mailto:tao-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tao-discuss>, <mailto:tao-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Sep 2022 14:56:33 -0000

Thanks Niels.  I had no intent to imply or suggest any deliberate error 
on anyone's part.  I assumed (and still understand) that it was an 
honest misunderstanding of the often confusing rules.

The proposed fix looks good.  Please send it to the trust for an extra 
check.

Thank you,

Joel

On 9/14/2022 7:04 AM, Niels ten Oever wrote:
> Hi Joel,
>
> On 14-09-2022 02:42, Joel Halpern wrote:
>> The text on copyright in section 6.1 is misleading in two ways, one 
>> more important than the other. While I understand we do not want to 
>> get the Tao into the details of copyright law, as a trustee I am 
>> concerned about being too misleading.
>>
>
> From Merriam-Webster:
>
> Def. Misleading
> : to lead in a wrong direction or into a mistaken action or belief 
> often by deliberate deceit
>
> I don't think there is any deliberate deceit here, but you might have 
> not meant that.
>
>> The problems are in the fourth paragraph.
>>
>> The first problem is that the grant to the trust occurs when the 
>> individual draft is submitted.  (It also occurs when any revision is 
>> made,  Or when the adopted version is adopted.)  The current text 
>> says that the grant occurs for the first time when the draft is adopted.
>>
>> The second issue is subtle and hard to get right here.  What happens 
>> is that the author retains their copyright in the document.  And 
>> grants the IETF (and thus the Trust) a copyright. The copyright is 
>> not transfererd but granted.  The wording in the fourth paragraph is 
>> confusing in this regard.
>>
>> To solve both these problems, I suggest that after the first 
>> paragraph, we add a new second paragraph:
>>
>> Note that as part of submitting an Internet Draft according to the 
>> rules, you grant the IETF certain rights.  These rights give the IETF 
>> the ability to reliably build upon the work you have brought forward. 
>> These rights are held by the IETF Trust.  Which is all you need to 
>> know about the Trust.
>
> I think this text is great, but maybe we can omit that last sentence? 
> It sounds a bit like: don't think about a pink elephant.
>
>>
>> I would then modify the fourth paragraph to make clear that the point 
>> of the paragraph is that once a WG adopts a document, the WG has 
>> change control.  And that one should only embark on this process if 
>> one is prepared to grant that change control.  No need to talk there 
>> about the Trust.
>>
>> I would suggest that the new paragraph be emailed to the trust to 
>> make sure it is close enough we can live with it, as I am not here 
>> speaking for the Trust.
>
> Does this look good to you: https://github.com/ietf/tao/pull/54 ?
>
> If so, am happy to also email it to the trust.
>
> Best,
>
> Niels
>
>
>
>>
>> Yours,
>>
>> Joel
>>
>> _______________________________________________
>> tao-discuss mailing list
>> tao-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/tao-discuss
>