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

["Salz, Rich" <[e-mail]>]

 Resending

From: Salz, Rich <[e-mail]>
Date: Sunday, October 5, 2025 at 1:38 PM
To: [e-mail] <[e-mail]>
Subject: Re: October 2025 Notice of Proposed Amendment to IETF IPMC Bylaws

I am used to seeing “redline” used to describe a document where the old words are struck out and the new ones are in [brackets like this] or other indication.  Can you post a “fixed” redline version?

Can you include a summary of changes?


From: The IETF Trust <[e-mail]>
Date: Friday, October 3, 2025 at 4:49 PM
To: IETF Announcement List <[e-mail]>
Cc: [e-mail] <[e-mail]>
Subject: October 2025 Notice of Proposed Amendment to IETF IPMC Bylaws

!-------------------------------------------------------------------|
  This Message Is From an External Sender
  This message came from outside your organization.
|-------------------------------------------------------------------!

October 2025 Notice of Proposed Amendment to IETF IPMC Bylaws

The IETF Intellectual Property Management Corporation (IPMC) Directors are considering adopting a proposed set of amendments to the IETF IPMC bylaws.

As required by the IETF IPMC bylaws, these amendments are undergoing a 60 day notice following the requirements of the current IETF IPMC bylaws “Article XII Amendments” before the IETF IPMC Directors can vote to adopt any proposed amendments.

This 60-day notice is being sent to bodies that appoint the 5 IETF IPMC Directors (IETF Trustees) -  the IESG, IETF NOMCOM, ISOC Board of Trustees, and announced more broadly through the IETF-Announcements list.

