January 2024 - 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

REMINDER / Meeting Invitaiton: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 31 January 2024 at 14:00 UTC
by ICANN At-Large Staff Jan. 31, 2024

Jan. 31, 2024

***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 January 2024 at 14:00 UTC for 90 mins. For other times: http://tinyurl.com/yzjbctup The agenda and call details can be found at: https://community.icann.org/x/ZYC5EQ 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> [signature_680046767]

1 1

Action needed | Call for Volunteers | SPIRT Charter Drafting Team | Due by 05 February 2024
by Andrew Chen Jan. 25, 2024

Jan. 25, 2024

Hi all, As mentioned during the 24 January CPWG call<https://community.icann.org/pages/viewpage.action?pageId=295043131>, please find below the GNSO Council’s SPIRT Charter Drafting Team Call for Volunteers information. If you wish to join the Drafting Team, please contact the GNSO Secretariat at gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> and cc staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. Please review the “Who Should Join” section below for membership requirements. The Call for Volunteers window will close on 05 February 2024. The Generic Names Supporting Organization (GNSO) Council seeks volunteers to serve on a Drafting Team that will develop a charter for the Standing Predictability Implementation Review Team (SPIRT). The SPIRT will be the body empowered to provide input to the GNSO Council, the ICANN Board, ICANN org, and the ICANN community on unforeseen issues arising for the Next Round of the New gTLD Program after the approval by the ICANN Board of the Applicant Guidebook (AGB). What This Drafting Team Will Do The Drafting Team is expected to develop a draft Charter for the SPIRT, which is a group recommended in the new gTLD Subsequent Procedures Final Report. The Drafting Team’s only task is to develop the draft Charter for the SPIRT, with the Charter being subject to GNSO Council approval. As background and for context, the SPIRT will utilize an output called the Predictability Framework, which will be an output of the implementation effort for New gTLD Subsequent Procedures as developed by ICANN org, in coordination with the Implementation Review Team (IRT). This Drafting Team will NOT be responsible for developing the Predictability Framework, but will be responsible for the limited task of determining how the SPIRT will utilize the Predictability Framework, by preparing the draft Charter. In developing the draft Charter, the Drafting Team will be expected to consider elements such as the composition of the SPIRT, detailing how issues are raised to the SPIRT procedurally, defining operating principles and decision-making, and other important aspects to support the proper functioning of the SPIRT. The New gTLD Subsequent Procedures Final Report included an annex [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> that provides detailed guidance on how the SPIRT should operate. The content included in this annex should serve as the starting point for the Drafting Team in developing the draft Charter, but the Drafting Team may determine that improvements can be made to what is suggested in that annex. The SPIRT Charter is a requirement for establishing the SPIRT. However, the SPIRT and the Predictability Framework are by definition, not intended to operate until the AGB is approved by the ICANN Board. Nevertheless, the Council anticipates that this Drafting Team should be able to complete its work in a timely manner (i.e., no more than 3 months), given the extensive existing details included in the annex. Who Should Join The GNSO Council invites interested parties within the GNSO community (i.e., GNSO's stakeholder groups and constituencies), as well as parties from other Supporting Organizations and Advisory Committees to join the Drafting Team. The GNSO Council asks that volunteers take into account the expected membership criteria for this Drafting Team: • Possess basic knowledge of the New gTLD Program from 2012; • Be familiar with the New gTLD Subsequent Procedures Final Report, especially Topic 2 on Predictability and Annex E on the Predictability Framework; • Be familiar with GNSO Working Group Guidelines [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> and Policy Development Process; • Be available to actively contribute to the discussion and activities of the Drafting Team for the duration of the effort; and, • Update your Statement of Interest in accordance with Section 5 of the GNSO Operating Procedures. How to Join GNSO community members who wish to join the Drafting Team should contact the GNSO Secretariat at gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> by 05 February 2024. Background For more information and to better prepare for participation on this Drafting Team, please read Topic 2: Predictability [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> in the New gTLD Subsequent Procedures Final Report, as well as Annex E[gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> Sincerely, Andrew -- Andrew Chen Policy Development Support Sr. Specialist, Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org/ Skype: atchen122

1 0

MEAC gTLDs - Totals with Locally and Externally hosted websites
by John McCormac Jan. 25, 2024

Jan. 25, 2024

