- CPWG - lists.icann.org

ICANN’s Contractual Governance Regime
by David Mackey July 25, 2023

July 25, 2023

fyi: Sharing this blog post by Milton Mueller <https://www.internetgovernance.org/2023/06/15/the-big-question-facing-icann…> regarding a discussion held at ICANN 77, because it seems relevant to the At-Large CPWG community ... *"ICANN never ceases to pose fascinating issues in global governance. At ICANN 77, held in Washington DC June 12 – 16, a dramatic debate took place about ICANN’s proper scope of authority. Some interest groups (mainly Registries and GAC) want ICANN to be empowered to enforce compliance with Registry Voluntary Commitments (RVCs), formerly known as Public Interest Commitments (PICs). Civil society groups and some Internet businesses see in the proposed change a threat to freedom of expression on the internet and an attempt to undermine ICANN’s multistakeholder policy development process.* *Underlying this debate are important questions about the relationship between private contracting, multistakeholder governance, and public policy."* *...* *"The RVC problem is really a derivative of a more fundamental flaw in ICANN’s new TLD processes. Instead of defining clear, simple rules for nondiscriminatory awards of new TLDs, ICANN has created a bureaucratic morass of regulations and veto powers. The fate of a TLD application is not governed by any predictable rules. It is all discretionary, and the GAC in particular wants to be in a position to veto or modify applications and names that it doesn’t like.* *Fortunately, Registry commitments that are designed to regulate content and services and make ICANN their enforcer are clearly violations of ICANN’s fundamental bylaws. The plot to bypass bottom up policy making process cannot succeed unless those bylaws are modified, and the modification would be so fundamental and the social gain so miniscule that it is hard to imagine it ever happening.* *Never underestimate the ability of ICANN’s board, the GAC and DNS industry short-term self-interest to screw things up, however. Keep an eye on this process, and we hope this blog post helped you understand the stakes."*

10 12

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

July 19, 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, 19 July 2023 at 19:00 UTC for 90 mins. For other times: https://tinyurl.com/4h3r8vaw The agenda (to be updated) and call details can be found at: https://community.icann.org/x/wILxDg<https://community.icann.org/x/iICCDg> 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: 1638 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

REMINDER - Draft call for comments on ALAC statement on Pending Rec 17.2
by Heidi Ullrich July 17, 2023

July 17, 2023

