September 2022 - GNSO-TPR - lists.icann.org

Notes and action items - TPR WG Meeting #59 - 13 September 2022 at 16:00 UTC
by Julie Hedlund Sept. 13, 2022

Sept. 13, 2022

Dear TPR WG members, Please find below the notes and action items from today’s meeting. The next meeting will be at ICANN75 on Saturday, 17 September at 10:30-12:00 MYT (local time KL). Best regards, Emily, Julie, Berry, and Caitlin ACTION ITEMS/HOMEWORK -- Preparation for ICANN75: 1. Staff to incorporate points raised in discussion during the meeting on 13 September on recommendation #2 for WG members to review. 2. WG members to review the proposed edits in the Recommendation 2 Public Comment Working Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1gyy9xfe0-ymW…> and also the following documents: * Public Comment Review Tool – Recommendation 1<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…>: Comment #5 * Public Comment Review Tool - Recommendation 2<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…>: All Comments * Public Comment Review Tool - Recommendation 3<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…>: Comments #10, #11, #12 * Public Comment Review Tool - Recommendation 4:<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…> Comment #10 * Public Comment Review Tool – Additional Input<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…>: Comments #1-#11 * Leap of Faith Financial Services Comment [itp.cdn.icann.org]<https://urldefense.com/v3/__https:/itp.cdn.icann.org/public-comment/proceed…> (full text, especially pages 19-24, 31-39) Notes: Proposed Agenda 13 September 2022 1. Roll Call & SOI updates 2. Welcome and Chair Updates * Today’s discussion will be continued into ICANN75. * Do have a pretty big topic here. We knew we would get some comments back on it. Nothing unexpected, but a lot of good comments to go through. * Question: What are we discussing in Kuala Lumpur? Answer: There will be a quick overview of the status of the work followed by a working session. 3. Approach to Public Comment Review -- Begin Discussion of Comments on Elimination of the Losing FOA: Overview: * Discussion with staff and leadership on how best to support the review of public comments. * Last week we began a discussion in the WG on Rec 19 and we’ll come back to that. * But now we’ll focus on early recommendations and determined that it would be helpful to give the WG some discussion papers to call out proposals for changes to the recommendations and/or current policy. * Staff to describe the working document for Recommendation 2 and welcome feedback. Recommendation 2 Public Comment Working Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1gyy9xfe0-ymW…> * Top of document – recommendation text. * Staff will avoid doing any synthesis of the comments so WG members should review and be familiar with comments, but staff will highlight key points or areas of agreements, proposals. Key Principles for Public Comment Review: * If suggested edits are minor and editorial in nature, focus on whether you can live with them. * If suggested edits are substantive, focus on what new information or insights that have been provided by the commenter. * If concerns, information, or perspectives have already been considered in the development of the recommendations, consider how the report can strengthen the rationale by showing how these have been addressed and why the WG took the approach it did. * Members are representing their groups, not their individual or employer positions/perspectives. Now is the time to make sure you are aligned. * The goal is to make recommendations that achieve consensus support. If there isn’t consensus to change the policy, the existing policy remains in place. Proposal for using these documents: * Staff prepared documents ahead of time. * Use last 15 minutes of the call for homework -- review comments and working documents, and then prep for the next week’s call, including coordination with their groups as necessary. * After deliberations staff will collect key points and agreements, update the report with suggested edits to review over the mailing list. * Alternative: more offline homework with WG expected to take time every week to review comments and provide written analysis for staff to synthesize. For the EPDP this required WG members to meet in between meetings to do homework, but we aren’t sure that’s needed here. Discussion on Process: * Question: If a proposal is nearly the same as a recommendation or policy, do WG members have to go back to their groups for approval? Answer: Each group will have its own procedures, but we just want to guard against a representative from advocating for a position that is at odds with their group. WG members should ask their groups how they want to address proposals discussed in reviewing the comments. * Timing: Try to work through dependencies first, with consolidated elements of the comments; staff will capture the discussions and incorporate them into the working documents and set a time frame for discussions/responses from groups. * As we review the comments and as on last week’s call, there was momentum building to adjust the recommendation #19 to something that the WG can agree on taking into consideration the comments. This isn’t the last chance to develop final recommendations – there will be time later for the full WG to consider the new revised recommendation and to reconfirm with their respective groups. Where there is agreement on a change to a recommendation we want to determine where we have general agreement on the text. * Hard to get input from our groups incrementally without seeing the impact on the full policy. WG members should have flexibility with their groups to bring forward proposals and suggest how the group should approach them – WG members need to understand what their group wants to see in the final product. There will be time to review and discuss any draft final language with their groups. * We can adjust the process as necessary as we go. Summary of public comments – see: Recommendation 2 Public Comment Working Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1gyy9xfe0-ymW…> * A number of people (registrants and BC) said that registrants need a way to NACK/deny the transfer before it takes place. For some of these the recommendation eliminates the ability of a registrant to deny a transfer. * Consider whether these concerns are new and whether they need to be address. * Concern that if the losing FOA is eliminated some registrars may adopt security measures that would delay the provision of the TAC making the process slower. * Another element is about the security of the TAC – that measures to increase the security of the TAC are not sufficient to replace the security of the FOA, and the recommendations don’t safeguard the security of the TAC. * References supporting the security of the consent model. Request for data from registrars. Discussion points: * Whether these concerns are new and how to address them – consider whether to revise the recommendations. * Not sure we discussed all of these ideas and if we didn’t we should think about whether or how to address them. * Encourage WG members to look at the responses to the charter questions in relation to this recommendation. * Make sure we address the issue that the dispute resolution process is not the same as stopping a fraudulent transfer before it happens. * Consider whether we need to be more direct even if it is in our current rationale. * Should be able to document how the group consider the comment (see below as an example re: violation of RFC9154). WG Comments: * Not persuaded by these arguments, think we address them. But maybe we need a better rationale for the recommendations – to explain how the WG addressed with their recommendations the concerns being raised. * Note how the Losing FOA didn’t really go away, it is addressed by the TAC. Maybe ask the registrars for data. * A NACK isn’t necessarily a negative thing. NACKing doesn’t happen often to begin with and not all is related to fraud. * In terms of explaining the recommendations – we are making sure that fraudulent transfers don’t even get off the ground. * Re: assertion that RFC9154 is being violated – disagree with the commenter. There is no RFC problem here. * On the issue of affirmative response, the reality is the "affirmative response" is the fact that an RNH logged in to the registrar account. That's the first line of defense and the FOA doesn't fix that. If someone gets into your account they change all those points of contact and the FOA serves no purpose. I hope that's clear enough. The point is the issue is still covered, the same as always. * These concerns are interlinked and difficult to talk about them in isolation. For example, could increase the number of days before the TAC is revealed. * Staff will need help from WG members to confirm if the rationale in the Final Report properly addresses the concerns raised in public comment – the rationale has to address these directly. * Well of course it's vulnerable to theft once it's generated. That's always been true. If the RNH doesn't do their part to keep it safe, well, oh well. This proposed system works better because the TAC doesn't exist until it's needed, which is different than history. That's a significant improvement, in my opinion. * Those who have concerns about recommendation #2 should look at recommendation #3 – specifically 3.2 – elements of TAC provision, steps the RNH can take to NACK the transfer. * Think that there is a misunderstanding about the security properties of the Losing FOA. The reality is that the first line of defense is that fact that you’ve logged into the registrar account. People are misattributing security properties to the FOA. * The losing FOA did provide something that we aren’t requiring today, particularly a 5-day window for an action. So that needs additional rationale. * Should highlight that this is a huge advancement. * If an account got hacked you’d never see a NACK anyway. You have ACKs that are fraudulent that you don’t see. * So, yes the 5 day window to NACK has been removed from today's traditional transfer process. But isn't this what the TTL of the TAC is meant to compensate for? * No it doesn't. They are solving different problems. * There still can be a 5-day window to provide the TAC, it’s just not mandatory. Registrants can choose a registrar with that level of security if they wish, or not. That is the flexibility we built in. * The TAC TTL is just providing some protection for the TAC, limiting the overall window of vulnerability when a domain is eligible for a transfer. the 5 days window is an extra step for a registrant at a cost of the delay waiting for the transfer. 4. Planning for ICANN75 session: Saturday, 17 September at 10:30 MYT * Staff will send the agenda shortly and WG members should review. * WG will continue the discussion from today’s meeting, starting with recommendation #2. ACTION ITEMS/HOMEWORK -- Preparation for ICANN75: 1. Staff to incorporate points raised in discussion during the meeting on 13 September on recommendation #2 for WG members to review. 2. WG members to review the proposed edits in the Recommendation 2 Public Comment Working Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1gyy9xfe0-ymW…> and also the following documents: * Public Comment Review Tool – Recommendation 1<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…>: Comment #5 * Public Comment Review Tool - Recommendation 2<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…>: All Comments * Public Comment Review Tool - Recommendation 3<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…>: Comments #10, #11, #12 * Public Comment Review Tool - Recommendation 4:<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…> Comment #10 * Public Comment Review Tool – Additional Input<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…>: Comments #1-#11 * Leap of Faith Financial Services Comment [itp.cdn.icann.org]<https://urldefense.com/v3/__https:/itp.cdn.icann.org/public-comment/proceed…> (full text, especially pages 19-24, 31-39) 6. AOB

