- CPWG - lists.icann.org

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

Jan. 7, 2025

EN - IMPORTANT INFORMATION FOR FRENCH AND SPANISH INTERPRETATION FR - INFORMATIONS IMPORTANTES POUR LES PARTICIPANTS EN FRANCAIS ET ESPAGNOL ES - INFORMACIÓN IMPORTANTE PARA LOS PARTICIPANTES FRANCESES Y ESPAÑOLES Dear All, EN - IMPORTANT INFORMATION FOR FRENCH AND SPANISH INTERPRETATION * To listen to interpretation for this meeting, please join Zoom using Computer Audio. * Choose the language you will listen to from the Language Interpretation menu in the Zoom toolbar. * Before speaking, ensure you have selected the language you will speak from in the interpretation menu. If for any reason, the audio you are listening to is silent, please select “unmute original audio”. FR - INFORMATIONS IMPORTANTES POUR LES PARTICIPANTS EN FRANCAIS ET ESPAGNOL * Pour écouter l’interprétation de cette reunion, veuillez rejoindre Zoom en utilisant l’audio ordinateur/tablette/telephone portable. Choisissez la langue que vous écouterez dans le menu “Interprétation” linquistique de la barre d’outils Zoom. * Avant de parler, assurez-vous d'avoir sélectionné la langue dans laquelle vous parlerez dans le menu d'interprétation. Si, pour une raison quelconque, l'audio que vous écoutez est silencieux, veuillez sélectionner « réactiver l'audio original ». ES - INFORMACIÓN IMPORTANTE PARA LOS PARTICIPANTES FRANCESES Y ESPAÑOLES * Para escuchar la interpretación para esta reunión, únase a Zoom mediante Computer Audio * Elija el idioma que escucharà en el menu Interpretación de idiomas en la barra de herramientas de Zoom * Antes de hablar, asegúrese de haber seleccionado el idioma que hablará en el menú de interpretación. Si por algún motivo el audio que está escuchando está en silencio, seleccione "activar audio original". Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call has been scheduled for Wednesday, 08 January 2025 at 14:00 UTC for 90 mins, For other times: https://tinyurl.com/4b99pykn The agenda and call details can be found at: https://community.icann.org/x/VoD3GQ 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 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

Amended Latin Script Diacritics PDP Charter
by Justine Chew Jan. 7, 2025

Jan. 7, 2025

Dear ALAC colleagues, At yesterday's ALAC Monthly Meeting, I reported that the GNSO Council will be considering and voting on an amended Latin Script Diacritics PDP Charter at its 19 Dec meeting. Three amendments are proposed to the earlier draft charter; these are as follows: 1) limiting the scope of work; 2) adjusting the membership structure to make it an “Open Model”; and 3) including the Global Public Interest (GPI) Framework <https://community.icann.org/display/prjxplrpublicint/GPI+Toolkit> and its checklist <https://docs.google.com/spreadsheets/d/1uVOXywoowxvM1Hn5GuCkkinuZiMc4smc/ed…> as a reference for analysis when conducting the PDP, per the ICANN Board’s recommendation. I welcome all 3 amendments, in particular the Open Model PDP and inclusion of the GPI Framework checklist which are completely aligned with positions I have put forth before. Having said that, Alan made an important point that even with an Open Model PDP, it would be necessary and useful for the ALAC to have designated participants who can bring PDP WG deliberations to the CPWG for discussion and to relay the ALAC/At-Large positions emanating from CPWG back to the PDP WG. Please let me know *by 18 Dec* whether the ALAC would like to relay any sentiments to Council on this amended PDP charter (which is attached). I intend to seek some clarify on next steps (eg when a call for a WG Chair, participants, etc will be made and when might the PDP WG be expected to commence its work). Thank you, Justine Chew ALAC Liaison to the GNSO GNSO Liaison Report Workspace <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> ------

2 4

Call for Volunteers - Phase 2 Final Report on the EPDP-IDNs for ICANN Board Consideration
by Andrew Chen Jan. 2, 2025

Jan. 2, 2025

