IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 21 July 2022 05:10 UTC

Return-Path: <brian.e.carpenter@gmail.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 7AD6FC157B3A for <tlp-interest@ietfa.amsl.com>; Wed, 20 Jul 2022 22:10:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level:
X-Spam-Status: No, score=-2.11 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 qiCDTWilJoqY for <tlp-interest@ietfa.amsl.com>; Wed, 20 Jul 2022 22:10:00 -0700 (PDT)
Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 11E31C14CF16 for <tlp-interest@ietf.org>; Wed, 20 Jul 2022 22:10:00 -0700 (PDT)
Received: by mail-pg1-x533.google.com with SMTP id 72so678522pge.0 for <tlp-interest@ietf.org>; Wed, 20 Jul 2022 22:10:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to:content-transfer-encoding; bh=iB3x/2GFcvn0FdmgxJzVnUeuYKafNqZ7AIOsjNGHjew=; b=EcKurPFhwFYbYq2YRf9J1YCOjbffyubWaGlMTKLPrgdBEc91duT+Y2Er8docI8JX0x Zx67XUJEYp6xIkcej+neDH62VbXSFXsXFrQQZvqBHORcm5KoCcmmRxNIVMwCrhaQ8KfB r4w+fpCoj38CGr9xYRm+rTIovsTowK931ljFeV5vomhGtp1r23QWNl216oeOmcSOb0M+ HIztY5WRTu9lbmMqpJ3j6ovIyijnQdbv7/VCvyA260QHWMWvnQ22S/19NCDxbvw/82U+ jPUANygtwR2qLhs8ErhHR+xWDxgQSaHwSe/6iIEWPHcxwKX7KMWILGpRuHbDBKTRjQBU 3Bkg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to :content-transfer-encoding; bh=iB3x/2GFcvn0FdmgxJzVnUeuYKafNqZ7AIOsjNGHjew=; b=p/OuolksXMz5U0SMZNqASZ92XeyzF00AvTNwfO1Q6mxNFMmDgBQOYVfv44sU1MqR0A byRC+IU7wnt/tCwHfD61dtDQjzA9TJI6rOPtLy9L3NG9FMutLWSNXggICYgeIN4Dni+u z4BQffpEXx0H2WMv29/v/1IeAVPQygsuhqf3izBjwyzCbUOeScM8zLFedKdqOsYtHsGH xz0WKChAXCi9IkQhcHli90HHRdM0OQBulhrEKq12mHuI0axZsjM/XNOxQRHQNsyq7ySD 5MYpEW/TAj6ozQar1Ev7WwJ+j5nalnPRkyrCSIMcmRRouK+T8sWbt/zuLQ/GGVYWU7hC mmHw==
X-Gm-Message-State: AJIora9oH+P8NiAPsYyoZfjk2H9SzCpvtWCBWJaBW08Lrp5KDbN2Olyn U9hpS4kpaKQOpvyurCVknJH1sH7NFxTs1Q==
X-Google-Smtp-Source: AGRyM1uHKmPy/QlSD8zkN4LY87qnahhb0hvouVRb2npGLG0ywye2l0O7ze2fRaAJ/Y8pu7CkoKGBqQ==
X-Received: by 2002:a62:1891:0:b0:528:5d43:c3ab with SMTP id 139-20020a621891000000b005285d43c3abmr42991208pfy.79.1658380198675; Wed, 20 Jul 2022 22:09:58 -0700 (PDT)
Received: from ?IPV6:2406:e003:1124:9301:80b2:5c79:2266:e431? ([2406:e003:1124:9301:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id v12-20020aa799cc000000b00528c149fe97sm584094pfi.89.2022.07.20.22.09.56 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 20 Jul 2022 22:09:58 -0700 (PDT)
Message-ID: <3bbebf01-8dfb-5df3-32c4-56605fc89531@gmail.com>
Date: Thu, 21 Jul 2022 17:09:53 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: John Levine <johnl@taugh.com>, tlp-interest@ietf.org
References: <20220721000617.82909464574C@ary.qy>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <20220721000617.82909464574C@ary.qy>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tlp-interest/2q6CF4_9wSR66FScLm3RKTn3rg4>
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 05:10:00 -0000

On 21-Jul-22 12:06, John Levine wrote:
> 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.

No, that isn't my concern. It's that the wording is a very specific
reference to a trust and its settlors. IANAL but ...
  
> 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.

... it's precisely to fend off perverse interpretations that I think
this should be reviewed before we declare the job done.

    Brian

v2.23.0 | Report a Bug | By Email