IETF Logo Mail Archive

Re: [tlp-interest] Results of 2022 Consultation on IETF Trust Restructuring

John Levine <johnl@taugh.com> Thu, 21 July 2022 00:06 UTC

Return-Path: <johnl@iecc.com>
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 6597DC13C539 for <tlp-interest@ietfa.amsl.com>; Wed, 20 Jul 2022 17:06:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.859
X-Spam-Level:
X-Spam-Status: No, score=-6.859 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.248, RCVD_IN_DNSWL_HI=-5, 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, 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=fwwP0+H2; dkim=pass (2048-bit key) header.d=taugh.com header.b=GRTJHDFz
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 W6-EqR0_YfQa for <tlp-interest@ietfa.amsl.com>; Wed, 20 Jul 2022 17:06:20 -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 98019C15A729 for <tlp-interest@ietf.org>; Wed, 20 Jul 2022 17:06:20 -0700 (PDT)
Received: (qmail 83497 invoked from network); 21 Jul 2022 00:06:18 -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=14627.62d8987a.k2207; bh=VNpstHtPh7GwhvW5YjQA6DcIyuKVLFyhqirye3XpMhM=; b=fwwP0+H2Y7K+PMz9cqUqaHgQbEMe1zzDlbfwPmvlm7Z6/hhFPMk2r9F5SGH1fv5dqZ4B3caYpXzF+XWXLCaiAo2AqvP1Oswpcmc1I3o2HmTGgf81wzHww7abOE2GJvCsiIdrPDKzt9ddM1/VDVV46EaKu2S7sVNhirybJACZoLhaSuU/JhJGMEd0wS1bt7IJOTfh7I0/ti4jRIWa8lyhNMwnb/XKWZCm6nZ6LCGyYXQEABxmbpjFUwiLWlaOEiIjpGHsLkvxFwZ1iqX/T+s5zHnOSHWvlLQUS5gv7zVPbgU7bxxs4dUXO31uBGyNRh0vRnk8N2Hxhy4CqHE3c3g8Ig==
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=14627.62d8987a.k2207; bh=VNpstHtPh7GwhvW5YjQA6DcIyuKVLFyhqirye3XpMhM=; b=GRTJHDFzFgDK1GG/n3j8xJNvfS4OazD7z+ZV5dik6a5RIGf2XkaS5MiEJ5rgZ80/ta8PbsD/CdYNqFLUX/qf84iciOTX5wUPZTbWMCjVEVukET5+v+VsBY2Cnaqe676LGJPGBn4nNzJyhgoTxHfQTTsGzKf3Rs1I5oOBF3sNiqdtEFoHDyRKJFohJLxFN6m0Q5uPb8bLzkDq2vO4koXP2J2YTF6gliJHh534KZWLi30g+pUg3se6JFr80fZbRn/1DPjv2ZUG9LUQrX6zL9Fz0eX6at8bEBhw+fLl1s/rr7ZimSVt50E6AGZLYuGn5olU7oIsqts9FCOuLjvEbyvEBQ==
Received: from ary.qy ([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; 21 Jul 2022 00:06:18 -0000
Received: by ary.qy (Postfix, from userid 501) id 82909464574C; Wed, 20 Jul 2022 20:06:16 -0400 (EDT)
Date: Wed, 20 Jul 2022 20:06:16 -0400
Message-Id: <20220721000617.82909464574C@ary.qy>
From: John Levine <johnl@taugh.com>
To: tlp-interest@ietf.org
In-Reply-To: <041320aa-e480-f115-d114-33f81c94d0d3@gmail.com>
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/tlp-interest/9gfrR9cdbyWxBLrNBPtTmNISAbU>
X-Mailman-Approved-At: Wed, 20 Jul 2022 17:07:53 -0700
Subject: Re: [tlp-interest] Results of 2022 Consultation on IETF Trust Restructuring
X-BeenThere: tlp-interest@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 21 Jul 2022 00:06:25 -0000

It appears that Brian E Carpenter  <brian.e.carpenter@gmail.com> said:
>Understood, but the words in RFC 8714 specifically talk about a trust and its settlors and trustees. I'd like to be sure
>that the pseudo-legal value of RFC 8714 isn't broken by the change of legal status. It's not a *problem*, just something
>to be checked in due course, since at most we'd need a one-paragraph update to 8714.

I suppose someone could do an 8714bis that changed IETF Trust to IETF
Trust, Inc. but I don't see any reason to do so.

We designed the "new" trust to have the same name and governance as
the existing one, and the bylaws specifically refer to the existing
processes. It would be perverse to imagine that 8714 does not apply.

R's,
John

v2.23.0 | Report a Bug | By Email