September 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

Ready, Fire, Aim
by Evan Leibovitch Oct. 24, 2023

Oct. 24, 2023

A high-level tangent inspired by the current discussion: A casual reader might look at this thread and come to an observation that there are two separate issues being discussed, that may not have much to do with each other. The conversation that Mike, Steinar, Olivier and others are having concern details -- contract language, specifics about volumes and dollar amounts and assignment of responsibilities. Meanwhile, I have barged in -- surely unwelcome by some -- to challenge the very premises upon which ALAC's participation is being conducted. I have done this because, in my observation, ALAC lacks -- and has always lacked -- an overarching set of objectives upon which to base strategy and ultimately tactics. We engage in the minutiae of contract language (etc) without clarity of what ALAC -- and what the constituency it is mandated to speak for -- wants from the end result of such engagement. *Strategy without tactics is the slowest route to victory. Tactics without > strategy is the noise before defeat -- Sun Tzu * > While I was involved deeply in At-Large I would note that any internal attempt to create a coherent statement of purpose would be invariably torpedoed by people insisting that we engage in a never-ending attempt to define the "public interest". As a result, all attempts inevitably sank in the bureaucratic mud. Two separate third-party ICANN reviews of At-Large seemed to wholly overlook the lack of overarching purpose and mandate service while themselves dwelling on the minutiae. It's probably best that we don't depend on outside consultants to define our purpose, but why can't we do it ourselves? WIthout a clear mission, ALAC has weighed in on many issues in which non-registrant end users have no stake at all. Take vertical integration. End-users don't know and don't care about the domain supply chain. Even domain consumers -- technically outside our remit but closest to end-users in the ICANN food chain -- could hardly care less if they bought their domain from a registrar or directly from a registry. And yet there we were at the virtual table, as if our constituency has a crucial stake in that topic's outcome. Think of how many parts of the current ALAC agenda fit the same description. Meanwhile, on high-profile issues that WOULD affect end-users, such as the delegation of .XXX and the attempted private takeover of .ORG, we were silent. Such choices of action and inaction clearly telegraph -- throughout ICANN and the world around us -- a lack of both purpose and focus. This glaring deficiency continues to retard ALAC's agency within the rest of the ICANN community. Over the years I have received many private emails insisting that ALAC has more respect now than it did in the past and that it is invited to the policy table more often. To me this is tokenism. I'll be more persuaded that At-Large has the respect of ICANN when we get that second Board seat that was recommended and promised so long ago. Until then, or until a policy we want that is opposed by the domain industry is implemented, I will maintain that ALAC is being pandered to. We are tolerated in working groups so long as we make little line-item corrections and don't challenge their very premises or the ability of contracted parties to maximize revenue. We have the authority to talk directly to the Board, yet we chase after Public Comment solicitations just like anyone in the world can. We respond to the actions of others, we never initiate or try to set the agenda. One of the last such initiatives by At-Large, a white paper of which I was a co-author, was received with a smile and summarily binned; not a single response was returned from staff or the community. Maybe the cosmetics have changed in the last 15 years but the underlying politics certainly have not. While the status quo is obviously sustainable -- so long as ALAC members get funded to pretend they're the UNSC at a cavernous U-shaped table three times a year and learn how to play the insider games -- it doesn't do anything to serve At-Large's bylaw mandate. The inmates will continue to run the asylum, because the only entity really capable of making them accountable to the world-at-large is just fine with being tolerated. - Evan

16 32

Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 04 October 2023 at 20:00 UTC
by ICANN At-Large Staff Oct. 4, 2023

Oct. 4, 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, 04 October 2023 at 20:00 UTC for 90 mins, For other times: https://tinyurl.com/94b6s3cc<https://tinyurl.com/22ne3mpb> The agenda (to be updated) and call details can be found at: https://community.icann.org/x/X4JME<https://community.icann.org/x/Y4FUDw> 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 (subject to availability) 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>

3 4

Need Advise: Tokenization of Domain Names
by gopal Sept. 30, 2023

Sept. 30, 2023

Dear All, Domain names have been a valuable asset for nearly 50 years. However, the lack of liquidity has been a challenge for domain owners. Tokenization could provide a solution to this liquidity issue. By tokenizing domain assets, owners can sell off interests in their domains, building liquidity from assets that would otherwise remain idle. Need advise on ICANN Remit pertaining to new crypto-themed top-level domains which could potentially increase the value and liquidity of domain assets. As a matter of fact, IDN can very well serve as a crypt of a tokenized domain name. Please advise. 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 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

8 17

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

Sept. 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, 27 September 2023 at 13:00 UTC for 90 mins, For other times: https://tinyurl.com/22ne3mpb The agenda and call details can be found at: https://community.icann.org/x/KYBFE 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 (subject to availability) 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

Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 27 September 2023 at 13:00 UTC
by ICANN At-Large Staff Sept. 22, 2023