1 0

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 04 October 2022
by Julie Bisland Sept. 13, 2022

Sept. 13, 2022

NOTE: The TPR PDP WG will meet at ICANN75 on Saturday, 17 September at 10:30 MYT. Please see the ICANN75 Session page<https://75.schedule.icann.org/meetings/hNdkMxTP2FLu93z6h> for join information (you must be registered for ICANN75; Zoom participation links will be published here 24 hours before the session starts.) and the Agenda wiki page<https://community.icann.org/x/JAJpD>. See the invite below for the next regularly scheduled call taking place after ICANN75. ************************* Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 04 October 2022 at 16:00 UTC for 90 minutes. Zoom Room 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/DQVpD * Check your time zone: https://tinyurl.com/3cba46wf ONLY FOR MEMBERS & ALTERNATES: * Please join via the Main Zoom Webinar link above; staff will promote you to panelist. * Chat: Members (and alternates replacing members), please select Everyone so everyone can see and so it’s captured afterwards. * Alternate replacement confirmations – For tracking alternate replacements, use the google form [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…> to communicate the replacement (alternate) and the duration. This information 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 THREE Zs (zzz) before your name and add, in parentheses (your affiliation - alternate) after your name. To rename in Zoom, hover over your name and click ‘rename’. * 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

1 0

