Skip to main content
  • The new GREEN working group gets ready for an energy efficient Internet

    The Getting Ready for Energy-Efficient Networking (GREEN) working group will explore use cases, derive requirements, and provide solutions to optimize energy efficiency across the Internet.

    29 Oct 2024
  • IETF Annual Report 2023

    The IETF Annual Report 2023 provides a summary of Internet Engineering Task Force (IETF), Internet Architecture Board (IAB), Internet Research Task Force (IRTF), and RFC Editor community activities from last year.

    25 Oct 2024
  • IETF 122 Bangkok registration open

    Registration is now available for the IETF 122 Bangkok meeting scheduled for 15-21 March 2025, which is the first time registration for an IETF meeting has been open before the preceding meeting registration has closed.

    25 Oct 2024
  • First Impressions from the IAB AI-CONTROL workshop

    The Internet Architecture Board (IAB) organized a workshop on 19-20 September 2024 to discuss issues around and possibilities for practical mechanisms that publishers of data on the Internet could employ to opt out of use by the Large Language Models and other machine learning techniques used for Artificial Intelligence (AI).

    24 Oct 2024
  • New Participant activities at the IETF: Major expansion coming for IETF 122!

    The IETF New Participants program has a long history of helping people just starting out in the IETF be more effective. Based on feedback from program participants over the past two years, and in consultation with the Internet Engineering Steering Group (IESG), the program will be significantly enhanced starting with IETF 122 Bangkok.

    22 Oct 2024

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