April 2023 - CPWG - lists.icann.org

Re: [CPWG] Are Blockchain Domains within the Mission of ICANN - WAS RE: Questions to the board about distributed DNS
by Chokri Ben Romdhane Oct. 18, 2024

Oct. 18, 2024

Dear Friends, Please find the record of the Emerging Identifier Technologies <https://icann.zoom.us/rec/play/4ZhSDuzFnVqw66kYgnTuHdDzi_RH0IFCKqKuAzmmcFy7…> session , held during the ICANN75 meeting, it provides some use cases of the emerging identifiers technologie. Thank you @MOULOUD KHELIF <kelif(a)hotmail.com> for the reminder. Friendly regards Chokri Le sam. 27 août 2022 à 19:17, Evan Leibovitch <evan(a)telly.org> a écrit : > On Thu, Aug 25, 2022 at 5:39 AM Chokri Ben Romdhane <chokribr(a)gmail.com> > wrote: > > >> 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. >> > > Hi again, > > You made one fatal error in your assessment above: Internet end-users are > not registrants. > > 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. > The "security" you mention protects registrants and works against the > interests of end-users. > > 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. > > 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. > > Cheers, > - Evan > >

11 33

Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 03 May 2023 at 13:00 UTC
by ICANN At-Large Staff May 2, 2023

May 2, 2023

***If you require a dial out or need to state an apology, please contact At-Large staff at staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> with your preferred number*** Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 03 May 2023 at 13:00 UTC for 90 mins. For other times: https://tinyurl.com/45bae8jk The agenda (to be updated) and call details can be found at: https://community.icann.org/x/KolXDg Zoom Room: https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09 / Passcode: #CPWG2345* Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN ADIGO Conference Bridge: EN, ES & FR: 3535 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind Regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

2 2

At-Large Consolidated Policy Working Group (CPWG)
by ICANN Policy Calendar April 27, 2023

April 27, 2023

***If you require a dial out or need to state an apology, please contact At-Large staff at staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> with your preferred number*** Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 03 May 2023 at 13:00 UTC for 90 mins. For other times: https://tinyurl.com/45bae8jk The agenda (to be updated) and call details can be found at: https://community.icann.org/x/KolXDg Zoom Room: https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09 / Passcode: #CPWG2345* Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN ADIGO Conference Bridge: EN, ES & FR: 3535 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind Regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 26 April 2023 at 19:00 UTC
by ICANN At-Large Staff April 26, 2023

April 26, 2023

***If you require a dial out or need to state an apology, please contact At-Large staff at staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> with your preferred number*** Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 26 April 2023 at 19:00 UTC for 90 mins. For other times: https://tinyurl.com/2p8mwpx9 The agenda and call details can be found at: https://community.icann.org/x/YYVXDg Zoom Room: https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09 / Passcode: #CPWG2345* Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN ADIGO Conference Bridge: EN, ES & FR: 3535 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind Regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 3

REMINDER / Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 26 April 2023 at 19:00 UTC
by ICANN At-Large Staff April 26, 2023

April 26, 2023

***If you require a dial out or need to state an apology, please contact At-Large staff at staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> with your preferred number*** Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 26 April 2023 at 19:00 UTC for 90 mins. For other times: https://tinyurl.com/2p8mwpx9 The agenda and call details can be found at: https://community.icann.org/x/YYVXDg Zoom Room: https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09 / Passcode: #CPWG2345* Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN ADIGO Conference Bridge: EN, ES & FR: 3535 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind Regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

Something of actual importance to end-users
by Evan Leibovitch April 21, 2023

April 21, 2023

https://freespeech.com/2023/04/19/red-alert-icann-and-verisign-proposal-wou… Let's briefly put aside the boasting about ALAC's incremental involvement in the trivial agendas set by ICANN's vested interests. Here's a real example of an issue that can negatively affect end-users. The aims of the proposed modification may be laudable, but there's too much room for arbitrariness and too much potential to curb political speech unwanted by a government. BTW ... Why was this not already flagged by ALAC as cause for concern? Why did I have to find out about this in the media rather than from the inside. Was ALAC intending to ignore it? This is EXACTLY what I'm talking about. ALAC is obsessed with the trivial and the self-absorbed, but asleep during the issues that actually affect the constituency we're supposed to serve. Does ALAC have what it takes to fight for the public interest on something that actually matters? Is it capable of balancing the various intertwining issues? If the CPWG meets on this issue I'll be there. Evan Leibovitch, Toronto Canada @evanleibovitch / @el56

7 18

RFC: The Debate on Policy and Mechanism Again
by gopal April 20, 2023

April 20, 2023

