<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>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<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:"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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:533494949;
mso-list-type:hybrid;
mso-list-template-ids:1063782916 67698711 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-number-format:alpha-lower;
mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Kathy,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">***<u>View as the Co-Chair</u> - I do not believe the guardrails you have proposed have support within the working group. The rules/guardrails you have proposed represent a drastic departure from what the Working Group has discussed, that
I do not believe it is realistic to think that they can be adopted at this point. Other members of the Working Group have supported the PICs and RVCs and have also supported the notion that they can be done in compliance with the Bylaws provided that we
do not put ICANN in the position of determining whether any content based commitment was actually violated. That adjudication may be beyond the scope of ICANN’s mission. But if the actual adjudication is done by a third party and the registry agrees to be
bound by the decision of that unrelated third party, then the Working Group members have weighed in that this seems in line with the Bylaws.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We will discuss this further.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">__________________________<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:red">****Personal View Follows**** Taking Co-Chair hat off – the following represents only my opinion. If the Working Group takes an opposing view, then as co-chair I will follow that.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">I personally disagree with the overbroad guardrails. Take the .gay registry as an example. The .gay registry has a very tight anti-bullying / anti-harassment policy and reserves
the right to take down sites that it finds violating that policy. Their goal is to present a safe space where a group of people that have historically been (and in a lot of cases still are) the subject of persecution, discrimination, harassment and bullying.
The registry wants a space where its registrants and end users feel safe to belong, participate, celebrate, and just be themselves. If they want to commit to a content based policy, then who are we to tell them that they cant.<o:p></o:p></li></ol>
<p class="MsoListParagraph"><o:p> </o:p></p>
<ol style="margin-top:0in" start="2" type="a">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">I believe I was at that American University event, and even explained then that registries aim to make TLDs a brand. If they want to have policies that distinguish their TLDs from
others, even if related to content, then why should they be forbidden from doing so. I think I raised the example of Anti-abuse policies. When Neustar in 2008 or 2009 (when I was there) adopted an anti-abuse policy stating it would take down names using
for phishing, pharming, malware, etc., it did so because it was starting to appear on ISP block lists for not taking that action. Legitimate registrants were having their e-mails blocked because the registry wasn’t taking action. The .biz brand was taking
a huge dip. We made the bold decision and actually became the first registry to adopt an anti-abuse policy addressing these behaviors. I believe the EFF and others made the same arguments you were making. But the registry cleaned up its act, got taken off
block lists and became (at the time) one of the safest TLDs. The brand became more respectable and registrants emails were again getting through. Over time, you, the EFF and others came to accept anti-abuse monitoring and now it is employed by virtually
every registry and registrar.<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<table class="MsoTableGrid" border="1" cellspacing="0" cellpadding="0" style="border-collapse:collapse;border:none">
<tbody>
<tr>
<td width="192" valign="bottom" style="width:144.3pt;border:none;border-top:solid #06175F 3.0pt;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black;border:none windowtext 1.0pt;padding:0in"><img width="178" height="81" style="width:1.8489in;height:.8437in" id="Picture_x0020_1" src="cid:image001.png@01D6D47E.6C5D25E0"></span><o:p></o:p></p>
</td>
<td width="173" valign="bottom" style="width:129.95pt;border:none;border-top:solid #06175F 3.0pt;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:#06175F">Jeffrey J. Neuman</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">Founder & CEO</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:#06175F">JJN Solutions, LLC</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">p: +1.202.549.5079</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">E:
</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><a href="mailto:jeff@jjnsolutions.com"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#1155CC">jeff@jjnsolutions.com</span></a><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">http://jjnsolutions.com</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Kathy Kleiman <kathy@kathykleiman.com> <br>
<b>Sent:</b> Thursday, December 17, 2020 1:43 PM<br>
<b>To:</b> gnso-newgtld-wg@icann.org; Jeff Neuman <jeff@jjnsolutions.com>; langdonorr@gmail.com<br>
<b>Subject:</b> Finishing up PICs<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in;line-height:105%">
All, <span style="font-size:12.0pt;line-height:105%;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in;line-height:105%">
Let’s remember that this is a contract between ICANN and the New gTLD Registries. It is not a Registry-Registrar Agreement or a Registrar-Registrant Agreement. Accordingly, everything in it must be legit under ICANN’s Bylaws. We want our ICANN Board Members,
including Becky, to sleep at night. <span style="font-size:12.0pt;line-height:105%;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in;line-height:105%">
To do so, terms that are put into an RVC must fall within terms to which ICANN, as a signatory to this contract, must agree. Again, this is *ICANN’s contract.* There are many things we would not put into the vPICs/RVCs therefore, even though they may happen.
Like some cooperation with local law enforcement and providing data on users and use. It may happen; it’s not in our contracts or blessed or enforced by ICANN. <span style="font-size:12.0pt;line-height:105%;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in;line-height:105%">
Accordingly, to the end of Recommendation 9.12, we must add something about the requirements of the RVC. A registrant cannot be required to paint the moon pink, and the PICs should not be allowed to push ICANN outside its mission, mandate, scope and core values.
These are ICANN commitments to all of us, and to the world, in its Bylaws. <i>Accordingly we must add: RVCs will not address the contents of websites or apps that use domain names, they will be consistent with ICANN’s Human Rights Core Value, they will not
allow the registry arbitrary discretion to suspend a domain name, and they will not be used to create new policies that did not come through ICANN processes. </i><span style="font-size:12.0pt;line-height:105%;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in;line-height:105%">
These limitations are substantive – they will keep the RVCs within the bounds of what ICANN is allowed to sign and what ICANN is allowed to do. The Attorney Generals do not want to see a spate of new contracts from California public interest corporation coming
without principles and guardrails for what one party, in its self-interest, can impose on other parties, particularly those who are weaker – a registry imposing arbitrary and unfair terms on its registrants (note: unfair RVCs
<i>did not, </i>in Round 1, come through the public processes we are working hard to protect, including GAC Early Warnings, GAC Consensus Advice, and settlements of Objections e.g., Community, Legal Rights, etc). <span style="font-size:12.0pt;line-height:105%;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in;line-height:105%">
We need to finish up 9.12 with the additions above. RVCs will no longer be the dumping ground or the “kitchen sink” as they were in 2013-2014. This is critical for ICANN’s integrity, and for this I quote, as I did in my March 11, 2020, CircleID article: Becky
Burr, then and still an ICANN Board member, speaking in her personal capacity at an event at American University Washington College of Law in February 2019, ICANN and New gTLDs,
<b>describing the Round 1 private PIC process: "<em><span style="font-family:"Calibri",sans-serif">I hope we never see any like that [again]", "the process by which that happened was appalling," "and most registries and registrars were appalled by that process
as well." "A subset of… registry applicants came in and made ... commitments that were like,
<u>literally, everything in the kitchen sink</u>."</span></em> </b>[emphasis added]<span style="font-size:12.0pt;line-height:105%;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in;line-height:105%">
<b>No more “kitchen sink,” and we’re done.</b> <span style="font-size:12.0pt;line-height:105%;font-family:"Times New Roman",serif">
<o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:8.0pt;margin-left:0in;line-height:105%">
Best, Kathy<span style="font-size:12.0pt;line-height:105%;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</div>
</body>
</html>