<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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:TrebuchetMS;
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: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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
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.m-6812473584670699400m-3215450327228791716m2074479673144817941apple-converted-space
{mso-style-name:m_-6812473584670699400m_-3215450327228791716m_2074479673144817941apple-converted-space;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Kathy,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">What “the drafter” is proposing is that ICANN take on the power to set prices for registries. I don’t want ICANN to do that or be that. First, I think prices
should be set by the market. Second, I think we can prevent registries from gouging their customers in better ways.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">--MM<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> NCSG-Discuss <NCSG-DISCUSS@LISTSERV.SYR.EDU>
<b>On Behalf Of </b>Nadira Alaraj<br>
<b>Sent:</b> Saturday, April 27, 2019 5:03 PM<br>
<b>To:</b> NCSG-DISCUSS@LISTSERV.SYR.EDU<br>
<b>Subject:</b> Re: [Urgent] [Public Comment] Proposed Renewal of .org Registry Agreement<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">+1 Kathy<o:p></o:p></p>
<div>
<p class="MsoNormal">Thank you very much.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Sat, Apr 27, 2019, 20:39 Kathy Kleiman <kathy@dnrc.tech> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p>Hi Nadira, Tx you for your comment. The drafter appears to have the same thoughts in writing the comment. He expresses a concern for the 10 million incumbent .ORG registrants, all of whom registered their domain names with the expectation of price caps
and limited price increases - and many of whom have been in their domain name space for years if not decades, with well-known websites, email address and listservs making switching costs very, very high.
<o:p></o:p></p>
<p>Here's what the comment proposes on this issue:<o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;text-align:justify" id="m_-6812473584670699400docs-internal-guid-03b944e4-7fff-d3eb-098e-7363a7f32928">
<span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black">"On the other hand, as the home for schools, community organizations, open-source projects, and other non-profit entities, this registry should not necessarily operate under the same
commercial realities that guide other domains. Fees should remain affordable, with domains which are priced within reach of everyone. Consequently, rather than removing the price cap provisions entirely, we suggest that they should be raised by a reasonable
level, or at the very least, that this aspect of the contract should be subject to review at the midpoint of the contract, to assess its impact on the ability of potential registrants, particularly non-profits or charities, to register and renew domains at
a reasonable cost."</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;text-align:justify"><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black">Recommendations:</span></b><o:p></o:p></p>
<p><b><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black">2. Rather than removing price caps from the agreement entirely, these should be retained but raised by an appropriate amount. In the alternative, this aspect of the contract
should be subject to a review midway through the contract, based on the impact of the price changes on non-profit registrants.</span></b><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;text-align:justify"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black">I think this address your middle ground of not typing PIR to its current 2013 prices, but not allowing unrestricted increases.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;text-align:justify"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black">Best, Kathy
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;text-align:justify"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:black"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal">On 4/27/2019 9:34 AM, Nadira Alaraj wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal">Note: I slipped the "not" from my sentence.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Arial",sans-serif">*so that the new contract not be retroactive, in order to the current .ORG registrants not be affected. </span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">On Sat, Apr 27, 2019, 15:37 Nadira Alaraj <<a href="mailto:nadira.araj@gmail.com" target="_blank">nadira.araj@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal">Dear Kathy and all<o:p></o:p></p>
</div>
<p class="MsoNormal">Thank you for the through investigations on this matter. <o:p>
</o:p></p>
<div>
<p class="MsoNormal">I was wondering if there is a way, so that the new contract to be retroactive, in order to the current .ORG registrants be affected. By any increase in case the community couldn't bring the cap increase down.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Another issue I didn't read in many of the comments that not all .ORG registrants are NGOs hence there are some registrants who might take advance of the current status.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">These are my 2 naive thoughts, <o:p></o:p></p>
<div>
<p class="MsoNormal">Best wishes,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Nadira <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Sat, Apr 27, 2019, 02:21 Kathy Kleiman <a href="mailto:kathy@dnrc.tech" target="_blank">
<kathy@dnrc.tech></a> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class="MsoNormal">Hi Milton, Amr and All, <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Unfortunately, I read the contract differently and fear that the current 10 million .ORG registrants face a difficult (and expensive) future. To Milton's excellent question,
<i>What, exactly, are those “protections for existing registrants”?</i>, the answer is
<i>"not much."</i> Here's the pricing provisions of the .ORG proposed agreement (and I’ve been checking with domain name attorneys all afternoon):
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">2.10(a) Registries provide registrars with a 30 day notice of price increases (registrations).
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">2.10(b) “With respect to renewal of domain name registrants” Registry will provide registrars with “advance written notice of any price increase, and “Registry Operator shall offer
registrars the option to obtain domain name registration renewals at the current price (i.e., the price in place prior to any noticed increase) for periods of one (1) to ten (10) years at the discretion of the registrar, but no greater than ten (10) years.”
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><i>But the option to allow renewal for 1 to 10 years is at the option of the registrar. There’s nothing that requires the registrar to notify registrants that the price of their
.ORG domain names will be going (possibly dramatically) and that the time to renew is now. This is something that is being written about a lot, but I don’t see it in the contract. (Some registrars may let their registrants know early; others may not.) There
is absolutely no requirement of notice to the registrant of a price increase for renewals – for .ORG (or any other registry which has signed this agreement).
</i></b><b><i><span style="font-family:"Cambria",serif"> </span></i></b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">2.10(c) “In addition, Registry Operator must have uniform pricing for renewals of domain name registrations (“Renewal Pricing”). For the purposes of determining Renewal Pricing,
the price for each domain registration renewal must be identical to the price of all other domain name registration renewals at the time of such renewal” with some vague additional language about not wanting to allow abusive and discriminatory renewal pricing.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><i>Thus, PIR’s job is to charge all registrars the same price for new registrations and renewals – whatever that price is and however much PIR wants to charge. This is no guidance
about abusive and discriminatory renewal pricing, no definitions and no clear limitations.
</i></b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Overall, I think Akriti Bopanna’s comment for The Centre for Internet and Society, India, today is right on point:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><b>“Removal of Price Caps</b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">“ICANN’s decision to remove price caps in the .org agreement will only intensify the unfettered power given to Registries with the presumption of renewal. The<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">organization has long heard accusations of engaging in closed door decision making<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">and with such a move that pushes for the rights of registries over registrars, such<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">concerns are only growing. As it is, .org can raise its prices by 10% every year which is<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">unduly generous in itself.5 Giving PIR a limitless ability to increase prices would be<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">doing grave injustice to domain owners who have bought such domains under the<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">assumption of price caps. This is in contrast to the new gTLDS where there is more of<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">a burden on such owners to keep up with the actions of private owners. Legacy<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">gTLDS, unlike the new ones, were not created and sold to private entities but handed<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">over to entities like PIR to maintain them in public interest.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">“Being one of the first TLD’s to be introduced, a multitude of significant websites and<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">therein, initiatives, have their home on the .org domain. As pointed out in the<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">community discussions several times, these domains are used by NGO’s, nonprofit<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">trade associations, individual member associations as well as tax-exempt charities.6<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">ICANN’s justification for proposing these steps is to align legacy gTLD agreements with those of the other newer gTLDS but as argued by the Internet Commerce<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Association;<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.75in">“They have completely different characteristics, history, and ownership<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.75in">structure. It is not acceptable for ICANN to ignore these differences and to<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.75in">propose that they be treated the same.7<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">“Given the longevity of these domains on .org, they have put in substantial investment<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">in maintaining their online presence and cultivating their identity and brand. They<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">are entitled to protection from arbitrary pricing and having the same financial rules<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">as when they originally bought their domains. If such caps are removed then many of<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">these domain owners can find it too expensive to maintain their sites, especially with<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">no guarantee of future price stability as well. A look at the mailing lists is enough to<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">see how small organizations are actively pleading with ICANN to not go ahead with<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">this because it will increase their operational costs.8<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">“None of this is to say that PIR would, in fact, go ahead and increase the prices<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">exorbitantly or at all, however leaving that option to them does not bode well for any<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">party save them. Further, no clear reasoning has been provided for such a step like<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">the need for any additional funds to maintain the domain and in absence of any<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">exceptionally necessary situation, the price cap should continue to exist. Given that<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">PIR is a not-for-profit organization, the rationale to remove caps seems even less<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">unclear than it would be, for say, Verisign. Allowing the removals could very well be<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">opening Pandora’s box with other Registries then demanding removals too. Registries<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">own all the extensions to their domain and lack of a price ceiling only enriches the<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">revenue of, ultimately, the one owner leading to a bigger monopolistic situation than<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">already is currently prevalent.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Needless to say, I support NCSG’s comment too!<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Best, Kathy <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">----------------------------<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Proposed 2019 .ORG Registry Agreement<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">2.10 Pricing for Registry Services.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">(a) With respect to initial domain name registrations, Registry Operator<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">shall provide each ICANN accredited registrar that has executed the Registry-Registrar<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">Agreement for the TLD advance written notice of any price increase (including as a result<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">of the elimination of any refunds, rebates, discounts, product tying or other programs<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">which had the effect of reducing the price charged to registrars, unless such refunds,<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">rebates, discounts, product tying or other programs are of a limited duration that is clearly<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">and conspicuously disclosed to the registrar when offered) of no less than thirty (30)<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">calendar days. Registry Operator shall offer registrars the option to obtain initial domain<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">name registrations for periods of one (1) to ten (10) years at the discretion of the registrar,<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">but no greater than ten (10) years.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">(b) With respect to renewal of domain name registrations, Registry<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">Operator shall provide each ICANN accredited registrar that has executed the Registry-<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">Registrar Agreement for the TLD advance written notice of any price increase (including as<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">a result of the elimination of any refunds, rebates, discounts, product tying, Qualified<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">Marketing Programs or other programs which had the effect of reducing the price charged<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">to registrars) of no less than one hundred eighty (180) calendar days. Notwithstanding the<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">foregoing sentence, with respect to renewal of domain name registrations: (i) Registry<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">Operator need only provide thirty (30) calendar days notice of any price increase if the<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">resulting price is less than or equal to (A) for the period beginning on the Effective Date<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">and ending twelve (12) months following the Effective Date, the initial price charged for<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">registrations in the TLD, or (B) for subsequent periods, a price for which Registry Operator<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">provided a notice pursuant to the first sentence of this Section 2.10(b) within the twelve<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">(12) month period preceding the effective date of the proposed price increase; and (ii)<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">Registry Operator need not provide notice of any price increase for the imposition of the<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">Variable Registry-Level Fee set forth in Section 6.3. Registry Operator shall offer registrars<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">the option to obtain domain name registration renewals at the current price (i.e., the price in place prior to any noticed increase) for periods of one (1) to ten (10) years at the discretion of the registrar,
but no greater than ten (10) years.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">(c) In addition, Registry Operator must have uniform pricing for renewals<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">of domain name registrations (“Renewal Pricing”). For the purposes of determining<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">Renewal Pricing, the price for each domain registration renewal must be identical to the<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">price of all other domain name registration renewals in place at the time of such renewal,<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">and such price must take into account universal application of any refunds, rebates,<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">discounts, product tying or other programs in place at the time of renewal. The foregoing<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">requirements of this Section 2.10(c) shall not apply for (i) purposes of determining<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">Renewal Pricing if the registrar has provided Registry Operator with documentation that<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">demonstrates that the applicable registrant expressly agreed in its registration agreement<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">with registrar to higher Renewal Pricing at the time of the initial registration of the domain<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">name following clear and conspicuous disclosure of such Renewal Pricing to such<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">registrant, and (ii) discounted Renewal Pricing pursuant to a Qualified Marketing Program<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">(as defined below). The parties acknowledge that the purpose of this Section 2.10(c) is to<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">prohibit abusive and/or discriminatory Renewal Pricing practices imposed by Registry<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">Operator without the written consent of the applicable registrant at the time of the initial<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">registration of the domain and this Section 2.10(c) will be interpreted broadly to prohibit<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">such practices. For purposes of this Section 2.10(c), a “Qualified Marketing Program” is a<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">marketing program pursuant to which Registry Operator offers discounted Renewal<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">Pricing, provided that each of the following criteria is satisfied: (i) the program and related<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">discounts are offered for a period of time not to exceed one hundred eighty (180) calendar<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">days (with consecutive substantially similar programs aggregated for purposes of<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">determining the number of calendar days of the program), (ii) all ICANN accredited<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">registrars are provided the same opportunity to qualify for such discounted Renewal<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">Pricing; and (iii) the intent or effect of the program is not to exclude any particular<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">class(es) of registrations (e.g., registrations held by large corporations) or increase the<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">renewal price of any particular class(es) of registrations. Nothing in this Section 2.10(c)<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">shall limit Registry Operator’s obligations pursuant to Section 2.10(b).<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">(d) Registry Operator shall provide public query-based DNS lookup<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">service for the TLD (that is, operate the Registry TLD zone servers) at its sole expense.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">-------------<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Here’s PIR’s current pricing language, from its 2013 agreement:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Section 7.3. Pricing for Domain Name Registrations and Registry Services.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">7.3(a) Pricing. From the Effective Date through 31 December 2013, the price to ICANN-accredited registrars for new and renewal domain name registrations and for transferring a domain
name registration from one ICANN-accredited registrar to another, shall not exceed a total fee of US$8.25 (the "Maximum Service Fee"). Commencing on 1 January 2014, the Maximum Service Fee charged during a calendar year for each annual increment of a new and
renewal domain name registration and for transferring a domain name registration from one ICANN-accredited registrar to another, may not exceed the Maximum Service Fee during the preceding calendar year multiplied by 1.10. The same Service Fee shall be charged
to all ICANN-accredited registrars for new and renewal domain name registrations. Volume discounts and marketing support and incentive programs may be made if the same opportunities to qualify for those discounts and marketing support and incentive programs
is available to all ICANN-accredited registrars.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> 7.3(b) Adjustments to Pricing for Domain Name Registrations. Registry Operator shall provide no less than six months prior notice in advance of any price increase for domain name
registrations and shall continue to offer domain name registrations for periods of up to ten years. Registry Operator is not required to give notice of the imposition of the Variable Registry-Level Fee set forth in Section 7.2(c).<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">----------------------------<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Hi Milton, <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If my understanding of Section 2.10 of the Registry Agreement is correct, registrars can continue to renew existing registrations without an increase in price following an increase in pricing of new registrations by the Registry Operator
(RO) for a period of up to 10 years. Additionally, ROs are required to have uniform pricing for registration renewals. This would mean that all renewal prices would remain unchanged, unless they all change across all registrars simultaneously.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The protections for existing registrants referred to are detailed in 2.10c of the Registry Agreement. The protection is basically that registrants have to agree to renewal prices higher than that of the original registration at the time
of the initial registration. It can’t be forced upon them at a later date. This is meant as a provision to
<i>“</i><i><span style="font-family:"Cambria",serif">prohibit abusive and/or discriminatory Renewal Pricing practices imposed by Registry Operator without the written consent of the applicable registrant at the time of the initial registration of the domain</span>“</i>.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Amr <o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On Apr 25, 2019, at 9:30 PM, Mueller, Milton L <<a href="mailto:milton@GATECH.EDU" target="_blank">milton@GATECH.EDU</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I agree with the letter’s discussion of URS and other RPMs. I agree with Amr that we may need to moderate the language about “unilateral ICANN action” however
because PIR may indeed have gone along with this.<span class="m-6812473584670699400m-3215450327228791716m2074479673144817941apple-converted-space"> </span></span><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">On the issue of price caps, I think we need some factual clarification. If Amr is right and the potential price increases only apply to new registrants, then
there is much less of an issue. The proposed renewal says “</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#333333;background:white">Protections for existing registrants will remain in place, in line with the base registry agreement.“</span><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">What, exactly, are those “protections for existing registrants”?</span><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">MM</span><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif"><o:p></o:p></span></p>
</div>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span class="m-6812473584670699400m-3215450327228791716m2074479673144817941apple-converted-space"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">NCSG-Discuss
<<a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU" target="_blank"><span style="color:purple">NCSG-DISCUSS@LISTSERV.SYR.EDU</span></a>><span class="m-6812473584670699400m-3215450327228791716m2074479673144817941apple-converted-space"> </span><b>On Behalf Of<span class="m-6812473584670699400m-3215450327228791716m2074479673144817941apple-converted-space"> </span></b>Amr
Elsadr<br>
<b>Sent:</b><span class="m-6812473584670699400m-3215450327228791716m2074479673144817941apple-converted-space"> </span>Thursday, April 25, 2019 10:33 AM<br>
<b>To:</b><span class="m-6812473584670699400m-3215450327228791716m2074479673144817941apple-converted-space"> </span><a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU" target="_blank"><span style="color:purple">NCSG-DISCUSS@LISTSERV.SYR.EDU</span></a><br>
<b>Subject:</b><span class="m-6812473584670699400m-3215450327228791716m2074479673144817941apple-converted-space"> </span>Re: [Urgent] [Public Comment] Proposed Renewal of .org Registry Agreement</span><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif"><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif">Hi,<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif">Thanks for sharing this, Rafik. Speaking for myself, I very much agree with the comment on adding the new gTLD Rights Protection Mechanisms (RPMs) to the PIR contract for .org
at this time. As the draft comment rightly points out, these RPMs will not actually be Consensus Policies until after the ICANN Board adopts the recommendations of the Review of all RPMs in all gTLDs PDP Working Group, and should not apply to any of the legacy
gTLDs, including .org. However to characterize the decision to do so as a unilateral ICANN decision is something I’m not sure of. I presume that PIR negotiated this with ICANN before the public comment period began? I might be wrong, as I’m making an assumption
here.<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif">To be clear, the RPMs that would be applicable here (if I’m not mistaken) are the Uniform Rapid Suspension (URS) and the Trademark Claims RPM (part of the Trademark Clearing
House), but not the Sunrise Registrations RPM, obviously, since .org has been around for a while.<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif">Substantively, I don’t believe the URS will be much of an issue, since it is largely deemed to be an unappealing mechanism for use by Trademark holders, as the stats and anecdotal
evidence that has been shared to date indicate. The impact of Trademark Claims, on the other hand, might be very different, and prior to it being reviewed by the RPMs PDP, and adopted as an ICANN policy, I don’t believe adding it to the .org contract in a
renewal is a good move.<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif">On the second issue, where the draft comment disagrees with removing price caps for .org registrations, I’m pretty sure I don’t agree with the rationale or conclusion. I don’t
believe PIR’s status as a non-profit entity justifies this. IMO, it imposes unreasonable obligations on PIR that other Registry Operators are not subject to, so effectively penalizing PIR for its status, and its continued mission to<span class="m-6812473584670699400m-3215450327228791716m2074479673144817941apple-converted-space"> </span><i>“support
many excellent causes”</i>, as pointed out in the draft.<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif">Furthermore, there is little to no evidence that I can see (at least in the draft) that registrants of .org domain names will be negatively impacted by removal of the price
cap. My understanding is that this will mainly impact new registrations, not existing ones, but this isn’t addressed at all.<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif">To me, PIR needs to set its own price taking in to consideration their own consumer base. If they make bad decisions that drive their customers away, I don’t believe this will
negatively impact registrants as much as it would PIR itself, especially considering that there are over a thousand gTLDs for registrants to migrate to, should they choose to do so.<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif">Thanks.<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif"> <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"TrebuchetMS",serif">Amr</o<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<pre>-- <o:p></o:p></pre>
<pre>Kathy Kleiman<o:p></o:p></pre>
<pre>Visiting Scholar, Center for Information Technology, Princeton University<o:p></o:p></pre>
<pre>President (on leave), Domain Name Rights Coalition<o:p></o:p></pre>
<div id="m_-6812473584670699400DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2">
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoNormalTable" border="1" cellspacing="3" cellpadding="0" style="border:none;border-top:solid #D3D4DE 1.0pt">
<tbody>
<tr>
<td width="57" style="width:41.25pt;border:none;padding:9.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon" target="_blank"><span style="border:solid windowtext 1.0pt;padding:0in;text-decoration:none"><img border="0" width="46" height="29" style="width:.4791in;height:.3055in" id="_x0000_i1025" src="cid:image001.jpg@01D4FD3A.9FA88920" alt="Image removed by sender."></span></a><o:p></o:p></p>
</td>
<td width="406" style="width:352.5pt;border:none;padding:9.0pt .75pt .75pt .75pt">
<p class="MsoNormal" style="line-height:13.5pt"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#41424E">Virus-free.
<a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link" target="_blank">
<span style="color:#4453EA">www.avast.com</span></a> <o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</blockquote>
</div>
</div>
</body>
</html>