January 2014 - gtld-tech - lists.icann.org

How to complain about http://newgtlds.icann.org/en/program-status/delegated-strings
by Chris Thompson Jan. 30, 2014

Jan. 30, 2014

Apologies for using this mailing list, but ICANN's feedback form proves useless for this purpose. The web page http://newgtlds.icann.org/en/program-status/delegated-strings is almost a week out of date (the latest 12 gTLDs are missing). Is anyone listening here capable of getting it unwedged again? -- 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.

3 2

DNS-OARC Call for Presentations
by Mehmet Akcin Jan. 30, 2014

Jan. 30, 2014

Call for Presentations - DNS-OARC Spring Workshop, May 2014 Next OARC Spring Workshop will take place in Warsaw, Poland on May 10th and 11th, the weekend before RIPE68. OARC is requesting proposals for presentations, with a preference for DNS privacy and confidentiality work and ideas, and DNS over alternative (non UDP) transports. This workshop continues OARC's tradition of having meetings include a strong operational component. Presentations from DNS operators are particularly welcome. We'll also gladly accept talks from DNS researchers, as well as any other DNS-related subjects such as tools, visualizations and data analysis. If you are an OARC member, and have a sensitive topic you would like to present for members-only, we will accommodate those talks too. Adopting practice from other conferences, a section of lightning talks will be added for short presentations. Workshop Milestones * 20 December 2013, Call for Presentations posted * 6 January 2014, Open for submissions * 1 March 2014, Deadline for submission * 28 March 2014, Final Program published * May 9 2014, Final deadline for slideset submission Details for abstract submission will be published here: https://indico.dns-oarc.net/event/workshop-2014-05 at the beginning of January 2014. If you consider submitting a presentation, please let the Programme Committee know in advance to help us organize the presentations tracks. You can contact the Programme Committee: https://www.dns-oarc.net/oarc/programme via submissions at dns-oarc.net if you have questions or concerns. Mehmet Akcin, for the OARC Programme Committee (Please note that OARC is run on a non-profit basis, and is not in a position to reimburse expenses or time for speakers at its meetings.)

1 0

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 - Invalid names
by Colosi, John Jan. 16, 2014

Jan. 16, 2014

These two names are in the S5.4.2.txt file: المملكة-المتحدة-لبريطانيا-العظمى-وآيرلندا-الشمالية соединенное-королевство-великобритании-и-северной-ирландии The resulting A-labels for these names are not valid in the DNS: xn--------lch4abbabcbafmcmf4d0bj3bg3f4c5a1a8y3aaefhfeceagqkzl0gzbxbdlm xn--------5veddhabeqmbbabeeb4cjbbabfcaznh0agq9bbaqifehdaegn7eolfhst1bm The A-labels are 70 characters long, and DNS requires a label to be no longer than 63 characters in length. I suggest these two string be removed from the file. -- John John Colosi Senior Manager of Product Development JColosi(a)Verisign.com m: 703-967-4062 t: 703-948-3211 12061 Bluemont Way, Reston VA 20190 VerisignInc.com “This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is non-public, proprietary, privileged, confidential and exempt from disclosure under applicable law or may be constituted as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this message in error, notify sender immediately and delete this message immediately.”

2 1

CA's accepting CSR's for nic.<new gTLDs> yet?
by Alexander Mayrhofer Jan. 14, 2014

Jan. 14, 2014

Hi, has anybody had success with convincing one of the well-know Certification Authorities to issue a certificate for names under nic.<newgTLD> yet? I understand that most CA's have either not whitelisted the TLDs - another factor is that in the light of the name collision discussions, they would probably confuse such requests with (now banned) "internal certificates".. Pointers and anecdotal experience appreciated :) thanks, Alex

2 2

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