April 2024 - GNSO-TPR - lists.icann.org

Post Call | Transfer Policy Review PDP WG | Tuesday, 09 April 2024
by Julie Bisland April 10, 2024

April 10, 2024

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Tuesday, 09 April 2024 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/bgATEw> (attendance included) and the GNSO Master calendar [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…>. These include: * Attendance * Audio recording * Zoom recording (including audio, visual, rough transcript, and chat.) * Transcript * Agenda and Notes/Action Items As a reminder only members and alternates can join the call as a Panelist, observers can join as an Attendee to listen. For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-tpr/> and the main wiki page<https://community.icann.org/x/P4aUCQ>. Thank you. With kind regards, Julie

1 0

2024-04-09 Transfer Policy Review PDP WG Call - Follow Up
by Feodora Hamza April 9, 2024

April 9, 2024

Dear TPR WG members, Please find below the brief notes and action items from today’s meeting. The next meeting will take place on Tuesday 16 April 2024 at 16:00 UTC. Kind regards, Christian, Caitlin, Berry, Julie and Feodora 2024-04-09 Transfer Policy Review PDP WG Call<https://community.icann.org/display/TPRPDP/2024-04-09+Transfer+Policy+Revie…> Main discussion and action items 1. Welcome and Chair Updates 2. Review WG inputs to CORD Requirements for Initial Report worksheet<https://docs.google.com/document/d/1_lZLOmNQJKqAsAqxHTv8W5TQeRIm58YvS4vCPIw…> * BC raised some concerns regarding Rec 2.3 and 2.4. Could lead to confusion and misunderstanding. * Some comments include the lack of rationale. * Cannot Live with comments focus on Rec 2.3, 2.4, 3, 3.4 and 4. * How can WG explain that the aim is not to reduce security levels with some changes but to be adaptive for many business models? * Suggestion: Members could put questions to WG via webinar regarding Recs? * Group 1)a) organised a previous webinar focus on awareness raising rather than answering questions. * Rec 2.4: The working group recommends eliminating from the future Change of Registrant Data Policy the requirement that the Registrar impose a 60-day inter-registrar transfer lock following a Change of Registrant. * WG suggested to remove 60 day lock for change of registrant, BC believes 30 day lock should be by default. * WG discussed the rationale of 30 days? Why that number why not other? * Some members suggested that current Rec 2.4 might cause compliance issues. * Others indicated that no amount of lock will provide more security. * BC doesn’t support opt-out of notification reg Rec. 3 due to security concerns. * BC suggests that for Rec 3.4 that notificiation should occure before change of registrant. * Can live with, but with changes focus on Rec: 3, 3.4, 4 and 17. * Members informed the WG that registrants have indicated to leave because they receive too many notification. * Members point out the importance of notifications due to security. * Initial comments results show the following input to the Recs: CANNOT LIVE WITH BC · (2.3) Keep confirmation to prior/new before change · (2.4) Reduce lock to 30 days, keep opt out · (3, 3.4, 4) No opt out of notifications, notifications before not after CAN LIVE WITH (with change) At-Large · (3, 4) No opt out of notifications · (17) Established Relationship concern RySG · (17) require record-keeping for removing lock early RrSG · (17) torn - some satisfied with ER test, others would remove ER restrictions · (4.4) Q - clarify record maintenance BC · (1.3) remove second part or require disclosure GRAMMATICAL EDITS RySG (Jim) · (3) add ref to Rec 2 · (4.6) update for consistency RrSG · (3, 3.4, 4.2, 17) clarity + grammar SUPPORT REC AS IS At-Large · 1,2,3 RySG · 1,2,3,4 RrSG · 1,2 BC · 1, 1.1, 1.2 (not 1.3) · 2.1, 2.3 (not 2, 2.2, 2.4) · 3.1, 3.2, 3.3, 3.5, 3.6, 3.7 (not 3, 3.4) 1. Continue discussion of updated Group 1(a) Rec 17 (Established Relationships) * At-Larg and RySG have concerns reg Rec 17. * AT-large considers the “Established Relationship” is confusing and difficult to understand. Reconsider wording? * RySG would like to see changes regarding the record keeping. * WG members suggested to discuss in more depth during the next call. 2. AOB * Not discussed Feodora Hamza Policy Development Support Manager (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +32 496 30 24 15 Email: feodora.hamza(a)icann.org<mailto:feodora.hamza@icann.org> Website: www.icann.org<http://www.icann.org>

1 0

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 16 April 2024
by Julie Bisland April 9, 2024

April 9, 2024

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 16 April 2024 at 16:00 UTC for 90 minutes. * If unable to attend, members must communicate their alternate replacement using this google form<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…>. Zoom Information: Main Zoom Webinar link: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/95363727469?pwd=N3A3OWFS…> Passcode: @TP/^*4wg# If you are joining via audio only: One tap mobile: US: +19294362866,,95363727469#,,,,*7490739013# or +13017158592,,95363727469#,,,,*7490739013# Telephone: Dial (for higher quality, dial a number based on your current location): US: +1 929 436 2866 or +1 301 715 8592 or +1 312 626 6799 or +1 669 900 6833 or +1 253 215 8782 or +1 346 248 7799 or 888 788 0099 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 953 6372 7469 Passcode: 7490739013 International numbers available: https://icann.zoom.us/u/acdLFXPLp6 <https://urldefense.com/v3/__https:/icann.zoom.us/u/acdLFXPLp6__;!!PtGJab4!v…> Members, alternates, and observers all have different access and participation directions, please read below! ALL: Before joining the call: * Please send apologies and dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> * Visit the Wiki Agenda meeting page: https://community.icann.org/x/cgATEw * Time conversion link: https://tinyurl.com/yeeb5w9a ONLY FOR MEMBERS & ALTERNATES: * Staff will promote members and alternates to panelist once joined. * Chat: Please select Everyone so everyone can see your chat, and so it’s captured in the recording. * If unable to attend, members must communicate their alternate replacement using this google form<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…>. * Alternate assignments will be publicly posted to the Alternate Log-Transfer Policy Review PDP<https://community.icann.org/x/V4aUCQ> wiki page. * Alternates (not replacing a member): Rename your line by adding 3 Zs (zzz) before your name and add, your affiliation - alternate after your name. * Alternates (not replacing a member) are not allowed to engage in the chat or use any of the other zoom room functionalities such as raising hands or agreeing/disagreeing. ONLY FOR OBSERVERS: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Julie Policy Team Supporting the GNSO

1 0

Re: [GNSO-TPR] TPR WG Action Item: CORD Recommendations Worksheet
by Christian Wheeler April 9, 2024

April 9, 2024

Dear TPR WG members, As a reminder, the current Action Item for each Working Group member is to fill out the CORD Recommendations for Initial Report<https://docs.google.com/document/d/1_lZLOmNQJKqAsAqxHTv8W5TQeRIm58YvS4vCPIw…> worksheet for your represented group, starting on page 9. Please complete this assignment before tomorrow’s meeting (09 April at 16:00 UTC) so that the WG can discuss the groups’ initial inputs on these preliminary CORD recommendations. Thank you. Kind regards, Caitlin, Berry, Julie, Feodora, and Christian From: GNSO-TPR <gnso-tpr-bounces(a)icann.org> on behalf of rcarney--- via GNSO-TPR <gnso-tpr(a)icann.org> Reply-To: "rcarney(a)godaddy.com" <rcarney(a)godaddy.com> Date: Monday, April 1, 2024 at 10:23 AM To: "gnso-tpr(a)icann.org" <gnso-tpr(a)icann.org> Subject: Re: [GNSO-TPR] TPR WG Action Item: CORD Recommendations Worksheet Hello Everyone, Just wanted to provide a nudge to make sure that everyone is working on the homework to review the CORD Recommendations [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1_lZLOmNQJKqA…> and fill-out the worksheet putting each CORD Recommendation into one of the four tables for your respective represented group. As staff mentioned on our last call, this is not the last opportunity to provide input, but we want to have as thorough of a review now versus trying to address later. Talk to everyone tomorrow. Thanks Roger ________________________________ From: GNSO-TPR <gnso-tpr-bounces(a)icann.org> on behalf of Christian Wheeler <christian.wheeler(a)icann.org> Sent: Wednesday, March 27, 2024 3:41 PM To: gnso-tpr(a)icann.org <gnso-tpr(a)icann.org> Subject: [GNSO-TPR] TPR WG Action Item: CORD Recommendations Worksheet Some people who received this message don't often get email from christian.wheeler(a)icann.org. Learn why this is important [aka.ms]<https://urldefense.com/v3/__https:/aka.ms/LearnAboutSenderIdentification__;…> Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Dear WG Members, We have reached an important point in our work where we need feedback from all working group members. We are nearing completion of our Group 1(b) Change of Registrant Data recommendations, and we will be finalizing them over the next few weeks. In short, if you are unable to participate over the next 2-3 weeks, please ensure your alternate(s) are available to participate on your behalf so that all representative groups share their perspectives on this important topic. The format under which we will be gathering feedback should be familiar to many of you. Support Staff has compiled the draft preliminary recommendations in this Group 1(b) Recommendations for Initial Report worksheet [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1_lZLOmNQJKqA…>. The yellow highlighted text denotes text that Support Staff has edited based on feedback from the last meeting. By Tuesday, 9 April, we ask that all Working Group members: 1. Please review the draft preliminary recommendations [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1_lZLOmNQJKqA…> in detail. 2. Using the tables provided (starting on p.9 of the worksheet [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1_lZLOmNQJKqA…>), please identify any recommendations you believe should be changed. The tables contemplate levels of support (or lack of support): * Cannot live with the recommendation as written - this means that, unless significantly altered, your group cannot live with the text being included in the Initial Report * Could live with, but would prefer a change * Grammatical/typographical edits * Support recommendation as written 1. If you do not agree with the current text or believe edits are necessary, please identify the category (can’t live with, could live with but prefer edited text, or grammatical change), and propose alternate text. 2. If you can support the recommendation as written, please also affirmatively indicate your support in the green table. 3. Please provide your feedback by group, rather than in an individual capacity. We will be using the next 2-3 weeks to go over proposed updated text (if any). We ask all groups to review the recommendations to ensure you are comfortable with the proposed text for purposes of inclusion in the Initial Report. While we do plan to have additional time to review the comprehensive report as a whole (including Group 1(a) and Group 2), the time to raise fundamental issues with the Group 1(b) text is now. Thank you for your attention and participation. Best regards, Caitlin, Berry, Julie, Feodora, and Christian

2 1

**Starting in 15 minutes** REMINDER | Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 09 April 2024
by Feodora Hamza April 9, 2024

April 9, 2024

Starting in **Starting in 15 minutes** / Visit the Wiki Agenda meeting page: https://community.icann.org/x/bgATEw Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 09 April 2024 at 16:00 UTC for 90 minutes. * If unable to attend, members must communicate their alternate replacement using this google form<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…>. Zoom Information: Main Zoom Webinar link: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/95363727469?pwd=N3A3OWFS…> Passcode: @TP/^*4wg# If you are joining via audio only: One tap mobile: US: +19294362866,,95363727469#,,,,*7490739013# or +13017158592,,95363727469#,,,,*7490739013# Telephone: Dial (for higher quality, dial a number based on your current location): US: +1 929 436 2866 or +1 301 715 8592 or +1 312 626 6799 or +1 669 900 6833 or +1 253 215 8782 or +1 346 248 7799 or 888 788 0099 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 953 6372 7469 Passcode: 7490739013 International numbers available: https://icann.zoom.us/u/acdLFXPLp6 <https://urldefense.com/v3/__https:/icann.zoom.us/u/acdLFXPLp6__;!!PtGJab4!v…> Members, alternates, and observers all have different access and participation directions, please read below! ALL: Before joining the call: * Please send apologies and dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> * Visit the Wiki Agenda meeting page: https://community.icann.org/x/bgATEw * Time conversion link: https://tinyurl.com/3k2nh6rp [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/3k2nh6rp__;!!PtGJab4!-5NQzyt…> ONLY FOR MEMBERS & ALTERNATES: * Staff will promote members and alternates to panelist once joined. * Chat: Please select Everyone so everyone can see your chat, and so it’s captured in the recording. * If unable to attend, members must communicate their alternate replacement using this google form<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…>. * Alternate assignments will be publicly posted to the Alternate Log-Transfer Policy Review PDP<https://community.icann.org/x/V4aUCQ> wiki page. * Alternates (not replacing a member): Rename your line by adding 3 Zs (zzz) before your name and add, your affiliation - alternate after your name. * Alternates (not replacing a member) are not allowed to engage in the chat or use any of the other zoom room functionalities such as raising hands or agreeing/disagreeing. ONLY FOR OBSERVERS: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Julie Policy Team Supporting the GNSO

1 0

REMINDER | Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 09 April 2024
by Terri Agnew April 8, 2024

April 8, 2024

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 09 April 2024 at 16:00 UTC for 90 minutes. * If unable to attend, members must communicate their alternate replacement using this google form<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…>. Zoom Information: Main Zoom Webinar link: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/95363727469?pwd=N3A3OWFS…> Passcode: @TP/^*4wg# If you are joining via audio only: One tap mobile: US: +19294362866,,95363727469#,,,,*7490739013# or +13017158592,,95363727469#,,,,*7490739013# Telephone: Dial (for higher quality, dial a number based on your current location): US: +1 929 436 2866 or +1 301 715 8592 or +1 312 626 6799 or +1 669 900 6833 or +1 253 215 8782 or +1 346 248 7799 or 888 788 0099 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 953 6372 7469 Passcode: 7490739013 International numbers available: https://icann.zoom.us/u/acdLFXPLp6 <https://urldefense.com/v3/__https:/icann.zoom.us/u/acdLFXPLp6__;!!PtGJab4!v…> Members, alternates, and observers all have different access and participation directions, please read below! ALL: Before joining the call: * Please send apologies and dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> * Visit the Wiki Agenda meeting page: https://community.icann.org/x/bgATEw * Time conversion link: https://tinyurl.com/3k2nh6rp [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/3k2nh6rp__;!!PtGJab4!-5NQzyt…> ONLY FOR MEMBERS & ALTERNATES: * Staff will promote members and alternates to panelist once joined. * Chat: Please select Everyone so everyone can see your chat, and so it’s captured in the recording. * If unable to attend, members must communicate their alternate replacement using this google form<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…>. * Alternate assignments will be publicly posted to the Alternate Log-Transfer Policy Review PDP<https://community.icann.org/x/V4aUCQ> wiki page. * Alternates (not replacing a member): Rename your line by adding 3 Zs (zzz) before your name and add, your affiliation - alternate after your name. * Alternates (not replacing a member) are not allowed to engage in the chat or use any of the other zoom room functionalities such as raising hands or agreeing/disagreeing. ONLY FOR OBSERVERS: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Julie Policy Team Supporting the GNSO

1 0

TPR WG Action Item: CORD Recommendations Worksheet
by Christian Wheeler April 5, 2024

April 5, 2024

Dear WG Members, We have reached an important point in our work where we need feedback from all working group members. We are nearing completion of our Group 1(b) Change of Registrant Data recommendations, and we will be finalizing them over the next few weeks. In short, if you are unable to participate over the next 2-3 weeks, please ensure your alternate(s) are available to participate on your behalf so that all representative groups share their perspectives on this important topic. The format under which we will be gathering feedback should be familiar to many of you. Support Staff has compiled the draft preliminary recommendations in this Group 1(b) Recommendations for Initial Report worksheet<https://docs.google.com/document/d/1_lZLOmNQJKqAsAqxHTv8W5TQeRIm58YvS4vCPIw…>. The yellow highlighted text denotes text that Support Staff has edited based on feedback from the last meeting. By Tuesday, 9 April, we ask that all Working Group members: 1. Please review the draft preliminary recommendations<https://docs.google.com/document/d/1_lZLOmNQJKqAsAqxHTv8W5TQeRIm58YvS4vCPIw…> in detail. 2. Using the tables provided (starting on p.9 of the worksheet<https://docs.google.com/document/d/1_lZLOmNQJKqAsAqxHTv8W5TQeRIm58YvS4vCPIw…>), please identify any recommendations you believe should be changed. The tables contemplate levels of support (or lack of support): * Cannot live with the recommendation as written - this means that, unless significantly altered, your group cannot live with the text being included in the Initial Report * Could live with, but would prefer a change * Grammatical/typographical edits * Support recommendation as written 1. If you do not agree with the current text or believe edits are necessary, please identify the category (can’t live with, could live with but prefer edited text, or grammatical change), and propose alternate text. 2. If you can support the recommendation as written, please also affirmatively indicate your support in the green table. 3. Please provide your feedback by group, rather than in an individual capacity. We will be using the next 2-3 weeks to go over proposed updated text (if any). We ask all groups to review the recommendations to ensure you are comfortable with the proposed text for purposes of inclusion in the Initial Report. While we do plan to have additional time to review the comprehensive report as a whole (including Group 1(a) and Group 2), the time to raise fundamental issues with the Group 1(b) text is now. Thank you for your attention and participation. Best regards, Caitlin, Berry, Julie, Feodora, and Christian

4 7

Proposed Agenda - TPR Working Group Meeting #125 - 09 April 2024
by Christian Wheeler April 4, 2024

April 4, 2024

Dear TPR WG members, Please find below the proposed agenda for our next call, taking place on Tuesday, 09 April 2024 at 16:00 UTC. As a reminder, the current Action Item for WG members is to review the draft CORD recommendations<https://docs.google.com/document/d/1_lZLOmNQJKqAsAqxHTv8W5TQeRIm58YvS4vCPIw…> and using the four tables provided on p.9 of the worksheet<https://docs.google.com/document/d/1_lZLOmNQJKqAsAqxHTv8W5TQeRIm58YvS4vCPIw…>, identify all recommendations you can support and/or believe should be changed. Please provide your feedback by group, rather than in an individual capacity. We ask that you strive to complete this exercise before our TPR WG call on Tuesday, 09 April at 16:00 UTC, as we plan to discuss the inputs to this worksheet<https://docs.google.com/document/d/1_lZLOmNQJKqAsAqxHTv8W5TQeRIm58YvS4vCPIw…> during our next meeting. Thank you, and we look forward to seeing you all virtually. Kind regards, Caitlin, Julie, Feodora, Berry, and Christian ---------- Transfer Policy Review - Meeting #125 Proposed Agenda 09 April 2024 1. Welcome and Chair Updates 2. Review WG inputs to CORD Requirements for Initial Report worksheet 3. Continue discussion of updated Group 1(a) Rec 17 (Established Relationships) 4. AOB

1 0

Action needed | Minimum Version Requirement of Zoom | by 04 May 2024
by Terri Agnew April 4, 2024

April 4, 2024

Dear all, Beginning May 4, Zoom will enforce a new minimum version [support.zoom.com]<https://urldefense.com/v3/__https:/support.zoom.com/hc/en/article?id=zm_kb&…> to use the Zoom application. This allows participants to use Zoom’s features and ensures security enhancements are in place. Users who are not up to date will join via browser. We encourage you to update your Zoom Client [support.zoom.com]<https://urldefense.com/v3/__https:/support.zoom.com/hc/en/article?id=zm_kb&…>. Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

2024-04-02 Transfer Policy Review PDP WG Call Follow- Up
by Feodora Hamza April 3, 2024

April 3, 2024

Dear TPR WG members, Please find below the brief notes and action items from yesterday’s meeting. The next meeting will take place on Tuesday 9 April 2024 at 16:00 UTC. Kind regards, Christian, Caitlin, Berry, Julie and Feodora 2024-04-02 Transfer Policy Review PDP WG Call<https://community.icann.org/display/TPRPDP/2024-04-02+Transfer+Policy+Revie…> 1. Welcome and Chair Updates * Attendees were reminded to complete the CORD Recommendations Worksheet:https://docs.google.com/document/d/1_lZLOmNQJKqAsAqxHTv8W5TQeRIm5… * Input on Group 1(b) recommendations is due on Tuesday, 9 April. * Chair opend the floor for questions: * Questions were raised regarding the impact of opting out from notifications, considering security risks or reduction of spam. * Operational issues for registrants and the rationale behind switching from confirmation to notification were discussed, emphasizing the need for clarity. 2. Preview Group 1(b) Recommendations Impact Chart * CORD Impact Analysis doc: https://docs.google.com/document/d/15h3nZhNboNnQHVnOuib33YNvKe7rnHYShFIevyz… * The support staff team, along with Roger, assessed the impact of the recommendations, specifically for Group 1(b) CORD recommendations. * Differences between proposed policy recommendations and current requirements in the transfer policy were highlighted. * The importance of providing rationale for significant policy changes was emphasized to aid the working group in solidifying its recommendations. * Attendees were informed that the document is subject to change and encouraged to contribute. * The need for accompanying rationale for high-impact changes was stressed. * Suggestions were made to adjust the coloring and assessment for neutrality and to include notes about changes driven by other policy or regulatory factors. 3. Continued Discussion of Recommendation 17(a) (Established Customer) * Discussion continued from the previous meeting, addressing concerns raised by WG members regarding Recommendation 17(a). * Attendees explored ideas or approaches that would not pose security concerns. Suggestions included clarifying the text, specifying criteria for established customers, and defining registrar obligations. * Attendees deliberated on the duration of the established customer period and the need for additional rationale to explain implementation and enforcement. * The importance of solid rationale and the likelihood of receiving comments without full context were emphasized. 4. Updates made as a result of last week's discussion * Not discussed. 5. Any Other Business (AOB) * Not discussed. Feodora Hamza Policy Development Support Manager (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +32 496 30 24 15 Email: feodora.hamza(a)icann.org<mailto:feodora.hamza@icann.org> Website: www.icann.org<http://www.icann.org>

1 0