- CPWG - lists.icann.org

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

Re: [CPWG] More interests "announced" to applying for New gTLDs in the Next Round
by Matthias M. Hudobnik June 9, 2024

June 9, 2024

1 0

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

June 5, 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 0

ICANN80 Talking Points
by Andrew Chen June 5, 2024

June 5, 2024

Dear CPWG Members, As we prepare for ICANN80, we kindly request your attention to review the ALAC ICANN80 Talking Points linked below. These points are essential to ensure alignment on the ALAC’s messaging regarding ongoing policy topics. ICANN80 Talking Points: https://docs.google.com/document/d/1Fy-BuHo82uqrCdrsNfoSKs6vF6dgyAe-KcYIdMz… Safe travels to those traveling to Kigali, Rwanda. See you all soon. 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, 05 June 2024 at 14:00 UTC
by ICANN At-Large Staff June 5, 2024

June 5, 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, 05 June 2024 at 14:00 UTC for 90 mins, For other times:https://tinyurl.com/5yzurhkp The agenda and call details can be found at: https://community.icann.org/x/AYBFF 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 (Please note, there will NOT be interpretation) 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, 05 June 2024 at 14:00 UTC
by ICANN At-Large Staff June 4, 2024

June 4, 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, 05 June 2024 at 14: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/AYBFF 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 (Please note, there will NOT be interpretation) 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

Reminder: Requesting input to GNSO-TPR Proposed Recommendations
by Steinar Grøtterød May 31, 2024

May 31, 2024

Dear All, ICANN staff has prepared a Google document with all proposed recommendations and instructed the working group to identify proposed recommendations that stakeholders CANNOT LIVE WITH. Deadline for this is set to June 3, 2024. The objective for this exercise is to identify any recommendations that must be "re-opened" for discussion. The goal is to start the Public Comment phase in (late) August 2024. CPWG version of the proposed recommendations I have made a copy of the document with the proposed recommendations<https://docs.google.com/document/d/137NjFpE9QslCXJzz5Ms0d8c10_L3xdMtCWCAz9d…>. The document is open for commenting for all with the link. I kindly ask for your input to the proposed recommendations that - in your view, is a recommendation that At-Large CANNOT LIVE WITH. ICANN staff has added a "Policy Impact Level": Low, Medium, High * An example of a LOW impact would be a definitional change, e.g., “Change of Registrant” to “Change of Registrant Data.” * An example of a MEDIUM impact would be a change to an existing requirement or a new requirement. * An example of a HIGH impact would be removing a previous requirement, such as the removal of the Post Change of Registrant 60-day transfer restriction. Criteria to consider when gauging impact: * Degree of change from existing requirement? [No change or confirm existing; Modification to existing req.; or New req.] * Security enhancement or detraction * Level of technical change (impact to CPs) * ICANN Contractual Compliance enforcement capability * RNH impacts (such as increased or reduced protections; level of confusion) Regards, Steinar Grøtterød At-Large representative to the GNSO-TPR PDP

1 0