<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
My answers in line below.<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 16.11.2019, at 17:41, Nat Cohen <<a href="mailto:ncohen@telepathy.com" class="">ncohen@telepathy.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div class="gmail_default" style="font-size:small">Hi Roberto,</div>
<div class="gmail_default" style="font-size:small"><br class="">
</div>
<div class="gmail_default" style="font-size:small">Could you further explain your view that a serious rise in the price will cause a substantial drop in the renewal rates?</div>
<div class="gmail_default" style="font-size:small"><br class="">
</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>It is public information that large part of .org registrations do not resolve - that means that they are in the hands of speculators, or are defensive registrations, or other. If not all .org registrants are locked-in, like the ones who have developed
a business over their domain name, that means that they are more price-sensitive than the ones that are locked-in.</div>
<div><br class="">
</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div dir="ltr" class="">
<div class="gmail_default" style="font-size:small">My understanding is that Ethos Capital will be able to raise renewal prices substantially and that active nonprofits will be forced to pay the increased renewal rates, because as you point out many of the 10M
registrants are locked in to their use of .org.</div>
<div class="gmail_default" style="font-size:small"><br class="">
</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>Many, true, several millions of them. But even if only 20% are not locked in, that makes 2M names anyway. Still enough income, true, but what I am trying to say is that indefinite raise of the price is no good long term strategy.</div>
<div><br class="">
</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div dir="ltr" class="">
<div class="gmail_default" style="font-size:small">I believe the challenge in moving to a different domain name is particularly great for nonprofits, in large part because those who engage with the nonprofit online, whether by making donations or making use
of their services, must have a high degree of trust that they are dealing with the actual nonprofit and not with an imposter seeking to defraud them. That level is trust is based on the nonprofit's long and continued use of its .org domain name. That trust
level would be lost if the non-profit were forced to move to a different extension.</div>
<div class="gmail_default" style="font-size:small"><br class="">
</div>
<div class="gmail_default" style="font-size:small">Moving to a different domain name does not merely involve porting content over to a different hosting service. It means changing the email address for every person at that organization, and updating the address
books of everyone who needs to communicate by email with that organization. It means the loss of all back links in the articles written about the organization. It means the loss of search engine ranking, meaning that those searching for the organization
online will have a harder time finding the organization, especially if it moves from the more intuitive and familiar .org extension to a less familiar extension. All marketing materials, banners, business cards, pamphlets and brochures would need to be reprinted
with the new domain name.</div>
<div class="gmail_default" style="font-size:small"><br class="">
</div>
<div class="gmail_default" style="font-size:small">Most organizations would willingly (or be forced to) spend tens of thousands of dollars to avoid such a severely harmful and expensive disruption to their organization. The harm incurred in moving domain names
leaves Ethos plenty of room to raise .org prices on active nonprofits, as those nonprofits would have no real choice but to pay the inflated rates.</div>
<div class="gmail_default" style="font-size:small"><br class="">
</div>
<div class="gmail_default" style="font-size:small">Even if you are correct that a serious rise in price will cause a substantial drop in the renewal rates, Ethos will still have the financial incentive to sharply increase prices. The math on this is quite
simple. PIR generates around $100 million annually in revenues from 10 million registrants paying around $10 per year for their .org domain names. If an increase to $20 causes renewals to drop by 20%, PIR would generate around $160 million annually in revenues
from 8 million registrants paying $20 per year, a $60 million increase in revenue. If an increase to $100 causes renewals to drop by 50%, PIR would generate revenues of around $500 million annual from 5 million registrants paying $100 per year, a $400 million
increase in revenues.</div>
<div class="gmail_default" style="font-size:small"><br class="">
</div>
<div class="gmail_default" style="font-size:small">While some domain investors may fail to renew their .org domain names as prices rise, .org domain names are a negligible portion of most domain investors' portfolios. Nonprofits are, on the other hand, the
predominant users of .org domain names. For the reasons given above, the nonprofits using .org will almost certainly be forced to pay the higher renewal rates as renewal rates reach $100 per year and higher. Even if the registrant base shrinks by half, a
$100 per year renewal rate would still allow Ethos to extract an additional $400 million per year in revenues from the donations that have been contributed to the nonprofits to further their public service missions, but instead will be diverted to increasing
the profits of the private equity funders of Ethos.</div>
<div class="gmail_default" style="font-size:small"><br class="">
</div>
<div class="gmail_default" style="font-size:small">But the harms described above are just the start of the harms that will be suffered by a nonprofit that gives up its .org address.</div>
<div class="gmail_default" style="font-size:small"><br class="">
</div>
<div class="gmail_default" style="font-size:small">The biggest flaw in the argument that nonprofits can easily move to another domain extension is that
<b class="">the nonprofit cannot abandon its existing .org domain name, </b>and must continue paying renewal fees even after it has moved to a new domain extension. To avoid paying rising .org renewal fees, the nonprofit must not only move to a new domain
name, it must also <b class="">abandon</b> its existing .org domain name. This means that organizations like <a href="https://www.lightthenight.org/" class="">https://www.lightthenight.org/</a>, who organize the walks against Leukemia, <a href="https://marthastable.org/" class="">https://marthastable.org/</a>,
which provides food and shelter to those in need, as well as much larger organizations such as
<a href="http://NPR.org" class="">NPR.org</a> and <a href="http://RedCross.org" class="">
RedCross.org</a>, must not only move to a different domain name, they must allow their registration of their long standing domain names to terminate and they must allow someone else to because the registrant of
<a href="http://LighttheNight.org" class="">LighttheNight.org</a> or the <a href="http://RedCross.org" class="">
RedCross.org</a>. That would be the only way to stop paying the higher renewal fees. Someone else could register
<a href="http://LighttheNight.org" class="">LighttheNight.org</a> and start asking for donations. Or a gun-control group could register
<a href="http://NRA.org" class="">NRA.org</a>, or an anti-abortion group could register
<a href="http://PlannedParenthood.org" class="">PlannedParenthood.org</a>. DNW recently wrote up an example of an expired website being registered and repurposed by a group with a contrary mission - <a href="https://domainnamewire.com/2019/10/17/oops-if-you-dont-renew-your-domain-name-this-could-happen/" class="">https://domainnamewire.com/2019/10/17/oops-if-you-dont-renew-your-domain-name-this-could-happen/</a>.</div>
<div class="gmail_default" style="font-size:small"><br class="">
</div>
<div class="gmail_default" style="font-size:small">Nonprofits therefore are truly locked in. To escape rising .org fees they must not only move to a different domain extension, they must also abandon their .org domain name, and this they cannot do.</div>
<div class="gmail_default" style="font-size:small"><br class="">
</div>
<div class="gmail_default" style="font-size:small">Even if they were to move - where would they move to? There are some domain name spaces that are managed for the benefit of registrants, not of the registries, but none of these name spaces are managed by
ICANN. For instance, .org registrants could flee to .de, the German country code, which is run by a nonprofit consortium of registrars at a cost to registrants of around 1 Euro per year. But moving to a .de would not be that desirable and would cause considerable
confusion. Perhaps the nonprofits could move to .foundation, a new gTLD operated by Donuts, but that is of course on the new gTLD agreement without price caps. Donuts, reportedly controlled by the same folks who control Ethos Capital, would have the same
ability to raise prices without limit that PIR now has without .org. Perhaps the nonprofit could move to a .charity, to a .gives or to a .church domain extension. Yet all those possible alternatives are operated by Donuts too. There is no safe sanctuary
where the nonprofits can go and be on a meaningful gTLD domain name that offers stable pricing. ICANN has taken the longstanding stable .org name space that was entrusted to it, and has destabilized it. The big money behind Ethos Capital gets richer. The
nonprofit community is deprived of essential funding and the suffering of those who rely on the work of the nonprofit community increases.</div>
<div class="gmail_default" style="font-size:small"><br class="">
</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>I do not disagree with what you say, except for the fact that milking the cow to the end - that means getting the most out of the current situation regardless the implications on image, adoption of alternative opportunities, fidelity of the channel, and
so on - is a good strategy only when the marketplace is towards the end of its lifetime. Although it goes without any doubt that the current situation is far from being the bonanza of a decade ago, I would argue that the domain name market is not about to
die - as .com growth is proving: the only challenge is to find a winning strategy, and that requires more thinking than just blunt doubling of prices.</div>
<div>Cheers,</div>
<div>Roberto</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div dir="ltr" class="">
<div class="gmail_default" style="font-size:small"><br class="">
</div>
<div class="gmail_default" style="font-size:small">Regards,</div>
<div class="gmail_default" style="font-size:small"><br class="">
</div>
<div class="gmail_default" style="font-size:small">Nat Cohen</div>
<div class="gmail_default" style="font-size:small"><br class="">
</div>
<div class="gmail_default" style="font-size:small"><br class="">
</div>
</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sat, Nov 16, 2019 at 4:10 AM Roberto Gaetano <<a href="mailto:roberto_gaetano@hotmail.com" class="">roberto_gaetano@hotmail.com</a>> wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div style="overflow-wrap: break-word;" class="">Hi all
<div class="">I am not sure whether ICANN has the power to stop the deal, because what is sold is not the .org contract but the whole PIR company. This said, it is by and large irrelevant because I believe that ICANN would not stand up to block the transfer
even if it could.</div>
<div class="">I agree with most of what the article says, first and foremost that one thing was lifting the price cap for a non-profit that claims to be operating in the public interest, and another thing is allowing an investment fund to have free hand in
deciding the prices in a situation where 10M customers are locked in. This said, I remain convinced that a serious rise in the price will cause a substantial drop in the renewal rates - although a small raise would not affect substantially the DUM base. But
a small raise was already allowed, under some circumstances, by the previous contract.</div>
<div class="">Cheers,</div>
<div class="">Roberto</div>
<div class=""><br class="">
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">On 16.11.2019, at 00:10, Carlton Samuels <<a href="mailto:carlton.samuels@gmail.com" target="_blank" class="">carlton.samuels@gmail.com</a>> wrote:</div>
<br class="">
<div class="">
<div dir="ltr" class="">
<div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large">
The Internet Commerce Association has gone nuclear on the .org deal. </div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large">
<br class="">
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large">
Somewhat lefthandedly but for the first time at last, I see in print what I have long believed; it is ICANN who is the 'effective<i class=""> owner</i>' of all domain names, dictionary word or no, every character set known and unknown, heretofore and after,
chattels and all! Damn, whoever thought this one up.....!!</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large">
<br class="">
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large">
<a href="https://domainnamewire.com/2019/11/15/ica-asks-icann-to-block-org-private-equity-deal-in-damning-letter/" target="_blank" class="">https://domainnamewire.com/2019/11/15/ica-asks-icann-to-block-org-private-equity-deal-in-damning-letter/</a> <br class="">
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large">
<br class="">
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:large">
Carlton</div>
<div class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div class="">
<div dir="ltr" class="">
<div class=""><br class="">
==============================<br class="">
<i class=""><font face="comic sans ms, sans-serif" class="">Carlton A Samuels</font></i><br class="">
<font face="comic sans ms, sans-serif" class=""><i class="">Mobile: 876-818-1799<br class="">
<font color="#33CC00" class="">Strategy, Process, Governance, Assessment & Turnaround</font></i></font><br class="">
=============================</div>
</div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br class="">
CPWG mailing list<br class="">
<a href="mailto:CPWG@icann.org" target="_blank" class="">CPWG@icann.org</a><br class="">
<a href="https://mm.icann.org/mailman/listinfo/cpwg" target="_blank" class="">https://mm.icann.org/mailman/listinfo/cpwg</a><br class="">
<br class="">
_______________________________________________<br class="">
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" target="_blank" class="">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank" class="">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing,
setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on._______________________________________________<br class="">
registration-issues-wg mailing list<br class="">
<a href="mailto:registration-issues-wg@atlarge-lists.icann.org" target="_blank" class="">registration-issues-wg@atlarge-lists.icann.org</a><br class="">
<a href="https://mm.icann.org/mailman/listinfo/registration-issues-wg" target="_blank" class="">https://mm.icann.org/mailman/listinfo/registration-issues-wg</a><br class="">
<br class="">
_______________________________________________<br class="">
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" target="_blank" class="">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank" class="">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing,
setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</div>
</blockquote>
</div>
<br class="">
</div>
</div>
_______________________________________________<br class="">
CPWG mailing list<br class="">
<a href="mailto:CPWG@icann.org" target="_blank" class="">CPWG@icann.org</a><br class="">
<a href="https://mm.icann.org/mailman/listinfo/cpwg" rel="noreferrer" target="_blank" class="">https://mm.icann.org/mailman/listinfo/cpwg</a><br class="">
<br class="">
_______________________________________________<br class="">
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank" class="">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank" class="">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including
unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</blockquote>
</div>
</div>
</blockquote>
</div>
<br class="">
</body>
</html>