[tlp-interest] Re: October 2025 Notice of Proposed Amendment to IETF IPMC Bylaws

Jay Daley <exec-director@ietf.org> Thu, 30 October 2025 01:41 UTC

Return-Path: <jay@staff.ietf.org>
X-Original-To: tlp-interest@mail2.ietf.org
Delivered-To: tlp-interest@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 4F5717E9BBF4 for <tlp-interest@mail2.ietf.org>; Wed, 29 Oct 2025 18:41:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=staff-ietf-org.20230601.gappssmtp.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32nx9ao1dd3L for <tlp-interest@mail2.ietf.org>; Wed, 29 Oct 2025 18:41:35 -0700 (PDT)
Received: from mail-qv1-xf29.google.com (mail-qv1-xf29.google.com [IPv6:2607:f8b0:4864:20::f29]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id CED117E9BBE9 for <tlp-interest@ietf.org>; Wed, 29 Oct 2025 18:41:35 -0700 (PDT)
Received: by mail-qv1-xf29.google.com with SMTP id 6a1803df08f44-87dcb1dd50cso8835376d6.3 for <tlp-interest@ietf.org>; Wed, 29 Oct 2025 18:41:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1761788489; x=1762393289; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=OS8N6F34lc9aWRU3KSYxthoXp54pVztCVFhLSLEz93c=; b=LH5J4/rBcid1GeciJj347BEGR4XfBBO5ubC7WERpL3VKpeFm8+WJu2+e4AMpcAUQRQ qc7M1f3fuGLJXvUaIknn1FFBSOstDGm0tsnsvxFoooeckshIcHGAj42g+nv5hrRiuasG LtLaPT/g8iek+m5kP3j2Jltxjx7lyJq4cJftqQXkRmoRHZkVh0JTHkUNpfMIEeWevRIt w1jygpQWv0427XmvxuRWeYt0moOz/FDZwJt+leDMtXy6tDL2WRMwKoN7Ldq24Pckpm5v cnPkVH0wEwaqHb9uvuoviPkU1/akhjcqbKPE2nzzvroJ5VI0ET8sbBY5RgMidThiMPP3 qDtg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1761788489; x=1762393289; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=OS8N6F34lc9aWRU3KSYxthoXp54pVztCVFhLSLEz93c=; b=qGjoiEfYe+EFoMU9qwG9Oa0J0ld3HZ4K/pyo7EavbeqyFhQC+dsr12IKEJf9DlC7fA LgrcpV5ZadLLroD3kUeS945JoDyMHw0IkZ32AYAOf62GlUVJRH1Js3RRPikP5T51W7T/ ePYBvO3ECLnA2yqzGBv1foeMKMtsoJfyuQjUkVPcZKMDjXoXlqgNR7CW79mfjTRZNcQV +KzhdRm6go3zle/mf5XoRGa8jbsIZYe9MsUwejBcoyZLLvaoWG0KRfp35G+1r9W+mfHK EhSCrQVTWOYDhFmVJGU6by+Wsx64184DFd9/ystKKPtMLc9AcQnqHus3vbzIKCUOKVWl QZXA==
X-Forwarded-Encrypted: i=1; AJvYcCVjQTBhDZDQcua0uXL9Butl3pAI1AwbRyTLFfiGLzNw0QYhBQCKl4Fn3VyaEiqzPcQ0cLZWdnBhuTp+xwQ=@ietf.org
X-Gm-Message-State: AOJu0YwZ/rSdcwKTL+h65TgmX4fn8j2aBGAJbznhHkTSttt9d5LjfRu2 njiH5138vQxr4AtC63AXTyQnDtBBwZ4pSSy8LLDyL8MDhVj4GCW4L5r2dokIpjI8f21caw==
X-Gm-Gg: ASbGncuqhII/pWe/5Hhe03jaTLtzp1vCWaAVUAANI1RyVx7NEaoHXs+Y1ghAx4kdKct kQjt+pgmEyG5UKSNvj+Hb6KzKG7thskdrFkZQ+p6IpMoDgoXmn1oPQEbTYadWKgG44r82F3VfiU InCwd64k0NEgddCuL3fNAMVsROjQxaHqASS9MaTNRCJn+fjIO1qKoAS8vrj738LnqpEvAUvtIqb pcGGh6Q3L/3xL4oQsTq5oh5qAEQQDRT5MmnPp6a98D27nvOHlAjio+xHnr7EUbkFOR9HLPJy/TG zPRldr35p+8bMvGs6VCYcoucQyORTEP8cEf6xsEXInI0fqDEK21tEAkiNXhwuilCgZbn4oYbBCU I+oaRVi5kvremrb4cskQYVFuMdaXZIhk+ikThfiRRjym2V+FPO/GmCejy+6QCGduXpkdJDDwmJ2 B6QT6onuQ09PlnF5dU9I2EEuAYwPTPZQ==
X-Google-Smtp-Source: AGHT+IERG6sDXEzJuI6unVyGUr+fRE1V49yqF0NYi0CHquHmWhz7K/e95tPgzGKffnWW3h4GUMxJHg==
X-Received: by 2002:a05:622a:1a8d:b0:4ec:f31a:1496 with SMTP id d75a77b69052e-4ed15c24f76mr70145281cf.56.1761788489038; Wed, 29 Oct 2025 18:41:29 -0700 (PDT)
Received: from smtpclient.apple ([207.164.22.53]) by smtp.gmail.com with ESMTPSA id d75a77b69052e-4ed11c88324sm33277681cf.1.2025.10.29.18.41.28 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Oct 2025 18:41:28 -0700 (PDT)
From: Jay Daley <exec-director@ietf.org>
Message-Id: <3E4E058A-72E2-4897-8F89-EB8913705DED@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
Date: Wed, 29 Oct 2025 18:41:16 -0700
In-Reply-To: <79B20F07-44A9-4BD2-8699-93D4CB4B2345@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
References: <175952451873.3281138.13288864131593743590@dt-datatracker-6c6cdf7f94-h6rnn> <9AD5796C-0427-4B02-BF4E-709974EC67D0@ietf.org> <313A6CA1-702C-4157-B0E5-6F9D0E4458C7@vigilsec.com> <59D1E0BD-BA92-41DE-82D9-19752E35113F@ietf.org> <79B20F07-44A9-4BD2-8699-93D4CB4B2345@vigilsec.com>
X-Mailer: Apple Mail (2.3826.700.81)
Message-ID-Hash: 3OTBEUBUSE3GQV3A4KLSXMJLL7A4Q4DN
X-Message-ID-Hash: 3OTBEUBUSE3GQV3A4KLSXMJLL7A4Q4DN
X-MailFrom: jay@staff.ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"
X-Content-Filtered-By: Mailman/MimeDel 3.3.9rc6
CC: IETF Trustees <trustees@ietf.org>, tlp-interest@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [tlp-interest] Re: October 2025 Notice of Proposed Amendment to IETF IPMC Bylaws
List-Id: Discussion of proposed revisions to the Trust Legal Provisions <tlp-interest.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tlp-interest/NqAQGd7SoA2WB1wsB_VLyYs4KJA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tlp-interest>
List-Help: <mailto:tlp-interest-request@ietf.org?subject=help>
List-Owner: <mailto:tlp-interest-owner@ietf.org>
List-Post: <mailto:tlp-interest@ietf.org>
List-Subscribe: <mailto:tlp-interest-join@ietf.org>
List-Unsubscribe: <mailto:tlp-interest-leave@ietf.org>

Hi Russ

The clause the note from the IETF LLC includes is clause 4.1   Currently that section begins:

> The Assets shall be used for the benefit of the IETF as a whole and not any individuals who may participate in IETF activities or either of the Settlors. 

The proposal from the IETF IPMC adds the clarification ", subject, with regard to the IANA IPR, to the Community Agreement," in the first sentence to comply with the request from the CCG, which makes

> The Assets shall be used for the benefit of the IETF as a whole, subject, with regard to the IANA IPR, to the Community Agreement, and not any individuals who may participate in IETF activities or either of the Settlors.


The recommendation from the IETF LLC is to remove clause 4.1 entirely, which then obviates the need to add that clarification to that clause and does not affect its addition to clauses 4.3 and 4.4.

Jay


> On 29 Oct 2025, at 13:04, Russ Housley <housley@vigilsec.com> wrote:
> 
> Jay:
> 
> The message that you cite wan the inout to discussion within the CCG.  The result of that discussion was this letter to the IETF Trust:
> 
> 	https://mailarchive.ietf.org/arch/msg/ccg/EkCxbPiAcwcW36N6PlNjzm1L0FQ/ <https://mailarchive.ietf.org/arch/msg/ccg/EkCxbPiAcwcW36N6PlNjzm1L0FQ/>
> 
> The part related to assets says:
> 
> """
> Second, in Article (IV) (Assets) (particularly 4.4 and the exception in Section 4.3(b)), add “subject to
> the Community Agreement” to clarify that the obligations in the Community Agreement limit the
> IETF IPMC with regard to the IANA IPR assets.
> """
> 
> Russ
> 
>> On Oct 29, 2025, at 2:28 PM, Jay Daley <exec-director@ietf.org> wrote:
>> 
>> Hi Russ
>> 
>>> On 30 Oct 2025, at 05:06, Russ Housley <housley@vigilsec.com> wrote:
>>> 
>>> Jay:
>>> 
>>> We now have two parts of the community making conflicting requests.  The CCG explicitly asked for the Community Agreement to be referenced by the IETF IPMC Bylaws.  As I read the sentence, the Community Agreement places additional consideration on the IANA IPR but not other IETF IPMC assets.
>> 
>> The CCG Chair also asked for this clause to be removed [1] and the addition to that clause of a reference to the IANA IPR was only added absent that removal.  While the two recommended texts are different, they are not in conflict in intent and I’m sure there would be no objections from the CCG to removing this clause and support from some parts of the CCG.
>> 
>> Jay
>> 
>>> 
>>> Russ
>>> 
>>> 
>>>> On Oct 28, 2025, at 3:39 PM, Jay Daley <exec-director@ietf.org> wrote:
>>>> 
>>>> 2. Removal of language effectively setting policy for IETF IP
>>>> 
>>>> The bylaws include the following as section 4.1 Use of Assets:
>>>> 
>>>>> The Assets shall be used for the benefit of the IETF as a whole, subject, with regard to the IANA IPR, to the Community Agreement, and not any individuals who may participate in IETF activities or either of the Settlors. In the event that the IETF ceases to, or plans to cease to, develop technical standards for the Internet, then upon and only upon the express written consent of the IESG, or the IESG’s successor as the leadership of the IETF, the IETF’s successor with respect to the development of technical standards for the Internet shall become the successor Beneficiary under this Corporation; provided that neither of the Settlors nor any affiliate of either Settlor shall become such successor organization or successor Beneficiary, and provided, further, that if either the IESG or its successor does not consent to the IETF’s successor becoming the Beneficiary hereunder, or if neither the IESG nor its successor are then existing, the successor Beneficiary shall be jointly designated by the Settlors.
>>>> 
>>>> This section is, as others have commented, inappropriate for corporate bylaws as corporations do not have beneficiaries or settlors and including this may therefore cause unintended consequences.  More importantly though, this is overriding the IETF’s ability to set its own policy for how its IP is used.  The IETF LLC therefore recommends that this section be removed in its entirety and that the use of the assets be governed by IETF’s BCPs, as described above.
>>> 
>>> 
>> 
>> [1]  https://mailarchive.ietf.org/arch/msg/ccg/n4PV3LTOUsBEkiVHb6-r_y7ziGU/
>> 
>> -- 
>> Jay Daley
>> IETF Executive Director
>> exec-director@ietf.org
>> 
> 

-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org