Skip to main content
  • A Journey from Surathkal to the IETF

    We are final-year undergraduate students majoring in Computer Science and Engineering at the National Institute of Technology Karnataka (NITK) in the Surathkal town of Mangalore, India. IETF 122 in Bangkok marked our first in-person participation in the Internet Engineering Task Force – and what a journey it was.

    7 May 2025
  • Working on Post-Quantum Cryptography for Open Source Software from Africa

    During the IETF 122 Hackathon in Bangkok and online last month, the cyberstorm.mu team from Mauritius, the United States, and Kenya participated remotely to implement post-quantum cryptography components currently missing from widely-used open source software such as nmap, zmap, wireshark, and GnuTLS.

    30 Apr 2025
  • IETF 122 post-meeting survey

    IETF 122 Bangkok was held 15-21 March 2025 and the results of the post-meeting survey are now available on a web-based interactive dashboard.

    17 Apr 2025
  • IETF Snapshot 2024

    Want to catch up on IETF activity in 2024? How many RFCs were published? How many Internet-Drafts were submitted? How many Working Groups were chartered or concluded? The IETF Snapshot provides a short summary of IETF activity for the previous year.

    17 Apr 2025
  • Report from RPC Retreat 2025

    In early April 2025, the RFC Production Center (RPC) and IETF LLC senior staff met for the first RPC retreat following the contract change that now has the RPC reporting directly to the IETF Executive Director. This was a high-level retreat, the first of its kind for the RPC, looking at community requirements and the RPC internal processes that deliver those.

    16 Apr 2025

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