June 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

Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 03 July 2024 at 14:00 UTC
by ICANN At-Large Staff July 3, 2024

July 3, 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, 03 July 2024 at 14:00 UTC for 90 mins, For other times: https://tinyurl.com/3dhnknub The agenda (to be updated) and call details can be found at: https://community.icann.org/x/x4DlF 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 1

At-Large Consolidated Policy Working Group (CPWG)
by ICANN Policy Calendar June 27, 2024

June 27, 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, 03 July 2024 at 14:00 UTC for 90 mins, For other times: https://tinyurl.com/3dhnknub The agenda (to be updated) and call details can be found at: https://community.icann.org/x/x4DlF 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

24-Hour Review Period Policy Status Report: GNSO Policy & Implementation Working Group Recommendations Public Comment
by Andrew Chen June 26, 2024

June 26, 2024

Dear CPWG Members, As discussed during today’s CPWG call, in preparation for the Public Comment Statement submission for the Policy Status Report: GNSO Policy & Implementation Working Group Recommendations<https://www.icann.org/en/public-comment/proceeding/policy-status-report-gns…>, please see linked below the Draft Public Comment Statement for the Policy Status Report: GNSO Policy & Implementation Working Group Recommendations public comment proceeding. Please review and provide your comments for finalization by tomorrow, 27 June 2024 at 21:00UTC. The ALAC is scheduled to vote on this statement between Friday, 28 June and Monday, 01 July 2024. The public comment submission period will close on Tuesday, 02 July 2024. Draft Public Comment Statement: https://docs.google.com/document/d/1tizocp_mNuONI-Gaf09ZRhPbMbior-N1k0wP9nY… Please let us know if you have any questions. 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

RDRS and SPIRT reports
by Alan Greenberg June 26, 2024

June 26, 2024

I may not be able to be on the call today, so I will make my brief report here. *RDRS * Several enhancements were just released: - *Registrar (NSp) Enhancements * - *Request submission date now shows inside the request in Naming Service portal * - *Request now defaults to have the accordion arrows open (instead of closed) so registrar can see the full request without clicks.* - *Request List View – Last request in list should no longer be blocked by footer of the page* - *RDRS (Platform) Requestor Enhancements:* - *Address & phone number is now required;* - *Organization/Affiliation field is new and optional* - *Increased character limit from 1000 to 2000 for all open text boxes.* - *Updated language to better explain what “expedited” means in RDRS* - *Added language to explain that providing misleading content, including representing yourself as law enforcement if you are not employed by or an official representative of a law enforcement agency, is a violation of the RDRS Terms of Service.* There is a long list of possible enhancements being discussed: https://docs.google.com/document/d/14b6bG1Odmx-pLkTHrLSNiqAA4JCky2bewidHa5Y… *SPIRT* We had hoped to have a draft SPIRT Charter ready for the GNSO Council in the next week, but there are still ongoing discussions largely to ensure that the Predictability Framework being designed by the IRT and the SPIRT Charter are compatible. There are currently two additional meetings scheduled with the hope of making appropriate adjustments. Note that the IRT will be sending the Predictability Framework out for public comment next year, so there may be further adjustments necessary. Alan

1 0

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

June 26, 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, 26 June 2024 at 19:00 UTC for 90 mins, For other times: https://tinyurl.com/5yzurhkp The agenda (to be updated) and call details can be found at: https://community.icann.org/x/pgBhF 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 1

Fwd: [SubPro-IRT] Board resolution relevant to next round
by Justine Chew June 12, 2024

June 12, 2024

