Summary

  • The IETF’s core intellectual-property assets transferred from the IETF Trust to the IETF Intellectual Property Management Corporation in March 2026.
  • At the IETF 126 plenary on 22 July, IPMC President Wendy Seltzer said final signatures on the IANA novation agreements were still required. IETF 125 materials counted five agreements.

This handover has two tracks, and the name makes them easy to confuse. The IETF’s March transfer moved the intellectual-property assets managed for the standards organization from the Virginia trust to its Delaware nonprofit successor. The IANA rights follow a separate set of agreements involving the communities and organizations that share responsibility for the naming, numbering and protocol-parameter functions. At the July meeting, that second track still needed final signatures.

The dates matter. Glenn Deen told the IETF 125 plenary on 18 March that he had signed the asset-transfer agreement on 9 March. He also said the transition was not fully finished. The IETF’s March executive-director report said the IANA transfer agreement had been signed by the IETF Executive Director, with several parties still required for full execution. A slide deck for the same meeting described signature collection across all five IANA agreement novations.

By IETF 126, the distinction was explicit. Seltzer said the IPMC held the IETF-related assets, including future-acquired assets. She then described the IANA IPR as transferring only after final signatures on the novation agreements. These are not two names for one closing condition. They are two document chains with different parties and different assets.

That leaves the October draft in a precise role. Version 04 of draft-deen-ietf-ipmc-update proposes how IETF publications should refer to the new custodian. It updates RFC 5378, RFC 8714 and RFC 8721, among other provisions, and says references to the IETF Trust in IETF documents should be read as references to the IPMC. It also preserves the old Trust website because older RFCs and licensing terms still point there, and it says old copyright notices do not need retroactive replacement.

The draft is housekeeping with consequences. Standards documents are the operating instructions for who holds rights, who receives licensing inquiries and which body carries duties on behalf of the IETF. A successor that already manages the transferred assets still needs the published record to name it consistently. But a blanket reading rule for RFCs cannot execute the missing signatures on the separate IANA agreements.

The chronology is plain: the IPMC was established in December 2022; the IETF-specific asset transfer was signed in March 2026; the latest dated public status found, from 22 July, still required final IANA novation signatures; and an October draft updates selected RFC and BCP language. The IETF Chair had adopted the draft for community feedback outside a working-group process, according to December 2025 LLC minutes. That makes it an active document proposal, not an adopted RFC.

Sources: draft-deen-ietf-ipmc-update-04; IETF 125 plenary minutes; IETF 126 plenary minutes; IETF Executive Director report, 9 March 2026; IETF 125 IPMC report slides; IETF LLC Board minutes, 17 December 2025.