Dear CPWG Members, On behalf of the CPWG co-chairs, we are seeking At-Large Community volunteers to consider the Phase 2 Final Report on the EPDP-IDNs for ICANN Board Consideration<https://www.icann.org/en/public-comment/proceeding/phase-2-final-report-on-…> recently posted for public comment by ICANN org. Your insights and/or expertise on the subject matter for public comment would be helpful for: * Firstly, reviewing and identifying any need for the ALAC to submit a comment, and secondly, where such need arises, presenting issues - in the form of bullet points - for discussion at one or more Working Group calls. * If the Working Group subsequently reaches consensus on the need for an ALAC comment, volunteering as a penholder to craft a concise thoughtful response (i.e. an ALAC statement) to this public comment proceeding. As this public comment proceeding will close on 03 February 2025, the proposed schedule for the above-mentioned tasks is as follows: * Reviewer(s): Establish if an ALAC comment is needed. * Reviewer(s): Initial Bullet Point(s) presentation and rationale for discussion in order to establish working group consensus – CPWG call on 08 January 2025 And if needed, * Penholder(s): First Draft Statement presentation and discussion - CPWG call on 15 January 2025 * Community: Comment on Draft Statement – 16 January 2025 – 21 January 2025 * Penholder(s): Final Draft Statement presentation – CPWG call on 22 January 2025 * ALAC: Vote on Final Statement – 23 January 2025 – 28 January 2025 * Staff: Submission of ALAC Statement – 29 January 2025 If you are interested in volunteering to be a reviewer and/or penholder, please reach out to At-Large Staff (staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>), copying the CPWG co-chairs, Olivier Crépin-Leblond (ocl(a)gih.com<mailto:ocl@gih.com>) and Avri Doria (avri(a)doria.org<mailto:avri@doria.org>), before the 08 January 2025 CPWG call. Your participation is greatly appreciated, and we look forward to your contributions! Kind Regards, ICANN Staff in support of the At-Large Community

1 0

What could have been, and what can still be
by Evan Leibovitch Dec. 25, 2024

Dec. 25, 2024

As a followup to my critique of a recent CircleID "defense" of multistakeholderism on the NARALO mailing list, I want to offer up some brief constructive commentary on what is generally regarded as Internet Governance: In a recent conversation with a well-known ICANNer, I was asked: if I could replace the current management of the Internet with some other model, what would it be? Complaining is easy, but does a superior alternative exist? My answer didn't take too long: something largely similar to the model that governs the world's air travel. The United Nations treaty agency ICAO and the airline industry IATA have their headquarters within a four-minute walk in downtown Montréal. They are highly interdependent -- maybe even symbiotic -- but have very specific roles that are generally not duplicated. They have public advisory bodies, regional bureaus and expert groups that propose standards and regulations. In other words, this infrastructure has been multistakeholder since the 1940s, long before the tech world thought it had invented the concept. And, generally speaking, that infrastructure has been proven to work, even between warring countries. Airlines under intense international sanctions remain members <https://www.iata.org/en/about/members/airline-list/s7-airlines/338/>. Safety and stability are the prime objectives of both, though IATA of course cares more about commercial sustainability while ICAO cares about interoperability and environmental sustainability. Having two separate complementary bodies offers plenty of advantages because they keep each other in check; as a result we have neither full government capture nor full commercial capture. The public interest is promoted through both bodies, especially if one is more concerned about results (ie, a global airline industry that is safe, reliable, adaptable and sustainable) than process (ie, splitting hairs about representation). I believe that this model is adaptable to Internet governance and that it would work better than what we think we have now. I also believe it is still possible. What needs to change is a) the arrogance of asserting the Internet is the first instance of multistakeholder governance, b) the misbelief that ICANN is a public-serving example of it, and c) the visceral hostility to anything multilateral, even as a partial component. -- Evan Leibovitch, Toronto Canada @evanleibovitch / @el56

8 15

Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 08 January 2025 at 14:00 UTC
by ICANN At-Large Staff Dec. 20, 2024

Dec. 20, 2024

EN - IMPORTANT INFORMATION FOR FRENCH AND SPANISH INTERPRETATION FR - INFORMATIONS IMPORTANTES POUR LES PARTICIPANTS EN FRANCAIS ET ESPAGNOL ES - INFORMACIÓN IMPORTANTE PARA LOS PARTICIPANTES FRANCESES Y ESPAÑOLES Dear All, EN - IMPORTANT INFORMATION FOR FRENCH AND SPANISH INTERPRETATION * To listen to interpretation for this meeting, please join Zoom using Computer Audio. * Choose the language you will listen to from the Language Interpretation menu in the Zoom toolbar. * Before speaking, ensure you have selected the language you will speak from in the interpretation menu. If for any reason, the audio you are listening to is silent, please select “unmute original audio”. FR - INFORMATIONS IMPORTANTES POUR LES PARTICIPANTS EN FRANCAIS ET ESPAGNOL * Pour écouter l’interprétation de cette reunion, veuillez rejoindre Zoom en utilisant l’audio ordinateur/tablette/telephone portable. Choisissez la langue que vous écouterez dans le menu “Interprétation” linquistique de la barre d’outils Zoom. * Avant de parler, assurez-vous d'avoir sélectionné la langue dans laquelle vous parlerez dans le menu d'interprétation. Si, pour une raison quelconque, l'audio que vous écoutez est silencieux, veuillez sélectionner « réactiver l'audio original ». ES - INFORMACIÓN IMPORTANTE PARA LOS PARTICIPANTES FRANCESES Y ESPAÑOLES * Para escuchar la interpretación para esta reunión, únase a Zoom mediante Computer Audio * Elija el idioma que escucharà en el menu Interpretación de idiomas en la barra de herramientas de Zoom * Antes de hablar, asegúrese de haber seleccionado el idioma que hablará en el menú de interpretación. Si por algún motivo el audio que está escuchando está en silencio, seleccione "activar audio original". Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call has been scheduled for Wednesday, 08 January 2025 at 14:00 UTC for 90 mins, For other times: https://tinyurl.com/4b99pykn<https://tinyurl.com/2xh6b9k4> The agenda (to be updated) and call details can be found at: https://community.icann.org/x/VoD3GQ 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 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