Dear all, I am forwarding the following notice that was given to the SubPro IRT, but taking the liberty to add the pertinent context/conclusion. On Saturday 8 June 2024, the ICANN Board passed a number of resolutions pertaining to the Next Round. - IDN EPDP Ph1 Recommendations <https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> - Resolved (2024.06.08.04), the ICANN Board adopts the Scorecard: IDN EPDP Phase 1 Recommendations <https://www.icann.org/en/system/files/files/scorecard-idn-epdp-phase-1-reco…> in full. *Section A of the Scorecard* identifies the Outputs that the Board adopts. *Section B* identifies the Outputs that the Board designates as pending. - Approach for Handling Content-Restrictive Commitments in Next Round Registry Agreements <https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> - Resolved (2024.06.08.08), the ICANN Board determines that ICANN should exclude from the Next Round RAs any RVCs and other comparable registry commitments that restrict content in gTLDs. - Supplemental Recommendations on the new gTLD SubPro PDP <https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> - Resolved, (2024.06.08.11), the Board adopts the June 2024 Scorecard: Subsequent Procedures Supplemental Recommendations <https://www.icann.org/en/system/files/files/scorecard-subsequent-procedures…> , dated 8 June 2024 (Supplemental Recommendations Scorecard), consisting of: - Section A, which details the Supplemental Recommendations that the Board adopts. - Topic 17: Applicant Support (17.2) - Topic 32: Limited Challenges and Appeals (32.1, 32.2 and 32.10) - Section B, which details the Supplemental Recommendations that the Board does not adopt, including a rationale. - Topic 9: Registry Voluntary Commitments / Public Interest Commitments (9.2) - Topic 18: Terms and Conditions (18.1 and 18.3) - GAC Advice in ICANN77 Communique Regarding Avoiding Auctions Between Commercial/Non-Commercial Applications <https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> - Whereas, the Board has identified concerns with GAC Consensus Advice item 4.a.i (i.e. Washington, D.C. Communiqué includes advice concerning Topic 35, and, specifically, the use of auctions between commercial and noncommercial applications) including concerns regarding the feasibility of implementation from both a practical and legal standpoint. - Whereas, the Board has noted that GAC Consensus Advice item 4.a.i does not align with the relevant SubPro recommendations related to Topic 35, which call for the continued use of ICANN Auctions of Last Resort as a contention resolution mechanism. - GGP for Applicant Support Recommendations <https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> - Resolved (2024.06.08.17), the ICANN Board adopts all nine guidance recommendations as documented in the GGP for Applicant Support Final Report. - Next Round Funding <https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> - Whereas, the BFC has recommended that the Board approve funding from the New gTLD Program: 2012 Round Application Fees of up to US$23 million to cover further implementation costs for the New gTLD Program: Next Round through 31 March 2025. - Resolved (2024.06.08.19), the Board authorizes the ICANN Interim President and CEO, or her designee(s), to spend up to US$23 million from the New gTLD Program: 2012 Round Application Fees to fund the implementation work of the New gTLD Program: Next Round through 31 March 2025. Justine ---------- Forwarded message --------- From: Lars Hoffmann <lars.hoffmann(a)icann.org> Date: Wed, 12 Jun 2024 at 11:56 Subject: [SubPro-IRT] Board resolution relevant to next round To: subpro-irt(a)icann.org <subpro-irt(a)icann.org> Dear IRT members, On Saturday 8 June 2024, the ICANN Board passed a number of resolutions pertaining to the Next Round. For ease of access, I have pasted the link the resolutions on: - IDN EPDP Ph1 Recommendations <https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> - Approach for Handling Content-Restrictive Commitments in Next Round Registry Agreements <https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> - Supplemental Recommendations on the new gTLD SubPro PDP <https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> - GAC Advice in ICANN77 Communique Regarding Avoiding Auctions Between Commercial/Non-Commercial Applications <https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> - GGP for Applicant Support Recommendations <https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> - Next Round Funding <https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> Best wishes. Lars _______________________________________________ SubPro-IRT mailing list SubPro-IRT(a)icann.org https://mm.icann.org/mailman/listinfo/subpro-irt _______________________________________________ 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.

3 3

Call for Volunteers - ICANN80 Session Reports
by Andrew Chen June 10, 2024

June 10, 2024

Dear CPWG Members, During today’s At-Large Leadership Welcome Session<https://sched.co/1dr1r>, ICANN80 Session Reports<https://community.icann.org/display/atlarge/At-Large+Session+Reports+from+I…> were discussed. The At-Large community still needs Rapporteurs for the following sessions: * GAC Discussion: New gTLD Program Next Round<https://sched.co/1dr3S> * GNSO: RDRS Standing Committee Work Session<https://sched.co/1dr4c> * Second IANA Naming Function Review (IFR2) Team Work Session<https://sched.co/1dr4G> * GNSO: CPH Registration Data Implementation Discussion<https://sched.co/1dr3D> * GDS: PPSAI IRT Work Session<https://sched.co/1dr4r> Please reach out to staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> if you would like to volunteer to be the Rapporteur for any of the sessions. Session reports will be discussed during the At-Large Leadership Wrap Up session<https://sched.co/1dr2E> on 13 June 2024 at 11:45 UTC (13:45 Kigali). 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

More interests "announced" to applying for New gTLDs in the Next Round
by Justine Chew June 10, 2024

June 10, 2024

https://cointelegraph.com/news/unstoppable-domains-blockchain-web3-domain-l… Save, that I do not know where Unstoppable Domains and Blockchain.com got the notion of "ICANN’s hotly anticipated six-year registration program next year". *_____________________________________________________* *Justine Chew* At-Large Advisory Committee (ALAC) Liaison to the GNSO Internet Corporation for Assigned Names and Numbers (ICANN) At-Large website: https://atlarge.icann.org/ ------

11 11

AI/ML Limitations - ICANN80 reminder
by Gisella Gruber June 10, 2024

June 10, 2024

Dear Michael, Thank you for your email. I have forwarded this message to the relevant department who will respond to this request. Wishing you a successful ICANN80 Meeting. Kind regards, Gisella From: CPWG <cpwg-bounces(a)icann.org> on behalf of CPWG <cpwg(a)icann.org> Reply to: "mike palage.com" <mike(a)palage.com> Date: Monday, 10 June 2024 at 10:50 To: CPWG <cpwg(a)icann.org>, John Jeffrey <john.jeffrey(a)icann.org>, "tripti.sinha(a)board.icann.org" <tripti.sinha(a)board.icann.org> Subject: [CPWG] AI/ML Limitations - ICANN80 reminder Hello All, I am rather bullish on the future of AI/ML, however, I think it is prudent to be mindful of its current limitations. I recently participated in a conference where the host offered the ability to have AI summarize the presentation. The panelists for a session I was moderating opted not to use this feature because of the highly legal and regulatory nature of the session. Having looked at the AI summarizes from other sessions, I think that this was a good session. I was reminded of this fact today. While listening to the Next gTLD round zoom session, I was concurrently reading the transcription from the GAC opening session. I did a double take when I saw the GNSO was responsible for the slaughter of over 1 million Tutsi in 1994. (see below) [cid:image001.png@01DABB29.61ED8420] I believe that ICANN Org does not generally edits its transcripts, however, I would hope that they could make an exception out of respect for those Tusti and other minority ethnic groups that lost their lives. I would not want a future LLM using this ICANN transcript to promote false and inaccurate information. As future LLM models continue to scrape the internet for as much knowledge as possible, we must never forget the old adage Garbage In Garbage Out. Best regards, Michael

1 0