**AT THE TOP OF THE HOUR** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 13 September 2022
by Julie Bisland Sept. 13, 2022

Sept. 13, 2022

**AT THE TOP OF THE HOUR** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 13 September 2022 at 16:00 UTC for 90 minutes. Zoom Room 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/CQVpD * Check your time zone: https://tinyurl.com/ycwjfk6t [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/ycwjfk6t__;!!PtGJab4!5hD4G4b…> ONLY FOR MEMBERS & ALTERNATES: * Please join via the Main Zoom Webinar link above; staff will promote you to panelist. * Chat: Members (and alternates replacing members), please select Everyone so everyone can see and so it’s captured afterwards. * Alternate replacement confirmations – For tracking alternate replacements, use the google form [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…> to communicate the replacement (alternate) and the duration. This information 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 THREE Zs (zzz) before your name and add, in parentheses (your affiliation - alternate) after your name. To rename in Zoom, hover over your name and click ‘rename’. * 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

1 0

REMINDER | Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 13 September 2022
by Devan Reed Sept. 12, 2022

Sept. 12, 2022

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 13 September 2022 at 16:00 UTC for 90 minutes. Zoom Room 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/CQVpD * Check your time zone: https://tinyurl.com/ycwjfk6t<https://urldefense.com/v3/__https:/tinyurl.com/ycwjfk6t__;!!PtGJab4!4tbcTnn…> ONLY FOR MEMBERS & ALTERNATES: * Please join via the Main Zoom Webinar link above; staff will promote you to panelist. * Chat: Members (and alternates replacing members), please select Everyone so everyone can see and so it’s captured afterwards. * Alternate replacement confirmations – For tracking alternate replacements, use the google form<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…> to communicate the replacement (alternate) and the duration. This information 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 THREE Zs (zzz) before your name and add, in parentheses (your affiliation - alternate) after your name. To rename in Zoom, hover over your name and click ‘rename’. * 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

