Alexander/all, Thanks for the note. I also opened Ticket 00113354 with ICANN on 11/14/2013 (see attached) on this very same issue. We need definitive, blessed by ICANN lists for these two sections (4.2 and 4.3) of Spec 5 so that we know exactly what to block and have assurances that all other backends are blocking the identical SLDs. As of Tues. (11/26), there has not been a response to my ticket. --Roy Dykes Neustar Registry Product Management -----Original Message----- From: gtld-tech-bounces@icann.org [mailto:gtld-tech-bounces@icann.org] On Behalf Of gtld-tech-request@icann.org Sent: Monday, November 25, 2013 11:59 AM To: gtld-tech@icann.org Subject: gtld-tech Digest, Vol 7, Issue 17 Send gtld-tech mailing list submissions to gtld-tech@icann.org To subscribe or unsubscribe via the World Wide Web, visit https://mm.icann.org/mailman/listinfo/gtld-tech or, via email, send a message with subject or body 'help' to gtld-tech-request@icann.org You can reach the person managing the list at gtld-tech-owner@icann.org When replying, please edit your Subject line so it is more specific than "Re: Contents of gtld-tech digest..." Today's Topics: 1. Specification 5 - Country names... again.. (Alexander Mayrhofer) 2. Re: Specification 5 - Country names... again.. (Luis Mu?oz) ---------------------------------------------------------------------- Message: 1 Date: Mon, 25 Nov 2013 16:18:46 +0000 From: Alexander Mayrhofer <alexander.mayrhofer@nic.at> To: "gtld-tech@icann.org" <gtld-tech@icann.org> Subject: [gtld-tech] Specification 5 - Country names... again.. Message-ID: <19F54F2956911544A32543B8A9BDE0750A37DB41@NICS-EXCH2.sbg.nic.at> Content-Type: text/plain; charset="us-ascii" I've started looking at the two PDFs of country names that ICANN mandates us to reserve in Section 4.2 and 4.3 of Specification 5 of the Registry Agreement. I have a couple of comments on this: a) I can only guess whether or not the PDFs that i use (http://unstats.un.org/unsd/geoinfo/ungegn/docs/ungegn-tech-ref-manual_M87_co... and http://unstats.un.org/unsd/geoinfo/UNGEGN/docs/26th-gegn-docs/WP/WP54_UNGEGN...) are the correct ones, since ICANN failed to include a reference to the documents in the Agreement. b) Extracting names from those documents (particularly in scripts that i'm not familiar with) is absolutely horrible, and will likely lead to interopability problems between registries. c) The mapping of the strings required to be reserved to the actual A-Label is undefined. Therefore, could ICANN please look into creating an reservation list covering these two requirements, and publish that list as a recommended way to implement the two requirements? ICANN could use a tiny tiny fraction of the application fees to contract someone to create an authoritative list of names to be reserved - Or, maybe as a secondary option in case there should be insufficient budget, allocate resources from their "Languages Services Department" http://blog.icann.org/2013/10/introducing-the-language-services-team/ to create this list? I'm sure that many members of the community would welcome this as a useful contribution to ensure a unified approach to those requirements. thanks, Alex Mayrhofer Head of R&D nic.at ------------------------------ Message: 2 Date: Mon, 25 Nov 2013 11:58:20 -0500 From: Luis Mu?oz <lem@isc.org> To: Alexander Mayrhofer <alexander.mayrhofer@nic.at> Cc: "gtld-tech@icann.org" <gtld-tech@icann.org> Subject: Re: [gtld-tech] Specification 5 - Country names... again.. Message-ID: <4BAD47C7-979B-406B-9C39-0C4490F87648@isc.org> Content-Type: text/plain; charset="us-ascii" On Nov 25, 2013, at 11:18 AM, Alexander Mayrhofer wrote:
I've started looking at the two PDFs of country names that ICANN mandates us to reserve in Section 4.2 and 4.3 of Specification 5 of the Registry Agreement. I have a couple of comments on this:
a) I can only guess whether or not the PDFs that i use (http://unstats.un.org/unsd/geoinfo/ungegn/docs/ungegn-tech-ref-manual_M87_co... and http://unstats.un.org/unsd/geoinfo/UNGEGN/docs/26th-gegn-docs/WP/WP54_UNGEGN...) are the correct ones, since ICANN failed to include a reference to the documents in the Agreement.
b) Extracting names from those documents (particularly in scripts that i'm not familiar with) is absolutely horrible, and will likely lead to interopability problems between registries.
c) The mapping of the strings required to be reserved to the actual A-Label is undefined.
Therefore, could ICANN please look into creating an reservation list covering these two requirements, and publish that list as a recommended way to implement the two requirements?
ICANN could use a tiny tiny fraction of the application fees to contract someone to create an authoritative list of names to be reserved - Or, maybe as a secondary option in case there should be insufficient budget, allocate resources from their "Languages Services Department" http://blog.icann.org/2013/10/introducing-the-language-services-team/ to create this list?
I'm sure that many members of the community would welcome this as a useful contribution to ensure a unified approach to those requirements.
++ I went to the trouble of interacting with the primary sources and obtaining workable references because what is published is quite hard to coerce into the format we all need it. In the process I received rather amusing responses from various organizations that should know better. I'm attaching a list that should be easier to work with. Rather than simply sending them to this mailing list, wouldn't it be better to setup a github repo or similar device so that updates can be made to the data, and we all have access to the latest version of the common work? In the meanwhile, comments and additions are welcome. Best regards -lem