May 2023 - CPWG - lists.icann.org

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

May 11, 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, 17 May 2023 at 13:00 UTC for 90 mins. For other times: https://tinyurl.com/d5b4ksy4 The agenda (to be updated) and call details can be found at: https://community.icann.org/x/moSCDg<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 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

PLEASE READ: Next Steps on NomCom2 Review and Operating Plans and Budgets
by ICANN At-Large Staff May 11, 2023

May 11, 2023

Dear Members of the ALAC, CPWG and OFB-WG, Please see below a note from Holly Raiche, the Chair of the OFB-WG, regarding next steps from Monday’s joint ALAC-OFB-WG meeting. ** Dear All, Three issues arose from the joint meeting of the OFB-WG and ALAC. The first (NomCom2 Review) needs a quick response. NomCom2 Review - Comments Due 29 May - COMMITTEE MEMBERS WANTED Given the very short space of time to provide comments, could anyone interested in responding to this issue let staff know BY THURSDAY, 11 May, and prepare a draft answers to the questions by 19 May - or at the latest- 22 May, allowing time for ALAC to vote on the response. Please see the Bylaws Amendments and Documents to Implement the NomCom2 Review<https://community.icann.org/display/alacpolicydev/Bylaws+Amendments+and+Doc…> workspace for the details and the template for the statement. Correspondence on NomCom Rebalancing This is another proposal coming out of the NomCom2 Review. While the GNSO has not responded to this recommendation - and thus it is not listed for public comment - the Board is still seeking a response from other AC/SOs. The members of the NomCom review group above could also develop a response to this request. See the Correspondence to the ALAC Chair<https://www.icann.org/en/system/files/correspondence/sinha-to-zuck-26apr23-…>. Operating Plans and Budgets FY24-28 Operating, and Financial Plans will take effect on 1 July 2023 if no Rejection Action Petition is raised. The meeting reviewed the planning process for next (financial) year’s Operating plans and budgets. The plans and budget will be published for public comments in July/August. Please let Holly know if you want to be part of the team to respond to the documents as they become available. There will also be a session during Prep Week on 31 May on the budgets. Staff will send a note with the details shortly. The links to all relevant documents are on the agenda<https://community.icann.org/pages/viewpage.action?pageId=243433717> of the joint OFB WG/ALAC meeting Kind regards, Holly ** 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 1

Webinars Next Week: Registration Data Request Service (RDRS) and EPDP on Internationalized Domain Names (EPDP-IDNs)
by Chantelle Doerksen May 10, 2023

May 10, 2023

Dear all, As mentioned during today’s CPWG call, staff wish to flag the two policy development related webinars scheduled for next week: Early development of the Registration Data Request Service (formerly known as the WHOIS Disclosure System). Two webinar times: · Tues, 16 May from 13:00-14:30 UTC | Register: https://icann.zoom.us/webinar/register/WN_NYL6fh9-SVWmEHeVQ4R4yQ · Weds, 17 May from 03:00-04:30 UTC | Register: https://icann.zoom.us/webinar/register/WN_xkAdv7uOTNeEOsM0_c-txQ Phase 1 Initial Report on the Internationalized Domain Names EPDP (EPDP-IDNs). To help the community learn more about the key recommendations and facilitate participation in the Public Comment proceeding. Weds, 17 May at 11:00-12:30 UTC | Webinar details: https://community.icann.org/display/epdpidn/2023-05-17+IDNs+EPDP+Community+… Best, Chantelle

1 0

GGP Update + request for feedback
by Sarah T. Kiden May 10, 2023

May 10, 2023

Dear CPWG, Thank you for the feedback to our GGP presentation at the just concluded CPWG meeting. There were some pending issues on the chat; for example, I need to check with our WG about under-represented communities in developed regions. We had an extensive discussion about this - some members felt that we should not open it up too much that it presents loopholes, while others felt that some communities in developing regions deserve support. Several scenarios were presented - would the program support small businesses in under-served regions? How about public entities (e.g., if a ccTLD that is operated by a public entity applies for support)? So it is an evolving discussion, and we are happy to check with the WG and come back to you (Greg, Justine and the CPWG) about this. For now, the agreement was to use the UN definition <https://unstats.un.org/unsd/methodology/m49/#fn2> for under-developed, and then use the GAC <https://gac.icann.org/working-group/gac-working-group-on-underserved-region…> and SubPro <https://gnso.icann.org/sites/default/files/file/field-file-attach/final-rep…> definition for under-served. Roberto promised to follow up, so we are happy to discuss this. This is the GAC definition: *An under-served region is defined as one that:* - *Does not have a well developed DNS and/or associated industry or economy; and/or * - *Has low awareness within its government of ICANN, ICANN’s role and functions and policy processes and the way that these policies affect it.* We have also noted John's suggestion about adjusting the review period to 3 years instead of 2 to investigate if applicants are still in business as registry operators. This is a welcome suggestion. Finally, kindly take a look at the attached document with revised lifecycle elements, implementation guidance and success metrics, then share any feedback with (preferably before our next GGP meeting on Monday, 08 May). The document is also available on the Wiki <https://community.icann.org/pages/viewpage.action?pageId=240617770#PDPs--62…> . Regards, Sarah

