IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 20 July 2022 23:26 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 EF02FC131925 for <tlp-interest@ietfa.amsl.com>; Wed, 20 Jul 2022 16:26:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, RCVD_IN_DNSWL_BLOCKED=0.001, 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 (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 hCuIP3GPn-vg for <tlp-interest@ietfa.amsl.com>; Wed, 20 Jul 2022 16:26:05 -0700 (PDT)
Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) (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 23FEAC13485C for <tlp-interest@ietf.org>; Wed, 20 Jul 2022 16:26:05 -0700 (PDT)
Received: by mail-pl1-x62d.google.com with SMTP id z3so234363plb.1 for <tlp-interest@ietf.org>; Wed, 20 Jul 2022 16:26:05 -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=RWvS5t/QkoMvSeeoa49ey3PUlgSTKCOUZtvAWR11eV4=; b=Rs6sYTeYvLCH3nWjuOR/69MXiKuBr8O+vko0i8cQrwZdmVWdq8VOXbHpyZ/gOs3DLH TN+GjRZTo7QDMgi/e3evjk1sOR4v28LBo5WLD+K2YQ4GkXq8a4LfNd2GdaX0UZd7u3cR UpolSp3LzqB+OdZEhk68ALgSkaPimYhP5hF58zvRYpcvQH85V7DXaTg5wrOTqTWXxYHI SlMRTLC698zSj2qzxoPWQtpqaL1zRIG2zM2MxCvx0u1UWS9Mypi6sRJKIKPl3V5TuF9m 1Gk1bzakukU78QnWXbsrHWzE7Y24IvqfKp/iYq88tEHu/bO2QSS6OKEv4AXdlu3DAus4 eBTA==
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=RWvS5t/QkoMvSeeoa49ey3PUlgSTKCOUZtvAWR11eV4=; b=HM+j3zxNTeu6Zjrf9GP3r8RdEcOS0b2q8dJsePRsDxSFIG5LgewgYuy1sFbZZd2QGR +fX+OjiGm7Ya7BAArB1TdHIOKUs+obyQHVMkWRNsdhbqFU1JzeOwjDDZbed3iCydhPIN 9zKDURp+adOZ3OI9p/leWJvyhR+K7B+xcKuIyXi3gUHVUnP7aApL8ForMRshFhTq4brS 104K8firUHVjFc7c73Vmx3AHdxjDgSb4V/ZWz+0HsJfTpu3RmZguemGdogo7upVXYpgx P3nGEXsRhLKCX+5MQUgdx6lTetv5qaml+IYbZIVAGOH1A8NX0pdFZKYQanxNqXKCceLH xy5w==
X-Gm-Message-State: AJIora8eArWwXxKwFazN8Kdy2UKtuB3i/sqI04/+c0bRWI37736nn5vz LnWemVdnLimRGlZlJrefGRlzGc3nOY0bcQ==
X-Google-Smtp-Source: AGRyM1sZSnvC2NdFrwqMX+kZC4PMrgrBwTodghgeCd/Kvg8iSjBlXLs3X4nuinpFba8vf+uaf8jSag==
X-Received: by 2002:a17:902:ea42:b0:16c:ca53:816c with SMTP id r2-20020a170902ea4200b0016cca53816cmr29655490plg.94.1658359564018; Wed, 20 Jul 2022 16:26:04 -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 x28-20020aa78f1c000000b0052ba859da14sm172481pfr.184.2022.07.20.16.26.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 20 Jul 2022 16:26:03 -0700 (PDT)
Message-ID: <041320aa-e480-f115-d114-33f81c94d0d3@gmail.com>
Date: Thu, 21 Jul 2022 11:25:59 +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: "Deen, Glenn (NBCUniversal)" <Glenn.Deen@nbcuni.com>, "tlp-interest@ietf.org" <tlp-interest@ietf.org>
References: <SJ0PR14MB42351E714BB17A8CA9233478E28E9@SJ0PR14MB4235.namprd14.prod.outlook.com> <445c8325-a75e-2d46-c7c2-22a68016b7cf@gmail.com> <SJ0PR14MB4235C916F2996836F45B4490E28E9@SJ0PR14MB4235.namprd14.prod.outlook.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <SJ0PR14MB4235C916F2996836F45B4490E28E9@SJ0PR14MB4235.namprd14.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/tlp-interest/CUg0YEY7OMByg5NpTm6yX1dtkYo>
X-Mailman-Approved-At: Wed, 20 Jul 2022 16:28:39 -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: Wed, 20 Jul 2022 23:26:09 -0000

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.

Regards
    Brian

On 21-Jul-22 09:57, Deen, Glenn (NBCUniversal) wrote:
> Brian,
> 
> The plan is to continue the use of the name “IETF Trust” for the not-for-profit corporation.  This makes things much easier since no documentation would need updating.
> 
> The final decision on using the name IETF Trust is with the State of Delaware but we did reach out to them during the planning phase and they indicated that due to having used the name for the entity for so long that they would be inclined to accept it.
> 
> We won’t know for sure until we file the articles of incorporation, and they are approved, but for now we are proceeding with the expectation that the new entity will continue to use the name of the old one.
> 
> -glenn
> 
> On 7/20/22, 1:47 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com> wrote:
> 
> Will we need any updates to RFC 8714? In particular there is a specific description of the Trust at https://urldefense.com/v3/__https://www.rfc-editor.org/rfc/rfc8714.html*name-ietf-trust__;Iw!!PIZeeW5wscynRQ!sCfPdNl-PTbp9ta5PPrdrGRxsMbi8HI1GzxyQ3JvwnVClCs2BhdB9mIkBhxikAScEu-8RM8ANXYbsDAZglIJOhREXlw$ <https://urldefense.com/v3/__https:/www.rfc-editor.org/rfc/rfc8714.html*name-ietf-trust__;Iw!!PIZeeW5wscynRQ!sCfPdNl-PTbp9ta5PPrdrGRxsMbi8HI1GzxyQ3JvwnVClCs2BhdB9mIkBhxikAScEu-8RM8ANXYbsDAZglIJOhREXlw$>  that refers to its current structure, not to its future structure.
> 
> Regards
>      Brian Carpenter
> 
> On 21-Jul-22 04:57, Deen, Glenn (NBCUniversal) wrote:
>> The IETF Trust conducted a community consultation on restructuring of the IETF Trust from a Virginia Common Trust to a not for profit corporation registered in Delaware.
>> 
>> The IETF Trust published a web page[1] holding materials explaining the motivation, the current IETF Trust Agreement which the Trust operates under, and the proposed bylaws of the new corporation which are based directly on the current Trust Agreement.
>> 
>> The Trustees used the TLP-INTEREST[2]  Mailing list to collect feedback and questions on the proposed restructuring.
>> 
>> The Trustees also presented on the restructuring at the IETF113 Plenary[3], the March 2022 ISOC Board of Trustees meeting, and held on May 23, 2022 an informational Q&A webinar[4].  The recordings of the webinar and IETF plenary are available on YouTube [3][4].
>> 
>> The IETF Trust serves several communities, and we received engagement from many interested parties including IETF community members, the IETF LLC, the Regional Internet Registry (RIR) community including ARIN, and ICANN.
>> 
>> Based on the feedback received during the consultation the IETF Trustees have concluded that the Trust will proceed with the proposed restructuring to a not for profit Delaware corporation.
>> 
>> During the consultation, the IETF LLC asked the Trustees to consider expanding the restructuring scope to include moving the functions of the IETF Trust into the IETF Administrative LLC.  The Trustees have discussed this suggestion and do not believe that  it is an appropriate change to make.  Replacing the currently independent IETF Trust with  the IETF LLC, and by association ISOC, would fundamentally alter the proposed restructuring and would greatly expand the scope to include the complex set of issues surrounding the role of the IETF Trust and the assets it manages.
>> 
>> 
>> The IETF Trust will move forward with the restructuring plan with the next phases to be formally filing the articles of incorporation for the new corporation, applying for IRS 501(c)3 non-profit status, and once obtained conduct the process of transferring  the Trust’s current assets, agreements, and licenses to the new not-for-profit corporation.  This is expected to run through 2023. The Trustees will provide updates to the community as the restructuring proceeds.
>> 
>> Thank you to the many people and organizations that participated in this consultation.
>> 
>> IETF Trustees:
>>       Glenn Deen (Chair)
>>       Kathleen Moriarity (Treasurer)
>>       John Levine,
>>       Stephan Wenger
>>       Joel Halpern
>> 
>> [1] https://urldefense.com/v3/__https://trustee.ietf.org/about/community-consultation-on-restructuring-the-ietf-trust/__;!!PIZeeW5wscynRQ!sCfPdNl-PTbp9ta5PPrdrGRxsMbi8HI1GzxyQ3JvwnVClCs2BhdB9mIkBhxikAScEu-8RM8ANXYbsDAZglIJSvArUkY$ <https://urldefense.com/v3/__https:/trustee.ietf.org/about/community-consultation-on-restructuring-the-ietf-trust/__;!!PIZeeW5wscynRQ!sCfPdNl-PTbp9ta5PPrdrGRxsMbi8HI1GzxyQ3JvwnVClCs2BhdB9mIkBhxikAScEu-8RM8ANXYbsDAZglIJSvArUkY$>  <https://urldefense.com/v3/__https://trustee.ietf.org/about/community-consultation-on-restructuring-the-ietf-trust/__;!!PIZeeW5wscynRQ!sCfPdNl-PTbp9ta5PPrdrGRxsMbi8HI1GzxyQ3JvwnVClCs2BhdB9mIkBhxikAScEu-8RM8ANXYbsDAZglIJSvArUkY$ >
>> 
>> [2] TLP-Interest Archive: https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/browse/tlp-interest/__;!!PIZeeW5wscynRQ!sCfPdNl-PTbp9ta5PPrdrGRxsMbi8HI1GzxyQ3JvwnVClCs2BhdB9mIkBhxikAScEu-8RM8ANXYbsDAZglIJmlxaAW0$ <https://urldefense.com/v3/__https:/mailarchive.ietf.org/arch/browse/tlp-interest/__;!!PIZeeW5wscynRQ!sCfPdNl-PTbp9ta5PPrdrGRxsMbi8HI1GzxyQ3JvwnVClCs2BhdB9mIkBhxikAScEu-8RM8ANXYbsDAZglIJmlxaAW0$>  <https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/browse/tlp-interest/__;!!PIZeeW5wscynRQ!sCfPdNl-PTbp9ta5PPrdrGRxsMbi8HI1GzxyQ3JvwnVClCs2BhdB9mIkBhxikAScEu-8RM8ANXYbsDAZglIJmlxaAW0$ >
>> 
>> [3] IETF 113 Plenary Recording: https://urldefense.com/v3/__https://www.youtube.com/watch?v=yviSgV27ULM&t=2940s__;!!PIZeeW5wscynRQ!sCfPdNl-PTbp9ta5PPrdrGRxsMbi8HI1GzxyQ3JvwnVClCs2BhdB9mIkBhxikAScEu-8RM8ANXYbsDAZglIJ_evzutQ$ <https://urldefense.com/v3/__https:/www.youtube.com/watch?v=yviSgV27ULM&t=2940s__;!!PIZeeW5wscynRQ!sCfPdNl-PTbp9ta5PPrdrGRxsMbi8HI1GzxyQ3JvwnVClCs2BhdB9mIkBhxikAScEu-8RM8ANXYbsDAZglIJ_evzutQ$>  <https://urldefense.com/v3/__https://www.youtube.com/watch?v=yviSgV27ULM&t=3123s__;!!PIZeeW5wscynRQ!sCfPdNl-PTbp9ta5PPrdrGRxsMbi8HI1GzxyQ3JvwnVClCs2BhdB9mIkBhxikAScEu-8RM8ANXYbsDAZglIJb0IGDOE$ >
>> 
>> [4] May 23 Webinar Recording: https://urldefense.com/v3/__https://youtu.be/wzJbLnjq_fk__;!!PIZeeW5wscynRQ!sCfPdNl-PTbp9ta5PPrdrGRxsMbi8HI1GzxyQ3JvwnVClCs2BhdB9mIkBhxikAScEu-8RM8ANXYbsDAZglIJsLF5yl4$ <https://urldefense.com/v3/__https:/youtu.be/wzJbLnjq_fk__;!!PIZeeW5wscynRQ!sCfPdNl-PTbp9ta5PPrdrGRxsMbi8HI1GzxyQ3JvwnVClCs2BhdB9mIkBhxikAScEu-8RM8ANXYbsDAZglIJsLF5yl4$>  <https://urldefense.com/v3/__https://youtu.be/wzJbLnjq_fk__;!!PIZeeW5wscynRQ!sCfPdNl-PTbp9ta5PPrdrGRxsMbi8HI1GzxyQ3JvwnVClCs2BhdB9mIkBhxikAScEu-8RM8ANXYbsDAZglIJsLF5yl4$ >
>> 
>> 
>> _______________________________________________
>> tlp-interest mailing list
>> tlp-interest@ietf.org
>> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/tlp-interest__;!!PIZeeW5wscynRQ!sCfPdNl-PTbp9ta5PPrdrGRxsMbi8HI1GzxyQ3JvwnVClCs2BhdB9mIkBhxikAScEu-8RM8ANXYbsDAZglIJEEJsH6Y$ <https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/tlp-interest__;!!PIZeeW5wscynRQ!sCfPdNl-PTbp9ta5PPrdrGRxsMbi8HI1GzxyQ3JvwnVClCs2BhdB9mIkBhxikAScEu-8RM8ANXYbsDAZglIJEEJsH6Y$>
>

v2.23.0 | Report a Bug | By Email