IETF Trust report at IETF116

The IETF Trust <ietf-trust@ietf.org> Tue, 28 March 2023 04:35 UTC

Return-Path: <ietf-trust@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 93CE5C151548 for <ietf-announce@ietf.org>; Mon, 27 Mar 2023 21:35:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: The IETF Trust <ietf-trust@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IETF Trust report at IETF116
X-Test-IDTracker: no
X-IETF-IDTracker: 9.15.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: IETF-announce@ietf.org
Message-ID: <167997814959.18879.15550837520471908326@ietfa.amsl.com>
Date: Mon, 27 Mar 2023 21:35:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/pmx7YEVrnqqE_wGST2vYR1r9HfU>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Mar 2023 04:35:49 -0000

Hello,

The IETF Trust will hold office hours at IETF 116 in Room 320 on Wednesday 3:30-4:30pm (local time) 


This is the first IETF Trust update email around an IETF meeting that we’re aware of, and is a bit of an experiment to see if there is interest in hearing from the Trust in this way.  Traditionally the IETF Trust has not published reports to the community ahead of IETF meetings, instead it has used the IETF Trust site announcements and IETF plenaries to provide updates, so look to those sources for previous updates.   

The IETF Trust is tasked with holding, managing, and protecting IP rights and assets assigned to it through IETF Contributions, IETF RFCs, IAB, IESG, and IRTF publications and the Independent RFC Stream.  The Trust also manages assets transferred to it from the IANA Transition.  In addition to copyrights and software licenses, assets such as domain names and trademarks including the marks for the IETF and IANA are also held and managed.

Most IETF participants will know the IETF Trust from its mention in the boilerplate copyright appearing in IETF Internet Drafts and RFCs and for the role it plays in BCP 78 and RFC 5378. More background on the Trust and the FAQ covering it’s role are available on the IETF Trust web site (https://trustee.ietf.org/) and (https://trustee.ietf.org/about/faq/)

As the Trust has shared in the past, we’re in the midst of restructuring the legal backend from a Virginia Trust to the Delaware based IETF Intellectual Property Management Corporation.  The background on the restructuring  is available at (https://trustee.ietf.org/about/community-consultation-on-restructuring-the-ietf-trust/).  

The latest restructuring update is that the corporation has been incorporated in Delaware and the process of establishing the new corporation as an IRS 501c3 non-for-profit entity is underway.   Once this is complete, the work of transferring the assets of the current Trust to the new corporation will begin. The restructuring is expected to continue throughout 2023.

Since the IETF 115 meeting, the IETF Trust has done the following actions:

Renewed Trademark Registrations

U.S. Trademark Reg. No. 2,764,089 for INTERNET ASSIGNED NUMBERS AUTHORITY
Trademark Registration No. TMA717943 for IETF in Canada

The Approved 2023 IETF Trust Budget is available at (https://trustee.ietf.org/wp-content/uploads/Approved-2023-IETF-Trust-Budget-Published.pdf).   

Of note for 2023 is that there is an expected one-time increase in legal services expenses related to the work of transferring the assets to the new corporation and an increase in the reserve funds with a goal of establishing a 2 year operating reserve.   For 2024, the guidance is that the operating budget will return to roughly pre-restructuring levels with increases related to inflation and the change in legal representation agreements taken into account.

Finally, the IETF Trust worked to correct the application of template text used to permit YANG Module security template text so it fit within the Trust Legal Provisions specification for TEMPLATE TEXT tags.  See draft-moriarty-yangsecuritytexts section 2 for the correct use of TEMPLATE TEXT tags that are in compliance with the TLP 5.0 use of template tags. (https://trustee.ietf.org/documents/trust-legal-provisions/tlp-5).    

The IETF Trust plans on providing some future education, likely around IETF 117, on the correct use of TEMPLATE TEXT tags for content that RFCs intend to be used as a modifiable template by adopters.

Regards
Glenn Deen, IETF Trust Chair on behalf of the the IETF Trustees,
Kathleen Moriarty(Treasurer), Joel Halpern, Stephan Wenger, Victor Kuarsingh

https://trustee.ietf.org/