Skip to main content
  • IETF 126 Highlights

    The IETF 126 meeting was held 18–24 July 2026 at the Hilton Vienna Park in Vienna, Austria, and online, hosted by Cisco. The week included the IETF Hackathon and Code Sprint, the New Participants' Program, five Birds-of-a-Feather (BoF) sessions, and more than 100 working group and research group sessions. The Applied Network Research Workshop also took place during the IETF 126 meeting week.

    1 Sep 2026
  • IETF email infrastructure transition planned for 11 September

    A transition to a new modern, modular, and containerized infrastructure for email services provided for ietf.org, iab.org, irtf.org, rfc-editor.org (including email lists) is scheduled for 11 September 2026 starting at 2200UTC, with message delivery delayed up to 60 minutes. Further updates will be provided closer to the transition.

    28 Aug 2026
  • Post-Quantum Authentication: Up Next

    Post-quantum key establishment has moved from standards into deployment. Post-quantum authentication has not moved nearly as far, and specification work is no longer the only constraint. The IAB is holding a workshop in Prague on 11 and 12 October 2026 to bring deployment experience together with the people working on the relevant protocols and standards.

    27 Aug 2026
  • IETF 126 post-meeting survey: what we heard

    The IETF 126 Vienna meeting was held 18-24 July 2026 and the results of the post-meeting survey are now available.

    27 Aug 2026
  • Meet our new IETF NOC Lead

    Joe Clarke has been appointed as the new IETF NOC Lead and in this post Joe introduces himself and sets out his priorities for the IETF Network.

    10 Aug 2026

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