5 4

Meeting Summary for At-Large Consolidated Policy Working Group (CPWG)
by DANIEL NANGHAKA via Otter.ai May 10, 2023

May 10, 2023

1 0

Live Notes Now: At-Large Consolidated Policy Working Group (CPWG)
by DANIEL NANGHAKA via Otter.ai May 10, 2023

May 10, 2023

1 0

STARTING IN 15 MINS! **REMINDER** Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 10 May 2023 at 19:00 UTC
by ICANN At-Large Staff May 10, 2023

May 10, 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, 10 May 2023 at 19:00 UTC for 90 mins. For other times: https://tinyurl.com/33s49wx3 The agenda and call details can be found at: 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 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

Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 10 May 2023 1
by ICANN At-Large Staff May 10, 2023

May 10, 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, 10 May 2023 at 19:00 UTC for 90 mins. For other times: https://tinyurl.com/33s49wx3 The agenda (to be updated) and call details can be found at: 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 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

.NET Public Comment Period
by mike palage.com May 9, 2023

May 9, 2023

Hello All, In response to the constructive dialog regarding the .NET Registry Agreement, or more specifically the Registry Registrar Agreement (RRA), I wanted to bring the community the following update to the .NET Public Comment Page posted April 26th, see https://www.icann.org/en/public-comment/proceeding/proposed-renewal-of-the-… I believe ICANN echoes many of the points I was previously trying to make on the CPWG list about this being a largely standardized provision in other agreements. Interestingly, ICANN has provided specific links to RRAs of other major Registry Operators. What I find somewhat concerning is that 2 of the documents are labeled confidential (GoDaddy and Google) and 1 is labeled "Not for Publication" (Identity Digital). By way of background, ICANN operates a mailing list which I believe is restricted to ICANN accredited registrars to which ICANN posts any potential Registry RRA changes for Registrar review. I know the registries that I have worked with generally do not make these documents publicly available, which I believe is why most are labeled confidential. Verisign to my knowledge is the only Registry Operator required to publicly publish their RRA as part of their Registry Agreement. So on one hand it is a good thing that ICANN is providing clear evidence of the previous point I was trying to make. However, I am hopeful that ICANN got permission from these Registry Operators before posting their RRA which many consider confidential. Best regards, Michael

2 1

GNSO-TPR Small Team proposal on transfer disputes (Resending with Google form included)
by Steinar Grøtterød May 4, 2023

May 4, 2023

Dear all, The majority of all transfer disputes are settled in a friendly way by the involved registrars. The GNSO-TPR created a Small Team with the task to codify the informal process when there is a dispute of a (inter-registrar) transfer (but a TDRP was not started). At the GNSO-TPR call on May 2, 2023, the chair asked all to get feedback from their stakeholders on whether the Small Team proposal should be “policy” or not. The deadline for feedback was set to Monday May 8, 2023 I have copied the Small Team proposal to a “At-Large” version<https://docs.google.com/document/d/16eXaNTW8pZXQSqZ7ksj-oMc1VPhYAyawNcfDT2C…> and kindly ask for our view whether this should be “policy” or not. My recommendation is to implement the proposal into the Inter-Registrar Transfer Policy, hence tune the wording in to more “policy text”. Please make your comment to https://docs.google.com/document/d/16eXaNTW8pZXQSqZ7ksj-oMc1VPhYAyawNcfDT2C… and indicate if you are in favor of making this a policy or not. The document includes a Google form for your “vote”. Please answer the form within May 7, 2023 @ 23:59 CET Regards, Steinar Grøtterød At-Large Representative Transfer Policy Review Policy Development Process (GNSO-TPR PDP)

2 1