May 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

Google pushes .zip and .mov domains onto the Internet, and the Internet pushes back
by Olivier MJ Crépin-Leblond June 28, 2023

June 28, 2023

From ARS Technica, 18 May 2023: A recent move by Google to populate the Internet with eight new top-level domains is prompting concerns that two of the additions could be a boon to online scammers who trick people into clicking on malicious links. https://arstechnica.com/information-technology/2023/05/critics-say-googles-…

13 19

CPWG call-31 May-2023: Justine's Slides (prep for ALAC-GNSO bilateral call)
by Chantelle Doerksen June 1, 2023

June 1, 2023

Dear all, As promised, attached is Justine’s presentation from today’s CPWG call (also available on the agenda page). The ALAC-GNSO Council Bilateral call (agenda forthcoming) will be on Tuesday, 6 June, 13 UTC. Best, Chantelle

2 1

Minutes from the GNSO Transfer Policy Review PDP meeting on May 30, 2023
by Steinar Grøtterød May 31, 2023

May 31, 2023

In order to save time. The WG continued the discussion to the TDRP Charter questions connected to Phase 2: >From the ICANN Staff minutes: At-Large has indicated support for the registrants to have a way into the TDRP in cases where the process isn’t followed. The tough part is that with the TDRP there has to be a clear policy violation – although most transfer dispute issues are not policy related. This WG is considering whether to make a recommendation to do something outside of this group. See charter question g3. Phase 2, charter question g3) If the TDRP is considered to be insufficient: i. Are additional mechanisms needed to supplement the TDRP? ii. Should the approach to the TDRP itself be reconsidered? In my view, the challenge is that the TDRP is to be used when there is a breach in the defined inter-registrar transfer process - not for cases connected to domain name theft, hijacking etc. Unfortunately, the majority of the WG members are in favour of creating another process to secure the registrant possibility to dispute. My recommendation is that ALAC review and comment the final version of responses to the Phase 2 charter questions in the Public Comments period. The WG final draft for the Phase 2 Charter questions will be completed and discussed at ICANN77 Regards, Steinar Grøtterød At-Large Representative (Also posted to the CPWG site<https://community.icann.org/pages/viewpage.action?pageId=244942680>)

2 2

ICANN Org Commissioned Economic Studies related to the gTLD marketplace (2008-2017)
by Chantelle Doerksen May 31, 2023

May 31, 2023

Dear all, Attached is a list of previous economic studies commissioned by ICANN org that might be of interest to the CPWG. A related 2015 study authored by the UCSD Dept of Computer Science that might also be of interest: From .academy to .zone: An Analysis of the New TLD Land Rush. Best Chantelle

3 2

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

May 31, 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, 31 May 2023 at 13:00 UTC for 90 mins. For other times: https://tinyurl.com/5eh6ahbb The agenda and call details can be found at: https://community.icann.org/x/WIeZDg 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: 3535 (Due to ICANN77 Prep Week, there will not be interpretation provided) 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 2

Krebs On Security - Phishing domains tanked in ccTLDs after Meta sued Freenom
by John McCormac May 29, 2023

May 29, 2023

Interesting article on Krebs on Security. It seems that phishing domain names in ccTLDs fell after Meta/Facebook sued Freenom. https://krebsonsecurity.com/2023/05/phishing-domains-tanked-after-meta-sued… It is an interesting precedent as brand owners may consider suing registries and registry service providers in future. 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

2 2

Public Comment opens for Amendments to the Base gTLD RA and RAA to Modify DNS Abuse Contract Obligations
by Justine Chew May 29, 2023

May 29, 2023

https://www.icann.org/en/public-comment/proceeding/amendments-base-gtld-ra-… Kind regards, Justine

1 0

.edu
by Roberto Gaetano May 27, 2023

May 27, 2023

Dear all, Yesterday I joined the call late, so I have probably missed something - sorry if I am saying something that was already did during the call. Mention was made of a registration under .edu, I believe by Gopal, and the issue was which registrar. When the SRS was developed for the separation between Ry and Rar this model was applied only to .com, .org and .net, while the other TLDs that were not open to public - like .gov, .mil, .int, .edu - were left unchanged. So the registration via an ICANN-approved Registrar only applied to the TLDs managed by Network Solution. As a consequence, there is no need to go through a Registrar for registering a SLD under .edu. Cheers, Roberto

3 4

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

May 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, 31 May 2023 at 13:00 UTC for 90 mins. For other times: https://tinyurl.com/5eh6ahbb The agenda (to be updated) and call details can be found at: https://community.icann.org/x/WIeZDg<https://community.icann.org/x/iICCDg> 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: 3535 (Due to ICANN77 Prep Week, there will not be interpretation provided) 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