<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=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<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;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
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-compose;
font-family:"Calibri",sans-serif;}
.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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p><span style="font-family:"Calibri",sans-serif">I am a .org registrant. </span>
<o:p></o:p></p>
<p><span style="font-family:"Calibri",sans-serif">ICANN staff should not unilaterally impose URS in legacy TLDs when that issue is precisely what is being examined by the volunteer ICANN Working Group who has been mandated to review this issue. ICANN policy
making is supposed to be a ‘bottom up, multi-stakeholder model’.</span><o:p></o:p></p>
<p><span style="font-family:"Calibri",sans-serif">I believe that legacy gTLDs are fundamentally different from for-profit new gTLDs. Legacy TLDs are essentially a public trust, unlike new gTLDs which were created, bought and paid for by private interests. Registrants
of legacy TLDs are entitled to price stability and predictability, and should not be subject to price increases with no maximums. Unlike new gTLDs, registrants of legacy TLDs registered their names and made their online presence on legacy TLDs on the basis
that price caps would continue to exist.</span><o:p></o:p></p>
<p><span style="font-family:"Calibri",sans-serif">Unrestrained price increases on the millions of .org registrants who are not-for-profits or non-profits would be unfair to them. Unchecked price increases have the potential to result in hundreds of millions
of dollars being transferred from these organizations to one non-profit, the Internet Society, with .org registrants receiving no benefit in return. ICANN should not allow one non-profit nearly unlimited access to the funds of other non-profits.</span><o:p></o:p></p>
<p><span style="font-family:"Calibri",sans-serif">ICANN appears to be entirely catering to registries by removing price caps. ICANN should stand up for the public interest and registrants!</span><o:p></o:p></p>
</div>
<HR><font color="gray"><BR>
<I><BR>
Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) to which it is addressed and may contain information that is confidential, privileged or exempt from disclosure under applicable law. Any unauthorized review, use, disclosure, printing, storing, copying or distribution is prohibited. If you are not the intended recipient, or if you have received this email in error, please contact the sender by reply e-mail and delete all copies of the original message. Unless specifically stated otherwise, nothing in this email is intended to serve as an electronic or digital signature.</I><BR>
</font><BR>
</body>
</html>