<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Paul,</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">That still doesn't answer the question of who actually wrote the letter. It's clear who signed onto it, but there's no evidence of who wrote it. (And BTW, EFF is not "a scholar.")<br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">As for reading the letter, I don't think anyone was suggesting that it not be read. But there's no reason to give it special consideration either.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><p style="margin:0in 0in 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"></p><div><p style="text-indent:0in"><span style="font-size:12.8px"><a name="UNIQUE_ID_SafeHtmlFilter_UNIQUE_ID_SafeHtmlFilter__GoBack"></a></span><b style="font-size:12.8px"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#002e62">Greg
Shatan<br>
</span></b><span style="font-size:10pt;font-family:Arial,sans-serif;color:black">C: 917-816-6428<br>
S: gsshatan<br>Phone-to-Skype: </span><font color="#000000" face="Arial, sans-serif"><span style="font-size:13.3333px">646-845-9428<br></span></font><a href="mailto:gregshatanipc@gmail.com" style="font-family:Arial,sans-serif;font-size:10pt;text-indent:0in" target="_blank"><span style="color:#1155cc">gregshatanipc@gmail.com</span></a></p><p style="font-size:12.8px;text-indent:0in"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""></span></p></div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Tue, Mar 28, 2017 at 2:48 PM, Paul Keating <span dir="ltr"><<a href="mailto:Paul@law.es" target="_blank">Paul@law.es</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">O please. If I wrote the letter you all should not care a whit. If EFF<br>
and other scholars (all listed) wrote the letter, I ask that we all stand<br>
up and read it.<br>
<br>
On 3/28/17, 6:39 PM, "Kiran Malancharuvil"<br>
<div class="HOEnZb"><div class="h5"><<a href="mailto:Kiran.Malancharuvil@markmonitor.com">Kiran.Malancharuvil@<wbr>markmonitor.com</a>> wrote:<br>
<br>
>With respect Paul, even if I agreed with that characterization, no one is<br>
>"heavier" than anyone else at ICANN.<br>
><br>
>Kiran Malancharuvil<br>
>Policy Counselor<br>
>MarkMonitor<br>
><a href="tel:415-419-9138" value="+14154199138">415-419-9138</a> (m)<br>
><br>
>Sent from my mobile, please excuse any typos.<br>
><br>
>> On Mar 28, 2017, at 10:36 AM, Paul Keating <<a href="mailto:Paul@law.es">Paul@law.es</a>> wrote:<br>
>><br>
>> Well it was written but some relatively heavies in the legal field.<br>
>><br>
>> On 3/28/17, 4:42 PM, "Kiran Malancharuvil via gnso-rpm-wg"<br>
>> <<a href="mailto:gnso-rpm-wg-bounces@icann.org">gnso-rpm-wg-bounces@icann.org</a> on behalf of <a href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a>><br>
>>wrote:<br>
>><br>
>>> Many of the signatories aren't members of the working group. When<br>
>>> input/comment is received by an ICANN working group by outside parties,<br>
>>> the working group often invites those people to attend a meeting to<br>
>>> facilitate the discussion so that there can be meaningful dialogue and<br>
>>>a<br>
>>> better common understanding of the issues raised.<br>
>>><br>
>>> There is a prescribed time in the icann policy development process for<br>
>>> solicitation of comments, as well as review and consideration of public<br>
>>> comment. My question (for staff, to be clear) is why we are considering<br>
>>> this public comment out of turn. Why does it have elevated importance?<br>
>>><br>
>>> Thanks,<br>
>>><br>
>>> Kiran<br>
>>><br>
>>> Kiran Malancharuvil<br>
>>> Policy Counselor<br>
>>> MarkMonitor<br>
>>> <a href="tel:415-419-9138" value="+14154199138">415-419-9138</a> (m)<br>
>>><br>
>>> Sent from my mobile, please excuse any typos.<br>
>>><br>
>>>> On Mar 28, 2017, at 8:33 AM, Rebecca Tushnet<br>
>>>> <<a href="mailto:Rebecca.Tushnet@law.georgetown.edu">Rebecca.Tushnet@law.<wbr>georgetown.edu</a>> wrote:<br>
>>>><br>
>>>> (1) Yes. (2) Invited by whom? (3) It's my understanding that all<br>
>>>> comments should be considered; are you aware of any we're ignoring?<br>
>>>> Rebecca Tushnet<br>
>>>> Georgetown Law<br>
>>>> <a href="tel:703%20593%206759" value="+17035936759">703 593 6759</a><br>
>>>><br>
>>>><br>
>>>> On Tue, Mar 28, 2017 at 11:30 AM, Kiran Malancharuvil via gnso-rpm-wg<br>
>>>> <<a href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a>> wrote:<br>
>>>>> Agree with Jeff.<br>
>>>>><br>
>>>>> Also, are these "trademark scholars" represented in the group? Are<br>
>>>>> they invited in for discussion? Why is this letter any more important<br>
>>>>> than any other public comment?<br>
>>>>><br>
>>>>> Thanks,<br>
>>>>><br>
>>>>> Kiran<br>
>>>>><br>
>>>>> Kiran Malancharuvil<br>
>>>>> Policy Counselor<br>
>>>>> MarkMonitor<br>
>>>>> <a href="tel:415-419-9138" value="+14154199138">415-419-9138</a> (m)<br>
>>>>><br>
>>>>> Sent from my mobile, please excuse any typos.<br>
>>>>><br>
>>>>> On Mar 28, 2017, at 7:54 AM, Jeff Neuman<br>
>>>>> <<a href="mailto:jeff.neuman@comlaude.com">jeff.neuman@comlaude.com</a><<wbr>mailto:<a href="mailto:jeff.neuman@comlaude.com">jeff.neuman@comlaude.<wbr>com</a>>> wrote:<br>
>>>>><br>
>>>>> Thanks Mary.<br>
>>>>><br>
>>>>> Co-Chairs,<br>
>>>>><br>
>>>>> Can I assume that with respect to the EFF letter, the only items we<br>
>>>>> would be discussing from that letter at this point are their comments<br>
>>>>> with respect to design marks and the transparency of the TMCH<br>
>>>>>database?<br>
>>>>><br>
>>>>> I am not saying the other comments are not important, but with<br>
>>>>>respect<br>
>>>>> to this Working Group at this time, we are not yet addressing those<br>
>>>>> other issues.<br>
>>>>><br>
>>>>> I would strongly urge that we not engage yet in the other discussion<br>
>>>>> around the other comments at this point (namely, trademark rights in<br>
>>>>> general), as I think that could lead us down a large rabbit hole and<br>
>>>>> considerably slow down out work.<br>
>>>>><br>
>>>>> Thanks.<br>
>>>>><br>
>>>>> Jeffrey J. Neuman<br>
>>>>> Senior Vice President |Valideus USA | Com Laude USA<br>
>>>>> 1751 Pinnacle Drive, Suite 600<br>
>>>>> Mclean, VA 22102, United States<br>
>>>>> E: <a href="mailto:jeff.neuman@valideus.com">jeff.neuman@valideus.com</a><<wbr>mailto:<a href="mailto:jeff.neuman@valideus.com">jeff.neuman@valideus.<wbr>com</a>> or<br>
>>>>> <a href="mailto:jeff.neuman@comlaude.com">jeff.neuman@comlaude.com</a><<wbr>mailto:<a href="mailto:jeff.neuman@comlaude.com">jeff.neuman@comlaude.<wbr>com</a>><br>
>>>>> T: <a href="tel:%2B1.703.635.7514" value="+17036357514">+1.703.635.7514</a><br>
>>>>> M: <a href="tel:%2B1.202.549.5079" value="+12025495079">+1.202.549.5079</a><br>
>>>>> @Jintlaw<br>
>>>>><br>
>>>>><br>
>>>>> From:<br>
>>>>> <a href="mailto:gnso-rpm-wg-bounces@icann.org">gnso-rpm-wg-bounces@icann.org</a><<wbr>mailto:<a href="mailto:gnso-rpm-wg-bounces@icann.org">gnso-rpm-wg-bounces@<wbr>icann.org</a>><br>
>>>>> [mailto:<a href="mailto:gnso-rpm-wg-bounces@icann.org">gnso-rpm-wg-bounces@<wbr>icann.org</a>] On Behalf Of Mary Wong<br>
>>>>> Sent: Tuesday, March 28, 2017 6:15 AM<br>
>>>>> To: <a href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a><mailto:<a href="mailto:gnso-rpm-wg@icann.org">g<wbr>nso-rpm-wg@icann.org</a>><br>
>>>>> Subject: [gnso-rpm-wg] FOR INFORMATION: Letter from trademark<br>
>>>>>scholars<br>
>>>>> and information on Deloitte Ancillary Services<br>
>>>>><br>
>>>>> Dear all,<br>
>>>>><br>
>>>>> During the ICANN58 Working Group sessions in Copenhagen, the<br>
>>>>>following<br>
>>>>> two matters came up for which staff is now following up with the<br>
>>>>> requested document (for #1) and information (for #2).<br>
>>>>><br>
>>>>> Item #1: Letter of 10 March 2017 from some trademark scholars and<br>
>>>>> practitioners to our Working Group co-chairs expressing concerns with<br>
>>>>> certain aspects of the TMCH:<br>
>>>>><br>
>>>>><a href="https://www.eff.org/files/2017/03/10/tm_scholars_letter_to_icann_final" rel="noreferrer" target="_blank">https://www.eff.org/<wbr>files/2017/03/10/tm_scholars_<wbr>letter_to_icann_final</a><br>
>>>>>.p<br>
>>>>> df.<br>
>>>>><br>
>>>>> Item #2: Question regarding the Ancillary Services that Deloitte is<br>
>>>>> permitted to provide under its Validation Agreement with ICANN,<br>
>>>>>subject<br>
>>>>> to ICANN's authorization.<br>
>>>>><br>
>>>>> Currently, two Ancillary Services have been approved by ICANN:<br>
>>>>><br>
>>>>> 1. Extended Claims Services<br>
>>>>> The extended claims services provide the Trademark Holder or<br>
>>>>>Trademark<br>
>>>>> Agent, as applicable, with an electronic notification when a domain<br>
>>>>> name registered in an Eligible TLD matches one or more of such<br>
>>>>>party's<br>
>>>>> recorded labels with the TMCH. The extended claims services does not<br>
>>>>> include a domain name pre-registration notification (i.e. a<br>
>>>>> notification to the potential registrant of a domain name that the<br>
>>>>> domain name such registrant intends to register matches a label<br>
>>>>> recorded with the Trademark Clearinghouse).<br>
>>>>><br>
>>>>><br>
>>>>> 2. Audit Report<br>
>>>>> Deloitte may offer an audit report service for Trademark Holders and<br>
>>>>> Trademark Agents with active Trademark Records recorded in the<br>
>>>>> Trademark Clearinghouse. Such audit reports shall consist primarily<br>
>>>>>of<br>
>>>>> a listing of matches between their recorded labels within the<br>
>>>>>Trademark<br>
>>>>> Clearinghouse and domain names registered in an Eligible TLD.<br>
>>>>><br>
>>>>> FYI, Deloitte's contract with ICANN is for an initial period expiring<br>
>>>>> on the fifth anniversary of ICANN's entry into a Registry Agreement<br>
>>>>> under the New gTLD Program, with consecutive one-year renewals<br>
>>>>> thereafter. Although Deloitte currently serves as the sole TMCH<br>
>>>>> validator, ICANN may appoint additional validators once ten Qualified<br>
>>>>> Sunrise Periods have been completed under the New gTLD Program.<br>
>>>>><br>
>>>>> Thanks and cheers<br>
>>>>> Mary<br>
>>>>> ______________________________<wbr>_________________<br>
>>>>> gnso-rpm-wg mailing list<br>
>>>>> <a href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a><mailto:<a href="mailto:gnso-rpm-wg@icann.org">g<wbr>nso-rpm-wg@icann.org</a>><br>
>>>>> <a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rpm-wg</a><br>
>>>>> ______________________________<wbr>_________________<br>
>>>>> gnso-rpm-wg mailing list<br>
>>>>> <a href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a><br>
>>>>> <a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rpm-wg</a><br>
>>> ______________________________<wbr>_________________<br>
>>> gnso-rpm-wg mailing list<br>
>>> <a href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a><br>
>>> <a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rpm-wg</a><br>
>><br>
>><br>
<br>
<br>
______________________________<wbr>_________________<br>
gnso-rpm-wg mailing list<br>
<a href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rpm-wg</a><br>
</div></div></blockquote></div><br></div>