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

John Levine <johnl@taugh.com> Tue, 25 October 2022 17:37 UTC

Return-Path: <johnl@iecc.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 65E14C14CE3A for <gendispatch@ietfa.amsl.com>; Tue, 25 Oct 2022 10:37:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.857
X-Spam-Level:
X-Spam-Status: No, score=-1.857 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, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=batXOLp/; dkim=pass (2048-bit key) header.d=taugh.com header.b=jFoMCcgK
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 cJazb5gpiMLn for <gendispatch@ietfa.amsl.com>; Tue, 25 Oct 2022 10:37:40 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 E18A8C14F731 for <gendispatch@ietf.org>; Tue, 25 Oct 2022 10:37:39 -0700 (PDT)
Received: (qmail 35450 invoked from network); 25 Oct 2022 17:37:37 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=8a72.63581ee1.k2210; bh=fIqxKQQYr7TZrNQGV7DAafzx1BiO4pD4+B5AEog8vLE=; b=batXOLp/kcCIF6RqM4dIYJlvd9uCpgi3r6yAU0RG028ujrrxdse+EMrZxWP4sx2LGmRZmbB6YEF32VqwzFDwFCnS0hpiILzOGwKi6R5w+iKjQJ31Wp2p0ts645UJWk4rtcxSGyyX1KiW0B0QMgeNnbqAfT+v68wXYuM8Sn7753Egt3jKWUO4CB2H28A0bmOwHxzqg6kfhvug1kuIPunJBr4YkhdyRYwgFBcVN4ZZMa4dS52O0jmvR8t2Yk6MLtmMWoMn6WnnZcAs99l1ZJwlxfZkVjCOqyjoFnMp2g2cCiz/+CCzdO3G/yQZxOzc59g6WD/cIV8kD9KggwWzLCuAOQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=8a72.63581ee1.k2210; bh=fIqxKQQYr7TZrNQGV7DAafzx1BiO4pD4+B5AEog8vLE=; b=jFoMCcgKEgyJoeveuiDixZaR5TMvkeUPAEVIZoRBuRKc/xbzqKfBA06Ol+rlDCdK1842JQ80sBnH5X1mNy17VzUpGtz89+LwdhXnSWi+LnnroL2aGOYhgLoG8SUTG1eFDsT/3cDkTQ6ZSP+vns8+ViOEAlW2nSeW+O3Ln1wBTSzy7ua0gstQXDH8Qv/RdFm+Pgz6Z0ZlyUmA3q/LLRZKNfEA8wJiTJre5GYBIjfvq3RqGPbx835Pn72p8W8jzAxBWcogZpsg5MpnyoyC8IKxlbotmhFB6sfiOsbODayhKzrMay+QqQrpt2V79gz+HTjQU2zFxmIMIDyzXss53Lp9gA==
Received: from ary.local ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 25 Oct 2022 17:37:36 -0000
Received: by ary.local (Postfix, from userid 501) id 092F04D3C77D; Tue, 25 Oct 2022 10:37:35 -0700 (PDT)
Date: Tue, 25 Oct 2022 10:37:35 -0700
Message-Id: <20221025173736.092F04D3C77D@ary.local>
From: John Levine <johnl@taugh.com>
To: gendispatch@ietf.org
In-Reply-To: <20221025061926.EA9D54D3B31D@ary.local>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/ORxMsKCG1ulxN6hOwEWWS5W3WhY>
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 17:37:45 -0000

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.