<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>I think Jon raises an important point. The recommendations of the
STI (as adopted by the GNSO Council and the ICANN Board) were for
the New gTLD Registry to choose between a Sunrise Period OR the 90
day TM Claims Notice -- "at registry discretion" (as Jon notes
below).</p>
<p>Is this something we should make a note to review -- and
accordingly pass on as a question to the Sunrise Period and TM
Claims Subgroups: is the right conjunction "or" or "and"? Should
we return to the policy of allowing registries to choose Sunrise
Period OR TM Claims for their roll-outs and would that provide a
more balanced set of protections? <i>Not a question to be
debated now, </i>but one we might to queue up for the
discussions ahead. <br>
</p>
<p>(Cue the music for Conjunction Junction from Schoolhouse Rock for
those from that generation...)</p>
<p>Best, Kathy<br>
</p>
<br>
<div class="moz-cite-prefix">On 4/6/2017 3:46 PM, Jon Nevett wrote:<br>
</div>
<blockquote
cite="mid:86211037-7869-4672-AD7B-4B82E786D8E4@donuts.email"
type="cite">
<pre wrap="">Michael, This is very helpful perspective. The 2012 round was supposed to require either sunrise or claims at registry discretion. Late in the process, ICANN staff changed it to require both sunrise and claims. Based on your email and your IP perspective, is it fair to assume that sunrise is the much more important RPM between the two? Thanks. Jon
</pre>
<blockquote type="cite">
<pre wrap="">On Apr 6, 2017, at 2:56 PM, Michael Graham (ELCA) <a class="moz-txt-link-rfc2396E" href="mailto:migraham@expedia.com"><migraham@expedia.com></a> wrote:
>From my point of view as a) an IP attorney generally and b) in-house counsel for Expedia, Inc., Sunrise is an essential part of the RPMs in order to ensure that the New gTLD program will provide the benefits it was intended to provide (Increasing Consumer Choice, Consumer Trust and Competition on the Internet) without unduly burdening either individuals or entities, or threatening any of their rights (be they privacy or intellectual property or expression). In regard to the use of Sunrise "preemption" by trademark owners, as indicated in the TMCH study, it is being used in a more limited manner than many presumed would be the case. Contrary to George's fears, for example, it seems clear from the study that Sunrise is not being used by trademark owners to monopolize generic terms. Nor is there any empirical evidence that it has had any negative effect on non-trademark owner registrants or applicants.
As to points 1 and 2:
1: We have learned that there are sufficient numbers of either bad or uninformed (i.e. do not take the time to search to determine whether a term is a registered trademark) actors that we cannot rely on their declaration, and
2: Despite the success of the UDRP, forcing trademark owners to rely on UDRPs alone is a costly, time-consuming process that fails to satisfy the New gTLD program's charter -- it does not further any of the goals of the New gTLD system.
In considering RPMs and the Application/Registration/DNS itself I think we need to always step back to consider: who benefits from and who is burdened by the various RPMs or their lack, and what is the cost and benefit to users/registrants/society. I raise this because it seems to me that personal profit motives have too often distorted and should not play as large a role in policy decisions as other types of considerations should.
Michael R. Graham
MICHAEL R. GRAHAM
SENIOR CORPORATE COUNSEL
GLOBAL DIRECTOR, INTELLECTUAL PROPERTY
Expedia Legal & Corporate Affairs
T +1 425.679.4330 | F +1 425.679.7251
M +1 425.241.1459
Expedia, Inc.
333 108th Avenue NE | Bellevue | WA 98004
<a class="moz-txt-link-abbreviated" href="mailto:MiGraham@Expedia.com">MiGraham@Expedia.com</a>
-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:gnso-rpm-wg-bounces@icann.org">gnso-rpm-wg-bounces@icann.org</a> [<a class="moz-txt-link-freetext" href="mailto:gnso-rpm-wg-bounces@icann.org">mailto:gnso-rpm-wg-bounces@icann.org</a>] On Behalf Of George Kirikos
Sent: Thursday, April 06, 2017 11:21 AM
To: <a class="moz-txt-link-abbreviated" href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a>
Subject: Re: [gnso-rpm-wg] Action Items, Slides and Notes from the Working Group call held earlier today
Hi folks,
On Thu, Apr 6, 2017 at 11:55 AM, J. Scott Evans <a class="moz-txt-link-rfc2396E" href="mailto:jsevans@adobe.com"><jsevans@adobe.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Let’s all pause here. It seems that George and those in his “camp” believe that (and feel free to correct me if I am wrong) that Sunrise is not balanced (or “unfair”) because it gives the owner of a trademark a preemptive veto to us of the domain, even for non-infringing uses. If that is the case, could we not require the registrars to have a policy for allowing a third party with a legitimate use to get the string subject to the Sunrise registration provided they make a case that their use is non-infringing. Of course, any such process would require the third party to agree that if the use became infringing that the owner of the original Sunrise could take back the domain. If we could come up with this type system (which I believe Donuts uses in its DPML system) wouldn’t that get to the root of the concern (that is, provided I have accurately articulated the concern).
</pre>
</blockquote>
<pre wrap="">
We don't have to "come up with this type of system" -- killing the Sunrise period would achieve this *today*, because:
(1) The domain name registration agreement *already* mandates the above. See Section 3.7.7.9 of:
<a class="moz-txt-link-freetext" href="https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en">https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en</a>
"3.7.7.9 The Registered Name Holder shall represent that, to the best of the Registered Name Holder's knowledge and belief, neither the registration of the Registered Name nor the manner in which it is directly or indirectly used infringes the legal rights of any third party."
unless you're suggesting that each prospective registrant needs to provide more than that representation to "make a case" (in your words). Fees for domain name registrations would have to go up considerably, and registrars would need a process to vet who is "worthy" and who is illegitimate, and presumably a challenge/appeal mechanism for that vetting too?
and,
(2) As for "Of course, any such process would require the third party to agree that if the use became infringing that the owner of the original Sunrise could take back the domain" --- we already have something called the UDRP for that, or the courts, which every registrant agrees to as well, so that any TM owner (TMCH recordal or
not) can challenge alleged misuse of a domain name.
Sincerely,
George Kirikos
416-588-0269
<a class="moz-txt-link-freetext" href="http://www.leap.com/">http://www.leap.com/</a>
_______________________________________________
gnso-rpm-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a>
_______________________________________________
gnso-rpm-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gnso-rpm-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a></pre>
</blockquote>
<br>
</body>
</html>