At-Large Consolidated Policy Working Group (CPWG)
by ICANN Policy Calendar Dec. 20, 2024

Dec. 20, 2024

EN - IMPORTANT INFORMATION FOR FRENCH AND SPANISH INTERPRETATION FR - INFORMATIONS IMPORTANTES POUR LES PARTICIPANTS EN FRANCAIS ET ESPAGNOL ES - INFORMACIÓN IMPORTANTE PARA LOS PARTICIPANTES FRANCESES Y ESPAÑOLES Dear All, EN - IMPORTANT INFORMATION FOR FRENCH AND SPANISH INTERPRETATION * To listen to interpretation for this meeting, please join Zoom using Computer Audio. * Choose the language you will listen to from the Language Interpretation menu in the Zoom toolbar. * Before speaking, ensure you have selected the language you will speak from in the interpretation menu. If for any reason, the audio you are listening to is silent, please select “unmute original audio”. FR - INFORMATIONS IMPORTANTES POUR LES PARTICIPANTS EN FRANCAIS ET ESPAGNOL * Pour écouter l’interprétation de cette reunion, veuillez rejoindre Zoom en utilisant l’audio ordinateur/tablette/telephone portable. Choisissez la langue que vous écouterez dans le menu “Interprétation” linquistique de la barre d’outils Zoom. * Avant de parler, assurez-vous d'avoir sélectionné la langue dans laquelle vous parlerez dans le menu d'interprétation. Si, pour une raison quelconque, l'audio que vous écoutez est silencieux, veuillez sélectionner « réactiver l'audio original ». ES - INFORMACIÓN IMPORTANTE PARA LOS PARTICIPANTES FRANCESES Y ESPAÑOLES * Para escuchar la interpretación para esta reunión, únase a Zoom mediante Computer Audio * Elija el idioma que escucharà en el menu Interpretación de idiomas en la barra de herramientas de Zoom * Antes de hablar, asegúrese de haber seleccionado el idioma que hablará en el menú de interpretación. Si por algún motivo el audio que está escuchando está en silencio, seleccione "activar audio original". Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call has been scheduled for Wednesday, 08 January 2025 at 14:00 UTC for 90 mins, For other times: https://tinyurl.com/4b99pykn<https://tinyurl.com/2xh6b9k4> The agenda (to be updated) and call details can be found at: https://community.icann.org/x/VoD3GQ 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 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

At-Large Consolidated Policy Working Group (CPWG) PLACEHOLDER
by ICANN Policy Calendar Dec. 20, 2024

Dec. 20, 2024

DETAILS TO FOLLOW AFTER MEETING ON JANUARY 15TH!

1 0

At-Large Consolidated Policy Working Group (CPWG) PLACEHOLDER
by ICANN Policy Calendar Dec. 20, 2024

Dec. 20, 2024

DETAILS TO FOLLOW AFTER MEETING ON JANUARY 8TH!

1 0

Call for Volunteers - Third Proceeding for Proposed Language for Draft Sections of Next Round AGB - by
by ICANN At-Large Staff Dec. 19, 2024

Dec. 19, 2024