Dear All, Last week, during the CPWG meeting, the sharp discrimination between policy and mechanism was mooted again. To the best of my knowledge, the separation of policy and mechanism stems from design principle in computer science. I subscribe to this principle. Please consider these working definitions. Policy: a set of ideas or a plan of what to do. Mechanism: a process, technique, or system for achieving a result. I agree that policy is being made by those who had a through grounding in the related mechanism and so it should work most of the times. However, getting to the policy from the mechanism (s) is becoming arbitrarily difficult. The very nature of computation as an idea is the primary cause for this. Bringing policy and mechanism together has the following concerns: #1. It makes policy rigid and harder to change in response to user requirements. #2. Trying to change policy has a strong tendency to destabilize the mechanisms. If we do not bring them together, the exercise will always be fragmented with the policy becoming a veneer to indicate a sort of binding of several mechanism. For the internet governance, it is always a tussle between keeping Policy and Mechanism "together and separate". The coming togeher can happen only if one includes the design. Hence, I suggest that "Technology" and "Managerial" concenrs may be separated and we work on interoprable interfaces. We may then have the "One World One Internet" with more tangible outcomes for all the stakeholders. Your comments are most welcome. Sincerely, Gopal T V 0 9840121302 https://vidwan.inflibnet.ac.in/profile/57545 https://www.facebook.com/gopal.tadepalli ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Dr. T V Gopal Professor Department of Computer Science and Engineering College of Engineering Anna University Chennai - 600 025, INDIA Ph : (Off) 22351723 Extn. 3340 (Res) 24454753 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

16 26

At-Large Consolidated Policy Working Group (CPWG)
by ICANN Policy Calendar April 19, 2023

April 19, 2023

***If you require a dial out or need to state an apology, please contact At-Large staff at staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> with your preferred number*** Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 26 April 2023 at 19:00 UTC for 90 mins. For other times: https://tinyurl.com/2p8mwpx9 The agenda and call details can be found at: https://community.icann.org/x/YYVXDg Zoom Room: https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09 / Passcode: #CPWG2345* Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN ADIGO Conference Bridge: EN, ES & FR: 3535 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind Regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

Bulk Registrations, missing data and assumptions?
by John McCormac April 19, 2023

April 19, 2023

Just reading through the agenda for today's meeting and the section on DNS Abuse. DNSAI, in the letter to Sebastien Ducos, mentioned that it had no data on bulk registrations. This is not surprising as much of the bulk registration activity took place before the founding of the DNSAI. It still happens. The problem with bulk registration is that it is intrinsically linked with certain types of websites and other activity such as spam and malware. A few years ago, there was an effort by CENTR and a few European registries to try to classify web usage (I think that there was also an Registry Registrar Data Group effort (RRDG) which suffered from a similar lack of data.). Some of it followed the inaccurate attempt to measure usage that was naively initiated by the CCT as an input to its deliberations. Of the supposedly developed sites in the new gTLDs mentioned in that CCT document, approximately 80% of the domain names had been deleted by the time CCT published its final report. The five year deletion rate for heavily discounted registrations is less than 1%. That means that just over 99% of bulk registrations will not be in the same gTLD's zone file five years later. As a numerical example, .LOAN had 1,866,032 registrations in February 2018. In February 2023, 2,227 of these domain names were still in the zone. That's approximately 0.12% of the February 2018 domain names. Measuring web usage is a lot more complex than merely breaking down websites by whether they are "parking" pages or have "rich" content. Such crude methodologies don't work with the bulk registrations problem. The ccTLDs are highly concentrated markets while gTLDs are often composite markets (registations from hundreds of countries) with a small global market. As a result of this, ccTLDs and gTLDs will have an overlap on some types of DNS abuse and will also have concentrations of some types. With the data, bulk registrations are apparent as spikes in new registation volume followed approximately a year later by a spike in deletions. (I've run this analysis back to January 2004 on the legacy gTLDs and also on the new gTLDs back to 2014.) The term "bulk registrations" is problematic because it ignored the primary economic factor: heavily discounted registrations. Without these heavily discounted registrations, the economic model of bulk registrations would be much less viable. Some of the references quoted by the DNSAI in the letter mentioned above, such as the Interisle report, are quite good. But bulk registrations aren't typically a ccTLD issue (apart from repurposed ccTLDs). This means that much of the analysis based on ccTLDs is useless in this context. Bulk registrations are very much a shifting target and that makes it difficult to measure their effects on the webscape with a good methodology and impossible with a crude one. The phrase "bulk registrations" does seem to be a problematic one. (There seems to be some pushback from the registries and registrars on this. Apart from measuring the effects with the data, it might be necessary to reframe the issue. Regards...jmcc -- ********************************************************** John McCormac * e-mail: jmcc(a)hosterstats.com MC2 * web: http://www.hosterstats.com/ 22 Viewmount * Domain Registrations Statistics Waterford * Domnomics - the business of domain names Ireland * https://amzn.to/2OPtEIO IE * Skype: hosterstats.com ********************************************************** -- This email has been checked for viruses by Avast antivirus software. www.avast.com

1 1

REMINDER / Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 19 April 2023 at 13:00 UTC
by ICANN At-Large Staff April 19, 2023

April 19, 2023

***If you require a dial out or need to state an apology, please contact At-Large staff at staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> with your preferred number*** Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 19 April 2023 at 13:00 UTC for 90 mins. For other times: https://tinyurl.com/jxunr6b3 The agenda and call details can be found at: https://community.icann.org/x/BYJXDg Zoom Room: https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09 / Passcode: #CPWG2345* Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN ADIGO Conference Bridge: EN, ES & FR: 3535 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind Regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0