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

The IETF meeting network is taking steps towards a bigger Internet

14 Mar 2025

The “ietf-ipv6-mostly” WiFi SSID at IETF 122 Bangkok will allow devices to signal a preference for IPv6-only operation while still supporting IPv4 (if needed) via translation mechanisms. Onsite participants are encouraged to try this service when they connect to the IETF meeting network.

The “ietf-ipv6-mostly” SSID will implement the “IPv6-Only Preferred Option” [RFC 8925] for IETF 122 Bangkok. This approach addresses a challenge in deploying IPv6-only LANs with heterogeneous collections of hosts that have differing capabilities to use IPv6. For IETF 123 Madrid (19-25 July 205), the intention is to deploy this service on the default “ietf” SSID. 

If you will be participating in person for the IETF 122 Bangkok meeting or the IETF Hackathon in Bangkok, the IETF NOC team strongly encourages you to try the “ietf-ipv6-mostly” service when you connect to the IETF meeting network. The NOC will be available onsite near the IETF meeting registration desk during its open hours to provide additional support, if required.

You can find out more details and get more information about the work of the IETF NOC at the IETF meeting network webpage.


Share this page