November 2013 - gtld-tech - lists.icann.org

Call for Presentations for TechDay at ICANN Buenos Aires
by Dr Eberhard Lisse Jan. 28, 2014

Jan. 28, 2014

As usual we shall be organizing TechDay on Monday of the coming ICANN meeting in Buenos Aires. Please submit ideas for presentations to the list addresses where this message appears or to any of the following email addresses: el(a)lisse.na ondrej.filip(a)nic.cz This time we would like to have an Latin American focus, if possible, hence Latin American presenters are strongly encouraged to come forward. As we have no budget presenters are responsible for their own transport and room and board. As the name suggests, talks must be of a technical (or operational, perhaps even administrative) nature, and should revolve around TLDs, but otherwise we are quite open. Please forward this to gNSO and other lists as well :-)-O el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist (Saar) el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 \ / Bachbrecht, Namibia ;____/

3 6

Specification 5 - Country names... again..
by Alexander Mayrhofer Jan. 13, 2014

Jan. 13, 2014

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_c… and http://unstats.un.org/unsd/geoinfo/UNGEGN/docs/26th-gegn-docs/WP/WP54_UNGEG…) 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

8 19

Version 1.0 of the URS technical requirements published
by Gustavo Lozano Dec. 4, 2013

Dec. 4, 2013

Colleagues, Version 1.0 of the URS technical requirements document has been published at: http://newgtlds.icann.org/en/applicants/urs The direct download link of the document is: http://newgtlds.icann.org/en/applicants/urs/tech-requirements-17oct13-en.pdf Regards, Gustavo

3 3

Re: [gtld-tech] gtld-tech Digest, Vol 7, Issue 17
by Dykes, Roy Nov. 26, 2013

Nov. 26, 2013

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(a)icann.org [mailto:gtld-tech-bounces@icann.org] On Behalf Of gtld-tech-request(a)icann.org Sent: Monday, November 25, 2013 11:59 AM To: gtld-tech(a)icann.org Subject: gtld-tech Digest, Vol 7, Issue 17 Send gtld-tech mailing list submissions to gtld-tech(a)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(a)icann.org You can reach the person managing the list at gtld-tech-owner(a)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(a)nic.at> To: "gtld-tech(a)icann.org" <gtld-tech(a)icann.org> Subject: [gtld-tech] Specification 5 - Country names... again.. Message-ID: <19F54F2956911544A32543B8A9BDE0750A37DB41(a)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_c… and http://unstats.un.org/unsd/geoinfo/UNGEGN/docs/26th-gegn-docs/WP/WP54_UNGEG…) 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(a)isc.org> To: Alexander Mayrhofer <alexander.mayrhofer(a)nic.at> Cc: "gtld-tech(a)icann.org" <gtld-tech(a)icann.org> Subject: Re: [gtld-tech] Specification 5 - Country names... again.. Message-ID: <4BAD47C7-979B-406B-9C39-0C4490F87648(a)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_c… and http://unstats.un.org/unsd/geoinfo/UNGEGN/docs/26th-gegn-docs/WP/WP54_UNGEG…) 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

1 0

Re: [gtld-tech] Specification 5 - Country names... again..
by Michele Neylon - Blacknight Nov. 25, 2013

Nov. 25, 2013

Gavin Nice work. You should probably add "eire" as the alternative for "Ireland", as our government tends to like having both the Irish and English versions Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting & Colocation, Domains http://www.blacknight.co/ http://blog.blacknight.com/ http://www.technology.ie Intl. +353 (0) 59 9183072 Locall: 1850 929 929 Direct Dial: +353 (0)59 9183090 Fax. +353 (0) 1 4811 763 Twitter: http://twitter.com/mneylon ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,Ireland Company No.: 370845 ________________________________________ From: gtld-tech-bounces(a)icann.org [gtld-tech-bounces(a)icann.org] on behalf of Gavin Brown [gavin.brown(a)centralnic.com] Sent: 25 November 2013 17:09 To: Luis Muñoz; Alexander Mayrhofer Cc: gtld-tech(a)icann.org Subject: Re: [gtld-tech] Specification 5 - Country names... again.. > 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. I agree: https://github.com/centralnic/spec5-reserved-names I've added your list, plus the file I was working on. Let's see if we can work out a format that makes sense for this - JSON? XML? YAML? G. -- Gavin Brown Chief Technology Officer CentralNic Group plc (LSE:CNIC) Innovative, Reliable and Flexible Registry Services for ccTLD, gTLD and private domain name registries https://www.centralnic.com/ CentralNic Group plc is a company registered in England and Wales with company number 8576358. Registered Offices: 35-39 Moorgate, London, EC2R 6AR.

1 0

Delegated strings: WHOIS & SLAs...
by Alexander Mayrhofer Nov. 21, 2013

Nov. 21, 2013

