[tlp-interest] Re: October 2025 Notice of Proposed Amendment to IETF IPMC Bylaws
Russ Housley <housley@vigilsec.com> Thu, 30 October 2025 14:39 UTC
Return-Path: <housley@vigilsec.com>
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 A0C5D7EEED7B; Thu, 30 Oct 2025 07:39:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=vigilsec.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 FBbYSpOjHg0c; Thu, 30 Oct 2025 07:39:15 -0700 (PDT)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id E9B207EEED69; Thu, 30 Oct 2025 07:39:15 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id BA9A91A0D1A; Thu, 30 Oct 2025 10:39:15 -0400 (EDT)
Received: from smtpclient.apple (pool-96-255-71-95.washdc.fios.verizon.net [96.255.71.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 994801A14C8; Thu, 30 Oct 2025 10:39:15 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <DD7C97AC-EB8D-4C75-90D7-8C806D5A205A@vigilsec.com>
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
Date: Thu, 30 Oct 2025 10:39:05 -0400
In-Reply-To: <3E4E058A-72E2-4897-8F89-EB8913705DED@ietf.org>
To: Jay Daley <exec-director@ietf.org>
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> <3E4E058A-72E2-4897-8F89-EB8913705DED@ietf.org>
X-Mailer: Apple Mail (2.3826.700.81)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vigilsec.com; h=from:message-id:content-type:mime-version:subject:date:in-reply-to:cc:to:references; s=pair-202402141609; bh=HeMr8S6/pqiFDyhEIpx/hFjMOIrN2DzGOZvAS6SsonM=; b=I4he7z5RtyefT2buWOxhQoi7SSpRivzP69e/5DXno8ZOUvOhrTr9a/hywAixLllWODlq3Nht7nJUe18zrjq1MaK9nZRKE33Lsc3xiLoIBI72TLjqhnf4JpqZGwKl2mMf7aN8L3bc3JKtMppOrrJLrpOyArnYdowt12oYod0ElzANr/++Hz3wJSYDLUTdUuEeJ283WXDg4eBeP6y+jmcdW8kBG+ic9N0cdliORpJ4rGjMG+jvpY/ThGk820VA+QK/mm2ZC7eo+6MfZMMLu00HGeewvHoGGdQLQ2DC7lF6UrFGriTIo5M/XnvthlrOih5BqWriQxSZQ59gF1jSOF+uTQ==
X-Scanned-By: mailmunge 3.09 on 66.39.134.11
Message-ID-Hash: SOH67Z6F2CIGNXZD6YI6AKO2S35D4DDR
X-Message-ID-Hash: SOH67Z6F2CIGNXZD6YI6AKO2S35D4DDR
X-MailFrom: housley@vigilsec.com
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/Twfv9VmjvWJJHLxGizJPhEm5K2M>
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>
Jay: I see. Sorry for the false alarm. Russ > On Oct 29, 2025, at 9:41 PM, Jay Daley <exec-director@ietf.org> wrote: > > 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 >
- [tlp-interest] October 2025 Notice of Proposed Am… The IETF Trust
- [tlp-interest] Re: October 2025 Notice of Propose… Salz, Rich
- [tlp-interest] Re: October 2025 Notice of Propose… Jay Daley
- [tlp-interest] Re: October 2025 Notice of Propose… Brian E Carpenter
- [tlp-interest] Re: October 2025 Notice of Propose… Russ Housley
- [tlp-interest] Re: October 2025 Notice of Propose… Jay Daley
- [tlp-interest] Re: October 2025 Notice of Propose… Russ Housley
- [tlp-interest] Re: October 2025 Notice of Propose… Jay Daley
- [tlp-interest] Re: October 2025 Notice of Propose… Russ Housley
- [tlp-interest] Re: October 2025 Notice of Propose… Olivier MJ Crépin-Leblond
- [tlp-interest] Re: October 2025 Notice of Propose… Glenn Deen
- [tlp-interest] Re: October 2025 Notice of Propose… Salz, Rich