The proposed amended bylaws, dated October 2 2025, have been published by the IPMC in both redline and in clean version along with the current active IPMC bylaws on the IPMC web site (https://urldefense.com/v3/__https://www.ietf-ipm.org/__;!!GjvTz_vk!X3SbCkS5lDsoE-B_ajosnVm-s1ME_gXKveggN2fN9eCBrdq-nBkNMijkqN6N6kNGCT5f0ZLKUDeTIWQR$ )

Links to IPMC bylaws:
Current Active Bylaws:
        https://urldefense.com/v3/__https://www.ietf-ipm.org/uploads/IPMC-bylaws.pdf__;!!GjvTz_vk!X3SbCkS5lDsoE-B_ajosnVm-s1ME_gXKveggN2fN9eCBrdq-nBkNMijkqN6N6kNGCT5f0ZLKUHxFqTFX$
Redline Proposed Bylaws:
        https://urldefense.com/v3/__https://www.ietf-ipm.org/uploads/Oct25_Proposed_Amended_Bylaws_REDLINE.pdf__;!!GjvTz_vk!X3SbCkS5lDsoE-B_ajosnVm-s1ME_gXKveggN2fN9eCBrdq-nBkNMijkqN6N6kNGCT5f0ZLKUNKp29ti$
Clean Proposed Bylaws:
        https://urldefense.com/v3/__https://www.ietf-ipm.org/uploads/Oct25_Proposed_Amended_Bylaws_CLEAN.pdf__;!!GjvTz_vk!X3SbCkS5lDsoE-B_ajosnVm-s1ME_gXKveggN2fN9eCBrdq-nBkNMijkqN6N6kNGCT5f0ZLKULuPKesN$


Summary of Proposed Amendments:

The Proposed Amendments cover three purposes:

1. Final Corporate Name
-------------------------------
Update the corporation’s name in the bylaws to reflect the final approved name of the organization.  At the time of original filing the bylaws, continuing to use IETF Trust as the corporate name had been approved by the State of Delaware, but this was later reversed resulting in the final name choice being the IETF Intellectual Property Management Corporation.

1. All uses of the name IETF Trust as the organization name in the bylaws have been changed to IETF Intellectual Property Management Corporation or IETF IPMC, reflecting the final registered name of the IETF Trust’s successor.

2. The term Trustee has been changed to Director.

2. ARTICLE Re-Numbering & Internal Cross-Reference Validation
--------------------------------------------------------------

Correcting a misnumbering of Article sections in the late half of the bylaws and internal cross reference citations, which are believed to have occurred due to import and export across document formats (DOCX/Google Docs) and interactions with automated numbering along with manual fix-ups during formatting.   All Articles and citations have been reviewed and revalidated, correcting as appropriate.

3. The current IPMC bylaws have misnumbered ARTICLES starting at Article VI.   The Amended bylaw proposal has had all ARTICLE numbering reviewed and correctly renumbered, including clause labels.

4. Related to the renumbering of Articles and automated numbers, all cross references and citations in the bylaws to Sections and Articles have been reviewed, validated and corrected as appropriate.

3. NEW language specific to the IANA IPR held by the IETF Trust
---------------------------------------------------------------

In addition to the IETF IP Assets held by the IETF Trust, the IETF Trust also holds Trademarks and DNS Domain name IP Assets for the IANA.   These assets were transferred to the IETF Trust under a set of agreements [3] (https://urldefense.com/v3/__https://trustee.ietf.org/iana-ipr/__;!!GjvTz_vk!X3SbCkS5lDsoE-B_ajosnVm-s1ME_gXKveggN2fN9eCBrdq-nBkNMijkqN6N6kNGCT5f0ZLKUH-o2TWD$ ) between the IETF Trust and the Protocols, Names and Numbers communities and ICANN in 2016.

These Proposed Amendments add new language into the IETF IPMC Bylaws to recognize the help IANA IPR and the Community Agreement [4] role with regard to it.

5. Add to Section 3.16 extending the annual reporting requirement to the IETF to also include annual reporting to the CCG.

6.  Amend the bylaws to add new language to Article IV: ASSETS to recognize the held IANA IPR assets and  the role of the Community Agreement with regard to these assets.

7.  The proposed amended bylaws now contain the new section 4.10 IANA IPR containing terms from the triggered Community Agreement Section 4.4.

Background: Under the terms of the Community Agreement [4] with the IETF Trust, the Community Agreement clause 4.4, the IANA CCG (Cross Community Group) has submitted the request to add IANA IPR Terms which asks additions to the IETF Trust Agreement specific for IANA IPR.    As the IETF IPMC is the successor to the IETF Trust the IPMC Directors are hereby applying  this request to the IPMC Bylaws instead of the IETF Trust Agreement.





IETF IPMC 60 Day Bylaw Notice Amendment Process:

This notice is being sent to the IESG, IAB, IETF NOMCOM, ISOC BoT and to the IETF-Announcement list.  The IETF IPMC Directors will hold a vote on adoption no earlier than 60 days from the publication of this notice.

Given that no structural or organizational changes are being made, this is following the required 60 day notice process and not a broader consultation such as was done around the IETF Trust restructuring.

Submitting Comments:

Concerns or objections to adopting any portion of these amendments, should be communicated to the IPMC Directors within the 60 day notice period.  Such comments may be sent directly to the IPMC Directors ([e-mail]) or to the public list [e-mail].

Helpful Links:

[1] Current IETF IPMC Bylaws
https://urldefense.com/v3/__https://www.ietf-ipm.org/uploads/IPMC-bylaws.pdf__;!!GjvTz_vk!X3SbCkS5lDsoE-B_ajosnVm-s1ME_gXKveggN2fN9eCBrdq-nBkNMijkqN6N6kNGCT5f0ZLKUHxFqTFX$

[2] Proposed Amended IPMC Bylaw drafts
https://urldefense.com/v3/__https://www.ietf-ipm.org/uploads/Oct25_Proposed_Amended_Bylaws_REDLINE.pdf__;!!GjvTz_vk!X3SbCkS5lDsoE-B_ajosnVm-s1ME_gXKveggN2fN9eCBrdq-nBkNMijkqN6N6kNGCT5f0ZLKUNKp29ti$
https://urldefense.com/v3/__https://www.ietf-ipm.org/uploads/Oct25_Proposed_Amended_Bylaws_CLEAN.pdf__;!!GjvTz_vk!X3SbCkS5lDsoE-B_ajosnVm-s1ME_gXKveggN2fN9eCBrdq-nBkNMijkqN6N6kNGCT5f0ZLKULuPKesN$

[3] IANA IPR Agreements from 2016 with IETF Trust
https://urldefense.com/v3/__https://trustee.ietf.org/iana-ipr/__;!!GjvTz_vk!X3SbCkS5lDsoE-B_ajosnVm-s1ME_gXKveggN2fN9eCBrdq-nBkNMijkqN6N6kNGCT5f0ZLKUH-o2TWD$

[4] IANA IPR Community Agreement
https://urldefense.com/v3/__https://trustee.ietf.org/wp-content/uploads/Community-Agreement-2016-09-30-Executed.pdf__;!!GjvTz_vk!X3SbCkS5lDsoE-B_ajosnVm-s1ME_gXKveggN2fN9eCBrdq-nBkNMijkqN6N6kNGCT5f0ZLKUGjbTkIJ$


This is also being announced on the IETF IPMC web site https://urldefense.com/v3/__https://www.ietf-ipm.org/__;!!GjvTz_vk!X3SbCkS5lDsoE-B_ajosnVm-s1ME_gXKveggN2fN9eCBrdq-nBkNMijkqN6N6kNGCT5f0ZLKUDeTIWQR$
---

Comments may be directed to [e-mail].

--
Glenn Deen, IETF IPMC President on behalf of the IPMC Board

_______________________________________________
IETF-Announce mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]