1 0

Proposed agenda for meeting #59 on Tuesday 13 September at 16:00 UTC
by Emily Barabas Sept. 12, 2022

Sept. 12, 2022

Dear Working Group members, Please find below the proposed agenda for the next meeting scheduled to take place tomorrow, Tuesday 13 September 2022 at 16:00 UTC. Prior to the call, please make sure to review the following and come prepared to discuss: * Recommendation 2 Public Comment Working Document<https://docs.google.com/document/d/1gyy9xfe0-ymW-irtY2gKSEy3za8IcG-GrF8EcCG…> * Public Comment Review Tool – Recommendation 1<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…>: Comment #5 * Public Comment Review Tool - Recommendation 2<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…>: All Comments * Public Comment Review Tool - Recommendation 3<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…>: Comments #10, #11, #12 * Public Comment Review Tool - Recommendation 4:<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…> Comment #10 * Public Comment Review Tool – Additional Input<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…>: Comments #1-#11 * Leap of Faith Financial Services Comment<https://itp.cdn.icann.org/public-comment/proceeding/Initial%20Report%20on%2…> (full text, especially pages 19-24, 31-39) Kind regards, Julie, Berry, Caitlin, and Emily Transfer Policy Review - Meeting #59 Proposed Agenda 13 September 2022 1. Roll Call & SOI updates 2. Welcome and Chair Updates 3. Approach to Public Comment Review 4. Begin Discussion of Comments on Elimination of the Losing FOA * Recommendation 2 Public Comment Working Document<https://docs.google.com/document/d/1gyy9xfe0-ymW-irtY2gKSEy3za8IcG-GrF8EcCG…> * Public Comment Review Tool – Recommendation 1<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…>: Comment #5 * Public Comment Review Tool - Recommendation 2<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…>: All Comments * Public Comment Review Tool - Recommendation 3<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…>: Comments #10, #11, #12 * Public Comment Review Tool - Recommendation 4:<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…> Comment #10 * Public Comment Review Tool – Additional Input<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…>: Comments #1-#11 * Leap of Faith Financial Services Comment<https://itp.cdn.icann.org/public-comment/proceeding/Initial%20Report%20on%2…> (full text, especially pages 19-24, 31-39) 5. Planning for ICANN75 session: Saturday, 17 September at 10:30 MYT 6. AOB

1 0

ICANN75 GNSO Policy Briefing Available for Download
by Julie Bisland Sept. 7, 2022

Sept. 7, 2022

Dear All, On behalf of the GNSO Team, I am happy to report that the GNSO Policy Briefing for ICANN75 is now available for download at https://go.icann.org/gnsobriefing. 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…>

1 0

Notes and action items - TPR WG Meeting #58 - 06 September 2022 at 16:00 UTC
by Julie Hedlund Sept. 6, 2022

Sept. 6, 2022

