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

Lars Eggert <lars@eggert.org> Sat, 22 October 2022 08:34 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 6C235C1522D9 for <gendispatch@ietfa.amsl.com>; Sat, 22 Oct 2022 01:34:41 -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, SPF_HELO_NONE=0.001, 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 (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 WHSwZtQ9ouop for <gendispatch@ietfa.amsl.com>; Sat, 22 Oct 2022 01:34:36 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 D7B14C1522D5 for <gendispatch@ietf.org>; Sat, 22 Oct 2022 01:34:35 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:c9c7:24a1:9fae:2cc5]) (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 ABB121DEA79; Sat, 22 Oct 2022 11:33:55 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1666427637; bh=jDSd2uzSGxwnhQa8M0RNhHvAtJob5clzICpxNU0xI8k=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=SGfBT8Ote2cK8IqwmnjZu16IeOs0SnH+/S1zmZySsgaTTpXVDcJTl+YfKrdzrcKT7 0wH2Oc+d3mOeOe3NMkvbLqcv2soZvlmkSNstmEh+Xnw9YdZxy2BTIV3/25G1eBjzFx 3kfP+1o2PSQ3I+BwRxPAcZxJsmLNVbsMNw/I68J0=
Content-Type: multipart/signed; boundary="Apple-Mail=_6A93FE3D-0756-4F98-9B57-0622DF15039A"; 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: <20221022034724.49A774D1F7CC@ary.local>
Date: Sat, 22 Oct 2022 11:33:55 +0300
Cc: gendispatch@ietf.org, sayrer@gmail.com
Message-Id: <AEDD55EF-3883-44A2-BE6E-233D4D8C7639@eggert.org>
References: <20221022034724.49A774D1F7CC@ary.local>
To: John Levine <johnl@taugh.com>
X-MailScanner-ID: ABB121DEA79.A65E5
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/KFyLa6a8as-SIHZxcUR_alQkoLw>
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 08:34:41 -0000

Hi,

On 2022-10-22, at 6:47, John Levine <johnl@taugh.com> wrote:
> As the guy who pushed the trust to set up the asset register a few
> years ago, I find the document's assertion both uncalled for and
> offensive.

is that asset register publicly accessible?

> Is there some reason neither of the authors nor anyone else
> who is interested was able to ask any of the trustees about it?

We did send a draft of this document to the Trust before submission, and Glenn provided feedback that we tried to reflect in the document. We even acknowledge that in the document.

> As far as I know, the asset register is complete other than perhaps
> one or two recent copyright licenses from authors of early RFCs.

Is it public?

> 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 am also baffled at the adversarial tone of this document, and the
> ahistorical way it ignores the Trust's unique history as an entity
> specifically set up to not be part of either ISOC or CNRI.

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.

Thanks,
Lars