October 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, 08 November 2023 at 13:00 UTC
by ICANN At-Large Staff Nov. 7, 2023

Nov. 7, 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, 08 November 2023 at 13:00 UTC for 90 mins, For other times: https://tinyurl.com/55vxamad<https://tinyurl.com/22ne3mpb> The agenda (to be updated) and call details can be found at: https://community.icann.org/x/4QJ6E<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>

1 2

Circleid - Universal acceptance issues
by Maureen Hilyard Oct. 24, 2023

Oct. 24, 2023

https://circleid.com/posts/20231014-universal-acceptance-issues-with-.tube-…

6 5

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

GAC and ALAC Chair Joint Letter on Next Steps for the ALAC-GAC-GNSO facilitated dialogue on Closed Generic gTLDs
by ICANN At-Large Staff Oct. 23, 2023

Oct. 23, 2023

Dear All, On behalf of Jonathan Zuck, ALAC Chair, please find the link to the GAC and ALAC Chair joint letter on next steps for the ALAC-GAC-GNSO facilitated dialogue on Closed Generic gTLDs sent to Tripti Sinha, Chair, ICANN Board of Directors at: https://www.icann.org/en/system/files/correspondence/cabellero-zuck-to-sinh…) 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_2353871133]

1 0

Meeting Invitation - ICANN78 - Sunday 22 October at 10h30 CEST (08h30 UTC)
by ICANN At-Large Staff Oct. 21, 2023

Oct. 21, 2023

Dear CPWG Members, Please join us on Sunday 22 October from 10h00-11h30 in the ALAC Room (Hall Y, 5-8). At-Large Consolidated Policy WG (CPWG) - Overview and Year Ahead Session Details: https://icann78.sched.com/event/1T4Kq/at-large-consolidated-policy-working-… Agenda: 1. Welcome and Aim of Meeting - Olivier Crepin-Leblond and Hadia Elminiawi, CPWG Co-Chairs (5 mins) 2. 2023 Highlights in ALAC Policy Advice Activities and Current Hot Topics - Olivier Crepin-Leblond (60 mins) * TPR-PDP<https://community.icann.org/pages/viewpage.action?pageId=272990249> - Steinar Grøtterød and Lutz Donnerhacke * EPDP-IDNs<https://community.icann.org/pages/viewpage.action?pageId=272990249> - Satish Babu and Hadia Elminiawi * RDA Scoping Team<https://community.icann.org/pages/viewpage.action?pageId=272990249> - Alan Greenberg * RDRS (formerly SSAD ODA)<https://community.icann.org/pages/viewpage.action?pageId=272990249> - Alan Greenberg * Closed Generics<https://community.icann.org/pages/viewpage.action?pageId=272990249> - Greg Shatan and Alan Greenberg * Applicant Support GGP<https://community.icann.org/pages/viewpage.action?pageId=272990249> - Maureen Hilyard and Satish Babu - Presentation<https://community.icann.org/download/attachments/268763271/GGP%20PPT%20-%20…> * New gTLD Next Round (SubPro)<https://community.icann.org/pages/viewpage.action?pageId=272990249> - Justine Chew and Cheryl Langdon-Orr 3. What to Expect in the Year Ahead in Policy Development - Justine Chew and Jonathan Zuck (20 mins) 4. Next Steps - Olivier Crepin-Leblond and Hadia Elminiawi, CPWG Co-Chairs (5 mins) Thank you. Kind regards, At-Large Staff ICANN Policy Team in support of the At-Large Community Website: atlarge.icann.org [atlarge.icann.org]<https://urldefense.com/v3/__https:/atlarge.icann.org/__;!!PtGJab4!_FMj7a2EP…> Facebook: facebook.com/icann [facebook.com]<https://urldefense.com/v3/__https:/www.facebook.com/icannatlarge__;!!PtGJab…>atlarge [facebook.com]<https://urldefense.com/v3/__https:/www.facebook.com/icannatlarge__;!!PtGJab…> Twitter: @ [twitter.com]<https://urldefense.com/v3/__https:/twitter.com/ICANNAtLarge__;!!PtGJab4!_FM…>ICANNAtLarge [twitter.com]<https://urldefense.com/v3/__https:/twitter.com/ICANNAtLarge__;!!PtGJab4!_FM…> [signature_1469161298]

