<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">Michael:</div><div class="gmail_default" style="font-family:tahoma,sans-serif">There are a few of us who long ago read the same bit of prose you did and interpreted a much wider ICANN role in the Internet ecosystem, for example, a role in provisioning a wider range of public goods and services. [For those of us who are ICT4D practitioners situated in the global South and concerned with so-called "end user interests", access and cost of access to the DNS are more compelling than not.]</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">I hate to tell you it is the orthodoxy of ICANN, the public benefit corporation, aided and abetted by a variety of interests resident in the ICANN [multistakeholder] community who say otherwise. </div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">The crowning argument is that stability and security and resilience are finely graded and represent a very narrow remit. </div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">I give you even money the 'smart money' thinks blockchain-based naming systems, such as this ENS, is just another alt that is doomed to failure. The obvious strategic response is to starve it of oxygen by not collaborating with [DNS root] integration initiatives. I actually think the orthodox are more concerned that ICANN-accredited registrars dabbling in the alt naming system trade is by far, the greater threat.</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">Carlton</div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><br>==============================<br><i><font face="comic sans ms, sans-serif">Carlton A Samuels</font></i><br><font face="comic sans ms, sans-serif"><i>Mobile: 876-818-1799<br><font color="#33CC00">Strategy, Process, Governance, Assessment & Turnaround</font></i></font><br>=============================</div></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 27 Sept 2022 at 10:43, mike <a href="http://palage.com">palage.com</a> via CPWG <<a href="mailto:cpwg@icann.org">cpwg@icann.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="msg6474018389689033682">
<div lang="EN-US" style="overflow-wrap: break-word;">
<div class="m_6474018389689033682WordSection1">
<p class="MsoNormal">Hello All,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I would encourage everyone to listen to the recording. However, I would actually start with the third presentation by CIRA (.CA). In my personal opinion that was the best of the three.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Evan I am going to push back. I think At-Large is probably the optimal place to discuss alternative root names. Per the At Large Website – “At-Large Community acts on the interests of Internet users.” I would argue that At Large is not
limited to just Root Zone domain names and IP addresses. Moreover, when you look at ICANN’s articles of incorporation, I think it provides a much larger mandate that just the coordination of domain names and IP addresses:<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-left:0.5in">pursue the charitable and public purposes of lessening the burdens of government and promoting the global public interest in the operational stability of the Internet by carrying out the mission set forth in the
bylaws of the Corporation (“<strong><span style="font-family:Calibri,sans-serif">Bylaws</span></strong>”). Such global public interest may be determined from time to time. Any determination of such global public interest shall be made by the multistakeholder
community through an inclusive bottom-up multistakeholder community process. <u></u>
<u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Best regards,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Michael<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class="MsoNormal"><b>From:</b> CPWG <<a href="mailto:cpwg-bounces@icann.org" target="_blank">cpwg-bounces@icann.org</a>> <b>On Behalf Of </b>
Chokri Ben Romdhane via CPWG<br>
<b>Sent:</b> Tuesday, September 27, 2022 11:10 AM<br>
<b>To:</b> CPWG <<a href="mailto:cpwg@icann.org" target="_blank">cpwg@icann.org</a>>; MOULOUD KHELIF <<a href="mailto:kelif@hotmail.com" target="_blank">kelif@hotmail.com</a>><br>
<b>Subject:</b> Re: [CPWG] Are Blockchain Domains within the Mission of ICANN - WAS RE: Questions to the board about distributed DNS<u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">Dear Friends,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Please find the record of the <a href="https://icann.zoom.us/rec/play/4ZhSDuzFnVqw66kYgnTuHdDzi_RH0IFCKqKuAzmmcFy7xUPX6aT1op_nmghEdsEV5jxGYZ_sInYl2Oow.4hEm0h7LHhMj6obE?startTime=1663743821000&_x_zm_rtaid=pNBkHu--SL-KGy5yfLrRoA.1664285662735.722e2ee0a7cb19b493f616b538af3f5b&_x_zm_rhtaid=161" target="_blank">Emerging
Identifier Technologies</a> session , held during the ICANN75 meeting, it provides some use cases of the emerging identifiers technologie. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Thank you <a href="mailto:kelif@hotmail.com" target="_blank">@MOULOUD KHELIF</a> for the reminder.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Friendly regards<u></u><u></u></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal">Chokri<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12pt"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">Le sam. 27 août 2022 à 19:17, Evan Leibovitch <<a href="mailto:evan@telly.org" target="_blank">evan@telly.org</a>> a écrit :<u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal">On Thu, Aug 25, 2022 at 5:39 AM Chokri Ben Romdhane <<a href="mailto:chokribr@gmail.com" target="_blank">chokribr@gmail.com</a>> wrote:<u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal">But be aware if you confirm that the collision issues is/will never happened , as you have mentioned in your previous mail, and cross your finger that the regular DNS market will continue to attract more customers, compared to those NFT,
Blockchain TLDs considering the ease of DNS management and security they are conferred to end users.<u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)">Hi again,<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)">You made one fatal error in your assessment above: Internet end-users are not registrants.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)">End users don't care about DNS management, and the security THEY seek is access to registrant details in the case of domains used for abuse.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)">The "security" you mention protects registrants and works against the interests of end-users.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12pt"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)">It's totally possible that the hubris of DNS alternatives may lead to collisions, but end-users will never see the effect of that, Browsers continue
to use the ICANN root and to date have never seen the benefit of pointing to alternames. Plus, two of the biggest browser makers, Google and Microsoft, have a deep vested interest in obstructing any alternative DNS. Any alternate DNS hoping to be successful
would need to create its own browser, which is what the TOR project did.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)">So even if alternative DNSs create TLDs that duplicate ICANN's they will never present any collision or confusion to end-users. The only losers will be registrants in the alternate
systems. I have zero pity for them and they are certainly not ALAC's concern or even ICANN's.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)">Cheers,<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)">- Evan<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)"><u></u> <u></u></span></p>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<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" rel="noreferrer" 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" rel="noreferrer" target="_blank">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">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>