[Gnso-newgtld-wg-wt5] WT5 Agenda, Work Plan & Consensus Call on Country & Territory Names - Please review before our call.
susan.payne at valideus.com
Wed Aug 8 12:59:35 UTC 2018
All, in the midst of the various other exchanges this email from Alexander seems to have been a little overlooked.
Alexander thanks for catching this. You are absolutely correct that the permutations provision (recommendation 7) should not cover 3-letter codes. We discussed this more than once during WG calls and there was no disagreement that I recall. Staff pointed out that your interpretation (ie that a permutation would cover, and exclude, the same three letters in any order) has not been applied in practice*. Many of us felt that your interpretation was never the intention, and indeed that you cannot change the order to create an entirely different 3-letter term and call that a permutation. Regardless, there was widespread agreement during the previous times this came up that this would benefit from clarification since the reference to permutations in relation to 3-letter codes is meaningless. I wouldn’t view this as you “giving” something to brands, since this has always been the case, but appreciate you spotting the error.
*Here’s an example from the last round: GIN (3-letter code for Guinea); ING (TLD delegated to Google). I haven’t bothered to look for multiple examples.
Head of Legal Policy | Valideus Ltd
E: susan.payne at valideus.com<mailto:susan.payne at valideus.com>
D: +44 20 7421 8255
T: +44 20 7421 8299
M: +44 7971 661175
From: Gnso-newgtld-wg-wt5 [mailto:gnso-newgtld-wg-wt5-bounces at icann.org] On Behalf Of Alexander Schubert
Sent: 07 August 2018 16:27
To: gnso-newgtld-wg-wt5 at icann.org
Subject: Re: [Gnso-newgtld-wg-wt5] WT5 Agenda, Work Plan & Consensus Call on Country & Territory Names - Please review before our call.
Hi work track members,
In the email from August 6th we got the attached document: “Recommendations - country and territory names - 6 August 2018 v2”.
I have some questions and corrections:
· “RECOMMENDATION #2” specifies “the 2012 Applicant Guidebook section 18.104.22.168.2.i”! Seems it should be section 22.214.171.124.1.i!
· We recommend to continue 126.96.36.199.1.vi in this document. In regard to 3-letter country codes section 188.8.131.52.1.vi specifies that permutations (ABC has the two permutations BCA and CAB, letters “rotate” but aren’t “scrambled” which would be a transposition) would be unavailable as well. Which never made ANY sense. Nobody would REMOTELY be able to guess what country permutation is hidden behind EUD or ALV (my two countries DE and LV).
· Hence I urge that we recommend to have 184.108.40.206.1.vi NOT anymore referencing to 220.127.116.11.1.i! Transpositions were anyway only referencing to long or short form country names (not to 3 letter codes), and you can’t “remove” punctuation or spaces from a 3 letter code (because by definition there is none). Brand Defenders listen up: If the permutation provision would remain then COUNTLESS 3-letter brands would be denied application without ANY real world reason. Every 3 letter code has two permutations – we would TRIPLE the reserved names by keeping 18.104.22.168.1.vi referencing to “I”. Instead I recommend change wording to:
“it is a permutation or transposition of any of the names included in items (ii) through (v). “.
I personally don’t much care – but my hope is if we do “something” that benefits brands – brands might agree to help protecting sizeable cities: by requiring Government support!
· The reference error continues in RECOMMENDATION #3: Should be 22.214.171.124.1.ii and so on.
I cannot recall full support of keeping them unavailable when we discussed permutations of 3 letter ISO 3166 country codes. In whose interest is that? Innocent question to the GAC members: is there ANY country out there that honestly believes that any of its two permutations might be in ANY way conflated with the original 3-letter code? While about 50% of the 3-letter codes are pure garbage (I doubt that there are many Germans who would create a connection between Germany and a domain ending in “.deu”) even for the 50% that are somewhat known (like ARG, LUX, BRA or ISR) it takes quite some effort to guess what country was meant if you see that just as gTLD WITHOUT knowing a country is potentially targeted. Once you only see the permutation without any other reference: there is just no connection with the country:
· RGA, GAR
· UXL, XLU
· RAB, ABR
· SRI, RIS
I doubt that anybody here could name just ONE permutation of a 3-letter country code (ISO 3166 Alpha-3) that one out of a ten thousand random Internet users would conflate with the original country. What exactly do we protect here? Whom? Certainly NOT the people of those countries, they are completely NOT affected at all. The good people of Israel most certainly wouldn’t mind if SRI International (sri.com, formerly “The Stanford Research Institute”) would apply for .sri and present their services there. Small detail: sri.com is the 8th oldest .com domain ever registered; It dates back to January 1986. This domain dates back to the inception of the DNS; SRI was one of the entities that MADE the Internet what it is today. Indeed they were part of the very first computer to computer connection in the Arpanet in 1969.
You all know that I am at times a very “protective” guy. But I wonder how I would explain to the people who literally started the Internet up how I supported a rule that denied SRI their 3-letter code to be part of the top-level of the Internet. Brand folks: you might want to weigh in. Because it is YOU that will have to answer that question to YOUR client one day!
From: Gnso-newgtld-wg-wt5 [mailto:gnso-newgtld-wg-wt5-bounces at icann.org] On Behalf Of Martin Sutton
Sent: Monday, August 06, 2018 3:42 PM
To: gnso-newgtld-wg-wt5 at icann.org<mailto:gnso-newgtld-wg-wt5 at icann.org>
Subject: [Gnso-newgtld-wg-wt5] WT5 Agenda, Work Plan & Consensus Call on Country & Territory Names - Please review before our call.
Dear Work Track members,
Please find below the proposed agenda for the WT5 call on Wednesday 8 August at 13:00 UTC:
1. Welcome/Agenda Review/SOI Updates
2. Review of Consensus Call Process and Work Plan
3. Consensus Call on Country and Territory Names
4. Wrap Up - Non-AGB Terms
On our upcoming call, the leadership team will introduce a work plan aimed at wrapping up WT5’s work and delivering an Initial Report by the end of September. In maintaining this timeline, the leadership is seeking to ensure that Work Track 5 inputs can be effectively integrated into the work of the broader New gTLD Subsequent Procedures PDP Working Group in time for delivery of the PDP’s Final Report. A copy of the work plan is attached.
As outlined in the work plan, the leadership team will be holding a series of consensus calls on potential recommendations to include in WT5’s Initial Report. These will be introduced in clusters, with the first set of recommendations focusing on country and territory names. The draft recommendations, which will be discussed on Wednesday, are attached. Work Track members are encouraged to review and provide feedback on these draft recommendations prior to the call on Wednesday. The leadership team will officially open the consensus call on this topic following Wednesday’s call. For more information on the consensus call process that will be followed, please see the GNSO Working Group Guidelines, Section 3.6:https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-1-gnso-wg-guidelines-18jun18-en.pdf [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_default_files_file_field-2Dfile-2Dattach_annex-2D1-2Dgnso-2Dwg-2Dguidelines-2D18jun18-2Den.pdf&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mBQzlSaM6eYCHFBU-v48zs-QSrjHB0aWmHuE4X4drzI&m=NVtIpaem-VqCNPYPOoZhv9ofczsIO-e3-mM3UoaoTMA&s=g15pYjxotpxtjftphXYKDMOR0bso7mS5i2CXTIVfcww&e=>.
If you need a dial out for the upcoming call or would like to send an apology, please email gnso-secs at icann.org<mailto:gnso-secs at icann.org>.
The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gnso-newgtld-wg-wt5