<div dir="ltr">For what it's worth....<div><br></div><div>There are people on ALAC who have seen explicit attempts by fraudsters to exploit red-cross-name domains to solicit fake charitable funds from unsuspecting people. Not only is there no problem within At-Large with doing "backflips" for the Red Cross, arguably protection of its names will lead to less *actual* end-user harm than most potential infringements in the commercial world.</div>
<div><br></div><div>There was IMO substantial progress and good news from the Board action, in that it separated protection for the Red Cross and International Olympic Committee, two cases which the GAC has repeatedly lumped together. The IOC was extremely aggressive in its participation in the Working Group formed to address the issue. The ALAC had fought hard to de-link the RC and IOC and I'm happy that the Board has chosen not to treat the two identically as the GAC had requested. The two are VERY different when it comes to public protection and fraud avoidance.</div>
<div><br></div><div>Anyway... I am writing here just as suggestion to perhaps cut the Red Cross a little slack. Its own internal politics notwithstanding, it is unarguably an extraordinary organization, that has a substantial public-facing presence and actively solicits charitable funds. Its names are very vulnerable to abuse, and its presence in short-term emergency events makes it especially exposed to quickly done exploitive registrations (ie, <a href="http://redcrosshaitistormrelief.com">redcrosshaitistormrelief.com</a>).</div>
<div><br></div><div>While there is much reason to be concerned in the over-reaching of name protection within ICANN, I think this is an instance -- maybe one of the very few -- where protection can provide real public benefit.</div>
<div><br></div><div>- Evan</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 19 June 2014 11:20, Robin Gross <span dir="ltr"><<a href="mailto:robin@ipjustice.org" target="_blank">robin@ipjustice.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">I am also VERY concerned about this latest attempt to change GNSO policy and expand trademark privileges even further post hoc. How many backflips is ICANN supposed to do for the Red Cross? How much community time and energy is spent on creating special privileges for these special interests. Just imagine if all this energy and resources could actually be put toward something worthwhile.<span class="HOEnZb"><font color="#888888"><div>
<br></div></font></span><div><span class="HOEnZb"><font color="#888888">Robin</font></span><div><div class="h5"><br><div><br><div><div>On Jun 17, 2014, at 5:33 AM, Kathy Kleiman wrote:</div><br><blockquote type="cite">
<div bgcolor="#FFFFFF" text="#000000">
<div>To NCSG Councilors,<br>
This is interesting as it expands the Trademark Clearinghouse in
ways that it was never intended to be expanded. As you know, the
TMCH was a narrow mechanism - to give trademark owners with a
clear, registered trademark, a place to put it.<br>
<br>
As these IGO names go into the Trademark Clearinghouse, we (NCSG
reps in the GNSO Council) must require them to have some sort of <u><b>description
of their purpose </b></u>-- something equivalent to the
"description of goods and services" of a trademark. Because of
these descriptions of goods and services, trademarks are limited,
and trademarks such as Delta Faucets, Delta Airlines and future
Deltas can co-exist.<br>
<br>
But here it appears we are being asked to protect the IGO acronym
in the abstract - some sort of protection of mere letters -- an
absolute ownership of characters. But that can't be right - as the
WHO (World Health Organization) coexists with The WHO (the rock
and roll group). <br>
<br>
Please remind everyone that the TMCH registrations are a basis for
URS proceedings (the ultra-fast uniform rapid suspension of New
gTLD domain names). So without descriptions, the World Health
Organization will come to own the string "WHO" with no bounds, no
limits, and an almost absolute ability to pull it from anyone else
using the string (including other noncommercial organizations
sharing these common 3-letter acronyms in completely different
areas of operation).<br>
<br>
Even IGOs have bounds and limits - and a clear description of the
areas and communities they serve. This needs to be added to the
requirements if these terms are to be added into the TMCH
database. <br>
<br>
<i><b>What is the deadline here, and how can we work together
(Councilors and those in NCSG who helped design (and limit)
the TMCH) to help define and further limit this new IGO
registration? </b></i><br>
<br>
Best,<br>
Kathy:<br>
</div>
<blockquote type="cite">
<pre>
-------- Original Message --------
Subject: [council] FW: Letter from Cherine Chalaby
Date: Mon, 16 Jun 2014 22:11:04 +0100
From: Jonathan Robinson <a href="mailto:jrobinson@afilias.info" target="_blank"><jrobinson@afilias.info></a>
Reply-To: <a href="mailto:jrobinson@afilias.info" target="_blank"><jrobinson@afilias.info></a>
Organization: Afilias
To: <a href="mailto:council@gnso.icann.org" target="_blank"><council@gnso.icann.org></a>
All,
FYI and for further discussion / follow-up.
Jonathan
*From:*Megan Bishop [<a href="mailto:megan.bishop@icann.org" target="_blank">mailto:megan.bishop@icann.org</a>]
*Sent:* 16 June 2014 21:09
*To:* <a href="mailto:jonathan.robinson@ipracon.com" target="_blank">jonathan.robinson@ipracon.com</a>
*Subject:* Letter from Cherine Chalaby
Dear Jonathan,
Attached please find a letter from Cherine Chalaby, providing an update
on the ongoing work by the NGPC in response to the GNSO policy
recommendations regarding Protection of IGO-INGO identifiers.
Regards,
Megan
Megan Bishop
Board Support Coordinator
Internet Corporation for Assigned Names and Numbers (ICANN)
12025 Waterfront Dr., Suite 300
Los Angeles, CA 90094
Mobile: <a href="tel:%2B1-310-795-1894" value="+13107951894" target="_blank">+1-310-795-1894</a>
Direct: <a href="tel:%2B1-310-301-5808" value="+13103015808" target="_blank">+1-310-301-5808</a>
/One World. One Internet./
</pre>
</blockquote>
<br>
<br><br>
<hr style="border:none;color:#909090;background-color:#b0b0b0;min-height:1px;width:99%">
<table style="border-collapse:collapse;border:none">
<tbody><tr>
<td style="border:none;padding:0px 15px 0px 8px">
<a href="http://www.avast.com/" target="_blank">
<img border="0" src="http://static.avast.com/emails/avast-mail-stamp.png">
</a>
</td>
<td><p style="color:#3d4d5a;font-family:"Calibri","Verdana","Arial","Helvetica";font-size:12pt">
This email is free from viruses and malware because <a href="http://www.avast.com/" target="_blank">avast! Antivirus</a> protection is active.
</p>
</td>
</tr>
</tbody></table>
<br>
</div>
</blockquote></div><br></div></div></div></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div style="text-align:center"><div style="text-align:left">Evan Leibovitch</div><div style="text-align:left">
Toronto Canada</div></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div style="text-align:center"><div style="text-align:left">Em: evan at telly dot org</div></div><div style="text-align:center"><div style="text-align:left">
Sk: evanleibovitch</div></div><div style="text-align:center"><div style="text-align:left">Tw: el56</div></div></blockquote>
</div>