Dear All, A friendly reminder of the call for end-user feedback to the ICANN Board’s indicative concerns on the pending Subsequent Procedures PDP Recommendation 17.2, which addresses the scope of financial resources offered to qualified applicants for applicant support. Please refer to the background information in this Google doc [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1fXWzGyf7uI1f…> for more understanding on the issues, and kindly provide comments (in suggest-mode) in the Google doc as prompted, no later than 26 July 2023. Kind regards, Heidi From: Heidi Ullrich <heidi.ullrich(a)icann.org> on behalf of ICANN Staff <staff(a)atlarge.icann.org> Date: Thursday, July 6, 2023 at 1:40 PM To: "cpwg(a)icann.org" <cpwg(a)icann.org> Cc: Jonathan Zuck <JZuck(a)innovatorsnetwork.org>, Justine Chew <justine.chew.icann(a)gmail.com>, ICANN Staff <staff(a)atlarge.icann.org> Subject: Draft call for comments on ALAC statement on Pending Rec 17.2 Dear All, On behalf of the Justine Chew, ALAC Liaison to the GNSO, please respond to this call for end-user input to the ICANN Board’s indicative concerns on the pending Subsequent Procedures PDP Recommendation 17.2. Recommendation 17.2 is the recommendation which addresses the scope of financial resources offered to qualified applicants for applicant support. Please refer to the background information in this Google doc [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1fXWzGyf7uI1f…> for more understanding on the issues, and kindly provide comments (in suggest-mode) in the Google doc as prompted, no later than 26 July 2023. Please feel free to contact Justine directly (justine.chew.icann(a)gmail.com<mailto:justine.chew.icann@gmail.com>) should you have questions regarding this call for input. 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

UPDATED Meeting invitation: (NO ES interpretation) - At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 12 July 2023 at 13:00 UTC
by ICANN At-Large Staff July 12, 2023

July 12, 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, 12 July 2023 at 13:00 UTC for 90 mins, (so we can get back on our regular rotation) For other times: https://tinyurl.com/y5tuczz2 The agenda (to be updated) and call details can be found at: https://community.icann.org/x/jpaZDg<https://community.icann.org/x/iICCDg> 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 & FR: 3535 (PLEASE NOTE ES Interpretation will NOT be available) 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

***REMINDER*** Meeting invitation: (NO ES interpretation) - At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 12 July 2023 at 13:00 UTC
by ICANN At-Large Staff July 12, 2023

July 12, 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, 12 July 2023 at 13:00 UTC for 90 mins, (so we can get back on our regular rotation) For other times: https://tinyurl.com/y5tuczz2 The agenda and call details can be found at: https://community.icann.org/x/jpaZDg 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 & FR: 3535 (PLEASE NOTE ES Interpretation will NOT be available) 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

FOR REVIEW: Possible Draft Joint ALAC/GAC Advice on Contention Resolution
by ICANN At-Large Staff July 10, 2023

July 10, 2023

Dear All, On behalf of Jonathan Zuck, ALAC Chair, please find a possible draft joint ALAC/GAC Advice statement on the topic of Contention Resolution for your review and comment (see: Google document<https://docs.google.com/document/d/1aPmsyavTtqqb7J7aXQgEmGCC-fFazrLMloXQe6j…>). Please use the suggesting mode or add comments no later than 11 July. Comments made to this draft statement will be discussed during the CPWG Meeting<https://docs.google.com/document/d/1aPmsyavTtqqb7J7aXQgEmGCC-fFazrLMloXQe6j…> scheduled on 12 July at 13:00 UTC. Many thanks. 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, 12 July 2023 at 13:00 UTC
by ICANN At-Large Staff July 7, 2023

July 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, 12 July 2023 at 13:00 UTC for 90 mins, (so we can get back on our regular rotation) For other times: https://tinyurl.com/y5tuczz2 The agenda (to be updated) and call details can be found at: https://community.icann.org/x/jpaZDg<https://community.icann.org/x/iICCDg> 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

Draft call for comments on ALAC statement on Pending Rec 17.2
by ICANN At-Large Staff July 6, 2023

July 6, 2023

Dear All, On behalf of the Justine Chew, ALAC Liaison to the GNSO, please respond to this call for end-user input to the ICANN Board’s indicative concerns on the pending Subsequent Procedures PDP Recommendation 17.2. Recommendation 17.2 is the recommendation which addresses the scope of financial resources offered to qualified applicants for applicant support. Please refer to the background information in this Google doc [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1fXWzGyf7uI1f…> for more understanding on the issues, and kindly provide comments (in suggest-mode) in the Google doc as prompted, no later than 26 July 2023. Please feel free to contact Justine directly (justine.chew.icann(a)gmail.com<mailto:justine.chew.icann@gmail.com>) should you have questions regarding this call for input. 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

REMINDER / Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 05. July 2023 t 13:00 UTC
by ICANN At-Large Staff July 5, 2023

July 5, 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, 05 July 2023 at 13:00 UTC for 90 mins. For other times:https://tinyurl.com/35c5pnpw The agenda (to be updated) and call details can be found at: https://community.icann.org/x/7ZKZDg 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

DRAFT COMMENT: Amendments to the Base gTLD RA and RAA
by Alan Greenberg July 4, 2023

July 4, 2023

I suggested something short and sweet and there was general CPWG agreement. FIRST DRAFT: DNS Abuse has been discussed and debated within ICANN for what seems forever. Going back to 2010, a GNSO group (Registration Abuse Policies Implementation Drafting Team - RAP-‐IDT) identified issues and recommended actions be taken. Much talk, little action. We have repeatedly heard registrars say that compliance should take action against “bad actors” and ICANN Compliance saying that they did not have the tools. The ALAC has repeatedly, over many years, advised that that the obvious need was for registrars and ICANN Org to sit down and ensure that ICANN have the necessary tools. It is with collective pleasure that the ALAC compliments registrars and ICANN Org for finally doing just that. There are no doubt additional changes that the ALAC could identify to make the RAA/RA changes even better in our view, but this is not the time for that discussion. The ALAC supports the planned contractual improvements and encourages all parties to take whatever action necessary to ensure that they are implemented with minimal delay.

4 3