<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 12 (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: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";}
span.EmailStyle18
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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=Section1>
<p><span style='font-family:"Calibri","sans-serif"'>I am a domain name
registrant. </span><o:p></o:p></p>
<p><span style='font-family:"Calibri","sans-serif"'>ICANN does not seem to
recognize the difference between a legacy extension created with the support of
the US government, that predates the existence of ICANN and that has millions
of existing users and the brand new extensions that started off with a new set
of rules, in particular no price controls, and no existing registrants. They
have completely different characteristics, history, and ownership structure. It
is not acceptable for ICANN to ignore these differences and to propose that
they be treated the same.</span><o:p></o:p></p>
<p><span style='font-family:"Calibri","sans-serif"'>Removing price caps is not
fair to .org domain owners. Many of them have websites that they have used for
years. If price caps are removed, the cost to renew their domain names may
become too expensive, and they could be forced to give up websites that are
important to them.</span><o:p></o:p></p>
<p><span style='font-family:"Calibri","sans-serif"'>The Uniform Rapid
Suspension policy is too new and untested to apply on domain names that may be
20 years old or more. With the URS, the domain names could be taken down in a
matter of days with little notice.</span><o:p></o:p></p>
<p><span style='font-family:"Calibri","sans-serif"'>ICANN should be doing more
to protect owners of .org domain names. Why is ICANN trying to remove price
protections for .org domain owners, so many of which are non-profits, so that
they can be overcharged for their domain names?</span><o:p></o:p></p>
</div>
</body>
</html>