<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1448965151;
mso-list-type:hybrid;
mso-list-template-ids:-1482765106 -1242774356 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:12.0pt;
font-family:"Times New Roman",serif;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">As a member of the WS2 Jurisdiction subgroup’s Questionnaire-Response Review and Evaluation team, I submit this analysis of the response from Rita Forsi, Director General of the Ministry of Economic Development of Italy, and Italian GAC
Representative (the “Forsi Response”).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The questionnaire can be seen <a href="https://community.icann.org/display/WEIA/Jurisdiction+Questionnaire">
here</a>.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The Forsi Response can be seen <a href="http://mm.icann.org/pipermail/ccwg-acctws2.jurisdiction.questionnaire/attachments/20170417/dc270ba8/20170413-ICANNJurisdiction_Italy.pdf">
here</a>.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The Forsi Response provided commentary in reply to questions 1, 2, and 4.b. Those questions and the Forsi Response answers are also pasted in at the bottom of this email.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>Reviewer’s Note: <o:p></o:p></b></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal">Consistent with my input in other workgroups, this analysis is my personal assessment and does not represent the views of my employer, Verisign, Inc., in any way.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>The Forsi Response <o:p></o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">With respect to Question 1., the Forsi Response states that Italy was directly involved in the so-called “dot wine” issue. It says that domain names which consist, contain or unduly evoke Geographical Indications (GI’s) can easily be registered
and used in a deceptive manner. And it says that this is because, in line with the American approach to GIs, they have not been accorded consistent protection as they would be if they fell under international treaties such as TRIPS and the Lisbon Agreement
for the Protection of Appellations of Origin and their International Registration.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The handling of the “dot wine” issue provides a good example of how U.S. jurisdiction of ICANN affected Italian business, the Forsi Response concludes. It posits this link between U.S. jurisdiction and ICANN’s conduct:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in">“The <i>de facto</i> non-recognition of GIs by US, and consequently by ICANN for example in its Registry Agreement and Uniform Domain Name Dispute Resolution Policy (UDRP), caused almost two years of intense debate
…” <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">With respect to Question 2., the Forsi Response notes that Italy filed two Reconsideration Requests over the “dot wine” issue and both were rejected. [One RR is dated April 9, 2014, and can be seen
<a href="https://www.icann.org/en/system/files/files/request-italian-government-09apr14-en.pdf">
here</a> – ICANN’s summary page of that RR is <a href="https://www.icann.org/resources/pages/14-19-2014-04-09-en">
here</a>; the other RR is dated April 18, 2014, and can be seen <a href="https://www.icann.org/en/system/files/files/request-italian-government-18apr14-en.pdf">
here</a> – ICANN’s summary page of that RR is <a href="https://www.icann.org/resources/pages/14-26-2014-04-18-en">
here</a>.]<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">With respect to Question 4b., the Forsi Response says that conflicts of jurisdiction on the Internet could have implications with respect to the “EU acquis” – for example as regards data protection and GIs. (I am unsure of the precise meaning
of “EU acquis” and considered this <a href="http://eur-lex.europa.eu/summary/glossary/acquis.html">
glossary term</a> as I prepared this analysis.)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The Forsi Response concludes: <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in">“For that reason it is necessary that an Independent third party studies possible conflicts of laws and jurisdictions in relation to the Internet and, on that basis and if warranted, consider options for action
in order to prevent these conflicts and to solve them should they occur.”<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>Analysis<o:p></o:p></b></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal">I recommend that each member of the subgroup read the Forsi Response to draw your own conclusions. It is brief and to the point.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The Forsi Response discusses an important issue in the ICANN community – the treatment of GIs within domain names. It is an issue that has challenged the community for some time and remains under debate in various WGs and other community
fora. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">My personal view is that the “dot wine” issue, while important, is a matter of differing points of view within the community rather than an issue implicating jurisdictional considerations. It seems a policy issue, not a legal one.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As I understand it, the issue in this debate concerns the treatment of a generic term as a TLD – in this case, “wine.” The perceived harm to be guarded against would, presumably, be registration of certain domain names at the second or
lower levels. Whether a case can be made to bar or limit the delegation of the TLD to prevent problematic lower-level registrations (e.g., Champage.wine or Toscana.wine), or not to bar nor limit delegation of the TLD because legitimate lower-level registrations
might be available (e.g., table.wine or red.wine), neither seems to me to be a case premised on jurisdiction.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Is it likely that ICANN’s U.S. HQ-jurisdiction led to the complained of treatment of GIs? Or was that outcome attributable instead to the community debate/deliberation/decision process as that process unfolded with respect to new gTLDs
and the Applicant Guidebook? Reasonable people may differ on that but in so doing it seems the debate enters the realm of opinion rather than fact. And as important as opinion is in the policy formation process, our jurisdiction inquiry is a fact-based effort.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">[Of possible note, if disputes should arise over registration of domain names in this regard, ICANN appears to be subject not only to U.S. jurisdiction but also to EU jurisdiction given that it maintains a physical presence in the EU in
an engagement office in Brussels.] <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Finally, the Forsi Response appears to make a link that is debatable: “The
<i>de facto </i>non-recognition of GIs by US, and <u>consequently</u> by ICANN …” (underline emphasis added). I am unaware of any U.S.-based requirement or inducement that would seek to prevent (or even dissuade) a private organization from adopting a policy
of protection toward GIs. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">To be fair, #1 of our questionnaire just asked about being <u>
affected </u>by ICANN’s jurisdiction “in any way.” Even so, any effect here, if such exists, seems remote.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In sum, then, and with respect, I think the Forsi Response makes an important contribution to the debate around geo-indications and domain names but is of limited impact in the discussions within our subgroup over jurisdiction.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">David (in personal capacity)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">David McAuley<o:p></o:p></p>
<p class="MsoNormal">Sr International Policy & Business Development Manager<o:p></o:p></p>
<p class="MsoNormal">Verisign Inc.<o:p></o:p></p>
<p class="MsoNormal">703-948-4154<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">--<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Pasted questions (asterisk directing to explanation of “jurisdiction” omitted – available online) and Forsi Response answers (footnotes omitted – available online):<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><b><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></b><![endif]><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Has your business, your privacy or your ability to use or purchase domain name-related services been affected by ICANN's jurisdiction in any way? If the answer is
Yes, please describe specific cases, situations or incidents, including the date, the parties involved, and links to any relevant documents. Please note that “affected” may refer to positive and/or negative effects.<o:p></o:p></span></b></p>
<p class="MsoNormal"><i><o:p> </o:p></i></p>
<p class="MsoNormal" style="text-indent:.5in">Answer:<o:p></o:p></p>
<p class="MsoNormal" style="text-indent:.5in"><i><o:p> </o:p></i></p>
<p class="MsoNormal" style="margin-left:.5in"><i><u>Yes. In 2013-2014 Italy was directly involved in the so-called “.wine issue”.<o:p></o:p></u></i></p>
<p class="MsoNormal" style="margin-left:.5in"><i><o:p> </o:p></i></p>
<p class="MsoNormal" style="margin-left:.5in"><i>Italy and European Union recognize the protection of Geographical Indications (GIs) through a very detailed regulation.
<o:p></o:p></i></p>
<p class="MsoNormal" style="margin-left:.5in"><i><o:p> </o:p></i></p>
<p class="MsoNormal" style="margin-left:.5in"><i>The <u>de facto</u> non-recognition of GIs by US, and consequently by ICANN for example in its Registry Agreement and Uniform Domain Name Dispute Resolution Policy (UDRP), caused almost two years of intense debate
among GAC members (US, Australia and New Zealand against the rest of the GAC), between GAC and the ICANN Board, between Governments and ICANN.<o:p></o:p></i></p>
<p class="MsoNormal" style="margin-left:.5in"><i><o:p> </o:p></i></p>
<p class="MsoNormal" style="margin-left:.5in"><i>In line with the American approach to the GIs, domain names which consist, contains or unduly evoke GIs, have not been accorded consistent protection as those defined in the International Treaty or the European
Regulation. <o:p></o:p></i></p>
<p class="MsoNormal" style="margin-left:.5in"><i><o:p> </o:p></i></p>
<p class="MsoNormal" style="margin-left:.5in"><i>For that reason, such domain names can be easily registered and used in a deceptive manner.
<o:p></o:p></i></p>
<p class="MsoNormal" style="margin-left:.5in"><i>Italy asked for protecting GIs by reserving the registration of their respective domain names to the rightholders, according to the TRIPS provisions, but ICANN was reluctant to impose such safeguards to the candidate
Registries. <o:p></o:p></i></p>
<p class="MsoNormal" style="margin-left:.5in"><i><o:p> </o:p></i></p>
<p class="MsoNormal" style="margin-left:.5in"><i>In the end .wine issue was closed not in a satisfactory but at least acceptable manner for Italian rightholders, but this could serve as a good example to show how the US jurisdiction of ICANN affected the Italian
business.<o:p></o:p></i></p>
<p class="MsoNormal" style="margin-left:.5in"><i><o:p> </o:p></i></p>
<p class="MsoListParagraphCxSpFirst" style="text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><b><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></b><![endif]><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Has ICANN's jurisdiction affected any dispute resolution process or litigation related to domain names you have been involved in?
<o:p></o:p></span></b></p>
<p class="MsoListParagraphCxSpLast"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></b></p>
<p class="MsoNormal" style="margin-left:.5in"><b>If the answer is Yes, please describe specific cases, situations or incidents, including the date, the parties involved, and links to any relevant documents. Please note that “affected” may refer to positive
and/or negative effects.<o:p></o:p></b></p>
<p class="MsoNormal" style="margin-left:.5in"><b><o:p> </o:p></b></p>
<p class="MsoNormal" style="text-indent:.5in">Answer:<o:p></o:p></p>
<p class="MsoNormal" style="text-indent:.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><i>Yes, for the .wine issue, Italy filed two Reconsideration Requests, one of which was signed by the then Minister of Economic Development, Ms. Federica Guidi. Both the Reconsideration Request were rejected
<o:p></o:p></i></p>
<p class="MsoNormal" style="margin-left:.5in"><i><o:p> </o:p></i></p>
<p class="MsoListParagraph"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">4b. Are you aware of and able to document the existence of an alternative jurisdiction where ICANN would not be so prevented from pursuing its Mission? If so, please
provide documentation.<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal" style="text-indent:.5in">Answer:<o:p></o:p></p>
<p class="MsoNormal" style="text-indent:.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><i>In general, conflicts of jurisdiction on the Internet might have implications with respect to the “EU acquis”, e.g. as regards data protection and geographical indications;<o:p></o:p></i></p>
<p class="MsoNormal" style="margin-left:.5in"><i><o:p> </o:p></i></p>
<p class="MsoNormal" style="margin-left:.5in"><i>For that reason it is necessary that an Independent third party studies possible conflicts of laws and jurisdictions in relation to the Internet and, on that basis and if warranted, consider options for action
in order to prevent these conflicts and to solve them should they occur.<o:p></o:p></i></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>