<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p> </p>
<div id="outerContainer">
<div id="sidebarContainer">
<div id="toolbarSidebar">
<div class="splitToolbarButton toggled"> </div>
</div>
</div>
</div>
<div id="sidebarContainer">
<div id="sidebarContent"> </div>
</div>
<div id="mainContainer">
<div class="toolbar">
<div id="toolbarContainer">
<div id="toolbarViewer">
<div id="toolbarViewerLeft"> </div>
</div>
</div>
</div>
</div>
<div class="splitToolbarButton"> </div>
Another part of our discussion on this issue in the first Round (for
better formatting, please read it from the link)<br>
<br>
Letter to Fadi, Steve, Akram, Alain and Heather Dryden, September
24, 2012<br>
<a class="moz-txt-link-freetext" href="https://www.icann.org/en/system/files/correspondence/neylon-et-al-to-chehade-et-al-24sep12-en.pdf">https://www.icann.org/en/system/files/correspondence/neylon-et-al-to-chehade-et-al-24sep12-en.pdf</a><br>
<br>
The rapid growth and adoption of the Internet over the past two
decades hastransformed the lives of billions of people, and
reinvented communication,<br>
commerce, and society. Countless economic and cultural barriers have
been eliminated as a direct result of the freedom of choice and
openness made<br>
possible by the Internet. <br>
<br>
Notably, the stated goals underlying ICANN’s current efforts to
expand the Domain Name System (DNS) by adding new generic Top-Level
Domains<br>
(gTLDs) are to “increase competition and choice.”<br>
<br>
We, the undersigned individuals and organizations, support those
goals wholeheartedly and without reservation.<br>
<br>
However, we are concerned that some pending gTLD applications seek
to be operated in a “closed” manner in reliance upon Section 6 of
Specification 1 (“Registry Operator Code of Conduct”) in Module 5
(“Base New gTLD Agreement”) of the Applicant Guidebook, which
provides: <br>
<i>Registry Operator may request an exemption to this Code of
Conduct, and such</i><i><br>
</i><i>exemption may be granted by ICANN in ICANN's reasonable
discretion, if Registry Operator demonstrates to ICANN's reas</i><i><br>
</i><i>onable satisfaction that (i) all domain name registrations in
the TLD are registered to, and maintained by, Registry Operator
for its own exclusive use, (ii) Registry Operator does not sell,</i><i><br>
</i><i>distribute or transfer control or use of any registrations in
the TLD to any third party that is not an Affiliate of Registry
Operator, and (iii) application of this Code</i><i><br>
</i><i>of Conduct to the TLD is not necessary to protect the public
interest.</i><i><br>
</i><br>
Based on our collective industry experience, we are of the opinion
that the underlying intention of Section 6 was to allow for the
operation of closed gTLDs<br>
only under very defined circumstances. Specifically, that closed
gTLDs should be reserved for only those strings in which<br>
the applicant possesses established (i.e., legally recognized)
intellectual property rights, basically brand names.<br>
We believe that this interpretation of Section 6 is inherently
logical especially in view of the discussions that preceded the
opening<br>
of gTLDs--which focused, in very large part, on expanding choices
and opportunities as well as promoting innovation, for Internet
consumers worldwide.<br>
<br>
Further, generic words used in a generic way belong to all people.
It is inherently<br>
in the public interest to allow access to generic new gTLDs to the
whole<br>
of the Internet Community, e.g., .BLOG, .MUSIC, .CLOUD. Allowing
everyone to<br>
register and use second level domain names of these powerful,
generic TLDs is<br>
exactly what we envisioned the New gTLD Program would do. In
contrast, to<br>
allow individual Registry Operators to segregate and close-off
common words for<br>
which they do not possess intellectual property rights in effect
allows them to<br>
circumvent nation-states’ entrenched legal processes for obtaining
legitimate and<br>
recognized trademark protections.<br>
<br>
Accordingly, we respectfully request that ICANN clarify the
circumstances under<br>
which the Section 6 exemption shall apply, and if necessary, allow
applicants to<br>
amend their applications to comply with such clarification.<br>
<br>
As an alternative, the Applicant could demonstrate that they have
internationally<br>
established and exclusive rights to the string in question, and that
it is not a<br>
generic term.<br>
<br>
Our goal, as always, is to foster consumer choice and nurture a free
and open<br>
Internet. <br>
<div style="left: 350.267px; top: 458.581px; font-size: 18.8px;
font-family: sans-serif; transform: scaleX(1.01273);">With sincere
thanks for your consideration,</div>
<div style="left: 150px; top: 527.381px; font-size: 18.8px;
font-family: sans-serif; transform: scaleX(0.971516);">Michele
Neylon, Blacknight</div>
<div style="left: 150px; top: 549.781px; font-size: 18.8px;
font-family: sans-serif; transform: scaleX(0.991299);">Scott
Pinzon, former Director of Marketing and Outreach, ICANN</div>
<div style="left: 150px; top: 571.781px; font-size: 18.8px;
font-family: sans-serif; transform: scaleX(1.01707);">Luc Seufer,
EuroDNS</div>
<div style="left: 150px; top: 593.781px; font-size: 18.8px;
font-family: sans-serif; transform: scaleX(1.0052);">Francesco
Cetraro</div>
<div style="left: 150px; top: 615.781px; font-size: 18.8px;
font-family: sans-serif; transform: scaleX(0.988627);">Nigel
Roberts</div>
<div style="left: 150px; top: 637.781px; font-size: 18.8px;
font-family: sans-serif; transform: scaleX(0.989227);">Chris Kurk,
DomainPeople Inc</div>
<div style="left: 150px; top: 659.781px; font-size: 18.8px;
font-family: sans-serif; transform: scaleX(0.982184);">Chris
Pelling, Netearth One Inc</div>
<div style="left: 306.618px; top: 681.781px; font-size: 18.8px;
font-family: sans-serif; transform: scaleX(1.03786);">Michael
Shohat, Conon AG</div>
<div style="left: 150px; top: 703.781px; font-size: 18.8px;
font-family: sans-serif; transform: scaleX(0.997068);">Paul
Andersen, Arctic Names</div>
<div style="left: 150px; top: 725.781px; font-size: 18.8px;
font-family: sans-serif; transform: scaleX(0.998074);">Frédéric
Guillemaut, MailClub.fr</div>
<div style="left: 150px; top: 747.781px; font-size: 18.8px;
font-family: sans-serif; transform: scaleX(0.995206);">Robert
Birkner, 1API GmbH</div>
<div style="left: 150px; top: 770.181px; font-size: 18.8px;
font-family: sans-serif; transform: scaleX(0.994454);">Kelly
Hardy, Kelly Hardy Consulting</div>
<div style="left: 150px; top: 792.181px; font-size: 18.8px;
font-family: sans-serif; transform: scaleX(0.972478);">Gerardo
Aristizabal, Cci reg s.a.</div>
<div style="left: 150px; top: 814.181px; font-size: 18.8px;
font-family: sans-serif; transform: scaleX(1.0015);">Benny
Samuelsen, Nordreg AB</div>
<div style="left: 150px; top: 836.181px; font-size: 18.8px;
font-family: sans-serif; transform: scaleX(0.991174);">Colin
McDermott, Banc Media</div>
<div style="left: 150px; top: 858.181px; font-size: 18.8px;
font-family: sans-serif; transform: scaleX(1.00785);">Tom Gilles,
newgtldsite.com</div>
<div id="outerContainer">
<div id="mainContainer"> </div>
</div>
<br>
<div class="moz-cite-prefix">On 4/13/2017 11:23 AM, Kathy Kleiman
wrote:<br>
</div>
<blockquote
cite="mid:cad831b0-99e7-364b-4963-fe448071b02c@kathykleiman.com"
type="cite">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<p>Hi All, <br>
</p>
<p>I'm a new member to this list, but there is a lot of material
about the harms and concerns behind Closed Generics. In
preparation for the meeting later today, I'll post some of it.
I'm copying Michele Neylon, who was a leader in sharing concerns
about Closed Generics with the ICANN Community in 2013.</p>
<p>I don't think there is the time to prepare a robust debate for
today, but hopefully at your next meeting, you might invite some
of the names (people & their organizations) that you see in
these materials into the discussion. There are also Community
Objections on this issue that you might want to evaluate. <br>
</p>
<p>Best regards, Kathy (Kleiman)</p>
<p>-----------------------------------------------------------------</p>
<pre><a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://forum.icann.org/lists/comments-closed-generic-05feb13/msg00174.html">https://forum.icann.org/lists/comments-closed-generic-05feb13/msg00174.html</a>
Dear Sir / Madam
I am submitting these comments on behalf of Blacknight, Ireland's only ICANN
accredited registrar.
They do not reflect the formal views of any stakeholder group, but those of our
company.
We are on the record with respect to our views on this issue, having spoken
during the public forum at ICANN Toronto
(<a moz-do-not-send="true" rel="nofollow" href="http://toronto45.icann.org/node/34215">http://toronto45.icann.org/node/34215</a>) and having sent several letters to
ICANN's board, which were co-signed by a broad cross-section of the ICANN
Community:
<a moz-do-not-send="true" rel="nofollow" href="http://newgtlds.icann.org/en/program-status/correspondence/neylon-et-al-to-chehade-et-al-24sep12-en.pdf">http://newgtlds.icann.org/en/program-status/correspondence/neylon-et-al-to-chehade-et-al-24sep12-en.pdf</a>
<a moz-do-not-send="true" rel="nofollow" href="http://newgtlds.icann.org/en/program-status/correspondence/neylon-et-al-to-chalaby-et-al-22jan13-en.pdf">http://newgtlds.icann.org/en/program-status/correspondence/neylon-et-al-to-chalaby-et-al-22jan13-en.pdf</a>
Rather than rehash our previous arguments I would prefer to simply state that
they are unchanged.
I've summarised some of the issues we see with them here:
<a moz-do-not-send="true" rel="nofollow" href="http://www.internetnews.me/2013/02/23/5-reasons-why-closed-generic-new-gtlds-should-be-opposed/">http://www.internetnews.me/2013/02/23/5-reasons-why-closed-generic-new-gtlds-should-be-opposed/</a>
It is also worth noting that our views are shared by some very large brands who
have taken the time to submit very rational comments on this topic.
But more importantly both consumer and trade organisations representing large
numbers of internet users and businesses have too.
Regards
Michele
Mr Michele Neylon
Blacknight Solutions ♞
Hosting & Domains
ICANN Accredited Registrar
<a moz-do-not-send="true" rel="nofollow" href="http://www.blacknight.co">http://www.blacknight.co</a>
<a moz-do-not-send="true" rel="nofollow" href="http://blog.blacknight.com/">http://blog.blacknight.com/</a>
Intl. +353 (0) 59 9183072
US: 213-233-1612
Locall: 1850 929 929
Facebook: <a moz-do-not-send="true" rel="nofollow" href="http://fb.me/blacknight">http://fb.me/blacknight</a>
Twitter: <a moz-do-not-send="true" rel="nofollow" href="http://twitter.com/mneylon">http://twitter.com/mneylon</a>
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,Ireland Company No.: 370845</pre>
<br>
<div class="moz-cite-prefix">On 4/12/2017 4:45 AM, Michael
Flemming wrote:<br>
</div>
<blockquote
cite="mid:CAAE6pKFb3emd2rTgvU0p0ZzpXNkORbTgqbuaLzSeZVLKp4c99w@mail.gmail.com"
type="cite">
<div dir="ltr">Dear All,
<div><br>
</div>
<div>Please find the material that we will be referring to in
order to address potential harms of Closed Generics.</div>
<div><br>
</div>
<div>Kind regards,</div>
<div><br>
</div>
<div>Michael Flemming</div>
<div><br>
<div class="gmail_extra"> <br>
<div class="gmail_quote">On Mon, Apr 10, 2017 at 6:28 PM,
Michael Flemming <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:flemming@brightsconsulting.com"
target="_blank">flemming@brightsconsulting.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><span style="font-size:12.8px">Dear
All,</span>
<div style="font-size:12.8px"><br>
</div>
<div style="font-size:12.8px">This week on 13 April
2017 at 21 UTC we will be once again discussing
Closed Generics. As of our last meeting, we went
through the Pros and Cons of Closed Generics by
looking at the comments made in the Public
Comments. We have not reached a consensus on
anything at this point, however, we have not had a
lot of input for the Cons and potential harm of
Closed Generics at the current time. This week we
will try to distinguish what potential harm exists
if Closed Generics were allowed by analyzing the
Public Comments even further. I welcome anyone who
would like to assist in this discussion and
analysis by joining us this week. Below is the <span
class="m_-8575844256750814590m_3745383161031865879gmail-il">agenda</span>.</div>
<div style="font-size:12.8px"><br>
</div>
<div style="font-size:12.8px">
<ol>
<li style="margin-left:15px"><i>Welcome<br>
<br>
</i></li>
<li style="margin-left:15px"><i>SOI<br>
<br>
</i></li>
<li style="margin-left:15px"><i>Closed Generics</i><br>
<br>
</li>
<li style="margin-left:15px"><i>AOB</i></li>
</ol>
<div><br>
</div>
<div>I look forward to speaking with everyone and
having an exciting conversation!</div>
<div><br>
</div>
<div>Kind regards,</div>
<div><br>
</div>
<div>Michael Flemming</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gnso-newgtld-wg-wt2 mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Gnso-newgtld-wg-wt2@icann.org">Gnso-newgtld-wg-wt2@icann.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt2">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt2</a></pre>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>