Dear TPR WG members, Please find below the notes and action items from today’s meeting. The next meeting will be Tuesday, 13 September at 16:00 UTC. Best regards, Emily, Julie, Berry, and Caitlin ACTION ITEM: WG members should be prepared to discuss the public comments on Recommendation #2<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…> of the Phase 1A Initial Report. Notes: Transfer Policy Review - Meeting #58 Proposed Agenda 6 September 2022 1. Roll Call & SOI updates 2. Welcome and Chair Updates * Busy next few weeks with ICANN75 coming up. * Public comment period ended and all comments (34) have been assembled. Support and identification of a few items to discuss. We’ll be reviewing all comments and updating recommendations as appropriate. * Update from Steiner on the At-Large summary of the CPWG discussion on Change of Registrant policy. See attached. * Had a fruitful discussion last week on the CPWG call. * Based on that discussion, if we are going to change anything on the transfer lock the CPWG would like some statistics/data supporting removing that part of the policy. But we don’t have any statistics. If we will have transfer lock period it might be reduced to less than 60 days. Specifically: “Input to the discussion were mostly connected to the question whether the present 60-days transfer lock after a change of registrant data is preventing domain name hijacking. Further - the majority of the CPWG attendees requested data about the volume of hijacked domain names. These statistics - if available, may indicate if the transfer lock after a change of registrant is needed. The discussion also covered whether a transfer lock is needed for mitigation of domain name hijacking.” * Discussion: * Wonder if Compliance has some data? * Registrars have indicated that they don’t have data. * Without data we should remove it. * From staff re: question about data: Compliance has provided data related to complaints about the lock itself in Phase 1A, but not specific enough in terms of hijacking. As to data to “prove” that a lock is necessary or not, we don’t have that level of breakdown/tracking to speak to that issue. * Compliance tracks transfer complaints in general, but does not break down to “inter registrar" vs. “COR”. * The best you can get is the NACK statistics from the Open Data Initiative, but only limited years and not recent. Does show significant use of the NACK, but can’t correlate it to hijacking. * Not sure that we can get valuable data as to why there was a NACK in the first place. * Registrars offer different levels of security and registrant can pick the model that fits their needs/shop around to get what they are looking for. * I also remember most complaints about COR to Compliance were people annoyed by not being to unlock their domains. For hijacked domains, the hijack happened even with COR process (which hijackers were able to bypass). * It’s a very interesting perspective. As registrars can and do provide security that is superior to minimum requirements under the Transfer Policy. Accordingly, it may be that this is the answer; leave it to registrants to select a registrar with desirable security protocols to prevent unauthorized transfer. 3. Review public comments on proposed edits to Transfer Policy section I.A.3.7.1 -- See Public Comment Review Tool for Recommendation 19<https://community.icann.org/display/TPRPDP/Phase+1A+-+Public+Comment+Review…> Overview of the Public Comment Review Tool (PCRT): * See the wiki page: https://community.icann.org/display/TPRPDP/Phase+1A+-+Public+Comment+Review… * Full compilation of 34 comments. Summary: * Include both those responding to specific questions and from those who didn’t follow the format. * Responses to questions. * Series of comments suggesting new topics that are consolidated. * Process and modalities (such as extension of the public comment period). * Series of comment that express concern about security issues. * PCRT: * For each recommendation, breakdown: support, support with wording change, significant change required, recommendation should be deleted, no opinion. Grouped the comments by type. * Grouped by themes. Recommendation #19 PCRT<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…> – Summary: * Expectation that WG members have reviewed these comments. * Support -- Ted Chang, RySG, ICANN Business Constituency (BC), ICANN Org, Samwel Kariuki, Philip Busca, Namecheap, RrSG, Newfold Digital, IPC * Support recommendation with wording change: * Tucows, GoDaddy, John Poole. * Significant change required: * Com Laude, ICA, Leap of Faith Financial Services Inc. * Recommendation should be deleted: NCSG. Discussion: * The evidence of fraud was discussed in the full WG and in the small group. * We expected to get comments on this. * Based on the comments, do we have a path forward on whether to change the recommendation? * Is there a possibility that fraud goes to a “MUST”? * There could be good reasons to leave fraud as a “MAY”-- could imagine that a registrar might allow a registrant to transfer away, so good to have the flexibility. * Maybe the losing registrar doesn’t want to deal with this registrant/domain name, so wants the flexibility to allow a transfer. * Does that mean that a losing registrar could allow a fraudulent registrant to transfer without the gaining registrar to know about the fraud? * How do you know that there is evidence of fraud? If you make it a “MUST” a registrar could be in breach without ever knowing it. Or something is illegal for one country but not in another. * Procedure element: The current language is limited to evidence of fraud in the “MAY” category. To put a change in policy forward to Council the WG will have to have consensus support for a change to the recommendation/policy. In this case the “MAY” is the current policy so there would need to be consensus for a change to “MUST”. * Suggest removing “domain use” from “Violation of the Registrar's domain use or anti-abuse policies or evidence of fraud.” * The above suggested change may not allow enough flexibility – to allow for things other than abuse or fraud. * Three scenarios: 1) keep the recommendation as “evidence of fraud”; 2) the recommended language; 3) “Violation of the Registrar's anti-abuse policies or evidence of fraud.” * Once we agree to language the change should go back to the groups and get approval. 4. Time permitting, Review public comments on other elements of Recommendations 18, 19, and 20 – See Public Comment Review Tools for Recommendations 18, 19, and 20<https://community.icann.org/display/TPRPDP/Phase+1A+-+Public+Comment+Review…> Recommendation 18 (brief discussion), PCRT<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…> – Summary: * Pretty good support. * Support as written: Ted Chang, Tucows, Com Laude, ICANN Business Constituency (BC), ICANN Org, GoDaddy, Samwel Kariuki, Philip Busca, NCSG, Namecheap, RrSG, Newfold Digital, IPC, ARTICLE 19, Leap of Faith Financial Services Inc., ICA Support with wording change: RySG and John Poole Discussion: * Registrars have a clear process for taking down domain names. Language we have now is good enough. * Not sure the gaining and Losing Registrar have the same data of abuse. 5. AOB: Next session: Tuesday 13 September at 16:00 UTC * Next topic will be the elimination of the FOA and security of the TAC. Current plan is to start on that topic on the 13 September meeting. Then continue on that topic at ICANN75. * In the meantime WG members should review Recommendation #2 and the comments, as well as how to reconcile them to find mutual agreeable updates to the recommendations. ACTION ITEM: WG members should be prepared to discuss the public comments on Recommendation #2<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…> of the Phase 1A Initial Report.

