[Ctn-crosscom] Next meeting

Thu Jun 4 08:00:41 UTC 2015

Dear all,

I agree with the concerns that have been expressed regarding two letter gTLD registrations.  The current protection of two letter codes has set a precedent, is understood by internet users and provides a dedicated space for national identities.  Changing this, changes the fundamental structure that end users are used to and will create confusion.

As others have already said there is also the risk of new country codes clashing with two letter stings that have been allocated as gTLDs which would have serious consequences.

Kind regards,

Laura Hutchison
Policy Executive

T: +44 (0) 1865 332242
M:  +44 (0)7931 384082
E: laurah at nominet.org.uk<mailto:laurah at nominet.org.uk>
W:  www.nominet.org.uk<http://www.nominet.org.uk/>

Nominet UK is a company limited by guarantee and registered in England under No. 3203859. Our registered office is Minerva House, Edmund Halley Road, Oxford Science Park, Oxford, OX4 4DQ, England.

From: ctn-crosscom-bounces at icann.org [mailto:ctn-crosscom-bounces at icann.org] On Behalf Of Daniel Kalchev
Sent: 03 June 2015 18:48
To: Joke Braeken
Cc: ctn-crosscom at icann.org
Subject: Re: [Ctn-crosscom] Next meeting

Dear colleagues,

I would too like to highlight this issue. Specifically, RFC1591 says
"IANA is not in the business to determine what is and what is not a country".

Assigning a two letter code to a gTLD will essentially make the ISO list obsolete/ignored. This might have many other implications,

Daniel Kalchev

Sent from my iPhone

On 2.06.2015 г., at 13:06, Joke Braeken <Joke.Braeken at eurid.eu<mailto:Joke.Braeken at eurid.eu>> wrote:
Dear all,

I share Annebeth’s concerns.

-          The clear distinction between ccTLDs and gTLDs, based on TLD length, is lost, once opening up 2-letters as gTLDs.  This will increase the end-user confusion.  After all, the legal frameworks governing ccTLDs and gTLDs  are different.

-          having a 2-character gTLD assigned, which might correspond to the 2-letter code of a potential future country, will disadvantage said country
Best regards.

Joke Braeken (Ms)
External Relations Deputy Manager

EURid
Woluwelaan 150
1831 Diegem - Belgium
TEL.: +32 (0) 2 401 27 50
DIRECT: +32 (0) 2 401 30 14
MOB.:+32 (0) 473 779 559
joke.braeken at eurid.eu<mailto:joke.braeken at eurid.eu>
http://www.eurid.eu<http://www.eurid.eu/>
[facebook_icon_email]<https://www.facebook.com/EUregistry><image002.png><https://twitter.com/Euregistry>

<image003.jpg>

From: ctn-crosscom-bounces at icann.org<mailto:ctn-crosscom-bounces at icann.org> [mailto:ctn-crosscom-bounces at icann.org] On Behalf Of Annebeth Lange
Sent: dinsdag 2 juni 2015 10:03
To: Jordi Iparraguirre; ctn-crosscom at icann.org<mailto:ctn-crosscom at icann.org>
Subject: Re: [Ctn-crosscom] Next meeting

Hi all,

Thanks for all the comments. I have added another argument under option 3 to hightlight the risks opening up for 2-letters for gTLDs. I understand that these brand owners would like to have their brand as domain name, but in my view this will ruin the system with the distinction between ccTLDs and gTLDs and discriminate possible new countries in the future.

Kind regards,
Annebeth

Annebeth B. Lange
Head of Legal and Policy
UNINETT Norid AS
C. J. Hambros plass 2 c
NO-0164 OSLO
annebeth.lange at uninett.no<mailto:annebeth.lange at uninett.no>
Mobile: +47 959 11 559

From: "Jordi Iparraguirre .cat" <jordi at iparraguirre.cat<mailto:jordi at iparraguirre.cat>>
Date: Tuesday 2 June 2015 09:44
To: "ctn-crosscom at icann.org<mailto:ctn-crosscom at icann.org>" <ctn-crosscom at icann.org<mailto:ctn-crosscom at icann.org>>
Subject: Re: [Ctn-crosscom] Next meeting

Hi and apologies for not being able to join the last conference.

Option 3 is an interesting one. I've added a couple of risks to it as I
think there is a risk of consumer confusion and brand overlapping.

Attached previous (Grigori+Colin) doc + my edits.

Thanks
jordi

