<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>
<!-- Template generated by Exclaimer Mail Disclaimers on 09:00:40 Tuesday, 29 September 2020 -->
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css">P.ImprintUniqueID {
MARGIN: 0cm 0cm 0pt
}
LI.ImprintUniqueID {
MARGIN: 0cm 0cm 0pt
}
DIV.ImprintUniqueID {
MARGIN: 0cm 0cm 0pt
}
TABLE.ImprintUniqueIDTable {
MARGIN: 0cm 0cm 0pt
}
DIV.Section1 {
page: Section1
}
</style>
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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:12.0pt;
font-family:"Times New Roman",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
{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;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
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;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Times New Roman",serif;
color:black;
font-weight:normal;
font-style:normal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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"><span style="color:black">Thanks Kathy. I was on the STI with you and I remember it quite well. The opening paragraph of the STI report you provided a link to makes it quite clear that the STI was implementation and not Policy:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">“</span>On 12 October 2009, the ICANN Board sent a letter1 to the GNSO requesting its review of the policy implications of certain trademark protection mechanisms proposed for the New gTLD Program, as described
in the Draft Applicant Guidebook and accompanying memoranda. Specifically, the Board Letter requested that the GNSO provide input on whether it approves the proposed staff model, or, in the alternative, the GNSO could propose an alternative that is equivalent
or more effective and implementable.”<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:black">The STI reviewed the already established Policy and the outputs from the IRT and from Staff and tried to select between two implementation models (the IRT’s and the Staff’s) to see which was “</span>more effective
and implementable.” <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So, we can disagree on lots of things in this PDP, but we can’t disagree about actual and knowable facts. The STI was implementation. The PDP proceeding it was Policy.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best,<o:p></o:p></p>
<p class="MsoNormal">Paul<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><img width="883" height="492" style="width:9.2in;height:5.125in" id="Picture_x0020_1" src="cid:image001.png@01D69636.9C1DB000"><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<div></div>
</div>
<br>
<p style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; COLOR: #816d5c"><font color="#97999b"><font size="3">To receive regular COVID-19 updates from Taft, </font><span style="font-family:Arial;font-size:12pt;color:#A22831;font-weight:normal;"><a href="https://www.taftlaw.com/general/subscribe" title="" target="" style="font-family:Arial;font-size:12pt;color:#A22831;font-weight:normal;"><span style="font-family:Arial; font-size:12pt; color:#A22831; font-weight:normal;">subscribe
here</span></a></span><font size="3">. For additional resources, visit Taft's COVID-19
</font><span style="font-size:12pt;color:#A22831;"><a href="https://www.taftlaw.com/general/coronavirus-covid-19-resource-toolkit" title="" target="" style="font-size:12pt;color:#A22831;"><span style="font-size:12pt; color:#A22831;">Resource Toolkit</span></a></span><font size="3">.</font><br>
<br>
This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please
notify the sender by reply e-mail and delete the message and any attachments.</font></p>
<div class="WordSection1">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Kathy Kleiman <kathy@kathykleiman.com>
<br>
<b>Sent:</b> Tuesday, September 29, 2020 7:34 AM<br>
<b>To:</b> McGrady, Paul D. <PMcGrady@taftlaw.com><br>
<b>Cc:</b> gnso-rpm-wg@icann.org; dmcauley@Verisign.com<br>
<b>Subject:</b> RE: [GNSO-RPM-WG] DEADLINE COB 25 Sept - ACTION ITEM: Sunrise Recommendation #2 and Small Team 2 Suggested Language:<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><<Hi Kathy,<o:p></o:p></span></p>
<p><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">We talked about this at some length on one of our calls. This is not how we did it for the URS and TM-PDDRP. Those were all done in implementation, not in policy. Here
are the Policy outputs for the first round: <a href="https://gnso.icann.org/en/issues/new-gtlds/pdp-dec05-fr-parta-08aug07.htm">
https://gnso.icann.org/en/issues/new-gtlds/pdp-dec05-fr-parta-08aug07.htm</a>. No mention of URS or TM-PDDRP. Those were implemented as a result of the ideas of the IRT as refined by the STI. The were not PDP policy and, like those, there is nothing that
would keep an IRT from exploring a third party challenge mechanism. The idea may be scrapped by the WG, but if it is it should be scrapped for accurate reasons.<o:p></o:p></span></p>
<p><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">Best, Paul >><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">Paul, we did talk and disagreed about processes awhile back. I've gone back and can see the basis for your confusion.
There was an IPC group (with all members selected by the IPC) which met to come up with a set of new RPMs for New gTLDs - and went by the acronym of "IRT" with a different meaning. This IPC-group then presented its result to the GNSO and ICANN at the Sydney
meeting, and there was great concern over its proposals presented to the Board (including the first joint ALAC-NCSG resolution). <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">The Board asked the GNSO to create an expedited policy group to decide which additional RPMs met the approval of
the full GNSO -- and on request of the ICANN Board, the GNSO Council created a STI (Special Trademarks Issues Review Team) which met with a pre-determined balance of representation from all GNSO Stakeholder Groups, as well as At-Large and other ACs. Very expedited
timeframes.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">The Chair of the STI was David Maher of RySG and longtime General Counsel of the Public Interest Registry (implementation
review teams, as you know, are run by ICANN Staff.). <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">The STI - we (as we both remember) - reported back in only a few months to the GNSO Council. Our STI Report was
reviewed and adopted by the GNSO Council and later the ICANN Board. Our policy recommendations then went to a traditional "IRT," for working through the details of the policy recommendations (including URS and TMCH) that we had made together. <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">I include the framing paragraphs of the STI report below and the link -- and absolutely submit that overlapping
acronyms make our lives difficult!<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">Overall, the URS, TMCH and UDRP all pass the criteria for being GNSO-approved policies. And I must return to my
concern that at least part of your proposal gives policy-making powers to a future "implementation review team" which is not the way we do things. <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">Best, Kathy<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">-------------------------------------------------------------------------------<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:13.5pt;font-family:"Arial",sans-serif">STI Report - </span><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:13.5pt;font-family:"Arial",sans-serif">"Background and Approach Taken</span><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:13.5pt;font-family:"Arial",sans-serif">On 12 October 2009, the ICANN Board sent a letter</span><span style="font-size:8.5pt;font-family:"Arial",sans-serif">1</span><span style="font-size:13.5pt;font-family:"Arial",sans-serif">to
the GNSO requesting its review of the policy implications of certain trademark protection mechanisms proposed for the New gTLD Program, as described in the Draft Applicant Guidebook and accompanying memoranda. Specifically, the Board Letter requested that
the GNSO provide input on whether it approves the proposed staff model,or, in the alternative, the GNSO could propose an alternative that is equivalent or more effective and implementable. In response, the GNSO adopted a resolution creating the Special Trademarks
Issues review team (STI) on 28 October 2009</span><span style="font-size:8.5pt;font-family:"Arial",sans-serif">2</span><span style="font-size:13.5pt;font-family:"Arial",sans-serif">which included representatives from each Stakeholder Group</span><span style="font-size:15.0pt;font-family:"Arial",sans-serif">,
</span><span style="font-size:13.5pt;font-family:"Arial",sans-serif">At-Large, Nominating Committee Appointees, and the GAC(identified on Annex 3), to analyze the specific rights protection mechanisms that have been proposed for inclusion into the Draft Applicant
Guidebook."</span><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:13.5pt;font-family:"Arial",sans-serif">Page 2, <a href="https://gnso.icann.org/sites/default/files/filefield_8000/sti-wt-recommendations-11dec09-en.pdf">https://gnso.icann.org/sites/default/files/filefield_8000/sti-wt-recommendations-11dec09-en.pdf</a></span><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><o:p></o:p></span></p>
</div>
<br>
<font face="Arial" color="Gray" size="1"><br>
</font>
</body>
</html>