1 0

Post Call | Transfer Policy Review PDP WG | Tuesday, 06 September 2022
by Julie Bisland Sept. 6, 2022

Sept. 6, 2022

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Tuesday, 06 September 2022 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/BwVpD> (attendance included) and the GNSO Master calendar <https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…> . These include: * Attendance * Audio recording * Zoom chat archive * Zoom recording (including audio, visual, rough transcript) * Transcript 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

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 13 September 2022
by Julie Bisland Sept. 6, 2022

Sept. 6, 2022

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 13 September 2022 at 16:00 UTC for 90 minutes. Zoom Room 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/CQVpD * Check your time zone: https://tinyurl.com/ycwjfk6t ONLY FOR MEMBERS & ALTERNATES: * Please join via the Main Zoom Webinar link above; staff will promote you to panelist. * Chat: Members (and alternates replacing members), please select Everyone so everyone can see and so it’s captured afterwards. * Alternate replacement confirmations – For tracking alternate replacements, use the google form [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…> to communicate the replacement (alternate) and the duration. This information 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 THREE Zs (zzz) before your name and add, in parentheses (your affiliation - alternate) after your name. To rename in Zoom, hover over your name and click ‘rename’. * 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

1 0

**On in 3 minutes** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 06 September 2022
by Julie Bisland Sept. 6, 2022

Sept. 6, 2022

**On in 3 minutes** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 06 September 2022 at 16:00 UTC for 90 minutes. Zoom Room 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/BwVpD * Check your time zone: https://tinyurl.com/2p9dervv [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2p9dervv__;!!PtGJab4!4oqEZen…> ONLY FOR MEMBERS & ALTERNATES: * Please join via the Main Zoom Webinar link above; staff will promote you to panelist. * Chat: Members (and alternates replacing members), please select Everyone so everyone can see and so it’s captured afterwards. * Alternate replacement confirmations – For tracking alternate replacements, use the google form [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…> to communicate the replacement (alternate) and the duration. This information 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 THREE Zs (zzz) before your name and add, in parentheses (your affiliation - alternate) after your name. To rename in Zoom, hover over your name and click ‘rename’. * 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

1 0