<span style="font-family: 'Lucida Sans Unicode','Lucida Grande',Sans-Serif; font-size: 14px"><div> </div>
<div>
<div><span style="font-family:lucida sans unicode,lucida grande,sans-serif;"><span style="font-size:14px;">Hi John,</span></span></div>
<div> </div>
<div><span style="font-family:lucida sans unicode,lucida grande,sans-serif;"><span style="font-size:14px;">Thanks for your contribution.</span></span></div>
<div> </div>
<div><span style="font-family:lucida sans unicode,lucida grande,sans-serif;"><span style="font-size:14px;">If we were talking about the process of how a trade marked word becomes generic, genericide if you will, or, for example, in Europe application of article 20 of the new Trademark Directive (Directive (EU) 2015 /2436), I would agree completely with you that a complicated legal analysis is called for. That simply is not the case here.</span></span></div>
<div> </div>
<div><span style="font-family:lucida sans unicode,lucida grande,sans-serif;"><span style="font-size:14px;">There is nothing mysterious or confusing about the definition of a generic word – every schoolchild knows the nouns they use every day such as truck, car, desk, book. The US Trademark Office even defines generic terms as what the <strong>public </strong>(not what a trade mark examiner or solicitor) understands them to be:</span></span></div>
<div><span style="font-family:lucida sans unicode,lucida grande,sans-serif;"><span style="font-size:14px;"> </span></span></div>
<div><span style="font-family:lucida sans unicode,lucida grande,sans-serif;"><span style="font-size:14px;"> US Patent and Trademark Office (USPTO) Glossary</span></span></div>
<div> </div>
<div><span style="font-family:lucida sans unicode,lucida grande,sans-serif;"><span style="font-size:14px;">generic term:</span></span></div>
<div> </div>
<div><span style="font-family:lucida sans unicode,lucida grande,sans-serif;"><span style="font-size:14px;">“terms that the relevant purchasing public understands primarily as the common or class name for the goods or services."</span></span></div>
<div> </div>
<div><font face="lucida sans unicode, lucida grande, sans-serif">These terms are simply incapable of functioning as trade marks denoting source in any jurisdiction I am aware of, and are not even registrable, for example, in the United States on the Principal Register under §2(f) or on the Supplemental Register. Illustrative examples include: CLASSES ONLINE for classes provided via the Internet, PIZZA.COM for pizza ordering and delivery services, and LIVE PLANTS for plant nurseries.” </font><a href="https://www.uspto.gov/learning-and-resources/glossary#sec-g" style="font-family: 'lucida sans unicode', 'lucida grande', sans-serif; font-size: 14px;">https://www.uspto.gov/learning-and-resources/glossary#sec-g</a></div>
<div> </div>
<div><span style="font-family:lucida sans unicode,lucida grande,sans-serif;"><span style="font-size:14px;">The INTA teaches the same “common knowledge” approach as the USPTO:</span></span></div>
<div> </div>
<div><span style="font-family:lucida sans unicode,lucida grande,sans-serif;"><span style="font-size:14px;">“Generic words can be thought of as the <em>common name of the problem or service in question – for example, “clock” is a generic word for timepieces.” </em> Because these are the <em>common names of goods and services, </em>the first rule of trade mark law is that “[s]uch words can never be appropriated by a single party as a trademark for the products and services they signify” ((from the INTA publication quoted below in the e-mail that started this thread).</span></span></div>
<div> </div>
<div><span style="font-family:lucida sans unicode,lucida grande,sans-serif;"><span style="font-size:14px;">The question our working group has been asked in its Charter is whether the TMCH Database and RPM Mechanisms are protecting a trade mark far beyond its category of goods and services. Are we perhaps creating processes that may remove the registration of domain names for generic words from domain name registrants? That seems a very valid question to ask with very important implications for our work.</span></span></div>
<div> </div>
<div><span style="font-family:lucida sans unicode,lucida grande,sans-serif;"><span style="font-size:14px;">As Kathy Kleiman pointed out in her post to this group of September 29th, there may even be free expression aspects to this issue. In responding to J. Scott’s raising of this issue she wrote:</span></span></div>
<div> </div>
<div><span style="font-family:lucida sans unicode,lucida grande,sans-serif;"><span style="font-size:14px;">“When basic words of political discourse such as FREEDOM (USPTO IC 028 Mounts and mounting devices adapted for use with suspended physical fitness equipment. Reg No. 5042693), LIBERTY (USPTO IC 009 Hearing muffs, namely, sound amplifiers. Reg No. 4793635), and TRUST (USPTO IC 028. In-line skate liners. Reg No. 4301142) are used as trademarks, but also play an integral role in the fabric of political dialogue, we have a Free Expression issue and concern before us.”</span></span></div>
<div> </div>
<div><span style="font-family:lucida sans unicode,lucida grande,sans-serif;"><span style="font-size:14px;">What happens if Registrants can’t register these words for the free expression uses to which they are most directly (and generically) directed and applied to?</span></span></div>
<div> </div>
<div><span style="font-family:lucida sans unicode,lucida grande,sans-serif;"><span style="font-size:14px;">Throwing “generic” out of the question seems, well, rather out of the question. It is a basic and understood term and it would be unfair to the group(s) that posed these questions, and to those of us on the GNSO Council who saw fit to send to these queries to this working group in the Charter itself, to exclude this line of inquiry. It seems to me that if we don’t want to inappropriately expand trademark protection, as Luc has pointed out, we really need to include this question as we move forward.</span></span></div>
<div> </div>
<div><span style="font-family:lucida sans unicode,lucida grande,sans-serif;"><span style="font-size:14px;">John, I do recognize that the wording itself may not be perfect. Perhaps you could offer a rephrasing the keeps the powerful and valid intent of the question with wording you might be more comfortable with.</span></span></div>
<div> </div>
<div><span style="font-family:lucida sans unicode,lucida grande,sans-serif;"><span style="font-size:14px;">Thanks for considering.</span></span></div>
<div> </div>
<div><span style="font-family:lucida sans unicode,lucida grande,sans-serif;"><span style="font-size:14px;">Kind Regards,</span></span></div>
<div> </div>
<div><span style="font-family:lucida sans unicode,lucida grande,sans-serif;"><span style="font-size:14px;">Edward Morris</span></span></div>
<div> </div>
</div>
<div> </div>
<div> </div>
<hr align="center" size="2" width="100%" />
<div><span style="font-family: tahoma,arial,sans-serif; font-size: 10pt;"><b>From</b>: "John McElwaine" <john.mcelwaine@nelsonmullins.com><br />
<b>Sent</b>: Tuesday, December 6, 2016 2:51 PM<br />
<b>To</b>: "David Tait" <david.tait@icann.org>, "gnso-rpm-wg@icann.org" <gnso-rpm-wg@icann.org><br />
<b>Subject</b>: Re: [gnso-rpm-wg] FW: Updated TMCH Charter Questions tabulated categories document - 2 December 2016</span>
<div> </div>
<style type="text/css"><!--
/* Font Definitions */
@font-face
{font-family:Courier;
panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
{font-family:Courier;
panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoFootnoteText, li.MsoFootnoteText, div.MsoFootnoteText
{mso-style-priority:99;
mso-style-link:"Footnote Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Calibri","sans-serif";}
span.MsoFootnoteReference
{mso-style-priority:99;
vertical-align:super;}
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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Courier;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.FootnoteTextChar
{mso-style-name:"Footnote Text Char";
mso-style-priority:99;
mso-style-link:"Footnote Text";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
/* Page Definitions */
@page
{mso-endnote-separator:url("cid:header.htm\@01D24FA5.F18CF270") es;
mso-endnote-continuation-separator:url("cid:header.htm\@01D24FA5.F18CF270") ecs;}
@page WordSection1
{size:595.0pt 842.0pt;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->
</style>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The point that Kiran is making is that words such as “generic” mean something. While it is possible to have a dictionary term as a domain name or mark, it is not possible to have a domain name or mark that is generic, solely because it can be found in the dictionary. An extra step of analysis and investigation is required, which is likely outside the scope of this Working Group’s remit and capabilities and outside the remit and capabilities of the TMCH.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Legally speaking, generic terms are words that the relevant purchasing public understands primarily as the common or class name for the goods or services. Applying United States trademark law, determining whether a mark is generic requires the finder of fact to examine (1) the genus of the goods or services at issue; and (2) whether the relevant public understands the applicant's mark/designation <u>primarily</u> to refer to that genus of services. <i>H. Marvin Ginn Corp. v. International Ass’n of Fire Chiefs, Inc.</i>, 782 F.2d 987, 228 U.S.P.Q. 528, 530 (Fed. Cir. 1986). </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">So to determine whether a mark is considered "generic" there must be an initial analysis of whether the mark is a word that is a genus of a quality, feature, function, or characteristic, but of what? In order to answer the rest of the question, we would be forced to look at the goods or services claimed in the registration or the content and/or stated mission and purpose of the domain name, to make a determination of genericness. Complicating things, this analysis is not a bright line analysis and there are several nuances to the relatively straight-forward test set forth above. For instance, a word that has been used on a wide range of different types of products or services that are not within the same species may be less likely to be considered generic. <i>See 2 J. Thomas McCarthy, McCarthy on Trademarks and Unfair Competition</i> § 12:23 (4th ed. 2009). Moreover, a proper analysis requires an in-depth factual investigation of the relevant public's understanding of the alleged generic term.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">As we have discussed on our calls, it is important to be precise in our terminology and for the reasons set forth above, I think we should remove the term “generic” from our discussions relating to the TMCH and dictionary terms. It would be a large (that may be an understatement) undertaking for this Working Group or the TMCH to make an accurate determination of whether a mark in the TMCH is generic or whether a domain name registrant (with a mark in the TMCH) intends to use it in a manner that would be considered generic.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks,</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">John</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> gnso-rpm-wg-bounces@icann.org [mailto:gnso-rpm-wg-bounces@icann.org] <b>On Behalf Of </b>David Tait<br />
<b>Sent:</b> Tuesday, December 06, 2016 5:54 AM<br />
<b>To:</b> gnso-rpm-wg@icann.org<br />
<b>Subject:</b> [gnso-rpm-wg] FW: Updated TMCH Charter Questions tabulated categories document - 2 December 2016</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Dear All</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">At Kathy Kleiman’s request, and to facilitate discussion of this, issue staff is circulating the email below to the full Working Group.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Kind regards,<br />
<br />
David</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:"Calibri","sans-serif";color:black">From: </span></b><span style="font-family:"Calibri","sans-serif";color:black">Kathy Kleiman <<a href="mailto:kathy@kathykleiman.com">kathy@kathykleiman.com</a>><br />
<b>Date: </b>Sunday, 4 December 2016 at 19:40<br />
<b>To: </b>Kiran Malancharuvil <<a href="mailto:Kiran.Malancharuvil@markmonitor.com">Kiran.Malancharuvil@markmonitor.com</a>>, David Tait <<a href="mailto:david.tait@icann.org">david.tait@icann.org</a>><br />
<b>Cc: </b>Mary Wong <<a href="mailto:mary.wong@icann.org">mary.wong@icann.org</a>>, Susan Payne <<a href="mailto:susan.payne@valideus.com">susan.payne@valideus.com</a>>, Edward Morris <<a href="mailto:edward.morris@alumni.usc.edu">edward.morris@alumni.usc.edu</a>>, Phil Corwin <<a href="mailto:psc@vlaw-dc.com">psc@vlaw-dc.com</a>>, "<a href="mailto:Sarahliannec@gmail.com">Sarahliannec@gmail.com</a>" <<a href="mailto:Sarahliannec@gmail.com">Sarahliannec@gmail.com</a>>, Paul Keating <<a href="mailto:paul@law.es">paul@law.es</a>>, "<a href="mailto:kurt@kjpritz.com">kurt@kjpritz.com</a>" <<a href="mailto:kurt@kjpritz.com">kurt@kjpritz.com</a>>, "<a href="mailto:gpmgroup@gmail.com">gpmgroup@gmail.com</a>" <<a href="mailto:gpmgroup@gmail.com">gpmgroup@gmail.com</a>>, "Vaibhav Aggarwal, Group CEO & Founder" <<a href="mailto:va@bladebrains.com">va@bladebrains.com</a>>, Sarah Clayton <<a href="mailto:Sarahliannec@gmail.com">Sarahliannec@gmail.com</a>><br />
<b>Subject: </b>Re: Updated TMCH Charter Questions tabulated categories document - 2 December 2016</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<p>I don't think anyone understood why it was legally inappropriate, Kiran. You referenced a discussion that took place a long time ago, and after which there was considerable discussion and disagreement online. </p>
<p>One major reference for the definition of "generic words" used in this question is the International Trademark Association. It's Fact Sheet on Trademark Strength references generic words and instructs:</p>
<p> => <strong>"Generic Words</strong>: A generic word or phrase is so inherently descriptive of a product or service or an entire class of products or services as to be incapable of ever functioning as a trademark. Generic words can be thought of as the common name of the product or service in question—for example, “clock” is a generic word for timepieces. Such words can never be appropriated by a single party as trademarks for the products or services they signify, since the public perceives and uses them solely as common nouns or terms. Generic words or phrases are not registrable or protectable in relation to the products or services they signify." <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.inta.org_TrademarkBasics_FactSheets_Pages_TrademarkStrengthFactSheet.aspx&d=DgMD-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KScfcqapcv0bzf6fXXUcv9ZJuEfDd3nQD1q6n87CfSA&m=zOLVsOmd1IUv-5M_9bsSfzw8tV61pLQgKc9fMl-Vz2c&s=KwlcAsU7w69ItoPjM20ttgmU4Grr51Qb3RqKsrNZTpY&e="> http://www.inta.org/TrademarkBasics/FactSheets/Pages/TrademarkStrengthFactSheet.aspx[inta.org]</a></p>
<p>So the question of whether, through the TMCH Database or its associated Rights Protection Mechanisms, is granting protection to a trademark, which also happens to be a generic word (see INTA above), beyond its categories of goods and services is a fair one.</p>
<p>Besides, there were numerous charter questions on this issue. We can't simply delete it. But if you would like to offer a clearer way to phrase the question, please do.</p>
<p>Best, Kathy</p>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">On 12/4/2016 12:54 PM, Kiran Malancharuvil wrote:</p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>
Hi David,</pre>
<pre>
</pre>
<pre>
I wasn't able to attend the call on Friday. Can you please explain why Question 10 was marked green for accepted with legally inappropriate terminology?</pre>
<pre>
</pre>
<pre>
Thanks,</pre>
<pre>
</pre>
<pre>
Kiran</pre>
<pre>
</pre>
<pre>
Kiran Malancharuvil</pre>
<pre>
Policy Counselor</pre>
<pre>
MarkMonitor</pre>
<pre>
415-419-9138 (m)</pre>
<pre>
</pre>
<pre>
Sent from my mobile, please excuse any typos.</pre>
<pre>
</pre>
<pre>
On Dec 4, 2016, at 9:26 AM, David Tait <<a href="mailto:david.tait@icann.org">david.tait@icann.org</a><a href="mailto:david.tait@icann.org"><mailto:david.tait@icann.org></a>> wrote:</pre>
<pre>
</pre>
<pre>
Dear All</pre>
<pre>
</pre>
<pre>
Following our call on Friday I am pleased to enclose the notes and outcomes from the meeting. Alongside these notes I attach an appropriately updated version of the TMCH Charter Questions document.</pre>
<pre>
</pre>
<pre>
The notes and outcomes are as follows:</pre>
<pre>
</pre>
<pre>
</pre>
<pre>
* Q10 - Should be marked green for accepted.</pre>
<pre>
</pre>
<pre>
</pre>
<pre>
* Q13 and 14- Proposal to merge Q13+14: "How accessible is the TMCH database and RPM Rights Protection Actions and Defenses to individuals, orgs, trademark owners and trademark agents in developing countries?"</pre>
<pre>
</pre>
<pre>
Proposal to keep question in but report findings to SubPro WG.</pre>
<pre>
</pre>
<pre>
</pre>
<pre>
* Q15- (now question 14 in latest draft) Revision agreed to "What concerns are being raised about the TMCH being closed, what are the reasons for having/keeping the TMCH Database private, and should the TMCH Database remain closed or become open?"</pre>
<pre>
</pre>
<pre>
</pre>
<pre>
* Q16- (now question 15 in latest draft) Proposal 1 "Does the present structuring of the TMCH optimize such operational considerations as cost, reliability, global reach, and service diversity and consistency, or should significant changes be considered?"</pre>
<pre>
</pre>
<pre>
Proposal 2 "What are the concerns with the TMCH Database being provided by a single Provider - and how might those concerns be addressed?"</pre>
<pre>
Both proposals to go to the Working Group.</pre>
<pre>
</pre>
<pre>
Should there be regional service desks if not regional providers?</pre>
<pre>
</pre>
<pre>
</pre>
<pre>
* Q17- (now question 16 in latest draft) Agreed revision: "Are the costs and benefits of the TMCH, for rights holders, for ICANN, for the community, proportionate?"</pre>
<pre>
</pre>
<pre>
</pre>
<pre>
I would also note that further to Mary Wong's email of 1 December 2016 we will now proceed to circulate this updated document to the full Working Group in advance of the next Working Group call on Wednesday. Additionally, we will note that the Sub-Team is expressly seeking the input of the full Working Group on the alternative formulations of Question 16 (this being the only outstanding question not agreed by the Sub-Team).</pre>
<pre>
</pre>
<pre>
Kind regards,</pre>
<pre>
</pre>
<pre>
David</pre>
<pre>
</pre>
<pre>
David A. Tait</pre>
<pre>
Policy Specialist (Solicitor qualified in Scotland, non-practicing)</pre>
<pre>
Internet Corporation for Assigned Names and Numbers (ICANN)</pre>
<pre>
</pre>
<pre>
Mobile: + 44-7864-793776</pre>
<pre>
Email: <a href="mailto:david.tait@icann.org">david.tait@icann.org</a><a href="mailto:david.tait@icann.org"><mailto:david.tait@icann.org></a></pre>
<pre>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org&d=DgMD-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KScfcqapcv0bzf6fXXUcv9ZJuEfDd3nQD1q6n87CfSA&m=zOLVsOmd1IUv-5M_9bsSfzw8tV61pLQgKc9fMl-Vz2c&s=JiMM6ztBpVOPYcTce-_P6-PVpsHNDiiwx9rqfKCTHiE&e=">www.icann.org[icann.org]</a><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org&d=DgMD-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KScfcqapcv0bzf6fXXUcv9ZJuEfDd3nQD1q6n87CfSA&m=zOLVsOmd1IUv-5M_9bsSfzw8tV61pLQgKc9fMl-Vz2c&s=JiMM6ztBpVOPYcTce-_P6-PVpsHNDiiwx9rqfKCTHiE&e="><http://www.icann.org>[icann.org]</a></pre>
<pre>
</pre>
<pre>
<Tabulated Categories - TMCH Questions 2 Dec 2016.docx></pre>
</blockquote>
<p class="MsoNormal" style="margin-bottom:12.0pt"> </p>
</div>
<p>Confidentiality Notice</p>
<p>This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged, confidential or otherwise legally exempt from disclosure.</p>
<p>If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately either by phone (800-237-2000) or reply to this e-mail and delete all copies of this message.</p>
</div></span>