Re: [Gendispatch] I-D Action: draft-eggert-ietf-and-trust-00.txt

John Levine <johnl@taugh.com> Tue, 25 October 2022 06:19 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 CB5D3C14CE42 for <gendispatch@ietfa.amsl.com>; Mon, 24 Oct 2022 23:19:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.16
X-Spam-Level:
X-Spam-Status: No, score=-4.16 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_MED=-2.3, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=bdvEgg9E; dkim=pass (2048-bit key) header.d=taugh.com header.b=DU22M5Bj
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 K2ZV0cYmrzHU for <gendispatch@ietfa.amsl.com>; Mon, 24 Oct 2022 23:19:31 -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 D00FDC14CE23 for <gendispatch@ietf.org>; Mon, 24 Oct 2022 23:19:30 -0700 (PDT)
Received: (qmail 12098 invoked from network); 25 Oct 2022 06:19:28 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=2f3e.63577ff0.k2210; bh=oEstb5vslT11Y2uaa0quQXk0OGueC/mpapaJiur/La8=; b=bdvEgg9E/tz29yFq2WGDcQNdJL1YKyDPakmBswB0HASVAWLtPqUIdOJl0sh8tvcFAoayweBodIf0p7l4N4QvcS75CAkMkbnJSa1vgHbwKnkrQwjMYuW/69fkCUOdmmU+nsT3EJYAzFrFVh5ii3GI1sQgtpCU16OgCPDwjSDW7jo0RNq8FSsjWwdDE6R9RFgJ8a+TjDriofyGfjSIR53vhm9E4OerfiPtiID1zz9OK2Y4Oy1FpqpfQ7KtkU7BnfcRGz3drJNZ7rMP5gJ2728h/XMfDASdO1huBA/BL9+4lO3FmMekFHoH7AKbJSEoZH09m8cZERZinOGGPjVm+Flm4Q==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=2f3e.63577ff0.k2210; bh=oEstb5vslT11Y2uaa0quQXk0OGueC/mpapaJiur/La8=; b=DU22M5BjEsX5zzypx7RLATa5JBdfpaxmW9vcFog5pexPN8EmXkMf31CKStUHJFcuLcJn4WgBqDXeV7dcY5ETFQARSn+KJRdTvUxG4Eqd/eFW+J9RcTbjg0et5z+x9aWZA0zZAAcZpUSZ2bnahukE0CafxC1OIHr+JM5W6dlbAQcYG735DURg3vpZC+dbylOD6sqIa6jM+YQLcSiwMsmR47neT1UCTF2YQhWeWW2E4FgjXQDysgqT708T7Klu1BZWPRX/d1GdTTS4Rhu0dlM53y9iMHNm+D2k362+0VRhm26n0fKJRCAOlrpj0CFccNQFfR8p8czAi9A1ikPTdH+gKQ==
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 06:19:27 -0000
Received: by ary.local (Postfix, from userid 501) id EA9D54D3B31D; Mon, 24 Oct 2022 23:19:26 -0700 (PDT)
Date: Mon, 24 Oct 2022 23:19:26 -0700
Message-Id: <20221025061926.EA9D54D3B31D@ary.local>
From: John Levine <johnl@taugh.com>
To: gendispatch@ietf.org
Cc: jay@staff.ietf.org
In-Reply-To: <08C644E1-6F7F-4DDF-8C03-F0430F22F3FC@ietf.org>
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/F2sRu5pabWq-B2A5oF2qbGp-OFc>
Subject: Re: [Gendispatch] 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 06:19:35 -0000

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.

Determining the copyright status of each pre-3978 RFC is a fact
specific labor intensive project. Who are the authors? What if any
copyright notice does the RFC have? Have the authors licensed rights?
(in most cases, no.) If there were multiple authors and one licensed
his rights, did he have authority to act for the rest of the authors?

Did the author(s) write the RFC as part of their job in which case the
rights belong to whoever they were working for, or as individuals? If
the former, do we have a license from the employer (unless it was ISI,
probably not.) Were they working for the US government which does not
assert copyright on its works? Etc., etc.

The vast majority of early RFCs are of purely historical interest.  No
new RFC will use text from them, so their copyright status does not matter.

Occasionally someone does want to use old material, at which point the
new authors look at all of those questions and try to figure out who
has the rights and whether they can use it. This has been happening
occasionally ever since we published RFC 3978.

I do not see why that would now be the trust's responsibility -- its
job is to hold whatever IP assets the IETF owns, not to be its legal
research department.

R's,
John