Sept. 22, 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, 27 September 2023 at 13:00 UTC for 90 mins, For other times: https://tinyurl.com/22ne3mpb The agenda (to be updated) and call details can be found at: https://community.icann.org/x/KYBFE<https://community.icann.org/x/Y4FUDw> 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 (subject to availability) 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, 20 September 2023 at 19:00 UTC
by ICANN At-Large Staff Sept. 20, 2023

Sept. 20, 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, 20 September 2023 at 19:00 UTC for 90 mins, For other times: https://tinyurl.com/bd7eu4rw The agenda (to be updated) and call details can be found at: https://community.icann.org/x/qwAFE<https://community.icann.org/x/Y4FUDw> 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 (subject to availability) 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>

5 8

The MEAC gTLDs markets (why wait until next year?)
by John McCormac Sept. 15, 2023

Sept. 15, 2023

I've crunched some data on all gTLDs, their websites and where they are hosted (all countries). ICANN has put out an RFP for a new Middle East and Adjacent Markets report with the draft report to be delivered next year. The RFP is full of wonderful aspirations. So, rather than waiting until next year for what will obviously be a fascinating report, here's a breakdown of the gTLDS in ICANN MEAC markets countries: Country All gTLDs Local External Sites (IP) United Arab Emirates 40,150 2,028 17,685 8,033 Afghanistan 44,622 1 35,455 94 Bahrain 421 3 31 224 Algeria 9,120 799 7,745 1,459 Egypt 8,766 2,552 4,053 4,604 Iraq 228 26 142 452 Iran, Islamic Republic of 266,301 113,123 47,320 338,675 Jordan 2,629 495 210 1,510 Kuwait 2,157 214 1,300 1,162 Lebanon 2,152 861 634 2,503 Libya 3,070 17 2,605 423 Morocco 37,003 7,845 13,962 9,245 Mauritania 13 0 1 8 Oman 1,045 119 679 535 Pakistan 64,298 1,368 54,319 8,355 Palestine, State of 590 387 86 1,179 Saudi Arabia 7,641 1,472 4,313 4,844 Somalia 234 0 197 276 Syrian Arab Republic 869 424 315 751 Tunisia 3,978 2,191 635 3,225 Turkey 1,432,750 1,023,052 84,765 1,280,958 Yemen 0 0 0 174 Totals 1,928,037 1,156,977 276,452 1,668,689 The All gTLD figure is the number of unique gTLD domain names hosted on identified registrars and resellers associated with the country. The Local figure is the number of gTLD domain names with websites hosted in the country. The External figure is the number of gTLD domain names with websites hosted outside of the country. The Sites (IP) figure is the number of gTLD websites identified on IP addresses associated with the country. It is based on identified registrars and resellers associated with countries. Most registrars and and resellers tend to be highly localised. The spreadsheet looks a lot better so apologies for the formatting. I haven't run a Web Usage study on the websites yet. 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

4 6

Summary of the last GNSO-TRT meeting
by Lutz Donnerhacke Sept. 15, 2023

Sept. 15, 2023

There are three major topics in the discussion yesterday: --- BEGIN OF SUMMARY --- Full Portfolio Transfers (Bulk Transfers): - Preliminary Agreement #1: Registry Operators MAY charge a fee for transferring full domain portfolios, with the option to waive fees in specific cases. - Concept 4: Ensures fees for full portfolio transfers involving multiple registries don't exceed a recommended ceiling, with fees distributed based on the number of domain names. Change of Sponsorship (Partial Bulk Transfers): - Preliminary Agreement #1: Registrars must notify affected registrants at least 30 days before a change of sponsorship, providing details like the change date, Gaining Registrar's name, and terms of service. - Preliminary Agreement #4: Registrants' existing Registration Agreements should allow transfers during a change of sponsorship, and registrants must confirm agreement with new terms before the transfer. Additional Discussions: - Consideration of replacing specific fee numbers with a flexible "reasonable fee" in policy language. - Debate on the relevance of a minimum threshold (e.g., 50,000 domain names) for fees. - Emphasis on clear language and use of "MAY" in fee-related policies. - Recognition of the need for project management representation and potential ICANN Org involvement in fee administration. --- END OF SUMMARY --- As a background, the current policy has a very simple fee: - Bulk transfers with less than n 50k domains = No fee - Bulk transfers with more than n 50k domains = 50k US$ flat >From the end user perspective there is only one notable point: - Registrants need to be informed about the change of the registrar (via reseller) beforehand. - Registrants need to accept the legal rules of the new registrar. For me there is only one point of interest: If "voluntary bulk transfers" are combined with "ICANN approved bulk transfers" into a single policy, the financial benefits and organisational simplifications of the "ICANN approved transfers" may be extended to ordinary, commercial activities. This may bring ICANN into the position of an omnipresent mediator, which is paying for the commercial gambling of the registrars and resellers.

3 3

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

Sept. 13, 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, 13 September 2023 at 13:00 UTC for 90 mins, For other times: https://tinyurl.com/2p8kdsdf The agenda (to be updated) and call details can be found at: https://community.icann.org/x/UwDfDw<https://community.icann.org/x/Y4FUDw> 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 4