Skip to main content
  • IETF Administration LLC 2026 Budget

    A draft budget was shared previously for community consultation and the IETF Administration LLC now has finalised its budget for 2026.

    28 Jan 2026
  • Agentic AI communications: Identifying the standards we need

    When it comes to standards work around agentic AI, we’re at an exciting threshold. As more tools emerge, we’re seeing the amazing things it can accomplish. Now, we’re trying to figure out what parts of it need to be standardized.

    22 Jan 2026
  • IETF@40

    Forty years ago today, 21 people gathered in San Diego, California for the first meeting of what became the Internet Engineering Task Force.

    16 Jan 2026
  • Launch of the IETF Community Survey 2025

    The IETF Community survey is our major annual survey of the whole of the IETF community and is used to inform the actions of IETF leadership throughout the year. The 2025 IETF Community Survey is live and we want to hear from you!

    23 Dec 2025
  • IETF Administration LLC 2026 Draft Budget

    The IETF Administration LLC has prepared its draft budget for 2026 and now seeks community feedback.

    19 Dec 2025

Filter by topic and date

Filter by topic and date

Informing the community on third-party correspondence regarding the W3C

8 Feb 2023

In accordance with our policy of transparency, this blog post aims to keep the community informed about recent correspondence we have received and replied to.

In late January 2023 the IETF received a letter from lawyers acting on behalf of the Movement for an Open Web setting out their concerns with the W3C in the area of competition law.  We responded with a query as to why they had sent it to us and they followed up with a second letter.

This second letter set out why they believe this is relevant to the IETF, made recommendations for changes within the IETF to address perceived antitrust issues and requested a discussion with us on this matter.  The IETF Chair, IAB Chair, LLC chair and IETF Executive Director, discussed this issue with counsel and concluded that 

  1. Unfortunately, this second letter was based on a significant misunderstanding of the role and nature of the IETF;
  2. Our reply should aim to educate about the nature of the IETF, with a particular focus on the multiple ways in which our policies aim to avoid capture by one or more industry players;
  3. This should be treated as an administrative matter with the response coming from the IETF Executive Director;
  4. It would be inappropriate to enter into any discussions about the W3C. 

This approach was then checked with the IESG and IAB and our reply sent.


Share this page