[CCG]IETF Trust Restructuring & Transfer of IANA Intellectual Property

Glenn Deen <gdeen@ietf-trust.org> Mon, 15 July 2024 18:25 UTC

Return-Path: <gdeen@ietf-trust.org>
X-Original-To: ccg@ietfa.amsl.com
Delivered-To: ccg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BED2C14F707 for <ccg@ietfa.amsl.com>; Mon, 15 Jul 2024 11:25:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=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=ietf-trust-org.20230601.gappssmtp.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 oAPdg0DHvVcQ for <ccg@ietfa.amsl.com>; Mon, 15 Jul 2024 11:25:49 -0700 (PDT)
Received: from mail-pf1-x433.google.com (mail-pf1-x433.google.com [IPv6:2607:f8b0:4864:20::433]) (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 7EAB0C14F74A for <ccg@ietf.org>; Mon, 15 Jul 2024 11:25:49 -0700 (PDT)
Received: by mail-pf1-x433.google.com with SMTP id d2e1a72fcca58-70b702be5e4so2230517b3a.0 for <ccg@ietf.org>; Mon, 15 Jul 2024 11:25:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf-trust-org.20230601.gappssmtp.com; s=20230601; t=1721067948; x=1721672748; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=UOG49bGXDJYMPoSWoXyU72Zc1TASJ49INTaMm8Hp72c=; b=Nc2CAcuYlitOmg6W8BCCMT+Cty499yBqdOQbZruIaLkWSsLRnL7xh7bSZ4jxN2QPoR bn9TaT1IRZsjoqgP9Vlf/NdP5v5oD2dAFOSHyHGMUnDwSBYizS1VNHDicns+nPQlh0Bt 3a841BRFoH1z0fEd51Ss+LFRaYt5ickmYcNvI51Zhwg957XNFaPGOuE0+JltM9etr3bS 5F5Bd8E8QBXC0HjluypvVgaUgqVK0HAY4pbG+Y4BJpg3A7IgMmRwxkJExco8h54UP0VG V+9OD9p5fXO6NyEPCXTkPbrY8WbIEIMRPLMc295cWsYL163nX6jC9nZe6PJoV2tu/eNY w6ow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721067948; x=1721672748; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=UOG49bGXDJYMPoSWoXyU72Zc1TASJ49INTaMm8Hp72c=; b=PWdp39o4Wf4fAQCDYH3zRZHWQ4Ma6ZEkDMZzEthiI7W2PA6Z2zoPDrtojMNXWTYSjc PzUXbmJ+ZpteMvVfU/zeSqm93BRjh9Ln6m2Rcz7lQWC3oTb4G8GrkL9AucKlbYSglGFs 2h3Zb7ckq4ftdryvcubWvGi0jqHHLojlrQZ+wGP14CJVMipDrOhxE8bufES+CINJDEJN ADA2CX7LZeMPG8+TKcxOlLFonB3RqUGN14gVKPF9RKElfs4939Jbwn5s15kKsAp6M/JL 7N+z3wsetk7ZSR+jTryF/kpVbLpVVVyECCzJdMYyF8z4JPViHsLRfRb4I4NdCuMajmz2 VrXw==
X-Gm-Message-State: AOJu0YyBtV022spNGNwqddqGPoUDUzPZm+li8f34ul9W3mpO5DIOokW7 BDFY+DDJ8Ibi+DM82rykzvtY2L6KwN54fDbCtq5oxWDpbqKF87GiM2D69XokaaJqmhL0zYdNimY TqI823Z6s+4AxcnWooBkVrYMTENty+sL8XOok+ZGIH2x2BjPK3uU=
X-Google-Smtp-Source: AGHT+IH3ZrD2k2u07YfZaMQrx0kw0IC8IvK4VXDDF3hf2f4R3qA0i2iFzEmQRETm4woRtnaznJUL6SQrkOBCm1I4g/8=
X-Received: by 2002:aa7:88cd:0:b0:706:8066:5cdf with SMTP id d2e1a72fcca58-70ba48c3dd2mr587419b3a.21.1721067948046; Mon, 15 Jul 2024 11:25:48 -0700 (PDT)
MIME-Version: 1.0
From: Glenn Deen <gdeen@ietf-trust.org>
Date: Mon, 15 Jul 2024 11:25:12 -0700
Message-ID: <CAFPasSBTaCARNPVh0kNF4n3nijf96fFHQ38BHumKLs-Xe1f=jw@mail.gmail.com>
To: ccg@ietf.org, trustees-restructuring@ietf.org, Glenn Deen <gdeen@ietf-trust.org>
Content-Type: multipart/alternative; boundary="000000000000ad9d3d061d4d5b57"
Message-ID-Hash: FHY4NXOUR7VLLEW4ASDP7TJMUYQSENSK
X-Message-ID-Hash: FHY4NXOUR7VLLEW4ASDP7TJMUYQSENSK
X-MailFrom: gdeen@ietf-trust.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ccg.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [CCG]IETF Trust Restructuring & Transfer of IANA Intellectual Property
List-Id: IANA IPR Community Coordination Group <ccg.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ccg/ppiab1Wr3pwXmiXZ_H89q2B2jQw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ccg>
List-Help: <mailto:ccg-request@ietf.org?subject=help>
List-Owner: <mailto:ccg-owner@ietf.org>
List-Post: <mailto:ccg@ietf.org>
List-Subscribe: <mailto:ccg-join@ietf.org>
List-Unsubscribe: <mailto:ccg-leave@ietf.org>

Hello CCG Chairs,


As Chair of the IETF Trust I'm writing to you on behalf of the IETF Trust
about the transfer of IANA Intellectual Property held and managed by the
IETF Trust to the new not-for-profit Delaware based IETF Intellectual
Property Management Corporation  (IPMC) that the current IETF Trust a
Virginia based Common Trust entity is restructuring into.


This IETF Trust restructuring has been underway for some time now and is
nearing its end.  We are now undertaking the final steps, which largely
involve the actual transfer of the Intellectual Property and IP rights held
by the IETF Trust.


For anyone not familiar with this restructuring work, the IETF Trust's role
remains the same, as does the appointment processes for the 5 IETF Trustees
(3 from IETF noncom, 1 from IETF IESG and 1 from ISOC Board of Trustees).
The IETF Trustees will now be Directors of the new corporation.


What has changed is all legal under the covers, with the IETF Trust legally
changing from a Virginia Common Trust to a Delaware not-for-profit
corporation which like the Virginia entity has been recognized by the IRS
as a not-profit 501c3.      If you're interested in the details , the new Legal
Documents <https://trustee.ietf.org/documents/founding-documents/> [1] and
the Community Consultation
<https://trustee.ietf.org/about/community-consultation-on-restructuring-the-ietf-trust/>
[2] are all available on the IETF Trust <https://trustee.ietf.org> website (
https://trustee.ietf.org)


The IETF Trust provides service beyond the IETF community by holding IANA
related Intellectual Property assigned to it as part of the 2016 IANA
restructuring.    See Exhibits A & B in the IANA Assignment Agreement
<https://trustee.ietf.org/wp-content/uploads/Assignment-Agreement-2016-09-30-Executed.pdf>
[3]
for the full asset list of IANA IP  consisting of Trademarks and Domain
Names.      Under the agreement, the IETF Trust holds the IANA TMs,
maintaining registrations and taking appropriate actions as needed to
protect the TMs.    The IETF Trustees also provide change approval for the
transferred DNS Domains whereby approval by any 3 of the 5 Trustees is
required for any technical changes to the domains.


During a review of reassignment of agreements the IETF Trust with different
parties, we recently came across a requirement in the 2016 IANA agreements
[3][4] around the IANA Intellectual Property held by the IETF Trust that
requires that we consult and get approval from the CCG for the Transfer of
the IANA IP assets.


BTW, Here is the requirement:   Section 4.2 of the Community Agreement
<https://trustee.ietf.org/wp-content/uploads/Community-Agreement-2016-09-30-Executed.pdf>
 [4]



*4.2 Encumbrances and Transfer. Except as contemplated by this Agreement
and the License Agreements, the IETF Trust shall not sell, lease (as
lessor), transfer or otherwise dispose of, or mortgage or pledge, or impose
or suffer to be imposed any Encumbrance on, in whole or in part, any of the
IANA Intellectual Property without the prior written approval of the CCG,
which shall not be unreasonably withheld.*


While the transfer isn't to outside of the IETF Trust, we've tried to err
on the side of compliance so we're writing to the CCG chairs.


To be fully transparent, if you check in the US TM database, you'll see
that the IANA TMs were transferred as part of a batch of transfers done for
the IETF TMs held by the Trust.   Our sincere apologies for getting ahead
of obtaining CCG approval, we had previously reviewed the IANA agreements
related to re-assignment, but only on a recent re-review came across the
specific need in Section 4.2 related to the CCG approval.     Now that we
see the requirement, we are working to correct and comply.


Current status of IANA IP: The IANA TMs transfers have been submitted to
various TM regimes that they are registered in and some like the US have
been processed.     The DNS Domains have not yet been transferred and the
Trustees of the Virginia Trust are continuing their role as technical
change approvers.


To comply with our IANA agreement under section 4.2, the IETF Trust intends
to send to the 3 CCG Chairs a formal transfer approval request for the IANA
IP via Docusign.


Since we've never done this sort of request with the CCG we don't have any
past process for IETF Trust::CCG interaction to follow, hence this note.


In terms of time, we'd like to resolve this as quickly as possible.  We're
very near the end of the restructuring and we'd like to complete our asset
transfers.


Are there any questions that you have, or should we go ahead and send the
notice over for signatures?


Referenced Links:


[1] https://trustee.ietf.org/documents/founding-documents/

[2]
https://trustee.ietf.org/about/community-consultation-on-restructuring-the-ietf-trust/

[3]
https://trustee.ietf.org/wp-content/uploads/Assignment-Agreement-2016-09-30-Executed.pdf

[4]
https://trustee.ietf.org/wp-content/uploads/Community-Agreement-2016-09-30-Executed.pdf




Regards

Glenn Deen,

IETF Trust Chair