Follow up on "exceptionally reserved" codes
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, Emily From: Jaap Akkerhuis <jaap@NLnetLabs.nl> Date: Friday, 9 November 2018 at 12:50 To: "lists@christopherwilkinson.eu Wilkinson" <lists@christopherwilkinson.eu> Cc: Emily Barabas <emily.barabas@icann.org>, <gnso-newgtld-wg-wt5@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@christopherwilkinson.eu<mailto:lists@christopherwilkinson.eu> Wilkinson <lists@christopherwilkinson.eu<mailto:lists@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: https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 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>. Regards, jaap
Thanks Emily and to Jaap (I hope you are feeling better now) and Christopher I was looking at whether I could propose some revised text for the draft report to get the ball rolling. So I can see from the online browsing platform that there are 12 codes we are talking about here: Alpha-2 code English short name Remark AC Refers to Ascension Island and reserved at the request of Universal Postal Union (UPU) CP Refers to Clipperton Island and reserved at the request of International Telecommunication Union (ITU). DG Refers to Diego Garcia and reserved at the request of International Telecommunication Union (ITU) EA Refers to Ceuta, Melilla and reserved at the request of World Customs Organization (WCO). EU Refers to European Union and reserved at the request of ISO 4217/MA (March 1998) for ISO 6166, Securities - International securities identification numbering system (ISIN). EZ Refers to European OTC derivatives and reserved at the request of ISO 6166/RA, Securities - International securities identification numbering system (ISIN). FX France, Metropolitan Refers to Metropolitan France and reserved at the request of France. IC Refers to the Canary Islands and reserved at the request of World Customs Organization (WCO) SU USSR Refers to the former USSR and reserved at the request of the Foundation for Internet Development (FID). TA Refers to Tristan da Cunha and reserved at the request of Universal Postal Union (UPU). UK Refers to the United Kingdom and reserved at the request of United Kingdom. UN Refers to the United Nations and reserved by the ISO 3166 Maintenance Agency. [Disclaimer obviously UK is one of those on the list, but since UK is already delegated and United Kingdom associated in any case with the GB code I don’t think what I suggest below makes any difference to us.] Looking at the draft text for the WT5 report, would it be better to amend as follows: The 2012 Applicant Guidebook reserved any string that is a “short- or long- form name association with a code that has been designated as “exceptionally reserved” by the ISO 3166 Maintenance Agency”. Upon more detailed advice and examination of those “exceptionally reserved” codes it has been highlighted that the effect of reserving the short- or long- form names associated with the “exceptionally reserved” codes in the 2012 Applicant Guidebook is unclear. For example in the case of EZ which is exceptionally reserved as referring to OTC derivatives, and whether or not this resulted in the exclusion of ‘United Nations’ and ‘European Union’ from being allowed as new gTLDs in the AGB2012 since those terms are not country names. This provision should be clarified for the next round of new gTLDs. Some Work Track members have stated that an “exceptionally reserved” list does not exist under the ISO 3166 standard, and therefore it is unclear what this provision references. Do you agree or disagree? Please explain. Anyway just a suggestion, feel free to adapt/ ignore! Best wishes Nick From: Gnso-newgtld-wg-wt5 <gnso-newgtld-wg-wt5-bounces@icann.org> On Behalf Of Emily Barabas Sent: 13 November 2018 12:27 To: Jaap Akkerhuis <jaap@NLnetLabs.nl>; lists@christopherwilkinson.eu Wilkinson <lists@christopherwilkinson.eu> Cc: gnso-newgtld-wg-wt5@icann.org Subject: [Gnso-newgtld-wg-wt5] Follow up on "exceptionally reserved" codes 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, Emily From: Jaap Akkerhuis <jaap@NLnetLabs.nl<mailto:jaap@NLnetLabs.nl>> Date: Friday, 9 November 2018 at 12:50 To: "lists@christopherwilkinson.eu Wilkinson<mailto:lists@christopherwilkinson.eu%20Wilkinson>" <lists@christopherwilkinson.eu<mailto:lists@christopherwilkinson.eu>> Cc: Emily Barabas <emily.barabas@icann.org<mailto:emily.barabas@icann.org>>, <gnso-newgtld-wg-wt5@icann.org<mailto:gnso-newgtld-wg-wt5@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@christopherwilkinson.eu<mailto:lists@christopherwilkinson.eu> Wilkinson <lists@christopherwilkinson.eu<mailto:lists@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: https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 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>. Regards, jaap
Thankyou Emily and Nick for continuing to work on this. I also do not know whether the exceptionally reserved codes are associated with short or long form names. However, it is clear that should <.europeanunion> not yet be clearly reserved, it will have to be so. Neither do I know whether the exceptionally reserved alpha2 codes all have an alpha3 buddy. This is not an issue for .EUR since that is, unusually, the SAME as the ISO 4217 currency code for the €. (That is not the only reason for which I consider that ALL the ISO4217 alpha3 codes must be protected.) With regard to Nick's draft text, please recall that <.eu> was delegated well before the 2012 Round. There never was any question of .EU being a gTLD: 1. the restriction on two character codes already applied for gTLDs 2. the European Commission applied for .EU as a ccTLD, for policy reasons. There never was an application for a gTLD. 3. in those days ICANN was still applying a highly restrictive policy with respect to creating new gTLDs. I suggest that we delete the bit about exclusions from gTLDs in the 2012 Round. Regards Christopher PS: Emily: I shall be driving tomorrow afternoon and will miss the WT5 call. Please note my apologies.
El 13 de noviembre de 2018 a las 15:59 Nick Wenban-Smith <Nick.Wenban-Smith@nominet.uk> escribió:
Thanks Emily and to Jaap (I hope you are feeling better now) and Christopher
I was looking at whether I could propose some revised text for the draft report to get the ball rolling.
So I can see from the online browsing platform that there are 12 codes we are talking about here:
Alpha-2 code
English short name
Remark
AC
Refers to Ascension Island and reserved at the request of Universal Postal Union (UPU)
CP
Refers to Clipperton Island and reserved at the request of International Telecommunication Union (ITU).
DG
Refers to Diego Garcia and reserved at the request of International Telecommunication Union (ITU)
EA
Refers to Ceuta, Melilla and reserved at the request of World Customs Organization (WCO).
EU
Refers to European Union and reserved at the request of ISO 4217/MA (March 1998) for ISO 6166, Securities - International securities identification numbering system (ISIN).
EZ
Refers to European OTC derivatives and reserved at the request of ISO 6166/RA, Securities - International securities identification numbering system (ISIN).
FX
France, Metropolitan
Refers to Metropolitan France and reserved at the request of France.
IC
Refers to the Canary Islands and reserved at the request of World Customs Organization (WCO)
SU
USSR
Refers to the former USSR and reserved at the request of the Foundation for Internet Development (FID).
TA
Refers to Tristan da Cunha and reserved at the request of Universal Postal Union (UPU).
UK
Refers to the United Kingdom and reserved at the request of United Kingdom.
UN
Refers to the United Nations and reserved by the ISO 3166 Maintenance Agency.
[Disclaimer obviously UK is one of those on the list, but since UK is already delegated and United Kingdom associated in any case with the GB code I don’t think what I suggest below makes any difference to us.]
Looking at the draft text for the WT5 report, would it be better to amend as follows:
The 2012 Applicant Guidebook reserved any string that is a “short- or long-
form name association with a code that has been designated as “exceptionally reserved” by the ISO 3166 Maintenance Agency”. Upon more detailed advice and examination of those “exceptionally reserved” codes it has been highlighted that the effect of reserving the short- or long- form names associated with the “exceptionally reserved” codes in the 2012 Applicant Guidebook is unclear. For example in the case of EZ which is exceptionally reserved as referring to OTC derivatives, and whether or not this resulted in the exclusion of ‘United Nations’ and ‘European Union’ from being allowed as new gTLDs in the AGB2012 since those terms are not country names. This provision should be clarified for the next round of new gTLDs. Some Work Track members have stated that an “exceptionally reserved” list does not exist under the ISO 3166 standard, and therefore it is unclear what this provision references. Do you agree or disagree? Please explain.
Anyway just a suggestion, feel free to adapt/ ignore!
Best wishes
Nick
From: Gnso-newgtld-wg-wt5 <gnso-newgtld-wg-wt5-bounces@icann.org> On Behalf Of Emily Barabas Sent: 13 November 2018 12:27 To: Jaap Akkerhuis <jaap@NLnetLabs.nl>; lists@christopherwilkinson.eu Wilkinson <lists@christopherwilkinson.eu> Cc: gnso-newgtld-wg-wt5@icann.org Subject: [Gnso-newgtld-wg-wt5] Follow up on "exceptionally reserved" codes
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 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,
Emily
From: Jaap Akkerhuis <jaap@NLnetLabs.nl mailto:jaap@NLnetLabs.nl > Date: Friday, 9 November 2018 at 12:50 To: "lists@christopherwilkinson.eu Wilkinson mailto:lists@christopherwilkinson.eu%20Wilkinson " <lists@christopherwilkinson.eu mailto:lists@christopherwilkinson.eu > Cc: Emily Barabas <emily.barabas@icann.org mailto:emily.barabas@icann.org >, <gnso-newgtld-wg-wt5@icann.org mailto:gnso-newgtld-wg-wt5@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@christopherwilkinson.eu mailto:lists@christopherwilkinson.eu Wilkinson <lists@christopherwilkinson.eu mailto:lists@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: https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 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 http://iso.org/ site. The link for the decoding table is <https://www.iso.org/obp/ui/#iso:pub:PUB500001:en>.
Regards,
jaap
Emily Barabas writes: <SNIPPED a lot>
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.
I'm really pressed for time so this will be very short. But since you asked, here is my thn=inking. I observe hat the exceptional reservations is only on alpha-2 and alpha-3 _codes_ (and the exceptional reserved alpha-3 codes are not considered in the AGB). Alpha-2 and -3 codes are already covered by other rules in the AGB, I'm wondering why they need to be discussed at all in the AGB. Furthermore, the 3166 is under review and noise have been made that the current use of reserved codes might be changed in this process. I do think that there are more important things to spend energy on than this very specific case (and I repeat, might already been covered by a more general rule). So adding more rules to the ADB about this (what the current proposal is), is to my (pragmatic) taste an overkill. jaap
participants (4)
-
Emily Barabas -
Jaap Akkerhuis -
lists＠christopherwilkinson.eu Wilkinson -
Nick Wenban-Smith