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

Proposed agenda for meeting #43 on Tuesday 19 April 2022 at 16:00 UTC
by Emily Barabas April 14, 2022

April 14, 2022

Dear Working Group members, Please find below the proposed agenda for the meeting scheduled to take place on Tuesday 19 April 2022 at 16:00 UTC. Before the meeting, please review the following: * proposed response to Charter Question h2 (see page 13 and 14 here<https://docs.google.com/document/d/1L2bZnhJUY3VxyAjVCrkyVqdttOPn2EaqBARRRnE…>) * proposed responses to EPDP Phase 1, Recommendation 27 “Wave 1” Report items (see document here<https://docs.google.com/document/d/1ZLkSqD2bHDBoQLn8c0E2KjwWubpO7-cB9eg23uc…>) * Outstanding Items on TAC (see summary document here<https://docs.google.com/spreadsheets/d/1VAeYHzXuA7qOYu2Fis8SlthcWsGxN6Jpzxd…>) Kind regards, Julie, Caitlin, Berry, and Emily Transfer Policy Review Phase 1 - Meeting #43 Proposed Agenda 1. Roll Call & SOI updates 2. Welcome & Chair updates 1. Overview of proposed response to Charter Question h2 (see page 13 and 14 here<https://docs.google.com/document/d/1L2bZnhJUY3VxyAjVCrkyVqdttOPn2EaqBARRRnE…>) 2. Overview of proposed responses to EPDP Phase 1, Recommendation 27 “Wave 1” Report items (see document here<https://docs.google.com/document/d/1ZLkSqD2bHDBoQLn8c0E2KjwWubpO7-cB9eg23uc…>) 3. Discussion of Outstanding Items on TAC (see summary document here<https://docs.google.com/spreadsheets/d/1VAeYHzXuA7qOYu2Fis8SlthcWsGxN6Jpzxd…>) 4. AOB * Next call: Tuesday 26 April 2022 at 16:00 UTC

1 0

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 19 April 2022
by Julie Bisland April 12, 2022

April 12, 2022

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 19 April 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/MBAiCw * Check your time zone: https://tinyurl.com/369duxjf 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

Post Call | Transfer Policy Review PDP WG | Tuesday, 12 April 2022
by Julie Bisland April 12, 2022

April 12, 2022

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Tuesday, 12 April 2022 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/LhAiCw> (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 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

Notes and action items - TPR WG Meeting #42 - 12 April 2022
by Julie Hedlund April 12, 2022

April 12, 2022

Dear TPR WG Members, Please find below the notes and action items from today’s meeting. The next TPR WG meeting will be on Tuesday, 19 April 2022 at 16:00 UTC. Best regards, Emily, Julie, Berry, and Caitlin Action Items: 1. WG members to provide language to justify the 30-day post-creation and post-transfer locks in the Working document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1RGow_TYPSESv…>. 2. REMINDER from 05 April meeting: WG members to review suggested new language from Sarah Wyld in the bulk use cases Working document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1mqPITDShqiVQ…> and possible suggested text (in recommendations 3, 8, and 9?) that the TAC has to be unique using the phrase “randomly generated value”. Notes: Transfer Policy Review Phase 1 - Meeting #42 Tuesday, 12 April 2022 Proposed Agenda 1. Roll Call & SOI updates 2. Welcome & Chair updates * Small Team on Denial of Transfer/NACKing: Meeting this week and will have draft language for the WG to review. * Single TAC for multiple domains: in Bulk Use Cases Working Document<https://docs.google.com/document/d/1mqPITDShqiVQ4rH6x-FlvePmL_c05CtyWGgkpj9…> Sarah Wyld has suggested language for the WG review and comment. * Reminder that as work is winding down the big tactical discussions are shortly behind us. We’ll be finalizing draft recommendations and closing up anything that is still open. Do think we have addressed the charter questions. Goal is to have the Initial Report in good shape in June. ACTION ITEM: REMINDER from 05 April meeting: WG members to review suggested new language from Sarah Wyld in the bulk use cases Working document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1mqPITDShqiVQ…> and possible suggested text (in recommendations 3, 8, and 9?) that the TAC has to be unique using the phrase “randomly generated value”. 3. Post-creation and post-transfer locks – see: Working document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1RGow_TYPSESv…> * Have some feedback from groups that 10 days may be too short. * Asking some questions in a short poll – whether there should be a post-creation lock, period of time, and enforcement, and same for a post-transfer lock. Not talking about a specific type of lock. Just whether there is a window of time during which a transfer shouldn’t occur. * Post-creation lock is a window of time after a domain is created that it cannot be transferred. The other item that was brought up was payment, that also had a window of time associate with it. See summary of the reasons suggested in the working document here on page 3: https://docs.google.com/document/d/1RGow_TYPSESvI9DFweF3T_g7vgufg6zCwEdSsUj…. Poll Responses: 1. Should a transfer lock be required after a domain is registered? * Yes – 88% responses * No – 13% responses * No answer – 0% responses Discussion: * Strong support for a lock. * Note that today this is an optional lock; some registrars do it and some don’t. Some registries do it. * This is what we expected. 2. What should be the period of the post-creation lock? * 10 days – 50% responses * 30 days – 39% responses * 60 days – 11% responses * Other period/don’t know – 0% responses Discussion: * Some thought 60 days was too long. Seems also that 10 days could be too short for some. * Some suggest that the period should be left to the registrar with a minimum requirement of 10 days. * Standardizing the period could be helpful. * Could there be exceptions to allow 10 days? * Could be a lot of value to aligning the time with the post-transfer lock period. Maybe we need to not decide until we decide what the fast-undo period would be, to make them aligned. * If the lock period is longer we should consider guardrails. * Question: Can we come back to Phase 1 recommendations in Phase 2? Answer: There will be a separate Final Report for Phases 1 and 2, so these are separate efforts. The idea when we drafted the charter was when the Phase 1 work is completed getting this out to market as fast as possible means that the IRT can start up the work on the Phase 1 recommendations. If Phase 2 required a change to a Phase1 recommendation this could be done because the recommendations won’t be implemented overnight, but the intention was that Phase 1 would be implemented while Phase 2 work is ongoing. * By and large there seems to be a high-degree of agreement that there should be a period of time post-creation doesn’t occur and some agreement on a 10- or 30-day period. Best if we have agreement before going into public comment on the Initial Report. If we have both options in the Initial Report we need strong rationale for each. * Key here is what the WG will take to public comment – better if we can take a limited set, with one time period being best if we can agree. * Question: Can we get justification from people who support 10 days and those who support 30 days? * There are different business registrar business models. Many of the reseller registrars take a pre-payment, so there are certain players that have surety of payment as part of their business model. Others have payment in real time and it’s not until a billing cycle occurs you wouldn’t see fraudulent payments. 60 days allows time for that to occur, but 30 days may not. This also is tethered to fast undo. * If we agree on 30 days, we need to justify it. 3. Should a transfer lock be required after a domain is transferred to a new registrar? * Yes – 94% responses * No – 6% responses * No answer – 0% responses Discussion: * Need a transfer lock because of the potential for domain theft. * Need to be thinking about the registrant and certainty of title/transfer of title. This about the period of time for lock plus undo. Need to find a sweet spot. Perhaps rather than discuss the lock period, talk about the lock plus undo period. Should be a fixed number of days and not per registrar or registry. * A flipper could wait the 30 days (post-transfer lock) before selling? You aren’t initiated a transfer in order to participate in the marketplace. Waiting period could affect when funds are released from escrow. * Would think we would want to balance protection for the average registrar and risks of abuse. * Most change of registrars would correspond with a change of registrant. When the customer changes ownership, that is the change of registrant lock. * As above, if we agree on 30 days when have to justify it. * Poll shows support for a post-transfer lock. 4. What should be the period of the post-transfer lock? * 10 days – 22% responses * 30 days – 72% responses * 60 days – 6% responses * Other period/don’t know – 0% responses Discussion: * Could there be a 3a question? Do people want continuity between a post-creation and post-transfer lock? * Seems to be support for continuity. * Poll results suggest that some people switched from 10 to 30 days. Seems that most feel 60 days is too long. * Question: Should there be no exceptions? Such if the registrar and registrant agree to a shorter period? Answer: That would not be allowed. * Reminder: We are talking about edge cases. * Wondering if 30 days could be a general rule with the possibility of exceptions? * We are again leaning towards 30 days. We haven’t yet gotten to any agreement on carve-outs. Could be a question in the Initial Report for public comment. * Seems logical that fast undo would fall within the lock period. * What if there is no quick-undo process? Maybe we shouldn’t assume that we can agree on such a process. * We brought the fast-undo process discussion forward to see if we could agree on it and to consider it in the context of locks. 5. How should the lock requirements be implemented? * Requirement in the Transfer Policy for a registrar lock – 80% responses * Requirement in the Registry Agreement for a registry lock – 13% responses * Other/don’t know – 7% responses Discussion: * Question: Registrars are bound through the RAA for consensus policies, and registries too, right? Why put a requirement in Registry Agreement. Answer: Just focus on whether it’s a registrar or registry lock. Ignore the part about the agreement. * Registrar locks can be removed, whereas that’s not possible with a registry lock. * Don’t think that registries have enough information to properly support this. You are overloading registry-specific rules with the need or purpose of registrars. Concerned about how this would be implemented. * Right now, for example, if a registry finds that there is a name being abused the registry may turn on various EPP statuses to prevent transfer, and may also take it out of the zone. Using those same locks for inter-registrar transfer would be overloading those mechanisms. * Instead of talking about a specific status, talk about a window in time. * Leaning toward registrar use and enforcement. * If there is a policy that states the period of time, could the registrar disallow these locks or set something shorter? * Big question is whether to go with 10 or 30 days. Do we have support for one or the other? Seems we have a good indication that some people want 30, but we need that to be documented with a solid rationale. ACTION ITEM: WG members to provide language to justify the 30-day post-creation and post-transfer locks in the Working document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1RGow_TYPSESv…>. 4. AOB * Next call: Tuesday 19 April 2022 at 16:00 UTC.

1 0

**STARTS IN 12 MINUTES** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 12 April 2022
by Julie Bisland April 12, 2022

April 12, 2022

**STARTS IN 12 MINUTES** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 12 April 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/LhAiCw * Check your time zone: https://tinyurl.com/47xbfjdu [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/47xbfjdu__;!!PtGJab4!tS6MnH2…> 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, 12 April 2022
by Julie Bisland April 11, 2022

April 11, 2022

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 12 April 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/LhAiCw * Check your time zone: https://tinyurl.com/47xbfjdu [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/47xbfjdu__;!!PtGJab4!tS6MnH2…> 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

Re: [GNSO-TPR] TPR planning - attending ICANN74?
by Emily Barabas April 11, 2022

April 11, 2022

Dear all, As a reminder, please fill out the poll below. The poll will close on Friday 15 April. Even if your travel plans are uncertain, it is helpful for us to have this information as we plan for the session. Kind regards, Julie, Berry, Caitlin and Emily From: GNSO-TPR <gnso-tpr-bounces(a)icann.org> on behalf of Emily Barabas <emily.barabas(a)icann.org> Date: Thursday, 7 April 2022 at 21:57 To: "gnso-tpr(a)icann.org" <gnso-tpr(a)icann.org> Subject: [GNSO-TPR] TPR planning - attending ICANN74? Dear Working Group members, To assist the leadership team with planning for ICANN74, please take a moment to share the status of your plans with respect to attending the meeting: https://forms.gle/6roJqSkXeoPUi6Hn6 [forms.gle]<https://urldefense.com/v3/__https:/forms.gle/6roJqSkXeoPUi6Hn6__;!!PtGJab4!…> Thanks in advance for your feedback, Kind regards, Julie, Berry, Caitlin and Emily Emily Barabas Policy Development Support Senior Manager Internet Corporation for Assigned Names and Numbers (ICANN) Phone: +31 (0)6 84507976 www.icann.org<http://www.icann.org/>

1 0

Proposed agenda for meeting #42 on Tuesday 12 April 2022 at 16:00 UTC
by Emily Barabas April 7, 2022

April 7, 2022

Dear Working Group members, Please find below the proposed agenda for the meeting scheduled to take place on Tuesday 12 April 2022 at 16:00 UTC. Please note that we will be doing polling during this call to get a sense of the current sentiment of the group on post-creation and post-transfer locks. This will inform drafting of recommendations on this topic for the Initial Report, so it is important that at least one representative from each group participates in next week’s call. Kind regards, Julie, Caitlin, Berry, and Emily Transfer Policy Review Phase 1 - Meeting #42 Proposed Agenda 1. Roll Call & SOI updates 2. Welcome & Chair updates 1. Post-creation and post-transfer locks * Working document<https://docs.google.com/document/d/1RGow_TYPSESvI9DFweF3T_g7vgufg6zCwEdSsUj…> 2. AOB * Next call: Tuesday 19 April 2022 at 16:00 UTC

1 0

TPR planning - attending ICANN74?
by Emily Barabas April 7, 2022

April 7, 2022

Dear Working Group members, To assist the leadership team with planning for ICANN74, please take a moment to share the status of your plans with respect to attending the meeting: https://forms.gle/6roJqSkXeoPUi6Hn6 Thanks in advance for your feedback, Kind regards, Julie, Berry, Caitlin and Emily Emily Barabas Policy Development Support Senior Manager Internet Corporation for Assigned Names and Numbers (ICANN) Phone: +31 (0)6 84507976 www.icann.org<http://www.icann.org/>

1 0

TPR-P1 // 31 Mar 2022 Project Package
by Berry Cobb April 6, 2022

April 6, 2022

Dear WG, Please find a link below to project package for the TPR-P1 PDP (31 Mar 2022). This package is a snap-shot at the close of each month and developed by the leadership team to report on the working group’s activities and status of the project. It is also distributed to the GNSO Council to keep them informed as managers of the PDP. The package is deposited on the wiki so that we can track access statistics. Link: https://community.icann.org/x/MQDQCQ 1. Page 01 – Summary dashboard 2. Page 02 – Project Sitrep – an extract from the Council’s Project List 3. Page 03,4 – Group roster 4. Page 05 – Work and activity metrics 5. Page 06,7 – Group attendance for plenary meetings 6. Page 08 – Project Plan, Gantt chart 7. Page 09 – Work plan & Action items for the period Key points: * The WG is proceeding according to plan against the charter topics/questions. Please let us know if you have questions. Thank you. B Berry Cobb Policy Development – Senior Program Manager Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: TBD Phone: +1 202 570 7240 Fax: +1 202 789 0104 Twitter: @berrycobb www.icann.org<https://www.icann.org/>

1 0