There seems to be no update from ICANN on the MEAC 2023 study. Here are some of the latest January 2024 gTLD hosting market figures (the MEAC countries from the full set of country level hosting markets spreadsheet) from a monthly domain name statistics report that I publish. The grouping is by hoster (registrar and resellers) associated with the country and the Local field is the number of locally hosted websites and the External field is the number of websites hosted outside that country's IP ranges. The Sites figure is the total number of gTLD websites hosted on the country's IP ranges. Country - ccTLD - region -All gTLDs - Local - External - Sites United Arab Emirates ae AP 42,825 2,160 19,384 11,367 Afghanistan af AP 373 3 331 150 Bahrain bh AP 670 3 263 219 Algeria dz AF 12,601 1,157 10,764 1,406 Egypt eg AF 15,828 2,749 10,247 4,621 Iran ir AP 390,120 182,753 73,212 305,710 Iraq iq AP 1,728 182 1,369 514 Jordan jo AP 3,619 567 970 1,512 Kuwait kw AP 2,308 274 1,324 1,085 Lebanon lb AP 2,827 865 1,181 1,422 Libya ly AF 3,258 22 2,689 404 Morocco ma AF 33,069 8,467 16,105 9,292 Mauritania mr AF 13 1 0 9 Oman om AP 1,167 154 728 508 Pakistan pk AP 97,229 1,860 82,016 5,067 Palestine ps AP 846 404 279 1,038 Qatar qa AP 2,077 67 1,649 423 Saudi Arabia sa AP 32,992 1,872 27,675 4,648 Sudan sd AF 1,014 6 864 46 Somalia so AF 726 1 565 266 Syria sy AP 1,495 573 746 737 Tunisia tn AF 8,447 4,364 2,264 4,885 Turkey tr AP 1,630,854 1,150,503 104,895 1,253,638 Yemen ye AP 320 0 305 179 The sheer vandalism of GDPR on the WHOIS has made the WHOIS records far less reliable when it comes to determining the country of a registration than they were at the time of the previous MEAC study in 2015. Due to GDPR kicking in May 2018, many of the gTLD registrations since then have critical data obscured or redacted. Most of the larger registrars automatically use WHOIS privacy. Some registrars actually provide no data even on the country fields. That's just the registrars. The registrants are far more creative on registration details and often put a completely different country for the registration. That's on some of the available records. From reading through the RFP (again), some of the ICANN requirements are worthy if a little on the optimistic side. Apart from major players like Turkey and Iran, a lot of registrations and websites are externally hosted on transnational registrars and hosting companies. Internet infrastructure, the importance of which was detailed in the draft Africa DNS Market Study 2023, plays a large part in where domain names are hosted. Globally, the reseller market share is approximately 21.98% of the gTLD market. 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 0

Meeting invitaiton: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 31 January 2024 at 14:00 UTC
by ICANN At-Large Staff Jan. 25, 2024

Jan. 25, 2024

***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 January 2024 at 14:00 UTC for 90 mins, For other times: http://tinyurl.com/yzjbctup<http://tinyurl.com/bdcm479f> The agenda (to be updated) and call details can be found at: https://community.icann.org/x/ZYC5EQ 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

Fwd: ICANN board nixes “closed generics” in next new round of TLDs
by Carlton Samuels Jan. 24, 2024

Jan. 24, 2024

