<html 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=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 5 4 2 2 2 2 2 4;}
@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:Roboto;
panose-1:2 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">In fairness, Bill, the contracted parties spend tons of cash to combat DNS abuse. Of course, we’ve just issued advice to the board suggesting they could do more, such as implementing the AI based solution used by .UK and .EU which look
really promising. So it’s a wee bit disingenuous to suggest that they WANT all the conflicts as they end up getting wrapped up in complaints about them all the time and I suspect they wish they weren’t there because they lose money, not make money, on them.
That we heard from Graham from Twocows and it makes sense. Once they “touch a domain” they’re losing money, he suggested, and I don’t have any reason to question him. I’d much rather work
<i>with</i> them to find a better way to go after the bad guys.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="border:none;padding:0in"><b>From: </b><a href="mailto:cpwg@icann.org">Bill Jouris via CPWG</a><br>
<b>Sent: </b>Monday, January 6, 2020 12:15 PM<br>
<b>To: </b><a href="mailto:lbweissinger@protonmail.com">Laurin B Weissinger</a><br>
<b>Cc: </b><a href="mailto:cpwg@icann.org">cpwg@icann.org</a><br>
<b>Subject: </b>Re: [CPWG] Verisign</p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica",sans-serif">Laurin, <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica",sans-serif">I'm not sure it is accurate to characterize the situation as the registries as "not having their houses in order." As for-profit companies, their duty is to their owners.
And the technical term of a situation requiring lots of defensive registrations is "gold mine" -- multiple sales, with only a single customer to deal with. And, for the most part, you can probably sell hosting services for the re-direct to the real website
as well. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica",sans-serif">From the point of view of the users, and of the Internet generally, simply blocking those potential abusive registrations is clearly the way to go. But for the registries?
All their incentive is to have as many potential conflicts as possible. Easy sales.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica",sans-serif">Bill Jouris<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:12.0pt;font-family:"Helvetica",sans-serif"><o:p> </o:p></span></p>
<div id="ydpee060786yiv8152429487ymail_android_signature">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica",sans-serif"><a href="https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature" target="_blank">Sent
from Yahoo Mail on Android</a><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Helvetica",sans-serif"><o:p> </o:p></span></p>
</div>
<div id="yiv8152429487yqt56901">
<blockquote style="margin-left:0in;margin-right:0in;margin-bottom:15.0pt">
<div>
<div>
<p class="MsoNormal"><span style="font-family:Roboto;color:#6D00F6">On Mon, Jan 6, 2020 at 8:50 AM, Laurin B Weissinger<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Roboto;color:#6D00F6"><lbweissinger@protonmail.com> wrote:<o:p></o:p></span></p>
</div>
</div>
<div style="border:none;border-left:solid #6D00F6 1.0pt;padding:0in 0in 0in 15.0pt;margin-top:7.5pt">
<p class="MsoNormal" style="margin-bottom:12.0pt">Dear all, <br>
<br>
> The only obvious defense, for registrants who want their customers to arrive reliably at their website, will be defensive registrations. Lots of defensive registrations. (I did a quick calculation for Citi Bank. 4 letter domain name. Close to 300 readily
confusable variations. Longer names would have more, of course.)<br>
<br>
It might very well be that this is an issue to start with? SSR2 will likely recommend measures to be taken here.<br>
<br>
In general though, it is quite ridiculous if you think about it — I have to pay for multiple domains to protect myself because contracted parties do not have their house in order… (Obviously, I am overstating slightly, on purpose)<br>
<br>
All the best<br>
Laurin <br>
<br>
<br>
<o:p></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal" style="margin-bottom:15.0pt"><br>
> On Jan 6, 2020, at 17:45, Jonathan Zuck <<a href="mailto:JZuck@innovatorsnetwork.org" target="_blank">JZuck@innovatorsnetwork.org</a>> wrote:<br>
> <br>
> Bill,<br>
> That's certainly an interesting take that I hadn't thought about. The reasoning from Evan, that make sense to me, is that higher prices would make it less likely that people would register the fraudulent names in the first place, making defensive registrations
less necessary. Of course, for truly premium names a small price hike will NOT make a difference but at volume it might. I'll noodle that more. My job is facilitator here so my opinion doesn't really matter. I'm just not interested in a knee jerk emotional
response from At-Large.<br>
> Jonathan<br>
> <br>
> From: Bill Jouris <<a href="mailto:b_jouris@yahoo.com" target="_blank">b_jouris@yahoo.com</a>><br>
> Sent: Monday, January 6, 2020 11:37 AM<br>
> To: Jonathan Zuck <<a href="mailto:JZuck@innovatorsnetwork.org" target="_blank">JZuck@innovatorsnetwork.org</a>>; Nat Cohen <<a href="mailto:ncohen@telepathy.com" target="_blank">ncohen@telepathy.com</a>>; Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca" target="_blank">alan.greenberg@mcgill.ca</a>><br>
> Cc: <a href="mailto:cpwg@icann.org" target="_blank">cpwg@icann.org</a> <<a href="mailto:cpwg@icann.org" target="_blank">cpwg@icann.org</a>><br>
> Subject: Re: [CPWG] Verisign<br>
> <br>
> Jonathan, <br>
> <br>
> In your last paragraph, you say: <br>
> "Individual end users don’t care about the wholesale price of domains. They care about whether they’re getting to the site they intend, that the site won’t infect their machine with malware, that the site won’t commit fraud on them, etc. etc...."
<br>
> <br>
> But that does give individual end users a stake in domain name prices. Thanks to the IDN effort, we are about to see a spike in the potential for DNS abuse -- specifically the easy opportunity (thanks to ICANN's approach) to generate quite misleading domain
names. <br>
> <br>
> The only obvious defense, for registrants who want their customers to arrive reliably at their website, will be defensive registrations. Lots of defensive registrations. (I did a quick calculation for Citi Bank. 4 letter domain name. Close to 300 readily
confusable variations. Longer names would have more, of course.)<br>
> <br>
> If the price of registrations goes up, they will do fewer defensive registrations. Which means end users will have more trouble reliably getting where they want to go. Which, I submit, we do care about.<br>
> <br>
> Bill Jouris <br>
> <br>
> Sent from Yahoo Mail on Android<br>
> <br>
> On Mon, Jan 6, 2020 at 7:23 AM, Jonathan Zuck<br>
> <<a href="mailto:JZuck@innovatorsnetwork.org" target="_blank">JZuck@innovatorsnetwork.org</a>> wrote:<br>
> _______________________________________________<br>
> CPWG mailing list<br>
> <a href="mailto:CPWG@icann.org" target="_blank">CPWG@icann.org</a><br>
> <a href="https://mm.icann.org/mailman/listinfo/cpwg" target="_blank">https://mm.icann.org/mailman/listinfo/cpwg</a><br>
> <br>
> _______________________________________________<br>
> 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">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>