Looking at some of the recently delegated new gTLDs, i was very surprised to learn that the WHOIS service is unreachable for some of those TLDs (which makes me wonder how they passed PDT, or why the service degraded since then?). Anyways, since WHOIS is included in the SLA requirements of ICANN, this makes me also wonder when the SLA actually "kicks in", and, whether the SLAs are actually being measured right now by ICANN ... Any information about this? Alex

13 33

Update to reserved names list for new gTLDs
by Francisco Arias Nov. 21, 2013

Nov. 21, 2013

Colleagues, This is a heads up that we have updated the list of reserved names for new gTLDs at http://www.icann.org/en/resources/registries/reserved Formal notifications to contracted parties will go out shortly. Regards, -- Francisco Arias gTLD Registry Technical Liaison ICANN PGP: 1FDE 819F 7BEC 1CB2 127E EE54 9A4D 337B D510 E397

9 12

IANA ID for "internal" registrar
by Alexander Mayrhofer Nov. 21, 2013

Nov. 21, 2013

I'm wondering what IANA ID "internal" registrars (such as those owning the "nic" 2nd-level domain, or any registrars used for monitoring) should be allocated? I understand that there was some documentation that recommended using 9999 for the "registry" registrar. But since more registrars are likely needed (such as the ICANN monitoring registrar), we probably need more than one ID. Any recommendations on that? Otherwise, we'll proceed with counting "up" from 9999.. or down... or negative IDs? ;) Alex

4 5

Re: [gtld-tech] Delegated strings: WHOIS & SLAs...
by Chris Thompson Nov. 21, 2013

Nov. 21, 2013

Is the ban on non-apex RRs (such as an SRV for _nicname._tcp.[TLD]) other than delegations at all driven by the fear that too much of the world is using BIND's "root-delegation-only" with an exclude list that they won't change to include new gTLDs (or any equivalent in other recursive nameserver implementations)? We all remember the incident(s) that caused that option to be invented, but I fear it is going to cause trouble for a long time to come. -- Chris Thompson University of Cambridge Computing Service, Email: cet1(a)ucs.cam.ac.uk Roger Needham Building, 7 JJ Thomson Avenue, Phone: +44 1223 334715 Cambridge CB3 0RB, United Kingdom.

1 0

Re: [gtld-tech] Delegated strings: WHOIS & SLAs...
by Michele Neylon - Blacknight Nov. 20, 2013

Nov. 20, 2013

They aren't obliged to use nic.tld afaik - the whois server is specified in their respective IANA entry -- Mr Michele Neylon Blacknight Solutions Hosting & Colocation, Domains http://www.blacknight.co/ http://blog.blacknight.com/ http://www.technology.ie Intl. +353 (0) 59 9183072 Locall: 1850 929 929 Direct Dial: +353 (0)59 9183090 Fax. +353 (0) 1 4811 763 Twitter: http://twitter.com/mneylon ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,Ireland Company No.: 370845 ________________________________________ From: gtld-tech-bounces(a)icann.org [gtld-tech-bounces(a)icann.org] on behalf of Alexander Mayrhofer [alexander.mayrhofer(a)nic.at] Sent: 20 November 2013 15:25 To: Rubens Kuhl Cc: gtld-tech(a)icann.org Subject: Re: [gtld-tech] Delegated strings: WHOIS & SLAs... I'm using whois.nic.<TLD> - and, yes, nic.<TLD> is properly delegated and reachable in that case, but "whois.nic.<tld>" returns an NXDOMAIN. My understanding is that ICANN requires the WHOIS service to be offered under that hostname... See the respective specification in the AGB.. Indeed, the IANA record shows a different server - so, do i understand correctly that you can actually submit to IANA a different WHOIS server than the one required by ICANN? Can anyone who's already delegated confirm this? Alex > -----Ursprüngliche Nachricht----- > Von: Rubens Kuhl [mailto:rubensk@nic.br] > Gesendet: Mittwoch, 20. November 2013 15:02 > An: Alexander Mayrhofer > Cc: gtld-tech(a)icann.org > Betreff: Re: [gtld-tech] Delegated strings: WHOIS & SLAs... > > > Are you using whois.nic.<TLD> or the WHOIS server mentioned at > http://www.iana.org/whois?q=<TLD> ? > > > Rubens > > On Nov 20, 2013, at 10:53 AM, Alexander Mayrhofer > <alexander.mayrhofer(a)nic.at> wrote: > > > > > Looking at some of the recently delegated new gTLDs, i was very surprised > to learn that the WHOIS service is unreachable for some of those TLDs (which > makes me wonder how they passed PDT, or why the service degraded since > then?). Anyways, since WHOIS is included in the SLA requirements of ICANN, > this makes me also wonder when the SLA actually "kicks in", and, whether > the SLAs are actually being measured right now by ICANN ... > > > > Any information about this? > > > > Alex > >

3 2