May 2024 - CPWG - lists.icann.org

Re: [CPWG] Are Blockchain Domains within the Mission of ICANN - WAS RE: Questions to the board about distributed DNS
by Chokri Ben Romdhane Oct. 18, 2024

Oct. 18, 2024

Dear Friends, Please find the record of the Emerging Identifier Technologies <https://icann.zoom.us/rec/play/4ZhSDuzFnVqw66kYgnTuHdDzi_RH0IFCKqKuAzmmcFy7…> session , held during the ICANN75 meeting, it provides some use cases of the emerging identifiers technologie. Thank you @MOULOUD KHELIF <kelif(a)hotmail.com> for the reminder. Friendly regards Chokri Le sam. 27 août 2022 à 19:17, Evan Leibovitch <evan(a)telly.org> a écrit : > On Thu, Aug 25, 2022 at 5:39 AM Chokri Ben Romdhane <chokribr(a)gmail.com> > wrote: > > >> But be aware if you confirm that the collision issues is/will never >> happened , as you have mentioned in your previous mail, and cross your >> finger that the regular DNS market will continue to attract more customers, >> compared to those NFT, Blockchain TLDs considering the ease of DNS >> management and security they are conferred to end users. >> > > Hi again, > > You made one fatal error in your assessment above: Internet end-users are > not registrants. > > End users don't care about DNS management, and the security THEY seek is > access to registrant details in the case of domains used for abuse. > The "security" you mention protects registrants and works against the > interests of end-users. > > It's totally possible that the hubris of DNS alternatives may lead to > collisions, but end-users will never see the effect of that, Browsers > continue to use the ICANN root and to date have never seen the benefit of > pointing to alternames. Plus, two of the biggest browser makers, Google and > Microsoft, have a deep vested interest in obstructing any alternative DNS. > Any alternate DNS hoping to be successful would need to create its own > browser, which is what the TOR project did. > > So even if alternative DNSs create TLDs that duplicate ICANN's they will > never present any collision or confusion to end-users. The only losers will > be registrants in the alternate systems. I have zero pity for them and they > are certainly not ALAC's concern or even ICANN's. > > Cheers, > - Evan > >

11 33

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

Fwd: [council] UPDATED LINK | Please share: ICANN80 Policy Outlook Report is now available
by Justine Chew May 30, 2024

May 30, 2024

FYI Kind regards, Justine ---------- Forwarded message --------- From: Terri Agnew Date: Fri, 31 May 2024 at 01:49 Subject: [council] UPDATED LINK | Please share: ICANN80 Policy Outlook Report is now available **Updated link below. Dear All, The ICANN80 Policy Outlook Report is now available! https://go.icann.org/outlook80 Happy reading! Kind regards, Terri Policy Team Supporting the GNSO _______________________________________________ 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.

2 1

At-Large Consolidated Policy Working Group (CPWG)
by ICANN Policy Calendar May 28, 2024

May 28, 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 0

ICANN80 Prep Week: Update on the New gTLD Program Next Round
by Justine Chew May 27, 2024

May 27, 2024

Sharing with those interested in the Next Round. Kind regards, Justine ---------- Forwarded message --------- From: Next Round Policy Implementation < NextRound_PolicyImplementation(a)icann.org> Date: Mon, 27 May 2024 at 16:52 Subject: [SubPro-IRT] Status update on the new gTLD Program: Next Round is available To: subpro-irt(a)icann.org <subpro-irt(a)icann.org> Dear all, Please note that the Pre-ICANN80 status update on the new gTLD Program: Next Round is now available for download: https://www.icann.org/en/system/files/files/status-update-new-gtld-program-…. A prep week session will take place on Tuesday 28 May at 18.00 UTC (see https://icann80.sched.com/event/1daZG/new-gtld-program-next-round-implement… ). Best regards, Renate _______________________________________________ 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.

1 0

Action Needed | Call for Volunteers | PPSAI Implementation Review Team
by Andrew Chen May 23, 2024

