October 2024 - CPWG - lists.icann.org

Draft Statement on .COM RA
by mike palage.com Nov. 5, 2024

Nov. 5, 2024

Hello All, In advance of our CPWG call later today, I wanted to share a draft of the proposed ALAC statement, see https://docs.google.com/document/d/1sk4dwR5_EGGj8vTwvtaxnfimgCQSkCFkxo0V142… My apologies for not getting this out sooner, but I have been juggling several day job conflicts. However, the statement is only two pages, so it is rather concise and an easy read. Taking the feedback of Avri on the doom and gloom of "this represents a systemic threat to the ICANN multistakeholder model" I have toned that wording down to "undermines the multistakeholder" which I think is a reasonable compromise. I look forward to answering any questions people may have on today's call. Best regards, Michael

11 23

RIPE on ICP-2
by avri＠doria.org Oct. 31, 2024

Oct. 31, 2024

Hi, I have been online attending RIPE89 this week. As part of the RIPE Community Plenary 4. Report from the ASO AC and ICP-2 Community Consultation Hervé Clement, ASO AC https://ripe89.ripe.net/archives/video/1533 For anyone following the topic, it may be interesting hearing it from that side of the perspective. avri

1 0

REQUEST FOR COMMENTS: ICANN81 Board Questions to the ALAC
by ICANN At-Large Staff Oct. 30, 2024

Oct. 30, 2024

Dear All, On behalf of Jonathan Zuck, ALAC Chair, you are requested to add your comments to two of the questions that the ICANN Board has asked the ALAC for discussion during the ICANN81 Board meeting with the ALAC. The two questions are below: 1. In addition to the resources that Org has provided, is there anything else that ALAC/At-Large needs to bring applicants into the Next Round from underserved communities? At-Large Shepherds: Hadia Elminiawi 1. ICANN's new CEO will come on board in December. What do you think his top three priorities should be, and why? Please be as concrete as possible. At-Large Shepherd: Justine Chew Please add your comments by Thursday, 7 November at 23:59 UTC using the comments function here: https://docs.google.com/document/d/1qTpHWuYlIvWDHIHcc166r85mK4hf2lVUSrsXMpW…. Kind regards, At-Large staff 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_215869771]

1 0

UPDATED with Zoom only - Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 30 October 2024 at 19:00 UTC
by ICANN At-Large Staff Oct. 30, 2024

Oct. 30, 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, 30 October 2024 at 19:00 UTC for 90 mins, For other times: https://tinyurl.com/223bemkp<https://tinyurl.com/5yzurhkp> The agenda (to be updated) and call details can be found at: https://community.icann.org/x/ogH_Fg 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 No Adigo - ZOOM ONLY (Due to ICANN81 Prep week, please note, there will NOT be interpretation!) 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>

2 3

Updates and comments to the GNSO-TPR received comments to the Initial Report
by Steinar Grøtterød Oct. 30, 2024

Oct. 30, 2024

Dear all, As informed on CPWG meetings, my proposals to the updated recommendations to the GNSP Transfer Policy Review PDP will be added to the At-Large Google document https://docs.google.com/presentation/d/1hvP7GQPvjpST6wuC0sKOFkocmri5ZRNrNvm…. All comments and suggestions to my proposals are welcomed. All with the link to the document can add comments. The Google document will be updated weekly based on the discussions in the GNSO-TPR Working Group. Regards, Steinar Grøtterød At-Large representaive

1 0

Fwd: [council] ICANN81 GNSO Policy Briefing & ICANN81 Policy Outlook Report
by Justine Chew Oct. 30, 2024

Oct. 30, 2024

Sharing, for those who are interested. Kind regards, Justine ---------- Forwarded message --------- From: Julie Bisland via council <council(a)icann.org> Date: Wed, 30 Oct 2024 at 04:16 Subject: [council] ICANN81 GNSO Policy Briefing & ICANN81 Policy Outlook Report Dear All, On behalf of the GNSO Team, I am happy to report that the* GNSO Policy Briefing for ICANN81* is now available for download: http://go.icann.org/gnsobriefing. In addition, the *ICANN81 Policy Outlook Report* is available: https://go.icann.org/outlook81 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…> _______________________________________________ council mailing list -- council(a)icann.org To unsubscribe send an email to council-leave(a)icann.org _______________________________________________ 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

Re: [ALAC-Announce] ICANN81 Policy Outlook Report is now available
by Justine Chew Oct. 29, 2024

Oct. 29, 2024

On Tue, 29 Oct 2024 at 04:17, ICANN At-Large Staff via ALAC-Announce < alac-announce(a)icann.org> wrote: > Dear All, > > > > The ICANN81 Policy Outlook report <https://go.icann.org/outlook81> is now > available! > > > > In preparation for the ICANN81 Annual General Meeting, the Policy > Development Support team has developed the ICANN81 Policy Outlook Report. > This report provides a high-level overview of the planned work and > activities of the Supporting Organizations and Advisory Committees during > ICANN81. > > > > Thank you and Happy Reading! > > > > Kind regards, > > > > At-Large Staff > > ICANN Policy Staff in support of the At-Large Community > > Website: 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> > > [image: signature_2461901693] > > > > > > > _______________________________________________ > ALAC-Announce mailing list -- alac-announce(a)icann.org > To unsubscribe send an email to alac-announce-leave(a)icann.org > > At-Large Official Site: http://www.atlarge.icann.org > _______________________________________________ > 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

