Re: [Gendispatch] the trust is not your lawyer, or I-D Action: draft-eggert-ietf-and-trust-00.txt

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 25 October 2022 20:05 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84460C14CE36 for <gendispatch@ietfa.amsl.com>; Tue, 25 Oct 2022 13:05:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, 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 (2048-bit key) header.d=gmail.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 XxqaHRsel6VT for <gendispatch@ietfa.amsl.com>; Tue, 25 Oct 2022 13:05:54 -0700 (PDT)
Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19206C14CE30 for <gendispatch@ietf.org>; Tue, 25 Oct 2022 13:05:54 -0700 (PDT)
Received: by mail-pg1-x530.google.com with SMTP id s196so12601706pgs.3 for <gendispatch@ietf.org>; Tue, 25 Oct 2022 13:05:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=iL9bqTWx2pTHWtqN+OBQ6QKMpbZ2fUJm9W5RKPhHeQc=; b=mv/5i1wRyFNL6ec3bu72dWv1tUG1OHmZwilHu+ambvtanbYxsrVJuwKuoD2RkPav+F So0HghjPuDfoCL5C3tmliUdEt366ePRu6i/2D1LDXvfa3ZfGjqql7aDYhvsqpuv/ze7P aKPIAXDOr6EZtwjHqmIDvpBc8MIOI2OcC+D9e6FdaT9XZA7Fq+lldwUwQ+YtyvJgK6Hv 1A4zesz5fnOGMkNziIqksJl57J+Srr59NLWKTQT7BARtLdBIBHBGlryDGLuXDw/OIr3I OTtgNfEknrp+BzpDQT55c224dqPTM6mZgiXODJiYE3yqPVoxSp9zYtzVYc0eFzwrkLeP WoMQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=iL9bqTWx2pTHWtqN+OBQ6QKMpbZ2fUJm9W5RKPhHeQc=; b=XlZCHa14HGoP0gK1zy77C8/jjF46ykhRsGZIl9zvXEW2Y84kNJGy38UhoObzC+Fllu kP+8H4IlzAONv9uEg6BN+hEG+9aTXkN/ZaTDVoRaC3AWvM+2ntqaMAZtGDHEvtwiKmbD RhSQapMi7EXjaKgft15It2frunK3f0ki6ojYDDKTl+ulQNSpVBIsU7yUtNskouNK4SIm LGDhhaZxkUClP83juWdzzbjWxUQz00OvUkbVel0j/GWqxaVnOY/rYRoisWaEEARD2EpB LLbQo/PHtydDrbFmkNlcnSaz8wsxE9nkEmUGDGoafkxcznRZGYHgta7lvACKIWBvMNRt OMEw==
X-Gm-Message-State: ACrzQf2MnX6PHCTDcX2HnFXOzw7NtzJxShF9L+V6g3xycV9WkQGe3bEr zHBcZPJSIECgg3xVDGZSypzEC6mozCcSwg==
X-Google-Smtp-Source: AMsMyM6igX6zMHD7GDFWP7TU6E7OBVQBIU4xfl9xIBhmajNj8yoSGEcOleZIoYT1p9pReXllvyJzIQ==
X-Received: by 2002:a63:dc54:0:b0:44c:ce26:fa35 with SMTP id f20-20020a63dc54000000b0044cce26fa35mr35129926pgj.374.1666728352876; Tue, 25 Oct 2022 13:05:52 -0700 (PDT)
Received: from ?IPV6:2406:e003:1124:9301:80b2:5c79:2266:e431? ([2406:e003:1124:9301:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id a36-20020a630b64000000b00439c6a4e1ccsm1586077pgl.62.2022.10.25.13.05.50 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 25 Oct 2022 13:05:52 -0700 (PDT)
Message-ID: <aaaa92c1-120d-54c5-5ad1-c27bc77906cc@gmail.com>
Date: Wed, 26 Oct 2022 09:05:47 +1300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: John Levine <johnl@taugh.com>, gendispatch@ietf.org
References: <20221025173736.092F04D3C77D@ary.local>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <20221025173736.092F04D3C77D@ary.local>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/N4t-0FY12ahrpmfVdSaTXXwgd5g>
Subject: Re: [Gendispatch] the trust is not your lawyer, or I-D Action: draft-eggert-ietf-and-trust-00.txt
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Oct 2022 20:05:54 -0000

+1 to everything John says.

To be clear, both the text of the "NON-EXCLUSIVE LICENSE" that I and others signed, and the wording of the pre-5378 disclaimer (Section 6.c.iii of the TLP) were designed to avoid putting the Trust in the line of fire if any copyright dispute arose.

If I, as a signer of the non-exclusive license, purported to grant rights that I didn't actually have, that wouldn't be the Trust's problem. That's why I was happy that IBM also signed the license (and why I'm unhappy that it's apparently been mislaid).

For the Trust to make assertions about any specific pre-5378 RFCs would be foolish. Running a new campaign to obtain non-exclusive licenses might be useful.

Regards
    Brian
On 26-Oct-22 06:37, John Levine wrote:
> It appears that John Levine  <johnl@taugh.com> said:
>> It appears that Jay Daley  <jay@staff.ietf.org> said:
>>> Maybe I’m missing something obvious, but how is it a “tremendous amount of work” to have a database (or even a spreadsheet) that lists every RFC and the
>>> known licensing of each one, even if that is just ‘unknown’?
>>>
>>> I’m sure it would be straightforward to add that into Datatracker.
>>
>> I suppose we could create a database that says UNKNOWN for every RFC
>> up to 3977 and TLP for everything after that, but more detail than
>> that would indeed be a huge amount of work, providing no benefit
>> that I can see.
> 
> I take that back, it wouldn't just be no benefit, it would be a significant risk.
> 
> For 3978 and later RFCs we can state with confidence what our rights are and
> what licenses we offer.  For earlier ones we can only guess, and due to the
> way copyright works, if we guessed wrong, it could be very very expensive.
> 
> Consider RFC 854, which defines Telnet.  It was written by Jon Postel and
> Joyce Reynolds, and published without a copyright notice in 1983.  Both of the
> authors are now dead, neither gave a license to the trust.  (Postel could
> not have since he died long before the trust was created.)  I think that
> they were both working for ISI when they wrote it, and that they probably
> did so as part of their ISI duties, so our license from ISI probably
> covers it.  But academic institutions sometimes have copyright carveouts
> in their employee agreements so they can publish journal papers.  I
> have no idea if USC or ISI did that.  I do not know who the authors'
> heirs are nor how they feel about that document or any other.  ISI has
> an archive of Postel's email and I do not know if there is anything
> about that RFC in the mail.
> 
> Given the overall situation and the authors' relation to the IETF, my
> personal opinion is that it is OK for the IETF to reuse that material.
> I am less sure that the ISI license lets the trust relicense it under
> the TLP, which would allow anyone to, say, translate it into Chinese
> and put it in a book. If the Trust purported to grant a license under
> the TLP and it turned out not to have the rights, the penalties for
> copyright infringement, even well-intentioned innocent infringement,
> mount up very fast.
> 
> But that is a personal opinion; if you want a legal opinion, ask an IP
> lawyer, and that will get you an opinion about one (1) RFC.
> 
> R's,
> John
> 
> PS: If this sounds like a total clusterf*, yes indeed. That's why we
> got one of the best IP lawyers in the world to help us draft 3978 and
> 5378 so for RFCs published after March 2005, we don't have this problem.
>