Have a look at his last paragraph. Hmm. When is "close enough" to that exclusivity objective good enough, I wonder? Price restrictions and market manipulation are generally not subject to oversight. So maybe AA is onto something here. Making price a barrier to access could pass every test and come out on the other side smelling like a rose. Carlton ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Process, Governance, Assessment & Turnaround* ============================= [image: Site logo image] Andrew Allemann posted: "Applicants will not be able to use generic terms exclusively. ICANN's Board of Directors has confirmed that it will not allow so-called "closed generics" in the next round of top level domain name expansion. Closed generics are generic/dictionar" Domain Name Wire | Domain Name News <https://domainnamewire.com> Read on blog <https://domainnamewire.com/2024/01/23/icann-board-nixes-closed-generics-in-…> or reader <https://public-api.wordpress.com/bar/?stat=groovemails-events&bin=wpcom_ema…> ICANN board nixes “closed generics” in next new round of TLDs <https://public-api.wordpress.com/bar/?stat=groovemails-events&bin=wpcom_ema…> Andrew Allemann Jan 23 *Applicants will not be able to use generic terms exclusively.* [image: The words "closed generics" with a circle and slash indicating they are banned] ICANN's Board of Directors has confirmed that it will not allow so-called "closed generics" in the next round of top level domain name expansion. Closed generics are generic/dictionary terms that one company wants to own but not offer to the general public. Think Google getting .search and only using it for its own purposes, or Amazon exclusively using .book. These types of TLDs weren't initially forbidden in the 2012 expansion round but were retroactively banned after applications were received. In a January 22 letter, Tripti Sinha, Chair of the ICANN's Board of Directors, confirmed <http://domainnamewire.com?action=user_content_redirect&uuid=b22fd54a9601f6e…> (pdf) that the board is squashing closed generics in the next round, too. There was a bit of a loophole in the original ban: companies could continue with their applications as open domains but never launch them. That's the case (so far) with .search and .book, which are still sitting on the shelf. The companies can't exclusively use them but can keep them out of the hands of others. If they want to use them exclusively, they could also launch them with very high registration prices to keep other users at bay. I wonder if some current owners of unlaunched generic TLDs were hoping for a retroactive reprieve in the upcoming round. Now that that's off the table, they might launch their domains with high prices. Domain Incite has done an excellent job chronicling <http://domainnamewire.com?action=user_content_redirect&uuid=18b35ba87f17b77…> the closed generics fight. Comment <https://public-api.wordpress.com/bar/?stat=groovemails-events&bin=wpcom_ema…> Domain Name Wire | Domain Name News © 2024. Manage <https://public-api.wordpress.com/bar/?stat=groovemails-events&bin=wpcom_ema…> your email settings or unsubscribe.

1 0

REMINDER / Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 24 January 2024 at 19:00 UTC
by ICANN At-Large Staff Jan. 24, 2024

Jan. 24, 2024

**f 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, 24 January 2024 at 19:00 UTC for 90 mins, For other times: http://tinyurl.com/bdcm479f The agenda and call details can be found at: https://community.icann.org/x/OwCWEQ 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> [signature_686146308]

1 0

Correspondence - Tripti Sinha to Jonathan Zuck and Greg DiBiase - Closed Generics
by Andrew Chen Jan. 23, 2024

Jan. 23, 2024

Hi all, Please find the linked letter from Tripti Sinha to Jonathan Zuck and Greg DiBiase regarding Closed Generics. Board Action on GAC and ALAC Advice on Closed Generics: https://www.icann.org/en/system/files/correspondence/sinha-to-zuck-dibiase-… Sincerely, Andrew -- Andrew Chen Policy Development Support Sr. Specialist, Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org/ Skype: atchen122

1 0

REMINDER / Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 24 January 2024 at 19:00 UTC
by ICANN At-Large Staff Jan. 23, 2024

Jan. 23, 2024

**f 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, 24 January 2024 at 19:00 UTC for 90 mins, For other times: http://tinyurl.com/bdcm479f The agenda (to be updated) and call details can be found at: https://community.icann.org/x/OwCWEQ 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> [signature_1806330897]

1 0

Webinar Information Africa Domain Name Industry Study Draft Final Report
by Andrew Chen Jan. 17, 2024

Jan. 17, 2024

Hi all, As mentioned during today’s CPWG call, please find below the registration sign-up link for the 23 January 2024 14:00 - 15:30 UTC webinar on the 2023 Africa Domain Name Industry Study Draft Final Report, the 2023 Africa Domain Name Industry Study Draft Final Report Public Comment Page, and the Draft Final Report. * 23 January 2024 14:00 - 15:30 UTC webinar sign-up link<https://icann.zoom.us/webinar/register/WN_xC4Sue1lR0-WW6KRa0VsxQ#/registrat…> * Draft Africa DNS Study Public Comment Page<https://www.icann.org/en/public-comment/proceeding/draft-final-report-of-th…> * Draft Africa DNS Study Report<https://itp.cdn.icann.org/en/files/stakeholder-engagement/2023-africa-domai…> As noted during the call, please email queries.nairobiec(a)icann.org<mailto:queries.nairobiec@icann.org> by Monday January 22, 2024 at Midnight (UTC) if you wish to follow the audio in French or Portuguese. Please state in the subject of your email “Webinar interpretation of January 23, 2024” and include your last name, first name, preferred language, and the telephone number that the operator can reach you at. Sincerely, Andrew -- Andrew Chen Policy Development Support Sr. Specialist, Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org/ Skype: atchen122

2 1