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

John R Levine <johnl@taugh.com> Sat, 22 October 2022 16:02 UTC

Return-Path: <johnl@taugh.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 CB224C14CE30 for <gendispatch@ietfa.amsl.com>; Sat, 22 Oct 2022 09:02:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=MYLbrZNz; dkim=pass (2048-bit key) header.d=taugh.com header.b=rsnKYGtB
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 EcxdkSvQSuY7 for <gendispatch@ietfa.amsl.com>; Sat, 22 Oct 2022 09:02:05 -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 89D69C14CE36 for <gendispatch@ietf.org>; Sat, 22 Oct 2022 09:02:04 -0700 (PDT)
Received: (qmail 10904 invoked from network); 22 Oct 2022 16:02:02 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=2a94.635413fa.k2210; bh=Z/fBCTzuMmRLc1Uk9GdNNmFUGoxkB7IS5Mmu8T9IWXY=; b=MYLbrZNznYXdt0tycN5pgj/OBSgnPwFa6XQ0uZTvVZm4oQI9Xyiv53L1zfYHYdADjjnRpr9tYpElTEScRzcwxnoNs5jiBBHThLlZ1N00ZJyBOpaQBxJ87D1/oPWZRxAufOHDTMFGV4bFbp+dyedlj4rCkZ7go0C4Yh62d2z2Sl1DYqaVvLNzJKNZqp9l5yKQYNrGt/GmLaFJWacIuEeWkc0c5ztdcSHBOqRv8TO4TPx5I7lnIGFYm2nz0fLxyEfvWAh2jQ0FoDHi5Yl7DkNXAteiIc0L4CgqASiQDx539awoVt0fAtpMT/n0QAYdrIva58RcxvpBsbrsIQWPLbqvtg==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=2a94.635413fa.k2210; bh=Z/fBCTzuMmRLc1Uk9GdNNmFUGoxkB7IS5Mmu8T9IWXY=; b=rsnKYGtBsy27tvRKV0UFfHnQOYIFVE7JsJDZItkhJhLMi2DUfGV4sd0BkEuQiaVSAZuiu0jvGntrf1SUaTTFqU18BUXSEwy0fML0xW3knVfXK63M8YP/eK5+YYyAO1IHJiDsrrEyjOz0OtlQKMgh5dq4hVTg7fwmkpdN8sD2V52JQUQj/SxtttiFbGiTkRF/YloGiAWbfYj6pEiXgkSGteOGQKgrqu6pHJpvuSSLNd7Vr0rlv4Tst3OGF3RxdJVvWg0mBKh+AkCwZaQ4y/S8LR9s/2S40SBvb86vlflE9lKf+rUfS9M/0Clx28N0ItecA8gnxEPGtwoU8Td5tOe5jg==
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; 22 Oct 2022 16:02:02 -0000
Received: by ary.local (Postfix, from userid 501) id DDB944D2523D; Sat, 22 Oct 2022 09:02:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by ary.local (Postfix) with ESMTP id 5BFF14D2521F; Sat, 22 Oct 2022 09:02:00 -0700 (PDT)
Date: Sat, 22 Oct 2022 09:02:00 -0700
Message-ID: <bcc9a910-ada0-c491-0bc4-8ac4effecf50@taugh.com>
From: John R Levine <johnl@taugh.com>
To: Lars Eggert <lars@eggert.org>
Cc: gendispatch@ietf.org
X-X-Sender: johnl@ary.local
In-Reply-To: <AEDD55EF-3883-44A2-BE6E-233D4D8C7639@eggert.org>
References: <20221022034724.49A774D1F7CC@ary.local> <AEDD55EF-3883-44A2-BE6E-233D4D8C7639@eggert.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/OW3MVULjZiZStNX4FAYRy83X2Vc>
Subject: Re: [Gendispatch] I-D Action: trust assets, 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: Sat, 22 Oct 2022 16:02:10 -0000

> is that asset register publicly accessible?

It's on the Trust's web site, with a link on the home page.  But if you 
had trouble finding it, why didn't you ask?

>> If you're wondering where the copyright or license info is for all of
>> the pre-3978 RFCs, other than a handful of licenses from ISI and a few
>> of the authors, there isn't any. As Joel noted, attempting to
>> determine the status of early RFCs would be a hugely expensive and
>> unproductive exercise in frustration. In a few cases I doubt that
>> anything short of a suit in a US federal court would resolve it (look
>> at RFC 20) and I hope none of us want to go there.
>
> I thought that when the Trust was established, it was supposed to 
> actively approach authors of pre-5378 documents, especially core 
> Internet specifications, to get the copyrights signed over. Has that 
> effort been abandoned?

I wasn't around in 2006, but if you had asked I would have told you that 
last year while I was a trustee I got licenses from two or three of the 
early authors who I knew.  Those are the ones that aren't in the asset 
register yet.

But really, it's not that simple.  Anything published in the US before 
1976 without a copyright notice is in the public domain.  In many cases it 
is unclear whether an author wrote an RFC as an individual, in which case 
he can license the rights, or as an employee in which case whoever he was 
working for at the time owns the rights, unless the employer was the US 
government in which case it's public domain.  In many cases the employers 
no longer exist, and I am unware of a practical way to figure out who 
might have inherited their assets.  In a few cases (RFC20) it is not clear 
whether the author even had the rights in the first place.

And of course, some authors are dead.  We believe that Jon Postel wrote 
all his RFCs as an ISI employee, and we have a license from ISI, so we're 
OK there.

Once again, if this was important, why didn't you ask?

> I'm sorry if the tone comes across as adversarial, that is not the 
> intent. The intent is to capture the IETF community's expectations of 
> the Trust.

If that is truly the intent, I strongly encourage you to withdraw this 
error riddled draft and talk to the trustees about all the assertions you 
made so you can at least get your facts straight.

I entirely agree that the trust's early recordkeeping was poor, and I was 
as surprised as anyone that there's supposed to be a decade old HSM 
somewhere.  But it is not 2006 any more, and I believe that the current 
trust is a lot different from what this document implies.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly