Summary

  • IETF LLC's approved 2026 budget assigns USD 170,000 to the Intellectual Property Management Corporation. IPMC's own budget records the same amount as an expected LLC contribution.
  • The public Executive Director report prepared for the LLC Board's 1 September meeting says the parties have an agreement covering intellectual property but no funding agreement. Counsel is drafting a proposal.
  • The matching budget entries do not prove that money was requested, accepted, paid or received. IPMC's projected USD 385,874 year-end reserve is likewise a forecast, not a current balance.
  • A durable agreement should join the financial chain to reporting and remedies while expressly preserving IPMC's separate authority over assets, licensing and enforcement.

The same number appears in two books

The IETF Administration LLC approved a USD 170,000 line for the Intellectual Property Management Corporation in its final 2026 budget. IPMC's final budget shows the mirror image: a USD 170,000 contribution from IETF LLC, against USD 166,426 of projected expense. Its model starts the year with a projected USD 382,300 reserve and ends with USD 385,874.

The symmetry is reassuring, but it is not a transaction receipt. One board authorised a budget. The other corporation anticipated a contribution. Between those entries sit several states that a public reader cannot safely merge: a request, the IPMC Board's acceptance, any conditions, an invoice or draw, a payment, a receipt and the eventual reconciliation of use.

That distinction became news in the public Executive Director report prepared for the IETF LLC Board's 1 September meeting. The report describes a discussion with the IETF Trust/IPMC and says the existing agreement covers intellectual property, but no funding agreement exists. It says counsel is drafting a proposal for the LLC. It also records IPMC's view that its reserves have probably reached a suitable level and that future requests are likely to decrease.

At the 30 August cutoff, the Board meeting was still two days away in UTC and one day away in Shanghai. The report therefore establishes neither approval nor execution. It exposes an unfinished control surface. Any later minutes or resolution may change the state.

A budget is authority to spend, not evidence of payment

Budget documents answer important questions. They show that each organisation planned for the same amount and that the LLC Board approved its side through the final budget. They also allow the community to compare the proposed contribution with IPMC's expense and reserve projections.

They do not answer whether IPMC submitted a request, whether its Board accepted restricted or unrestricted funds, when cash moved, which expenses were eligible, what unused money becomes, or how the two books will be reconciled. The figures are plans. The article does not report that USD 170,000 was paid or received.

The reserve numbers require the same restraint. IPMC projected a USD 382,300 opening reserve, a USD 3,574 annual surplus and a USD 385,874 closing reserve. Those figures help explain why future requests could fall. They are not a bank statement. A funding agreement should define the reserve method—what belongs in the calculation, the target or range, who approves an exception and when a smaller request follows—so that “suitable” can become a reproducible decision rather than a conversational conclusion.

This is not a demand to publish account numbers, payment credentials or privileged negotiations. A public status receipt can identify an approved amount, agreement version, transfer state and reporting period without exposing operational security.

The recipient is also the IP custodian

The institutional separation is the reason the missing agreement matters.

IETF LLC is the corporate legal home for the IETF's administrative and fiscal support. IPMC is a different corporation with its own Board. Its current bylaws make the IETF the beneficiary and direct the corporation to hold, maintain and license IETF-related intellectual property for the IETF as a whole. The IPMC Board approves contributions, controls corporate assets and decides enforcement of unauthorised use within that purpose.

Official IETF 125 minutes say an agreement formally transferred IETF intellectual-property assets from the predecessor IETF Trust to IPMC on 9 March 2026. That move placed asset custody and financial support on opposite sides of a corporate boundary. The same community ultimately benefits from both, but the boards do not become interchangeable.

A cheque should not silently buy a veto over a trademark licence or an enforcement decision. Conversely, independent custody should not make a funding commitment incapable of audit or remedy. The agreement has to hold both propositions at once: IPMC retains the authority assigned to it over IP assets, while IETF LLC receives the evidence and contractual protections appropriate to community money.

That is a more precise question than whether the organisations trust one another. Governance instruments are built for the day on which recollections differ, boards change or a routine transfer becomes contested.

The report raises a remedy question, not a legal conclusion

The Executive Director report adds a sharper point. It says the transfer from the IETF Trust to IETF LLC may have limited the LLC's standing to sue the IPMC for not acting in IETF's best interests. It then says the parties agreed that LLC would propose something for the funding agreement.

The sentence deserves exact treatment. It does not say IPMC acted against IETF's interests. It does not say a lawsuit exists. It does not establish that standing was lost. “May have limited” records a concern for counsel and the boards to resolve.

Nor should a funding agreement manufacture a general supervisory power merely to solve that concern. Standing, contractual enforcement and control of the underlying assets are different things. A party may need a right to require financial reports, recover misspent funds or enforce an agreed use without gaining authority to direct every licence, registration or infringement response.

The public version can state the remedy architecture while legal advice remains confidential: which party may give notice, what failure is curable, what dispute process applies, which forum has jurisdiction, what relief is available and what happens when the agreement ends. Authoritative counsel must determine whether those terms are legally sufficient.

Two signatures, two ledgers and an IP firewall

A useful agreement receipt would begin with authority. It would identify the exact legal parties, the approving body on each side, the version, effective date, duration and signatures. The IPMC Board's acceptance matters independently of the LLC's appropriation.

The financial section would state the amount and schedule; eligible expense classes; whether the contribution is restricted; the request and acceptance packet; payment and receipt evidence; reporting periods; audit access; correction of errors; treatment of unspent funds; and the reserve formula that can reduce a later request. Each change would remain versioned.

The remedy section would set notice, cure, escalation, dispute, termination and continuity rules. A disagreement must not accidentally interrupt trademark renewals, licence administration or preservation of records. A cross-default should not put the IP assets themselves at risk merely because a financial report is late.

Finally, the instrument should contain an IP firewall. Funding conditions should not create an implied LLC veto over IPMC's licensing, enforcement or custody decisions. If the community intends a power of that kind, it requires an express authority source and public explanation, not an inference drawn from who pays the bill.

This proposed receipt is Daniel Kade's governance design, not a description of fields already adopted by IETF LLC or IPMC. It could be implemented through a multi-year agreement, an annual grant letter or a reimbursement contract. The form matters less than the state transitions it makes provable.

Heng Lu's account of the agency problem supplies a useful discipline here, not evidence of wrongdoing. Delegated bodies can rationally optimise their own measures when duties, evidence and consequences drift apart. The answer is not to erase institutional independence. It is to link the money to bounded duties and observable receipts while leaving asset authority where the public mandate placed it.

Sources

  1. IETF LLC — Public Executive Director Report for the 1 September 2026 Board meeting
  2. IETF — 1 September 2026 LLC Board meeting announcement
  3. IETF LLC — Final 2026 budget
  4. IETF IPMC — Final 2026 budget
  5. IETF IPMC — Financials
  6. IETF IPMC — Current bylaws
  7. IETF IPMC — 2025 amended bylaws, clean copy
  8. IETF 125 minutes
  9. RFC 8711 — Structure of the IETF Administrative Support Activity, Version 2.0
  10. IETF IPMC — Board minutes
  11. IETF LLC Board — resolutions and meeting materials
  12. Heng Lu — On the Agency Problem at the Core of Internet Governance