Re: Talking points for Board consultation on RDRS
by alberto＠soto.net.ar Oct. 28, 2024

Oct. 28, 2024

And if someone is not certified in that country, the Digital Signature Administration is responsible for reliably identifying them, whether they are a natural person or legal entity. Locally… Best Alberto De: Vanda Scartezini <vanda(a)scartezini.org> Enviado el: lunes, 28 de octubre de 2024 15:24 Para: alberto(a)soto.net.ar; 'Alan Greenberg' <greenberg.alan(a)gmail.com>; 'CPWG' <cpwg(a)icann.org> Asunto: Re: [CPWG] Re: Talking points for Board consultation on RDRS Agree Alberto and Alan with such suggestions. We need to have stronger guarantees and Blockchain, dif=gital certification are key and very usual these days. Here government offers free digital signature ( we have national identification too so easy for the government to check it. From: Alberto Soto via CPWG <cpwg(a)icann.org <mailto:cpwg@icann.org> > Date: Sunday, 27 October 2024 at 17:04 To: 'Alan Greenberg' <greenberg.alan(a)gmail.com <mailto:greenberg.alan@gmail.com> >, 'CPWG' <cpwg(a)icann.org <mailto:cpwg@icann.org> > Subject: [CPWG] Re: Talking points for Board consultation on RDRS I agree Alan. Regarding "Improvements will be needed. Some level of registration and authentication of applicants would be an advantage, but it should not be too cumbersome." Why is the digital signature system not used? There are many governments that offer digital signature services. Interested parties in each country should digitally certify themselves before that local system and at the other end would be ICANN: I don't know if each government would do it for free or for a fee. There are private providers of digital signature services, but I don't know the cost at this time. Regards Alberto De: Alan Greenberg via CPWG <cpwg(a)icann.org <mailto:cpwg@icann.org> > Enviado el: domingo, 27 de octubre de 2024 00:18 Para: CPWG <cpwg(a)icann.org <mailto:cpwg@icann.org> > Asunto: [CPWG] Talking points for Board consultation on RDRS * A system such as the RDRS/SSAD is needed, but its use by Registrars (and Registries) should be mandatory. * Enhancements will be needed. Some level of requestor registration and authentication would be an asset, but it must not be overly cumbersome. * Although the RDRS is not perfect, it should not be shut down until an enhanced or replacement system is available. * The system must include legitimate access to Privacy/Proxy beneficial user information * Implementation of national laws and regulations will introduce specific registrar and registry requirements. ICANN policy needs to ensure a level playing field. * The At-Large Community hopes that a mandatory and uniform system will strengthen trust and transparency between end users and businesses * ICANN org should consider reassessing the operational cost of implementing SSAD recommendations as it will provide insight in how those specifications should be altered.

1 0

Talking points for Board consultation on RDRS
by Alan Greenberg Oct. 27, 2024

Oct. 27, 2024

- A system such as the RDRS/SSAD is needed, but its use by Registrars (and Registries) should be mandatory. - Enhancements will be needed. Some level of requestor registration and authentication would be an asset, but it must not be overly cumbersome. - Although the RDRS is not perfect, it should not be shut down until an enhanced or replacement system is available. - The system must include legitimate access to Privacy/Proxy beneficial user information - Implementation of national laws and regulations will introduce specific registrar and registry requirements. ICANN policy needs to ensure a level playing field. - The At-Large Community hopes that a mandatory and uniform system will strengthen trust and transparency between end users and businesses - ICANN org should consider reassessing the operational cost of implementing SSAD recommendations as it will provide insight in how those specifications should be altered.

3 3

[At-Large Community] ICANN81 Board Engagement Session Talking Points
by ICANN At-Large Staff Oct. 25, 2024

Oct. 25, 2024

Dear At-Large Community Members, As we prepare for ICANN81 Prep Week, we kindly request your attention to review the ALAC/At-Large ICANN81 Board Engagement Session Talking Points<https://docs.google.com/document/d/16k6mnbxmXaVVEnT84TYsMpd-KowPuTxn227GjE9…> in preparation for the 28 October Board Engagement Session<https://sched.co/1nJjv>. These points are essential to ensure alignment on the ALAC/At-Large messaging regarding the Registration Data Request Service (RDRS) and New gTLD Program Applications in rounds or continuously accepting applications (first come, first serve). ICANN81 Board Engagement Session Talking Points: https://docs.google.com/document/d/16k6mnbxmXaVVEnT84TYsMpd-KowPuTxn227GjE9… Thank you to those who have contributed to the development of these talking points. Please let us know if you have any questions. 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