May 23, 2024

Dear CPWG Members, As mentioned during the 22 May CPWG call<https://community.icann.org/pages/viewpage.action?pageId=335839738#PDPs--77…>, please find below ICANN org’s Privacy and Proxy Services Accreditation Issues (PPSAI) Policy Implementation Review Team (IRT) Call for Volunteers information<https://www.icann.org/en/announcements/details/icann-seeks-volunteers-for-t…>. If you wish to join the (IRT), please email irt-rsvp(a)icann.org<mailto:irt-rsvp@icann.org> with the subject line "PPSAI Policy Implementation Review Team candidate" and cc staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. Please review the “Who Should Join” and “Required Skills and Knowledge” sections below for additional details. The Call for Volunteers window will close on 31 May 2024. The Internet Corporation for Assigned Names and Numbers (ICANN) is seeking volunteers to assist in the implementation of the policy recommendations<https://gnso.icann.org/sites/default/files/filefield_48305/ppsai-final-07de…> detailed in the Generic Names Supporting Organization's Privacy and Proxy Services Accreditation Issues (PPSAI) Policy Development Process (PDP) Final Report. The ICANN Board adopted all recommendations of the PPSAI PDP Working Group on 9 August 2016<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…>. Supported by a volunteer IRT, the ICANN organization (org) began implementing the recommendations in 2016. The implementation was put on hold in 2019<https://www.icann.org/en/system/files/correspondence/namazi-to-drazek-et-al…> due to overlapping issues with ongoing work. Following the publication of the Registration Data Policy<https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en> on 21 February 2024, ICANN org is now seeking to convene an IRT to support continuing implementation of the PPSAI Recommendations. Per the Consensus Policy Implementation Framework<https://www.icann.org/uploads/ckeditor/CPIF_v2.0_2019CLEAN.pdf> and the IRT Principles and Guidelines<https://www.icann.org/en/system/files/files/irt-principles-guidelines-23aug…>, the IRT will: * Serve as a resource to ICANN org on policy and technical questions that arise. * Review the implementation documentation as drafted by ICANN org for consistency with Final Report<https://gnso.icann.org/sites/default/files/filefield_48305/ppsai-final-07de…> recommendations. * Advise on technical and operational details. Who Should Join Any interested party, particularly those who were involved in the previous work, and who have a deep understanding of the Final Report, are encouraged to volunteer. Previous IRT members should reconfirm their interest to participate (if applicable). Required Skills and Knowledge * Understanding of the Final Report of the PPSAI PDP and its recommendations. * Ability to work constructively in a diverse group of stakeholders. * Willingness to join calls outside of standard office hours. Time Commitment * Approximately 10 to 20 hours per month for the duration of the project. IRT Start Date June 2024 How to Apply To join the IRT as a participant, please email irt-rsvp(a)icann.org<mailto:irt-rsvp@icann.org> with the subject line "PPSAI Policy Implementation Review Team candidate" by 31 May 2024. Further Details For further details, please see the community workspace wiki<https://community.icann.org/x/lQDSEw>. 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

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

May 22, 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, 22 May 2024 at 19:00 UTC for 90 mins, For other times: https://tinyurl.com/5ejeuau2<http://tinyurl.com/bdcm479f> The agenda (to be updated) and call details can be found at: https://community.icann.org/x/_oEEF <https://community.icann.org/x/cABkEw> 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: (subject to availability) 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

**TODAY 19:00 UTC ** At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 22 May 2024 at 19:00 UTC
by ICANN At-Large Staff May 22, 2024

May 22, 2024

Dial-outs & Apologies = Please do NOT reply to all Demandes d’appels & excuses = Merci de ne PAS répondre a tous Llamadas y disculpas = Por favor, NO responda a todos **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, 22 May 2024 at 19:00 UTC for 90 mins, For other times: https://tinyurl.com/5ejeuau2 The agenda and call details can be found at: https://community.icann.org/x/_oEEF 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: (subject to availability) 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 0

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

May 22, 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