[Gnso-newgtld-wg-wt5] Follow up on "exceptionally reserved" codes

Emily Barabas emily.barabas at icann.org
Tue Nov 13 12:26:40 UTC 2018

Dear Work Track 5 members,

Thanks to Jaap and Christopher for continuing this conversation and for sharing the below links. This is a brief attempt to summarize some of the points Jaap has previously raised about “exceptionally reserved” codes and consider next steps. Jaap, please correct, as necessary, but I believe these are the items you have raised:

  *   They are not officially reserved code points, although data about these codes is available at the ISO’s Online Browsing Platform (OBP<https://www.iso.org/obp/ui#search>), with the decoding table at https://www.iso.org/obp/ui/#iso:pub:PUB500001:en, and the definition of "exceptional reservations" is included in the current standard,  (ISO 3166-1:2013(E/F)) Section 7.5, Reservation of Code Elements
  *   The list may be out of date
  *   Not all exceptionally reserved codes have a short and long form name associated with them
  *   Some exceptionally reserved codes do not refer to a country or territory (for example “UN” for United Nations)
  *   Some places may have more than one code associated with them, for example Tristan da Cunha has both an assigned 2-letter code (SH) and an exceptionally reserved code (TA)

Regarding the fourth bullet above, staff has connected with GDD colleagues to get additional clarification about the relevant provision in the 2012 Applicant Guidebook: Applications for strings that are country or territory names will not be approved, as they are not available under the New gTLD Program in this application round. A string shall be considered to be a country or territory name if:  iv. it is the short- or long-form name association with a code that has been designated as “exceptionally reserved” by the ISO 3166 Maintenance Agency. GDD has confirmed that all such short- and long- form names were reserved, regardless of whether they referred to a country or territory.
Jaap, I believe your briefly mentioned previously that it might be appropriate to remove or modify this provision of the AGB. If you would like to include a proposal in the Initial Report, can you kindly provide some language, along with (if possible) a description of the problem that this proposal would solve? All other Work Track members are welcome to submit proposals on this issue, as well.

Kind regards,

From: Jaap Akkerhuis <jaap at NLnetLabs.nl>
Date: Friday, 9 November 2018 at 12:50
To: "lists at christopherwilkinson.eu Wilkinson" <lists at christopherwilkinson.eu>
Cc: Emily Barabas <emily.barabas at icann.org>, <gnso-newgtld-wg-wt5 at icann.org>
Subject: [Ext] Re: [Gnso-newgtld-wg-wt5] Notes and Action Items - Work Track 5 - 7 November 2018

[Oops, sending from a proper account this time]

On Nov 7, 2018, at 18:42, lists at christopherwilkinson.eu<mailto:lists at christopherwilkinson.eu> Wilkinson <lists at christopherwilkinson.eu<mailto:lists at christopherwilkinson.eu>> wrote:

Good evening:
Further to the WT5 discussion this morning, the table of ISO-3166 alpha2 exceptionally reserved codes can be found at:
Click on 2.4.1 Exceptional Reservations, in the Contents.
This is a table indeed. Note that wikipedia is not always aligned with the website from ISO. As said in my previous mail, the data is also available at the Online Browsing Platform (OBP<https://www.iso.org/obp/ui#search>) on the iso.org<http://iso.org/> site. The link for the decoding table is <https://www.iso.org/obp/ui/#iso:pub:PUB500001:en>.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg-wt5/attachments/20181113/ae3831c1/attachment.html>

More information about the Gnso-newgtld-wg-wt5 mailing list