IETF Logo Mail Archive

Re: [tlp-interest] [admin-discuss] A clerical correction to the IETF Trust Legal Provisions 5.0

Lars Eggert <lars@eggert.org> Tue, 21 September 2021 08:57 UTC

Return-Path: <lars@eggert.org>
X-Original-To: tlp-interest@ietfa.amsl.com
Delivered-To: tlp-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B8883A1365; Tue, 21 Sep 2021 01:57:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zHidC_6buRXP; Tue, 21 Sep 2021 01:57: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 8D22A3A1363; Tue, 21 Sep 2021 01:57:16 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:e86e:250b:c4c0:fcfb]) (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 4442F600639; Tue, 21 Sep 2021 11:57:09 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1632214629; bh=CCj1KtCjksFweh8D744c8yTZAPzdAcz7M1pinjX/84k=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=wfLwcrpS+whi00ZAKawh6bUjK9bg3hmXqLeaUdK3E86pcjuQasNwWUnrI3uuWwavk 2epmPec54dfDwBh3VQJobiNCDh6K+/rSmbC6SzN4qBTmo89c1nFth8xFBHo5W7nxM/ HQ6rVZFSfK3oavZQTZIoH3uQ9y61gIC+np1M9+us=
From: Lars Eggert <lars@eggert.org>
Message-Id: <A3B87699-956A-4209-A850-62B940799ADB@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_F24E3A78-7C68-45E9-AE8C-53930CBC6D20"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Tue, 21 Sep 2021 11:57:08 +0300
In-Reply-To: <cab44b30-90fe-7abf-1bb4-12ce844f41aa@taugh.com>
Cc: admin-discuss@ietf.org
To: tlp-interest@ietf.org
References: <cab44b30-90fe-7abf-1bb4-12ce844f41aa@taugh.com>
X-MailScanner-ID: 4442F600639.ADF6B
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/tlp-interest/_ZXti5D1SACNSTQzSwaQ-3aHa74>
Subject: Re: [tlp-interest] [admin-discuss] A clerical correction to the IETF Trust Legal Provisions 5.0
X-BeenThere: tlp-interest@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of proposed revisions to the Trust Legal Provisions <tlp-interest.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tlp-interest>, <mailto:tlp-interest-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tlp-interest/>
List-Post: <mailto:tlp-interest@ietf.org>
List-Help: <mailto:tlp-interest-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tlp-interest>, <mailto:tlp-interest-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Sep 2021 08:57:21 -0000

Hi,

On 2021-8-24, at 5:18, John R Levine <johnl@taugh.com> wrote:
> The trustees recently noted a confusing clerical error in the TLP where it describes the license we offer on code components of RFCs and other IETF contributions.
...
> Since this update only corrects a mistake and makes no substantive change to the TLP or the licenses it grants, we plan to post this as a correction rather than as a new version of the TLP.  Once we have done that we also plan to request changes to I-D and RFC boilerplate that use the wrong name, again, with no changes to the licenses themselves.

is there a timeline for this correction to happen?

I'm asking, because while for the Trust this is a relatively straightforward update to some of their web pages, on the IETF side we need some tools work to implement this change (in addition to also needing to update a larger number of web sites and open source repositories.)

Thanks,
Lars

v2.31.3 | Report a Bug | By Email | System Status