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

Countries Listed in IETF Systems

31 Oct 2023

The IETF Administration LLC and Secretariat regularly receive questions and requests from the IETF community about the countries that are listed in IETF systems, in particular the list in the meeting registration system. Recent communications include a request for a new country to be added to this list and a recommendation that this list should be titled ‘Country or Region’. This post explains how this list is chosen and why we will not be acting on these requests.

As you might expect from a technical standards organization, IETF systems use ISO 3166,  the global standard technical list of codes for countries and their subdivisions, which incorporates the names of countries from UN sources.  

For practical reasons, we do not directly implement this list but rely instead on third-party code libraries, which generally include features that go beyond that standard.  The one non-standard feature used in IETF systems, is the replacement of some official short names of countries with more commonly used short names, as this simplifies and improves the user experience.  For example, in the meeting registration system the ISO 3166 short name of “Netherlands (Kingdom of the)” is replaced with “Netherlands”.  Similarly “Taiwan (Province of China)” is replaced with “Taiwan”.

We understand that there are a lot of strong feelings about this subject and the combination of choices above will leave some people very unhappy.  However, there is no straightforward neutral way to do this, nor is it possible to address a request to change without upsetting someone else. The choices above are a fair way to balance the many competing interests for what are, after all, just a set of IT systems.

In response to the two specific requests above:

On the question of adding a new country - we do not think it is appropriate for us to create a custom list instead of ISO 3166.  That is simply not an area of political controversy that we should be entering into.

On the question of renaming the list from ‘Country’ to ‘Country or Region’ - our current approach of simplifying ‘countries and their subdivisions’ is the same approach taken in ISO 3166 itself which is the standard for ‘Country Codes’.  While there are some places where the UI could support a more expansive term, in other places that would be problematic and we prefer consistency as that delivers a better user experience.

If you have any questions or comments, then please feel free to contact me directly at exec-director@ietf.org


Share this page