El 01/06/15 a les 21:04, Colin O'Brien ha escrit:
Hello all,

I have added an additional option to Grigori’s document.  I feel there
should be an option that allows the owners of 2 character trademarks to
operate closed brand registries as long as there is no conflict with ISO
3166-1.

Cordially,

Colin

*From:*ctn-crosscom-bounces at icann.org<mailto:*ctn-crosscom-bounces at icann.org>
[mailto:ctn-crosscom-bounces at icann.org] *On Behalf Of *Lars Hoffmann
*Sent:* Thursday, May 28, 2015 11:36 AM
*To:* ctn-crosscom at icann.org<mailto:ctn-crosscom at icann.org>
*Subject:* [Ctn-crosscom] Next meeting

Dear all,

Apologies for the late email, but due to a number of scheduling issues
we will cancel next week’s call. Instead we will resume our calls on
Monday 8 June at 20:00 UTC (local times
<http://www.timeanddate.com/worldclock/fixedtime.html?msg=CWG+Country+and+Territory+Names+-+WG+Call&iso=20150608T19&p1=1440&ah=1><http://www.timeanddate.com/worldclock/fixedtime.html?msg=CWG+Country+and+Territory+Names+-+WG+Call&iso=20150608T19&p1=1440&ah=1%3e>).

A detailed agenda will follow.

This also means, that there will be more time for participants to send
back their views on the 2-letter code options. I have attached all
documents received so far. In time for the next meeting I will send out
a collated document.

Please note, if you send a document please feel free to post directly to
the list, I will collate it from there.

Many thanks and best wishes,
Lars

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
_______________________________________________
Ctn-crosscom mailing list
Ctn-crosscom at icann.org<mailto:Ctn-crosscom at icann.org>
https://mm.icann.org/mailman/listinfo/ctn-crosscom

Disclaimer:
This email and any attachment hereto is intended solely for the person to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient or if you have received this email in error, please delete it and immediately contact the sender by telephone or email, and destroy any copies of this information. You should not use or copy it, nor disclose its content to any other person or rely upon this information. Please note that any views presented in the email and any attachment hereto are solely those of the author and do not necessarily represent those of EURid. While all care has been taken to avoid any known viruses, the recipient is advised to check this email and any attachment for presence of viruses.
Other languages:
English<http://www.eurid.eu/en/legal-disclaimer>

Estonian<http://www.eurid.eu/et/legal-disclaimer>

Italian<http://www.eurid.eu/it/legal-disclaimer>

Maltese<http://www.eurid.eu/mt/legal-disclaimer>

Romanian<http://www.eurid.eu/ro/legal-disclaimer>

Swedish<http://www.eurid.eu/sv/legal-disclaimer>

Czech<http://www.eurid.eu/cs/legal-disclaimer>

Spanish<http://www.eurid.eu/es/legal-disclaimer>

Latvian<http://www.eurid.eu/lv/legal-disclaimer>

Dutch<http://www.eurid.eu/nl/legal-disclaimer>

Slovak<http://www.eurid.eu/sk/legal-disclaimer>

Greek<http://www.eurid.eu/el/legal-disclaimer>

Danish<http://www.eurid.eu/da/legal-disclaimer>

French<http://www.eurid.eu/fr/legal-disclaimer>

Lithuanian<http://www.eurid.eu/lt/legal-disclaimer>

Polish<http://www.eurid.eu/pl/legal-disclaimer>

Slovenian<http://www.eurid.eu/sl/legal-disclaimer>

Bulgarian<http://www.eurid.eu/bg/legal-disclaimer>

German<http://www.eurid.eu/de/legal-disclaimer>

Gaelic<http://www.eurid.eu/ga/legal-disclaimer>

Hungarian<http://www.eurid.eu/hu/legal-disclaimer>

Portuguese<http://www.eurid.eu/pt/legal-disclaimer>

Finnish<http://www.eurid.eu/fi/legal-disclaimer>

Croatian<http://www.eurid.eu/hr/legal-disclaimer>

_______________________________________________
Ctn-crosscom mailing list
Ctn-crosscom at icann.org<mailto:Ctn-crosscom at icann.org>
https://mm.icann.org/mailman/listinfo/ctn-crosscom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/ctn-crosscom/attachments/20150604/ca12f368/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 3541 bytes
Desc: image001.png
URL: <http://mm.icann.org/pipermail/ctn-crosscom/attachments/20150604/ca12f368/image001-0001.png>