Dear CPWG Members, On behalf of CPWG co-chairs, we are seeking At-Large Community volunteers to consider the Third Proceeding for Proposed Language for Draft Sections of Next Round Applicant Guidebook (AGB)<https://www.icann.org/en/public-comment/proceeding/third-proceeding-for-pro…> recently posted for public comment by ICANN org. Your insights and/or expertise on the subject matter for public comment would be helpful for: * Firstly, reviewing and identifying any need for the ALAC to submit a comment, and secondly, where such need arises, presenting issues - in the form of bullet points - for discussion at one or more Working Group calls. * If the Working Group subsequently reaches consensus on the need for an ALAC comment, volunteering as a penholder to craft a concise thoughtful response (i.e. an ALAC statement) to this public comment proceeding. As this public comment proceeding will close on 07 February 2025, the proposed schedule for the above-mentioned tasks is as follows: * Reviewer(s): Establish if an ALAC comment is needed. * Reviewer(s): Initial Bullet Point(s) presentation and rationale for discussion in order to establish working group consensus – CPWG call on 08 January 2025 And if needed, * Penholder(s): First Draft Statement presentation and discussion - CPWG call on 15 January 2025 * Community: Comment on Draft Statement – 16 January 2025 – 21 January 2025 * Penholder(s): Final Draft Statement presentation – CPWG call on 22 January 2025 * Penholder(s): First and Final Draft Statement presentation – CPWG call on 29 January 2025 * ALAC: Vote on Final Statement – 30 January 2025 – 05 February 2025 * Staff: Submission of ALAC Statement – 06 February 2025 If you are interested in volunteering to be a reviewer, please reach out to At-Large Staff (staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>), copying the CPWG co-chairs, Olivier Crépin-Leblond (ocl(a)gih.com<mailto:ocl@gih.com>) and Avri Doria (avri(a)doria.org<mailto:avri@doria.org>) by 07 January 2025 at 23:59 UTC. The following AGB sections are open for comment: * Community Input and Dispute Resolution * Application Comments (Topic 28: Role of Application Comment) * GAC Member Early Warnings (Topic 30: GAC Consensus Advice and GAC Early Warning) * GAC Advice (Topic 30: GAC Consensus Advice and GAC Early Warning) * Singular/Plural Notification (Topic 24: String Similarity Evaluations) * Objections (Topic 31: Objections and Topic 32: Limited Challenge/Appeal Mechanism) * Topic 31: Objections and Topic 32: Limited Challenge/Appeal Mechanism * ICANN Dispute Resolution Procedure * ICANN Objection Appeals Procedure * New gTLD Program: Next Round Privacy Policy * Post-Contracting * DNS Stability * Security and Stability (Topic 26: Security and Stability) * Different TLD Types (Topic 4: Different TLD Types) * Legal Compliance Check Your participation is greatly appreciated, and we look forward to your contributions! Kind Regards, ICANN Staff in support of the At-Large Community

1 0

MINUTES FROM THE GNSO-TPR MEETING ON DECEMBER 17, 2024
by Andrew Chen Dec. 18, 2024

Dec. 18, 2024

Dear CPWG Members, On behalf of Steinar Grøtterød, we are sharing the minutes from the 17 December 2024 Transfer Policy Review. Please feel free to reach out if you have any questions. Review of updated recommendations Rec. #9: TAC Time to Live (TTL) Added by the Registry Stakeholder Group (RySG): 9.4: The Registry MAY reset any TAC to null4 prior to the end of the 336 hours (i) by agreement by the Registrar of Record OR (ii) without the agreement of the Registrar of Record in cases where when resetting the TAC to null is in the best interests of the Registrar of Record or the RNH, e.g., security breach, account compromise, etc. 9.5: If the Registry resets any TAC to null without the agreement of the Registrar of Record, the Registry MUST provide the rationale to the Registrar of Record if requested by the Registrar of Record. Rationale: Similar to the Registrars requirements, the Registry Operator MAY reset the Transfer Authorisation code (TAC). This option for the sponsoring Registrar and the Registry Operator will reduce the harm when there is a security breach, account compromise, etc. Reco. #17: Losing Form of Authorization (FOA) 17.5: The Transfer Confirmation MUST NOT include a mechanism for immediately approving the inter-Registrar transfer. Implementation Guidance: The working group notes that Recommendation 17.5 does not prevent Registrars from sending a transfer approval mechanism to the RNH, but rather stipulates that this mechanism must not be included within the Transfer Confirmation. Rationale: There is agreement to have a 5 days "freeze" from the time where the transfer is initiated. Rec. #17.2: The Transfer Confirmation language MUST include the Gaining Registrar’s IANA ID and a link to ICANN-maintained webpage listing accredited Registrars and corresponding IANA IDs. If available, the name of the Gaining Registrar MAY also be included. This notification shall not include an "auto approve link". Rec. #33: Request to GNSO for further work on Transfer Dispute Resolution Policy and Potential New Dispute Mechanism See TPR Public Comment Review <https://docs.google.com/document/d/1YODFe-aZOi1AQ3c8f2-y8MXtcUU4PjzsByFzk-d…> for proposed wording. Another session of discussion between At-Large and "the Rest". The final recommendation is not presented for the Working Group. My understanding is that there is consensus for a policy where the RNH can challenge improper transfers, including compromised and stolen domain names. However, the majority of the Registrars believe the TDPR is not the best place to add the RNH rights. -- 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