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

Lars Eggert <lars@eggert.org> Mon, 24 October 2022 07:11 UTC

Return-Path: <lars@eggert.org>
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 D94E6C1522AE for <gendispatch@ietfa.amsl.com>; Mon, 24 Oct 2022 00:11:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_HELO_NONE=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 (1024-bit key) header.d=eggert.org
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 sFmSM44IYzby for <gendispatch@ietfa.amsl.com>; Mon, 24 Oct 2022 00:11:16 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:4000:400:211:32ff:fe22:186f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C7C8C1522A6 for <gendispatch@ietf.org>; Mon, 24 Oct 2022 00:11:16 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:c4c:e5f9:1db5:c2ce]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 9F2D61DC2EE; Mon, 24 Oct 2022 10:11:06 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1666595466; bh=en8ATVEyzcSzx6CeC4ezcOEruuoRiDeWI4WxBKp3Dus=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=JtKi11kqY4xg8YBEshGc3oHcGWfPkEMiGAPIuQFWUd3BfT5ujxK54qAUyDvzItKnI wVA+PdZVrAbiHCOLthKJsUA0jDHOUyQIoUJ+e+m0zQJaavEI7AzJF1jh1hx8sxrmbu tL9CHKEt6m7D/EVXQbCT9gKoSpsVxM++MgTQncAI=
Content-Type: multipart/signed; boundary="Apple-Mail=_7721C135-A036-4573-87B7-92F4A8916810"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <6beaaf54-8342-673f-a4c8-332edf529070@gmail.com>
Date: Mon, 24 Oct 2022 10:11:06 +0300
Cc: John R Levine <johnl@taugh.com>, gendispatch@ietf.org
Message-Id: <48BE6660-65D2-44DB-B316-C11241386253@eggert.org>
References: <20221022034724.49A774D1F7CC@ary.local> <AEDD55EF-3883-44A2-BE6E-233D4D8C7639@eggert.org> <bcc9a910-ada0-c491-0bc4-8ac4effecf50@taugh.com> <6beaaf54-8342-673f-a4c8-332edf529070@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-MailScanner-ID: 9F2D61DC2EE.A75C5
X-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/BCWcI5Uk_ygsWJR3S6ZFMdK8Qxo>
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: Mon, 24 Oct 2022 07:11:20 -0000

Hi,

On 2022-10-23, at 0:25, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> On 23-Oct-22 05:02, John R Levine wrote:
>>> 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?
> 
> As far as I recall, the idea of "actively" approaching those several
> thousand authors was abandoned about 10 seconds after it was suggested,
> as completely impractical. It would have involved tracking down a large
> number of people, or in some cases their executors or heirs. A rough
> count of the number of distinct author names in the pre-5378 RFCs is
> 3810, although that includes some probable duplicates like 'V.Cerf' and
> 'V.G.Cerf'. (I wrote a Python script to compute that number. Run
> against the complete RFC index, it finds 6328 distinct author names.)
> 
> We (the original Trustees) did send messages to the obvious places
> asking people to sign the "RFC DOCUMENTS NON-EXCLUSIVE LICENSE"
> and some people did happily sign it, but the response was underwhelming.

thanks for the history; I wasn't aware that the Trust at some point decided to give up on acquiring per-5378 licenses from authors.

I'll again say that if we had published procedures for management of the Trust assets, presumably that change in the Trust's strategy would have been reflected in that document, and would have been visible to the community.

> It is absolutely true that not all the signed licenses are listed in the
> asset register; several more than the three listed were signed in 2007, but
> I have no records. I signed one myself. As a Trustee, I assumed that the
> IAD would retain and archive them. They may be gathering dust in a
> filing cabinet somewhere.

See my reply to John; I find that a deeply disturbing answer. The Trust has a key function in the overall IETF, one that necessitates accurate record-keeping. I find it astonishing that having documents "gather dust in a filing cabinet somewhere" is apparently how (some of) the assets the community has entrusted to the Trust are being maintained.

Thanks,
Lars