Skip to main content
  • IETF Community Survey 2025

    Each year the IETF Community Survey provides a comprehensive assessment of community demographics, engagement patterns, and perceptions of organizational effectiveness. The full report from the 2025 edition is now available.

    14 Jul 2026
  • Birds of a Feather at IETF 126

    The IETF 126 Vienna meeting takes place 18–24 July 2026. As at every IETF meeting, alongside the established Working Groups there will be a handful of Birds-of-a-Feather (BoF) sessions—and these are often the most interesting place to watch where Internet standards work is heading next.

    2 Jul 2026
  • From Lab to RFC: A PhD Student's Journey through the IETF

    Martine Sophie Lenders has been regularly participating in the IETF for over a decade, starting with the IETF 93 meeting in Prague in 2015. She has authored several Internet-Drafts—two of which recently were published as RFCs—and at the same time works on a PhD at FU Berlin and as a research associate at TU Dresden. We asked a few questions about what her experience in the IETF has been like while pursuing an academic journey.

    1 Jul 2026
  • Suggested IETF 126 Sessions for Getting Familiar with New Topics

    These IETF 126 meeting sessions are likely to include discussions and proposals that are accessible to a broad range of Internet technologists whether they are new to the IETF or long-time participants.

    29 Jun 2026
  • IETF LLC Board Retreat 2026

    The IETF Administration LLC Board of Directors held its annual retreat 29-30 April 2026 in Amsterdam. In addition to all Board members, the IETF Executive Director, the Director of Finance, and the Board Secretary were present. Here is a short summary of the main points we discussed.

    4 Jun 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