<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:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
p.MsoFootnoteText, li.MsoFootnoteText, div.MsoFootnoteText
{mso-style-priority:99;
mso-style-link:"Footnote Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Times New Roman",serif;
mso-fareast-language:EN-US;}
span.MsoFootnoteReference
{mso-style-priority:99;
vertical-align:super;}
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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
p.Default, li.Default, div.Default
{mso-style-name:Default;
margin:0cm;
margin-bottom:.0001pt;
text-autospace:none;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;
mso-fareast-language:EN-US;}
span.FootnoteTextChar
{mso-style-name:"Footnote Text Char";
mso-style-priority:99;
mso-style-link:"Footnote Text";
font-family:"Times New Roman",serif;}
span.ETNormalChar
{mso-style-name:"ETNormal Char";
mso-style-link:ETNormal;
font-family:"Times New Roman",serif;}
p.ETNormal, li.ETNormal, div.ETNormal
{mso-style-name:ETNormal;
mso-style-link:"ETNormal Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
mso-fareast-language:EN-US;}
p.ETHeader, li.ETHeader, div.ETHeader
{mso-style-name:ETHeader;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
mso-fareast-language:EN-US;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
/* Page Definitions */
@page
{mso-endnote-separator:url("cid:header.htm\@01D5CB8E.8990A410") es;
mso-endnote-continuation-separator:url("cid:header.htm\@01D5CB8E.8990A410") ecs;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1027" />
</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-CA" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif">Dear Mr. Namazi,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="Default"><span style="font-family:"Arial",sans-serif">Please see the Internet Commerce Association’s attached Comment in connection with the Proposed Amendment 3 to the .COM Registry Agreement. We are also appending below, a plain text version of
our Comment without footnotes.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-CA">Yours truly,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-CA">Zak Muscovitch<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-CA">General Counsel, ICA<o:p></o:p></span></p>
<div style="mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0cm 0cm 1.0pt 0cm">
<p class="MsoNormal" style="border:none;padding:0cm"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-CA">InternetCommerce.org<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="mso-fareast-language:EN-CA"><o:p> </o:p></span></p>
<p class="ETNormal"><span lang="EN-US" style="font-size:11.5pt">January15, 2020<o:p></o:p></span></p>
<p class="ETNormal"><span lang="EN-US" style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="ETHeader"><span lang="EN-US" style="font-size:11.5pt">ICANN <o:p></o:p></span></p>
<p class="ETHeader"><span lang="EN-US" style="font-size:11.5pt">Global Domains Division<o:p></o:p></span></p>
<p class="ETHeader"><span lang="EN-US" style="font-size:11.5pt">12025 Waterfront Drive, Suite 300<o:p></o:p></span></p>
<p class="ETHeader"><span lang="EN-US" style="font-size:11.5pt">Los Angeles, California
<o:p></o:p></span></p>
<p class="ETHeader"><span lang="EN-US" style="font-size:11.5pt">90094-2536, USA<o:p></o:p></span></p>
<p class="ETHeader"><span lang="EN-US" style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="ETHeader"><span lang="EN-US" style="font-size:11.5pt">Attn: Cyrus Namazi<o:p></o:p></span></p>
<p class="ETHeader"><span lang="EN-US" style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="ETHeader"><span lang="EN-US" style="font-size:11.5pt">Dear Mr. Namazi: </span>
<span lang="EN-US" style="font-size:11.5pt"><o:p></o:p></span></p>
<p class="ETHeader"><span lang="EN-US" style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="ETHeader" style="margin-left:36.0pt;text-indent:-36.0pt"><b><span lang="EN-US" style="font-size:11.5pt">Re: Proposed Amendment 3 to the .COM Registry Agreement<o:p></o:p></span></b></p>
<p class="ETHeader"><u><span lang="EN-US" style="font-size:11.5pt">
<o:p></o:p></span></u></p>
<p class="MsoNormal"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">We are writing to you in response to your request for public comments (“Public Comments”) on the above-noted proposal (the “Proposed Amendment”).<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><b><u><span style="font-size:11.5pt">Introduction</span></u></b><b><span style="font-size:11.5pt"><o:p></o:p></span></b></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">1. We trust that you can appreciated that your request for Public Comments must be viewed with considerable skepticism considering that the last time that you requested
feedback from the public on an amendment to a registry agreement, public comment resulted in exactly
<i>zero </i>changes to the .org Registry Agreement despite near universal opposition and condemnation from stakeholders. Your failure to pay more than lip service to the multi-stakeholder model resulted in what is now widely considered to be the “.Org Fiasco”.
This has called into question whether ICANN is actually capable of representing the public interest.
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">In the future, should ICANN genuinely seek public comment on something as crucial as a multi-billion dollar service agreement that involves crucial policy questions, it would seem
to make sense to request such feedback, or even engage a policy development process,
<i>before</i> “reaching a proposed agreement”, which is not the case now. In fact, on January 3, 2020, you announced that you had
<i>already</i></span> “reached a proposed agreement”, whereas it would make far more sense and be far more credible, if you sought community input
<i>before </i>reaching any proposed agreement. Otherwise, ICANN’s position is already firmly entrenched and its direction already established, thereby putting the cart before the horse.
<span style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">Nevertheless, in case there is someone with a decision-making capacity at ICANN Org or on the ICANN Board of Directors who is prepared to actually receive public comments with a
view to possibly reconsidering the Proposed Amendment, we are submitting our comments herein.
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><b><span style="font-size:11.5pt"><o:p> </o:p></span></b></p>
<p class="MsoNormal" style="text-align:justify"><b><u><span style="font-size:11.5pt">ICANN is Under No Legal Obligation to Permit Verisign to Raise its Prices to the Maximum or At All
<o:p></o:p></span></u></b></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">2. ICANN has expressly claimed that the Proposed Amendment “fulfills commitments that ICANN and Verisign made in 2016 when they previously amended the .COM RA”.
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">This is false. ICANN never committed to raising the Maximum Price that Verisign was permitted to charge for .com registrations. All that ICANN committed to in the First Amendment
to the 2016 .COM Registration Agreement, was to “cooperate and negotiate in good faith to amend the terms of the Agreement “as may be necessary for consistency with changes to…the Cooperative Agreement”.
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">Amendment 35 to the Cooperative Agreement merely stated that “the yearly price for the registration and renewal of domain names in the .com registry
<i><u>may</u></i> be changed” [emphasis added], and that” ICANN <i><u>may</u></i> agree to amend” the Maximum Price [emphasis added]. NTIA’s Statement<a style="mso-footnote-id:ftn1" href="#_ftn1" name="_ftnref1" title=""><span class="MsoFootnoteReference"><span class="MsoFootnoteReference"><span style="font-size:11.5pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">[1]</span></span></span></a>
on Amendment 35 expressly stated that Amendment 35, under the heading of “Pricing Flexibility”, merely “<i>permits</i> Verisign to
<i>pursue </i>with ICANN<i> </i>an<i> up to </i>7 percent increase in the prices of .com domain names” [emphasis added].
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">It is therefore clear from the .COM Registry Agreement, Amendment 35, and NTIA’s Statement, that NTIA did
<u>not</u></span> require or impose a 7% increase in price and that it remains up to ICANN whether to agree to give Verisign any increase at all, or if an increase is to be granted, whether it should be within the maximum of 7% instead of at the maximum.<span style="font-size:11.5pt">
Since </span>Amendment 35 requires no increase in price whatsoever, and at most provides “flexibility” of up to a maximum 7% annual increase in 4 out of 6 years, it would be consistent with Amendment 35
<i>if no changes at all</i> were made to the .COM Registry Agreement. At most, all that ICANN is required to do pursuant to its .COM Registry Agreement obligations is to consider whether allowing Verisign to charge more, is justifiable. It is not.
<span style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">It is an extraordinarily serious concern that ICANN would apparently assume that it “has no choice” but to give Verisign permission to raise its prices, when there is no such legal
obligation. If ICANN has been led to believe that its hands are tied by the existing terms of the .COM Registry Agreement or that NTIA required ICANN to permit Verisign to raise its prices all the way to the permitted Maximum, it is nothing short of a multi-billion
dollar error. <o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">We previously highlighted to you the absence of any obligation to permit Verisign to raise prices in our letter dated November 16, 2018. We are once again reiterating this crucial
understanding of ICANN’s legal obligations, and in light of this it is incumbent upon you to reconsider your options and proceed pursuant to your actual legal obligations instead of pursuant to your misapprehended ones. You should also cease misrepresenting
to stakeholders that the Proposed Amendment is in any sense “required” of you under a mistaken notion of “consistency”, as opposed to it being an entirely gratuitous concession to your contracted .COM registry service provider.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><b><u><span style="font-size:11.5pt">There is No Factual Justification for Permitting Verisign to Raise its Prices<o:p></o:p></span></u></b></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">3. At the outset, it should be clear to you that no one other than Verisign (and perhaps other contracted registry operators) want increases in .COM prices. There is obviously
no stakeholder outcry to increase prices on registrants. Registrants themselves obviously don’t want to pay more.
<i>So who does the proposed price increase stand to benefit?</i> Only Verisign. It stands to reap billions of dollars more, all paid for by registrants, and for no genuine reason whatsoever.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify">Verisign is entitled to a reasonable fee for running the registry on behalf of ICANN. Verisign currently charges $7.85 per .com domain name per year. The cost to operate the registry, after taking into account
the expensive infrastructure necessary to provide reliable and secure operations and high overhead, has been estimated at $1.00<a style="mso-footnote-id:ftn2" href="#_ftn2" name="_ftnref2" title=""><span class="MsoFootnoteReference"><span class="MsoFootnoteReference"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">[2]</span></span></span></a>
to $3.50 per domain name per year.<span style="font-size:11.5pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify">If the proposed fee increases go into effect, by the end of the six-year agreement term, the fee for each .com domain name will increase to $10.29 per year, a 30% jump from current levels. Even conservatively
assuming that in six years’ time there are only 140 million .com domain name registrants, that increase of $2.44 per year, per domain name, would result in
<b>$341,000,000 more revenue for Verisign <u>per year</u>.</b> Bear in mind, that without any price increase and as things already stand now, Verisign, has a market capitalization of nearly $25 billion dollars and had net income in 2017 of US $457 million on
revenue of $1.14 billion. Making things even more remarkable is that Verisign enjoys an incredible operating margin of around 60%.<a style="mso-footnote-id:ftn3" href="#_ftn3" name="_ftnref3" title=""><span class="MsoFootnoteReference"><span class="MsoFootnoteReference"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">[3]</span></span></span></a><b><span style="font-size:12.0pt"><o:p></o:p></span></b></p>
<p class="MsoNormal" style="text-align:justify"><b><o:p> </o:p></b></p>
<p class="MsoNormal" style="text-align:justify">Despite benefiting from the economies of scale from operating the largest domain name registry together with the .net registry, Verisign already charges
<i>far more</i> for its registry services than other registry operators. For instance, as reported by Domain Name Wire, a recent bid to manage the registry for India’s .in domain name was made by Neustar at just 70 cents per domain name per year, and registry
operator Afilias offered to run it for $1.65 per domain name per year. Afilias runs the much smaller .org registry, with its 10 million domain names under management for approximately $1.80 per domain name per year.<o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><o:p> </o:p></p>
<p class="MsoNormal" style="text-align:justify">Accordingly, by any reasonable estimation, Verisign is not suffering for lack of revenue nor is it deserving of increased revenue. The current rate of $7.85 is already far in excess of market rates as determined
through competitive bidding processes elsewhere. <b>Simply put, there is no justification for increasing prices, whatsoever.
<o:p></o:p></b></p>
<p class="MsoNormal" style="text-align:justify"><b><o:p> </o:p></b></p>
<p class="MsoNormal" style="text-align:justify">If ICANN is to be trusted as the steward of the .COM Registry on behalf of the global public interest, ICANN must ask itself why it would effectively hand over billions of dollars in registrant money to its contracted
service provider? Verisign is merely your manager of the .COM Registry – it has no business dictating the price, particularly when it is already handsomely paid and others could do it for far less. As we saw with the .Org Fiasco, bad things happen when a registry
operator treats the registry as an asset that belongs to it, rather than acting as a mere contracted manager.
<o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><b><u><span style="font-size:11.5pt">The Refrain That ICANN Is Not a Regulator is a Dangerous and Misguided Red Herring<o:p></o:p></span></u></b></p>
<p class="MsoNormal" style="text-align:justify"><u><span style="font-size:11.5pt"><o:p><span style="text-decoration:none"> </span></o:p></span></u></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">ICANN repeatedly and apparently reflexively, repeats the mantra, that “ICANN is not a price regulator”, as if it makes any sense. It does not. The latest reflexive utterance of this
misguided mantra regrettably appears in the background info on the Public Comments Page.<a style="mso-footnote-id:ftn4" href="#_ftn4" name="_ftnref4" title=""><span class="MsoFootnoteReference"><span class="MsoFootnoteReference"><span style="font-size:11.5pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">[4]</span></span></span></a>
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">First, no matter how many times this mantra is repeated, doesn’t make it any more meaningful or truthful.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">Second, at most it is a statement of a purported policy, not of a fact.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">Third, ICANN has been setting prices for years. It sets prices every time it enters into a contract with a service provider and has consistently set prices for legacy TLDs.
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">Fourth, ICANN as the steward of the .COM Registry, is of course entitled to determine what its service provider, Verisign, can charge in respect of a public resource that ICANN is
supposed to manage in the public interest.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">Fifth, if there was ever any hope that the new gTLDs would present such effective competition to .COM that prices would naturally be constrained by market forces, the results are
in and it didn’t happen. The Antitrust Division of the U.S. Department of Justice specifically determined in 2008 that Verisign possesses significant market power as the operator of the .COM Registry because many registrants do not perceive .com and other
gTLDs and ccTLDS to be substitutes. That has not changed. Verisign still has market power due to the unique market position of .COM. This market power means that Verisign is not constrained by competitive forces from raising prices on its captive base of
.COM registrants especially given the prohibitive switching costs for registrants. Further, as there is no genuinely adequate substitute TLD for .COM, Verisign is the only source for new registrants wishing to enjoy the distinct benefits of branding on a
.COM domain name. Because of Verisign’s market power, and in the absence of putting the .COM Registry out for bid, price caps are necessary to protect the public from Verisign’s ability to abuse its market power by raising prices far above levels that would
exist in a market where there was effective competition. Verisign’s prices already far exceed market levels. Any further increases are unjustified.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">Sixth, to the extent that being a “regulator” by definition entails being a government agency, then of course ICANN is not a “price regulator” per se. But ICANN needn’t be a price
regulator to negotiate with its supplier a reasonable price on .COM domain names, as ICANN was entrusted with the DNS to operate it for the public benefit.
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">Seventh, if ICANN is not a price regulator, then who is? The Department of Commerce does not set prices for the .COM Registry. Rather, it leaves it up to ICANN. And if neither the
DOC nor ICANN sets prices, then who gets to set prices? Verisign, the service provider with market power? That is an absurd situation which if allowed to occur, would surely cause untold damage to the public interest.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">Eighth, setting prices is a policy matter when it comes to the .COM Registry. If ICANN intended to adopt such a radical policy of permitting Verisign to set its own prices, that
is a matter for stakeholders to determine, and there has never been any such policy development nor agreement amongst stakeholders.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">Ninth, to the extent that ICANN took a hands-off approach to pricing when it came to new gTLDs, that is an entirely different situation than with legacy registries. New gTLDs were,
for better or worse, ‘bought and paid for’ by new gTLD applicants who were determined as a matter of consensus policy, to be able to charge what they wanted. But as we have seen with the .Org Fiasco, when it comes to long-established legacy TLDs, stakeholders
and registrants in particular want price stability and certainty. They want prices that are as low as possible while maintaining reliable DNS services.
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.5pt">Lastly, fair, stable, and certain pricing when it comes to legacy TLDs, is a core mission of ICANN despite what you may have been told or have come to believe. In ICANN’s Announcement
regarding the Proposed Amendment, </span>ICANN expressly acknowledged, in the very same statement wherein ICANN stated that “it is not a price regulator”, that “<i><span style="color:black;background:white">pricing certainty</span></i><span style="color:black;background:white">
[will be achieved] by limiting the potential maximum wholesale price for .COM domain names”. ICANN goes on to state, “the .COM </span>TLD<span style="color:black;background:white"> is
<i>an important part of global commerce, making its continued secure, stable and resilient
</i>operation a top priority for both </span>ICANN<span style="color:black;background:white"> and Verisign”. Accordingly, by its own admission, ICANN itself implicitly acknowledges that it has a crucial role to play in maintaining stable pricing in order to
ensure .COM’s important place in the public interest.</span><span style="font-size:12.0pt;background:white"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal">Yours truly,<span style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><b>INTERNET COMMERCE ASSOCIATION<o:p></o:p></b></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal">“Zak Muscovitch”<br clear="all">
Per: <o:p></o:p></p>
<p class="MsoNormal">Zak A. Muscovitch<o:p></o:p></p>
<p class="MsoNormal">ZM/cm<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.5pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div style="mso-element:footnote-list"><br clear="all">
<hr align="left" size="1" width="33%">
<div style="mso-element:footnote" id="ftn1">
<p class="MsoFootnoteText"><a style="mso-footnote-id:ftn1" href="#_ftnref1" name="_ftn1" title=""><span class="MsoFootnoteReference"><span lang="EN-US"><span class="MsoFootnoteReference"><span lang="EN-US" style="font-size:10.0pt;font-family:"Times New Roman",serif;mso-fareast-language:EN-US">[1]</span></span></span></span></a><span lang="EN-US">
</span>See: NTIA Statement on Amendment 35 (<span lang="EN-US"><a href="https://www.ntia.doc.gov/press-release/2018/ntia-statement-amendment-35-cooperative-agreement-verisign">https://www.ntia.doc.gov/press-release/2018/ntia-statement-amendment-35-cooperative-agreement-verisign</a>)</span><o:p></o:p></p>
</div>
<div style="mso-element:footnote" id="ftn2">
<p class="MsoFootnoteText"><a style="mso-footnote-id:ftn2" href="#_ftnref2" name="_ftn2" title=""><span class="MsoFootnoteReference"><span lang="EN-US"><span class="MsoFootnoteReference"><span lang="EN-US" style="font-size:10.0pt;font-family:"Times New Roman",serif;mso-fareast-language:EN-US">[2]</span></span></span></span></a><span lang="EN-US">
See; https://www.theregister.co.uk/2018/11/02/dotcom_domains_pricing/</span><o:p></o:p></p>
</div>
<div style="mso-element:footnote" id="ftn3">
<p class="MsoFootnoteText"><a style="mso-footnote-id:ftn3" href="#_ftnref3" name="_ftn3" title=""><span class="MsoFootnoteReference"><span lang="EN-US"><span class="MsoFootnoteReference"><span lang="EN-US" style="font-size:10.0pt;font-family:"Times New Roman",serif;mso-fareast-language:EN-US">[3]</span></span></span></span></a><span lang="EN-US">
</span><i>Ibid.<o:p></o:p></i></p>
</div>
<div style="mso-element:footnote" id="ftn4">
<p class="MsoFootnoteText"><a style="mso-footnote-id:ftn4" href="#_ftnref4" name="_ftn4" title=""><span class="MsoFootnoteReference"><span lang="EN-US"><span class="MsoFootnoteReference"><span lang="EN-US" style="font-size:10.0pt;font-family:"Times New Roman",serif;mso-fareast-language:EN-US">[4]</span></span></span></span></a><span lang="EN-US">
</span>See <span lang="EN-US"><a href="https://www.icann.org/public-comments/com-amendment-3-2020-01-03-en">https://www.icann.org/public-comments/com-amendment-3-2020-01-03-en</a></span><o:p></o:p></p>
</div>
</div>
</body>
</html>