3 2

GNSO-TPR: Proposed recommendations to ICANN Bulk transfers and Change of sponsorship (BTAPP)
by Steinar Grøtterød Oct. 13, 2023

Oct. 13, 2023

Dear all, The Inter-Registrar Transfer PDP has proposed a set of recommendations for “ICANN Approved transfers” and “Change of sponsorship (BTAPPA)”. As the At-Large representant in the working group, I asked for your comments to the proposals. Please refer to the proposed recommendation to you comments. Example: Change of Sponsorship (BTAPPA) RECOMMENDATIONS, Prelim. Rec. #xx.2: [Your comment] The deadline to comment is set to COB Tuesday, 17 October. ICANN Approved Transfer is transfer of the sponsorship of all the registrations sponsored by one Registrar as the result of (i) acquisition of that Registrar or its assets by another Registrar, or (ii) lack of accreditation of that Registrar or lack of its authorization with the Registry Operator. Bulk Transfer After Partial Portfolio Acquisition (“BTAPPA”) is a registry service available to consenting registrars in the circumstance where (i) one ICANN-accredited registrar purchases, by means of a stock or asset purchase, merger or similar transaction, a portion but not all, of another ICANN-accredited registrar's domain name portfolio in the TLD or (ii) a newly accredited registrar (gaining registrar) requests a transfer of all domain names from the losing registrar for which the gaining registrar has served as the reseller. Upon completion of the transfer, the gaining registrar is the new sponsoring registrar. The gaining registrar must certify the BTAPPA would not otherwise qualify under ICANN’s Transfer Policy. Regards, Steinar Grøtterød

1 0

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

Oct. 11, 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, 11 October 2023 at 13:00 UTC for 90 mins, For other times: https://tinyurl.com/23wjnspv The agenda (to be updated) and call details can be found at: https://community.icann.org/x/ApBME 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: (Please note, there will NOT be interpretation due ICANN78 Prep Week) EN: 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_85309757]

1 1

ICANN78 Policy Outlook Report / ICANN78 GNSO Policy Briefing - Available for download!
by Justine Chew Oct. 9, 2023

Oct. 9, 2023

FYI Kind regards, Justine --------- ---------- Forwarded message --------- From: Julie Bisland via council <council(a)gnso.icann.org> Date: Mon, 9 Oct 2023, 23:56 Subject: [council] ICANN78 Policy Outlook Report / ICANN78 GNSO Policy Briefing - Available for download! To: council(a)gnso.icann.org <council(a)gnso.icann.org> Cc: gnso-secs(a)icann.org <gnso-secs(a)icann.org> Dear All, On behalf of the GNSO Team, I am happy to report that * the GNSO Policy Briefing for ICANN7**8* is now available for download at http://go.icann.org/gnsobriefing <https://go.icann.org/gnsobriefing>. In addition, the *ICANN78 Policy Outlook Report* is available: *https://go.icann.org/outlook78 <https://go.icann.org/outlook78> * Happy reading! Best Regards, Julie -- *Julie Bisland* Policy Operations Sr. Coordinator (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) *Skype ID:* 79613b691cb8a6c1 Find out more about the GNSO by visiting: https://learn.icann.org/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> [image: signature_3449104943] _______________________________________________ council mailing list council(a)gnso.icann.org https://mm.icann.org/mailman/listinfo/council _______________________________________________ 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 (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) 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.

1 0

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

Oct. 6, 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, 11 October 2023 at 13:00 UTC for 90 mins, For other times: https://tinyurl.com/23wjnspv<https://tinyurl.com/22ne3mpb> The agenda (to be updated) and call details can be found at: https://community.icann.org/x/ApBME<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: (Please note, there will NOT be interpretation due ICANN78 Prep Week) EN: 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