<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 07:12:15 Friday, 11 December 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:"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;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:ArialMT;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Arial-BoldMT;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{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;}
/* List Definitions */
@list l0
{mso-list-id:1258513673;
mso-list-type:hybrid;
mso-list-template-ids:336743848 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{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;}
@list l1
{mso-list-id:1495800749;
mso-list-type:hybrid;
mso-list-template-ids:2073860464 1255033818 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.25in;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:1.75in;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.75in;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:3.25in;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.75in;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:4.25in;
text-indent:-.25in;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:4.75in;
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="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black">Hi All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black">Well, clearly these are brand new ideas from Kathy that have never been discussed by the working group or put out for public comment. We have no time to consider
the merits (if any) of such sweeping changes to the entire ICANN ecosystem with exactly one substantive call left. Additionally, the sweeping changes are unnecessary as even a casual review of the Bylaws indicate no issues. Below is an informal position
developed through kicking this around on a recent IPC call (it can’t be considered a formal position, since the sweeping, last minute ideas were introduced with no time left in the PDP timeline to respond to them formally). We hope this is helpful.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black">Paul<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black">_______________________________<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-family:"Arial",sans-serif;color:#002060">1. ICANN can enter into and enforce PICS in service of its Mission.</span></b><span style="font-family:"Arial",sans-serif;color:#002060"> 1.1 (d)
B (iv)</span><span style="color:#002060"> </span><span style="color:#1F497D">“</span><span style="font-family:"ArialMT",sans-serif">(iv) ICANN shall have the ability to negotiate, enter into and enforce agreements, including public interest commitments, with
any party in service of its Mission.”<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-family:"Arial",sans-serif;color:#002060">2. ICANN is not “imposing” rules and restrictions on parties by acceptance of PICs and RVCs.</span></b><span style="font-family:"Arial",sans-serif;color:#002060">
RVCs don’t constitute “regulation” of any type, much less content regulation. (refer to history of Accountability Workstream 1 ). The ByLaws provision re “imposing” rules and restrictions in 1.1 (c) states as follows:
</span><span style="color:#1F497D">.</span><span style="font-family:"ArialMT",sans-serif"> (c) ICANN shall not regulate (i.e., impose rules and restrictions on) services that use the Internet’s unique identifiers or the content that such services carry or provide,
outside the express scope of Section 1.1(a). For the avoidance of doubt, ICANN does not hold any governmentally authorized regulatory authority.
<span style="color:#002060">This language makes it clear that ICANN does not intend to act as a government regulator. It does not prohibit adoption and enforcement of PICs.
<o:p></o:p></span></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif;color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif;color:#002060">The ByLaws clearly state that all previously-adopted PICs are in force and may be renewed going forward. See 1.1 (d) which states as follows:<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif;color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">(d) For the avoidance of doubt and notwithstanding the foregoing:<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">(i) the foregoing prohibitions are not intended to limit ICANN’s authority or<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">ability to adopt or implement policies or procedures that take into<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">account the use of domain names as natural-language identifiers;<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">(ii) Notwithstanding any provision of the Bylaws to the contrary, the terms<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">and conditions of the documents listed in subsections (A) through (C)<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">below, and ICANN’s performance of its obligations or duties<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">thereunder, may not be challenged by any party in any proceeding<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">against, or process involving, ICANN (including a request for<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">reconsideration or an independent review process pursuant to Article<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">4) on the basis that such terms and conditions conflict with, or are in<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">violation of, ICANN’s Mission or otherwise exceed the scope of<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">ICANN’s authority or powers pursuant to these Bylaws (“</span><b><span style="font-family:"Arial-BoldMT",sans-serif">Bylaws</span></b><span style="font-family:"ArialMT",sans-serif">”)
or<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">ICANN’s Articles of Incorporation (“</span><b><span style="font-family:"Arial-BoldMT",sans-serif">Articles of Incorporation</span></b><span style="font-family:"ArialMT",sans-serif">”):<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">(A)<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">(1) all registry agreements and registrar accreditation<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">agreements between ICANN and registry operators or<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">registrars in force on [1 October 2016]</span><span style="font-size:8.0pt;font-family:"ArialMT",sans-serif">1</span><span style="font-family:"ArialMT",sans-serif">,
including, in<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">each case, any terms or conditions therein that are<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">not contained in the underlying form of registry<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">agreement and registrar accreditation agreement;<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">(2) any registry agreement or registrar accreditation<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">agreement not encompassed by (1) above to the<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">extent its terms do not vary materially from the form of<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">registry agreement or registrar accreditation<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">agreement that existed on [1 October 2016];<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">(B)any renewals of agreements described in subsection (A) pursuant<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">to their terms and conditions for renewal;<span style="color:#002060"><o:p></o:p></span></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif;color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif;color:#002060">The fact that even voluntary PICS may be renewed going forward confirms without a doubt that they are not outside of ICANN’s power under the new ByLaws.
Thus, adoption and enforcement of voluntary PICs (RVCs) is not ultra vires. <b>
Unfortunately the recently proposed “guardrails” around the adoption of voluntary PICs and Registry Voluntary commitments would in fact make ICANN a regulator of content, making ICANN the judge of a Registry’s Human Rights compliance and making ICANN (rather
than the Registry) the arbiter of whether a particular RVC addresses content. In other words, the guardrails proposed increase the danger that ICANN would be acting as a content regulator.
</b></span><b><span style="font-family:"ArialMT",sans-serif"><o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-family:"Arial",sans-serif;color:#002060">3.</span></b><span style="font-family:"Arial",sans-serif;color:#002060">
<b>No revision to the ByLaws is necessary for ICANN to accept and approve the PICs and RVC policy developed by the WG.</b> The ICANN ByLaws clearly state in the Mission section that the PDP process acts as a “guiding light” in the development of policy that
relates to ICANN’s Mission. Current ByLaws Section 1.1. (a) states:<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">Specifically, ICANN:<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">(i) Coordinates the allocation and assignment of names in the root zone<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">of the Domain Name System (“</span><b><span style="font-family:"Arial-BoldMT",sans-serif">DNS</span></b><span style="font-family:"ArialMT",sans-serif">”) and coordinates
the<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">development and implementation of policies concerning the<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">registration of second-level domain names in generic top-level<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">domains (“</span><b><span style="font-family:"Arial-BoldMT",sans-serif">gTLDs</span></b><span style="font-family:"ArialMT",sans-serif">”). In this role, ICANN’s
scope is to coordinate the<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">development and implementation of policies:<o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:.5in;text-autospace:none"><b><span style="font-family:Symbol">•
</span></b><b><span style="font-family:"ArialMT",sans-serif">For which uniform or coordinated resolution is reasonably<o:p></o:p></span></b></p>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-family:"ArialMT",sans-serif">necessary to facilitate the openness, interoperability, resilience,<o:p></o:p></span></b></p>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-family:"ArialMT",sans-serif">security and/or stability of the DNS including, with respect to<o:p></o:p></span></b></p>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-family:"ArialMT",sans-serif">gTLD registrars and registries,</span></b><span style="font-family:"ArialMT",sans-serif"> policies in the areas described in<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-family:"ArialMT",sans-serif">Annex G-1 and Annex G-2; and<o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:.5in;text-autospace:none"><b><span style="font-family:Symbol">•
</span></b><b><span style="font-family:"ArialMT",sans-serif">That are developed through a bottom-up consensus-based<o:p></o:p></span></b></p>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-family:"ArialMT",sans-serif">multistakeholder process and designed to ensure the stable and<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-family:"ArialMT",sans-serif">secure operation of the Internet’s unique names systems.</span></b><b><span style="font-family:"Arial",sans-serif;color:#002060"><o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-family:"Arial",sans-serif;color:#002060">During its deliberations, the Sub Pro Working Group majority implicitly determined that the recommended system of PICs and RVCs is reasonably necessary to facilitate the openness,
resilience, and stability of the DNS.</span></b><span style="font-family:"Arial",sans-serif;color:#002060"> The policies developed are perfectly aligned with the scope of the Mission and do NOT constitute governmental content “regulation”. In fact, PICs
and RVCs are not about content at all. They are about resolving potential disputes that might otherwise lead to litigation and/or a chilling effect of preventing the launch of a TLD. This means that the system of PICs and RVCs will serve ICANN’s Mission to
preserve and support security, stability, and resiliency. Furthermore, all voluntary PICs and RVCs will be open for public comment and super transparent. ICANN has the power and even a duty to enforce PICs that shore up security, resiliency, and stability
as determined via PDP recommendations unless such recommendations are voted down by a 2/3 majority of the Board. In addition, if RVCs are not entered into and enforced within the ICANN system, transparency is defeated because back room deals can still be
made as a matter of private contract law. PICs and RVCs keep these commitments out in the open.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#002060"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#002060">4<b>. If ICANN is concerned about the burden of enforcement, it can refer RVCs to an independent panel that ICANN does not pay and cannot override, just like UDRP</b>. The RVC-DRP
can be created in a way to allow ICANN to step back from any ICANN.org determination re RVC compliance.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="0" style="width:547.5pt;border-collapse:collapse">
<tbody>
<tr>
<td width="57" valign="top" style="width:3.75pt;padding:0in 0in 0in 0in">
<p class="MsoNormal"><strong><span style="font-size:22.0pt;font-family:"Arial",sans-serif">Taft</span></strong><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</td>
<td width="38" valign="top" style="width:22.5pt;padding:0in 15.0pt 0in 0in">
<p class="MsoNormal"><strong><span style="font-size:22.0pt;font-family:"Arial",sans-serif;color:#A22831"> /</span></strong><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</td>
<td width="635" style="width:454.5pt;padding:0in 0in 0in 0in">
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;border-collapse:collapse">
<tbody>
<tr style="height:33.0pt">
<td style="padding:0in 0in 0in 0in;height:33.0pt">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#A22831">Paul D. McGrady</span></b><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#A22831">,</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#97999B">Partner</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#97999B">Intellectual Property/Trademark/Domains/Privacy/Social Media</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#97999B">Direct: 312.836.4094</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#97999B">|</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#97999B">Office Ext: 34094</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#97999B">Taft Office: Chicago</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;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">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>From:</b> Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org>
<b>On Behalf Of </b>Jeff Neuman<br>
<b>Sent:</b> Wednesday, December 9, 2020 8:13 PM<br>
<b>To:</b> trachtenbergm@gtlaw.com; gnso-newgtld-wg@icann.org<br>
<b>Subject:</b> Re: [Gnso-newgtld-wg] Thoughts on PICs / RVCs (LONG NOTE)<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks Marc. That may be true (ICANN not wanting to be in that role), but if this is something we believe should happen, then we should state as such. The issue is that there is no other party that would be in a position to implement
the decision. In other words, if the parties in example 1 (brand owner and applicant) agree in advance that one of the potential remedies for the violation of the voluntary commitment would be an issuance of a letter of breach (which must be cured) of
their registry obligations. Lets say they also agree that failure to “cure the breach” would result in the loss of the registry. The only party that would be in a position to “implement” the remedy is ICANN itself.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">What are the other options?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<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.8583in;height:.8416in" id="Picture_x0020_3" src="cid:image002.png@01D6CF84.6AF45B00"></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"><a href="http://jjnsolutions.com">http://jjnsolutions.com</a></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> <a href="mailto:trachtenbergm@gtlaw.com">trachtenbergm@gtlaw.com</a> <<a href="mailto:trachtenbergm@gtlaw.com">trachtenbergm@gtlaw.com</a>>
<br>
<b>Sent:</b> Wednesday, December 9, 2020 8:20 PM<br>
<b>To:</b> Jeff Neuman <<a href="mailto:jeff@jjnsolutions.com">jeff@jjnsolutions.com</a>>;
<a href="mailto:gnso-newgtld-wg@icann.org">gnso-newgtld-wg@icann.org</a><br>
<b>Subject:</b> RE: Thoughts on PICs / RVCs (LONG NOTE)<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Jeff,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">With respect to your use cases, I don’t think ICANN will be receptive to 1.f and 2.d (i.e. that they implement the decision by the independent third party) as that just opens up ICANN to potential disputes and litigation.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><b><span style="font-size:8.0pt;font-family:"Georgia",serif;color:black">Marc H. Trachtenberg
</span></b><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:black"><br>
Shareholder<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:black">Chair, Internet, Domain Name, e-Commmerce and Social Media Practice<br>
Greenberg Traurig, LLP <br>
77 West Wacker Drive | Suite 3100 | Chicago, IL 60601 <br>
T +1 312.456.1020 <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:black">M +1 773.677.3305<br>
</span><a href="mailto:trachtenbergm@gtlaw.com"><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#BE9B39">trac@gtlaw.com</span></a><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#BE9B39"> | </span><a href="http://www.gtlaw.com/"><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#BE9B39">www.gtlaw.com</span></a><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:black">
| </span><a href="https://www.gtlaw.com/en/professionals/t/trachtenberg-marc-h"><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#BE9B39">View GT Biography
</span></a><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:black"><br>
<br>
<img border="0" width="192" height="31" style="width:2.0in;height:.325in" id="Picture_x0020_2" src="cid:image003.png@01D6CF84.6AF45B00" alt="Greenberg Traurig"></span><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> Gnso-newgtld-wg <<a href="mailto:gnso-newgtld-wg-bounces@icann.org">gnso-newgtld-wg-bounces@icann.org</a>>
<b>On Behalf Of </b>Jeff Neuman<br>
<b>Sent:</b> Wednesday, December 9, 2020 2:23 PM<br>
<b>To:</b> <a href="mailto:gnso-newgtld-wg@icann.org">gnso-newgtld-wg@icann.org</a><br>
<b>Subject:</b> [Gnso-newgtld-wg] Thoughts on PICs / RVCs (LONG NOTE)<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="color:#0E0E3F">*EXTERNAL TO GT*</span></b><o:p></o:p></p>
</div>
<p class="MsoNormal">All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I know there have been a lot of e-mails on this subject in the last week or so. I wanted to give you some perspectives that we discussed at the leadership level to see if we can find some common themes and then we can see if any language
in our report needs to change (which I am not convinced there will need to be substantial changes). This is my (Jeff Neuman) summary to move the discussion along.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So, here is where I think we are on principles:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo1"><u>Existing PICs used as PICs in New Registry</u> Agreements: We believe that the existing PICs – worded substantially the same as they were in 2012 – are ok under ICANN’s Bylaws as they are specifically
“grandfathered” in.<o:p></o:p></li></ol>
<p class="MsoListParagraph"><o:p> </o:p></p>
<ol style="margin-top:0in" start="2" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo1"><u>Domain Name Eligibility Rules</u>: We all seem to be on the same page that eligibility rules for the registration/renewal (but not necessarily usage) can be included in PICs/RVCs under ICANN Bylaws.<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="3" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo1"><u>Voluntary Registry Commitments</u>:<o:p></o:p></li></ol>
<p class="MsoListParagraph"><o:p> </o:p></p>
<ol style="margin-top:0in" start="3" type="1">
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoNormal" style="mso-list:l0 level2 lfo1"><u>Commitments made by Registries without ICANN Enforcement<o:p></o:p></u></li></ol>
</ol>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo1">
<![if !supportLists]><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman"">
</span>i.<span style="font:7.0pt "Times New Roman""> </span></span><![endif]>Registries and Registrars have reserved their rights to take down domain names for phishing, pharming, malware, and other forms of domain name abuse. With respect to Registries,
some have built these directly in as PICs while others have just built this into their Registry-Registrar Agreements (and some do both). These types of PICs / RVCs do not seem to present any issue under the ICANN Bylaws (in our view).
<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in"><o:p> </o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo1">
<![if !supportLists]><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman"">
</span>ii.<span style="font:7.0pt "Times New Roman""> </span></span><![endif]>We also believe that it is fairly common for registries to have policies that allow them to take down any domains used in connection with illegal activity, child exploitation,
fraud, the sale of illegal pharmaceuticals, etc. <o:p></o:p></p>
<p class="MsoListParagraph"><o:p> </o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo1">
<![if !supportLists]><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman"">
</span>iii.<span style="font:7.0pt "Times New Roman""> </span></span><![endif]>Because these do not require ICANN enforcement, we see no reason how or why this would present an ICANN Bylaw issues. Conversely, we see no reason why we (through a PDP) would
have any ability to restrict the ability of a registry to impose these types of commitments on their registrants (through registrars or directly). So while we appreciate Kathy’s concern about a Registry’s ability to take down domain names, we do not believe
that we are in a position to either require registries to take down names based on content or to prohibit them from doing so either. Both could be considered forms of regulation (imposing rules on what a registry has to do or what it may not do).<o:p></o:p></p>
<p class="MsoListParagraph"><o:p> </o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-1.5in;mso-text-indent-alt:-9.0pt;mso-list:l0 level3 lfo1">
<![if !supportLists]><span style="mso-list:Ignore"><span style="font:7.0pt "Times New Roman"">
</span>iv.<span style="font:7.0pt "Times New Roman""> </span></span><![endif]><u>Real Example Today</u>. .gay. The Registry Operator for .gay (Top Level Design) want to have a safe space for the LGBTQ community. That community, as most of you know, has
historically been the subject of hate speech, violence, bullying, etc. Having a safe space for the gay community according to the registry is its differentiator and is absolutely necessary. It has an incredibly strict Rights Protections Policy (<a href="https://urldefense.com/v3/__https:/www.ohhey.gay/gay-cares__;!!DUT_TFPxUQ!Qi5DM39VSsHFTOKBE-yGg52J_tO_YfjEOO0qejDn038YnywJTzDpdsi_SJ9GdXiBe6A$">https://www.ohhey.gay/gay-cares</a>)
that prevents Registrants from (i) inciting or promoting violence against others, (ii) Bullying, engaging in cyber bullying or inciting others to bully, (iii) Harassing, or encouraging others to harass or harm others, (iv) Stalking, (v) Abusive intent to cause
fear or threaten violence, (vi) Hate Speech, (vii) Or activity intended to organize, coordinate, or otherwise enable one of the above. It also reserves the right to take down any sites that do any of the above at its sole discretion. <o:p></o:p></p>
<p class="MsoListParagraph"><o:p> </o:p></p>
<ol style="margin-top:0in" start="3" type="1">
<ol style="margin-top:0in" start="2" type="a">
<li class="MsoNormal" style="mso-list:l0 level2 lfo1"><u>Commitments made by Registries that may require ICANN Enforcement in some capacity</u><o:p></o:p></li></ol>
</ol>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Some Registries will want to make voluntary commitments in response to public comments, Government early warnings, objections, GAC Advice, etc. We do not see an issue with having these commitments reflected in Registry
Agreements even if they fall outside of ICANN’s core mission IF in the case where the commitment does not fall within ICANN’s mission, neither ICANN itself nor any third party under ICANN’s control is involved in the decision as to whether the commitment itself
has been violated. Where an independent third party finds a violation of the commitment, ICANN should be able to rely on that third party decision and enforce a pre-arranged contractual remedy, which could include sanctions and/or termination of the Registry
Agreement.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><u>Examples / Use Cases:</u><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.75in;text-indent:-.25in;mso-list:l1 level1 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>If an Applicant applies for the TLD “.dictionarywordthatisalsobrandx” and Brand X objects to the application. Applicant agrees with Brand X that it will not use the TLD in an infringing manner to Brand X. In exchange for that Agreement,
Brand X agrees to drop its Objection IF the Applicant agrees to put this commitment into its Registry Agreement in the form of an RVC.
<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-.25in;mso-list:l1 level2 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">a.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>As a PDP Working Group we have often said that it is our preference for disputes, objections, etc. to be worked out between the parties where this is possible. This is in line with our desire to see future expansion of the TLD space
and encourage innovation and competition.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-.25in;mso-list:l1 level2 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">b.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>As a result, this type of private resolution should be encouraged.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-.25in;mso-list:l1 level2 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">c.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>The question, however, is whether ICANN could enforce this commitment.
<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-.25in;mso-list:l1 level2 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">d.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>After our discussions with the ICANN Board liaisons and the comments we received by the community, the real concern was that ICANN did not believe it could be put in a decision to make these types of decisions (namely in this case whether
Applicant’s use of the TLD violates its commitment to Brand X).<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-.25in;mso-list:l1 level2 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">e.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>If the Applicant and Brand X agree that any disputes involving their “settlement” are resolved by an independent third party (not ICANN) and the costs are borne by the parties (as opposed to ICANN), this should not present a problem.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-.25in;mso-list:l1 level2 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">f.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>If ICANN implements the decision by the independent third party (which the Applicant agreed in its Registry Agreement to allow ICANN to do), this too should not present a Bylaws issue.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-.25in;mso-list:l1 level2 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">g.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>The key point here is that ICANN itself is not imposing the restrictions on the Applicant and therefore should not be violating its own Bylaws.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.75in;text-indent:-.25in;mso-list:l1 level1 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>What if an Applicant applies for .ideaexchange? The Applicant wants to run the TLD as a place where registrants can put their open source ideas on the Internet and allow others to use their ideas in connection with whatever they want.
Comments are filed by businesses, governments, intellectual property owners and others concerned that this will be a space where users will exchange intellectual property that they do not own. Lets also assume that the Independent Objector files an objection
as well. Assume Applicant never intended that and agrees that it will have a policy whereby Registrants agree that they will not use the TLD to distribute any intellectual property that is not owned by them. And the Applicant also reserves the right to take
down any names that use the TLD in violation of this policy. To resolve the comments filed by governments, businesses, etc., the Applicant voluntarily agrees to have an RVC that states this policy and the takedown processes. Each of the commenters and the
Independent Objector agree that this would settle the matter and if documented in the Registry Agreement, they would drop their challenges.
<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-.25in;mso-list:l1 level2 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">a.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>We believe that having these comments resolved in an amicable manner should be encouraged.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-.25in;mso-list:l1 level2 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">b.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>Because this new policy has to be documented somewhere, the only real place it can be documented is as an RVC in the Registry Agreement.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-.25in;mso-list:l1 level2 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">c.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>ICANN should not be the arbiter of whether there is a violation of this policy. This would certainly arguably be beyond its mission.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-.25in;mso-list:l1 level2 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">d.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]>However, if the arbiter of any disputes is an independent third party, not paid by ICANN, etc., then this would seemingly be ok even if it is agreed by the Applicant to follow the third party decision and to allow ICANN to impose the
appropriate remedy.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.25in"><o:p> </o:p></p>
<p class="MsoListParagraph" style="margin-left:.75in"><b>Bottom Line: I believe that so long as ICANN is not the ultimate decision maker in whether a policy that may arguably be outside of its mission, there should be no issues with having new PICs and/or
Registry Voluntary Commitments. If this indeed is the case, then we would just need to add a recommendation that (a) independent third parties must be used to resolved any potential violations of the PICs / RVCs, and (b) Applicants would need to agree in
a Registry Agreement to be bound by the decision of the third party and to allow ICANN to impose sanctions / penalties.
<o:p></o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<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 border="0" width="178" height="81" style="width:1.8583in;height:.8416in" id="Picture_x0020_1" src="cid:image004.png@01D6CF84.6AF45B00"></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><a href="mailto:jeff@jjnsolutions.com"><span style="font-family:"Arial",sans-serif;color:#1155CC">jeff@jjnsolutions.com</span></a><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"><a href="https://urldefense.com/v3/__http:/jjnsolutions.com__;!!DUT_TFPxUQ!VHmb5agRvDnEibexbA2Yq3aU_7mAttGzjVKym8ZTnNE9UdXY5-Ks_wl1wezdcOaZOw$"><span style="font-family:"Arial",sans-serif">http://jjnsolutions.com</span></a><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 class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<p class="MsoNormal">If you are not an intended recipient of confidential and privileged information in this email, please delete it, notify us immediately at
<a href="mailto:postmaster@gtlaw.com">postmaster@gtlaw.com</a>, and do not use or disseminate the information.<o:p></o:p></p>
</div>
<br>
<font face="Arial" color="Gray" size="1"><br>
</font>
</body>
</html>