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

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 08 February 2022 at 16:00 UTC
by Nathalie Peregrine Jan. 31, 2022

Jan. 31, 2022

** The Transfer Policy Review PDP WG call on the 1 February 2022 has been cancelled. Please remove this entry from your calendars. Below is the invitation for the call on the 8 February 2022. ** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 08 February 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/cYHOCg * Check your time zone: https://tinyurl.com/2p8tpvjj 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, Nathalie

1 0

Canceled: Transfer Policy Review PDP WG
by ICANN Policy Calendar Jan. 31, 2022

Jan. 31, 2022

Meeting: Transfer Policy Review PDP WG Date/Time: Recurring every Tuesday at 16:00 UTC for 90 minutes, 04 January 2022 through 22 February 2022 Join the Zoom Webinar: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 Passcode: @TP/^*4wg# 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> Wiki Agenda meeting pages 2021: https://community.icann.org/x/Z4HOCg Check your time zone: https://tinyurl.com/sb3srr8b ONLY for Members & Alternates: * Please join via the above Zoom Webinar link and staff will promote you to Panelist * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form<https://docs.google.com/forms/d/e/1FAIpQLScXP3-H595xH4EFgaR3ydOr-1o9BLAVGUI…> to communicate who the alternate is replacing and for which period. This information will be posted to the Alternate Log-Transfer Policy Review PDP wiki page<https://community.icann.org/x/V4aUCQ>. * Members and alternates replacing members, please select Panelists and Attendees, or Everyone when posting to the chat in order for everyone to see and to be captured afterwards. * Alternates (not replacing a member): Please rename your line in Zoom by adding THREE Zs “zzz” before your name, and 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. For 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

1 0

Call canceled for Tuesday 1 February and WG "homework assignment"
by Emily Barabas Jan. 29, 2022

Jan. 29, 2022

Dear Working Group members, Thanks to all who contributed to a productive discussion on Tuesday regarding post-creation and post-transfer locks. Drawing on this conversation and the other inputs so far on this topic, staff has started a new working document<https://docs.google.com/document/d/1RGow_TYPSESvI9DFweF3T_g7vgufg6zCwEdSsUj…> to support ongoing deliberations. For this coming Tuesday (1 February), Roger will be unavailable to Chair, and rather than trying to progress the work without him, the leadership team suggests canceling the call. This will give everyone time to digest the material in the working document and provide comments as appropriate in the document or on the mailing list. This is also a great opportunity to coordinate with your groups, so that any additional input can be brought into the discussion when we resume meeting on 8 February. As an additional “homework assignment”, please take some time in the coming week to review the working document on NACKing<https://docs.google.com/document/d/1L2bZnhJUY3VxyAjVCrkyVqdttOPn2EaqBARRRnE…> and give some thought to the related charter questions. This will be the next area of focus for the group. If you have any questions, please share them on list or reach out directly. Kind regards, Caitlin, Berry, Julie 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

Post Call | Transfer Policy Review PDP WG | Tuesday, 25 January 2022
by Julie Bisland Jan. 25, 2022

Jan. 25, 2022

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Tuesday, 25 January 2022 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/b4HOCg> (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 (please let me know if your name has been left off the attendance list) * 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

2 1

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 01 February 2022 at 16:00 UTC
by Julie Bisland Jan. 25, 2022

Jan. 25, 2022

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 01 February 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/cYHOCg * Check your time zone: https://tinyurl.com/ut4pwpjp 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

Transfer Policy Review PDP WG
by ICANN Policy Calendar Jan. 25, 2022

Jan. 25, 2022

Meeting: Transfer Policy Review PDP WG Date/Time: Recurring every Tuesday at 16:00 UTC for 90 minutes, 04 January 2022 through 22 February 2022 Join the Zoom Webinar: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 Passcode: @TP/^*4wg# 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> Wiki Agenda meeting pages 2022: https://community.icann.org/x/Z4HOCg Check your time zone: https://tinyurl.com/sb3srr8b ONLY for Members & Alternates: * Please join via the above Zoom Webinar link and staff will promote you to Panelist * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form<https://docs.google.com/forms/d/e/1FAIpQLScXP3-H595xH4EFgaR3ydOr-1o9BLAVGUI…> to communicate who the alternate is replacing and for which period. This information will be posted to the Alternate Log-Transfer Policy Review PDP wiki page<https://community.icann.org/x/V4aUCQ>. * Members and alternates replacing members, please select Everyone when posting to the chat in order for everyone to see and to be captured afterwards. * Alternates (not replacing a member): Please rename your line in Zoom by adding THREE Zs “zzz” before your name, and 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. For 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

1 0

Notes and action items - TPR WG Meeting #33 - 25 Jan 2022
by Julie Hedlund Jan. 25, 2022

Jan. 25, 2022

Dear TPR WG Members, Please find below the notes and action items from today’s call. The next TPR WG meeting will be on Tuesday, 01 February 2022 at 16:00 UTC. Best regards, Emily, Julie, Berry, and Caitlin Action Items: None. Transfer Policy Review Phase 1 - Meeting #33 Tuesday 25 January 2022 at 16:00 UTC 1. Roll Call & SOI updates (5 minutes): * No updates provided. 2. Welcome & Chair updates (5 minutes) * No updates provided. 3. Discussion of registrar-applied lock upon domain creation (75 minutes) See overview of inter-registrar transfer locks here [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1q7xaJuxi50Q6…> Previous discussions on this topic are captured in the parking lot working document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1e4hwyxKTx2JF…> 60-Day Creation Lock: * Went through a lot of the locks, even those for which we aren’t responsible. * Charter questions relate to the 60-day creation date and transfer locks. Should there be changes to the current 60-day lock in the policy. * Summary of previous discussions suggests that people were leaning towards some period of time in which transfers are prohibited. * Current policy has these as “MAY”. * Question is do we need to make the locks consistent and do they still serve a purpose? * The 60-day lock on creation – having a universal approach would help protect new people entering the market. * Get some clarification on charge back – is this a live issue, or a legacy? * 60-day lock is handy now if you have a fraudulent reseller. * 60-day lock is a problem for the registrants and isn’t consistently applied. Don’t see charge-backs as such a big problem. * The anti-fraud mechanisms today with credit cards are more robust than they used to be, so the risk has shifted to the credit card companies. The fraud situation has been ameliorated. * Even if the registrar is not incurring the charge, we would like to avoid the name transferring fraudulently. * Why not make this optional for the registrar? * The individual user should have the right to choose this option. * Standardization would help many parties. * There was a reference made to domain tasting and the lock as a mitigation. Not aware of domain tasting as a problem relating to a transfer. * Also observe that claw-backs are a separate process and independent of the lock. You should be able to claw back whether it’s locked or not.’ * At-Large submitted results of a survey and from that At-Large was not in favor of locks. Also inconsistent application is confusing for end users. * Felt that claw-back would be part of the transfer dispute discussions the WG is undertaking later. * Question: Is the current policy of a 60-day lock mandatory (MUST) or optional (MAY)? Answer: Current policy is “MAP” on the sponsoring registrar. May be able to deny a request. * It is NOT an ICANN requirement under the current Transfer policy. * The 60-day lock after creation is contractual (Registry Agreement) for SOME registries but not all. For example it is a contractual requirement in our Registry Agreement with ICANN, but it’s not a requirement across the board – some new gTLDs don’t have it in their RAs, but many follow that model. * This WG could recommend that the RAs could be revised to not include the mandate for a 60-day lock. Does the WG have any interest in making that recommendation. * From the TPR Parking Lot document, bottom of page 1: “Proposal for additional consideration: Include in policy a 60-day lock post creation and post transfer but with an opt out feature (for registrants? For registrar?) -- Should there be exceptions/constraints to the opt out?” * Lock after transfer and lock after creation should be handled differently. Creation lock should be made mandatory. For transfer 60 days is way too long. * How can this WG make a consistent policy across all registries when the original policy is written into the registry agreements? Problem is that it is not written into all agreements. We can make it consistent at least with post-creation lock. * If the only available option is to impose the 60-day post creation lock on all registries that don’t already have it in their agreements. * If the WG were to form consensus around a creation lock, the consensus policy adopted by the GNSO Council and the Board would supersede any provisions in the registry agreements. Where the provisions were lacking they would have to be included in amendments of the agreements. * Look at the pros and cons of the lock for security and consistency. * Can we find out which registry agreements have the locks and which don’t? * All ICANN contracted parties are required to meet requirements of consensus policies. * Haven’t heard a solid security reason for why there is a lock after creation. * Creation lock is less about security and more about consistency, while the transfer lock is more about security but also consistency. * Is 60-day lock the ultimate security (versus 30-days, etc.)? 60-day is more historical. * Caution to make sure we are looking at this holistically and its potential impact on other policies, such as the (Add Grace Period) AGP Limits Policy. * Seems like we should have a lock that is as long as the grace period, which is currently 5 days. * Should look for a correlation between ccTLDs and gTLDs as they are very different. * Sounds like the WG is leaning towards a shorter mandatory period. * If we lower the period of time but keep the mandatory lock we should provide a rational. * The lock after transfer could be just a “transferProhibited” lock, so other changes, e.g., updates, could still occur. * The WG should make sure its recommendations are as nailed down as possible. * For the Initial Report the WG could ask specific questions in a survey format to get quantitative and qualitative responses. * Instead of calling it a lock, could call it a non-transfer period. * Seems that we are leaning towards shortening the 60-days but keeping the requirement that a transfer not occur in the X-day (say 7 days) period and we need to provide the rationale. We should considering the period in calendar days or hours. * There is nothing that prevents any RDAP server from adding anything in response. Do you want to require the publication of a value, or you could just do it. 60-day Transfer Lock: * Could call it a transfer window availability. * There are more security issues here. * Registrar survey responses leaning towards a shorter lock (30 days). * If we have 7 days for the creation lock we could make it 7 days for the transfer, for consistency. * First question is what the length of time should be, but the second question is whether that period of time has to be the same for all? Or whether there are exceptions. * There is also the question of should we have a lock. * I wonder if 7 days is long enough for a dispute … maybe 30 makes more sense. * Like the ability to lift the lock upon request. * Need to have the flexibility to resolve the dispute. * What if the gaining registrar is not responsive and thus does not want to place a lock due to the dispute? * It's all connected. Dispute process, fast undo, lock timing, etc. and TEAC. * But disputes can take months. Could it have it long enough for the dispute to be filed. * Is 7 days enough to file a dispute? * In the case of suspicious behaviour (abuse), will clientHold be sufficient? I.e. clientTransferProhibited can be removed. Update to my idea: serverTransferProhibited is removed, replaced with clientTransferProhibited when abuse. * TDRP is also in scope for this PDP. * Need to make a distinction between a 7-day lock and a dispute lock. 4. AOB (5 minutes): * Next call: Tuesday 1 February 2022 at 16:00 UTC

1 0

**On in 10 minutes** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 25 January 2022 at 16:00 UTC
by Julie Bisland Jan. 25, 2022

Jan. 25, 2022

**On in 10 minutes** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 25 January 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/b4HOCg * Check your time zone: https://tinyurl.com/yjt4mvdf [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/yjt4mvdf__;!!PtGJab4!vVkny0c…> 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, 25 January 2022 at 16:00 UTC
by Julie Bisland Jan. 24, 2022

Jan. 24, 2022

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 25 January 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/b4HOCg * Check your time zone: https://tinyurl.com/yjt4mvdf [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/yjt4mvdf__;!!PtGJab4!vVkny0c…> 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

Proposed agenda for meeting #33 on Tuesday 25 January 2022 at 16:00 UTC
by Emily Barabas Jan. 21, 2022

Jan. 21, 2022

Dear Working Group members, Please find below the proposed agenda for the meeting scheduled to take place on Tuesday 25 January 2022 at 16:00 UTC. Kind regards, Julie, Caitlin, Berry, and Emily Transfer Policy Review Phase 1 - Meeting #33 Proposed Agenda 1. Roll Call & SOI updates (5 minutes) 2. Welcome & Chair updates (5 minutes) 1. Discussion of registrar-applied lock upon domain creation (75 minutes) * See overview of inter-registrar transfer locks here<https://docs.google.com/document/d/1q7xaJuxi50Q6TDD26H92P6wOfZ8luap1wdWOtIg…> * Previous discussions on this topic are captured in the parking lot working document<https://docs.google.com/document/d/1e4hwyxKTx2JFROQ0qpqm_KREHIuZqIugRlzl_gY…> 2. AOB (5 minutes) * Next call: Tuesday 1 February 2022 at 16:00 UTC

1 0

Post Call | Transfer Policy Review PDP WG | Tuesday, 18 January 2022
by Julie Bisland Jan. 18, 2022

Jan. 18, 2022

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Tuesday, 18 January 2022 at 16:30 UTC can be found on the agenda wiki page <https://community.icann.org/x/bYHOCg> (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 (please let me know if your name has been left off the attendance list) * 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 #32 - 18 Jan 2022
by Julie Hedlund Jan. 18, 2022

Jan. 18, 2022

Dear TPR WG Members, Please find below the notes and action items from today’s call. The next TPR WG meeting will be on Tuesday, 25 January 2022 at 16:00 UTC. Best regards, Emily, Julie, Berry, and Caitlin Action Items: Losing FOA Working Document <https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> (beginning on p. 14) Recommendation 15: ACTION ITEM: Delete recommendation 15 unless there are objections over the next week. Gaining FOA Working Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1QOCzbLh7w4hd…> (beginning on p. 16) Recommendation 16: ACTION ITEM: Change from a “Candidate” recommendation to a recommendation. Swimlane Diagram: ACTION ITEM: Staff to update the swimlane diagram per the discussion. Transfer Policy Review Phase 1 - Meeting #32 Tuesday 18 January 2022 at 16:30 UTC 1. Roll Call & SOI updates (5 minutes) * No updates provided. 2. Welcome & Chair updates (5 minutes) * Jim Galvin, RySG: The RySG is looking at a number of issues. We will press on those issues in our group and then bring them to the PDP WG for discussion. 3. Second reading: TAC and FOA (15 minutes) Losing FOA Working Document <https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> (beginning on p. 14) Recommendation 13: * Suggest several edits on last week’s call. * Removed 13.2. * Provided revised new 13.2. * 11 Jan: Consider making this two different bulleted lists: 1. TAC is provided via control panel 2. TAC is not provided via control panel. * Two footnotes: Old footnote is #2, new footnote is #3. Do we need to be clearer that the notification is not via the control panel? Also, is the new footnote #3 helpful? “The Registrar of Record may choose to send the "Notification of TAC Provision" and the TAC together in a single communication.” Want the TAC notification to be provided through some other mechanism than how it was delivered. So if you deliver the TAC via email the notification should be via some other method. Want to make sure the registrant gets the notice. * Notification can include the TAC. * Concerns about limiting methods. * One is to make sure it gets to the registrant and two that it gets delivered via a distinct mechanism. * Think there's value in making sure that the domain owner is notified that the TAC was provided. * The thought here is to notify the registrant directly. You could still ask your reseller to do it, but it will be the registrar’s responsibility. * It doesn’t have to be a “MUST” but important to call out the different mechanisms – put is as a “SHOULD”. * Should be fine as a footnote. Recommendation 15: * Do we need this recommendation? What is the purpose? Registrars could do it anyway. * Doesn’t make any sense to have this recommendation. * Only value would be for the consistency and transparency in the process. * Not sure how it adds to consistency if it is only optional. * If we make it optional it still has a cost, such as in the time spent on implementation. * Can lead to confusion as an optional requirement. ACTION ITEM: Delete recommendation 15 unless there are objections over the next week. Gaining FOA Working Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1QOCzbLh7w4hd…> (beginning on p. 16) Recommendation 16: “The Working Group recommends eliminating from the Transfer Policy the requirement that the Gaining Registrar send a Gaining Form of Authorization. This requirement is detailed in sections [xxxx] of the Transfer Policy.” * Pretty straightforward. Rationale explains how we got to this recommendation. ACTION ITEM: Change from a “Candidate” recommendation to a recommendation. 4. Overview of swimlane diagram for inter-registrar transfer process (60 minutes) – see attached document * Expect that this while change when we get into NACKing of transfers and the bulk transfer discussion. * Goal is to pick up where we left off when Sarah produced a Google sheet of the current state transfer process. Staff agreed that we need a more visual representation. * Charter questions are not in the order that actually occurs in the charter process. * Swimlane model has interactions occurring across the rows, otherwise read from top left to bottom right. * The primary objects: 1) Blue boxes are a required step for the process flow; 2) Tan box is a sub-process step (such as for the NACK, etc.), which could lead to a separate process page; 3) White circle is a “worm hole”; 4) Diamonds are decision points. * Specific recommendations are called out for the steps where they apply, subject to change when recommendations are finalized. * Like that this raises the question of whether we need a recommendation to confirm that domains in Expiry Grace Period may still be transferred. * The question of whether there needs to be a recommendation at some point concerning transfer of expired domain – out of scope but WG can consider making a statement (not a recommendation). * Recommendation #15 is going away (if no objections), so this will be removed. * There has to be a section shortly after the decision to transfer the domain that the RNH has to decide on the gaining registrar, inc. make an account at the gaining registrar. * Recommendation 13.2 (original) goes away and replaces 13.3. * Recommendations 5.1 and 5.2 may go away so those steps are shaded. * Question re: “OR Move Domain to G-Rr Credentials; Add 1 Year to Registration GFoA” – is this the current policy? Answer: Yes. See “The completion by Registry Operator of a holder-authorized transfer under Section I.A shall result in a one-year extension of the existing registration, provided that in no event shall the total unexpired term of a registration exceed ten (10) years.” This is out of scope of our charter so it would stay at one year. Setting the TAC to Null: * Per Recommendation 11.2, the Registrar of Record/Losing Registrar has the option to set the TAC to null. WG may want to consider providing some color commentary on what would happen if the TAC was set to null – such as resolving the issue on why it is set to null; address the issue of whether the transfer moves forward – go into a worm hole at letter A. * The registry takes the submitted TAC from the Gaining Registrar and it either matches or it doesn’t. There does need to be a process whereby the Registrar of Record can change their mind, and thus they can set it to NULL. The registry MUST set the TAC to NULL when the transfer is successful, i.e., the TAC gets to be used once. * From the point of view of a registry operator, from a pure process point of view: the registry only cares if the TAC matches when we get a request or not. If it doesn’t match the transfer is non-eligible. If it matches the transfer is successful, and then the TAC is set to null so it is only used once. It is an outside step if the Registrar of Record changes its mind – the registry doesn’t care – just whether the TAC matches/is valid. * Confirmed that in the swimlane if the Registrar or Record chooses to set the TAC to null the registry won’t see it. * From a swimlane perspective the fact that the TAC could be set to null by the Registrar of Record shouldn’t appear in this process flow. * Doesn't setting TAC to null need a corresponding box in the Registry lane to show that it's affected in the registry system? * We have a draft recommendation #11.2 that the Registrar of Record can set the TAC to null – so how should we reflect that recommendation? * The problem is where it is in this document – doesn’t below in this spot. Should be between the TAC is provisioned and when it goes to the registry. * Doesn’t fit well in the swimlane model – it’s just here for reference. * Move the TAC to null to a secondary page and then move the steps around. Transfer Locks: * The question here concerning the order of the steps depends on what you are giving priority to. Need to find out if the transfer is going to occur – given that a TAC is present in my system I need to find out whether you are the right person for the transfer. Once I have a valid TAC I know the domain should transfer; at that point I look for any domain locks and resolve them. Don’t want to do a lock release before I know whether a transfer is eligible. * Question: There are different types of locks – which ones are we talking about here? Answer: We are being generic since putting in all of the locks would make it very complex with sub-process pages; we also need to consider NACK locks. * If you want to keep it high level that is okay, but make sure they are different processes not tied to each other. * To check if the domain is locked and the TAC if valid happens at the same time – don’t need to say what order they are in. * In EPP and policy at ICANN there is client lock and registry lock – may be other non-policy locks. * client lock = registrar / server lock = registry – 2 types of locks but for a variety of reasons. * There are also court-ordered locks (UDRP). * Maybe there’s a process step for the Registrar of Record to clear registrar/client locks and a separate place for server locks. * Some registrars may keep a client lock on for security. Corporate registrars may remove client lock at a later point in the process if RNH/registrars are concerned. * There is a point where you talk about removing a client lock – there needs to be further elaboration and removal of client locks and what that means. There should be some discussion of what it means for the server lock. * So maybe the only discussion is whether or not there will be a policy about unlocking prior to transfer (which means removing the client lock release earlier in the swimlanes). In that case, I agree a step when the TAC is received at the registry to resolve any locks that are present is sufficient. * Probably needs to be discussion about what it means to release locks, but no policy recommendation I would think. * Staff has built an inventory of the types of locks and where they are applied that will be useful for the upcoming discussion on locks. ACTION ITEM: Staff to update the swimlane diagram per the discussion. 5. AOB (5 minutes) * Next call: Tuesday 25 January 2022 at 16:00 UTC

1 0

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 25 January 2022 at 16:00 UTC
by Julie Bisland Jan. 18, 2022

Jan. 18, 2022

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 25 January 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/b4HOCg * Check your time zone: https://tinyurl.com/yjt4mvdf 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 15 minutes** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 18 January 2022 at 16:30 UTC
by Julie Bisland Jan. 18, 2022

Jan. 18, 2022

**On in 15 minutes** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 18 January 2022 at 16:30 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/bYHOCg * Check your time zone: https://tinyurl.com/mr8kae8h [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/mr8kae8h__;!!PtGJab4!vNdSUWS…> 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: UPDATED TIME | Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 18 January 2022 at 16:30 UTC
by Nathalie Peregrine Jan. 17, 2022

Jan. 17, 2022

**Updated time to avoid conflict with SSAD ODP Webinar Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 18 January 2022 at 16:30 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/bYHOCg * Check your time zone: https://tinyurl.com/mr8kae8h [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/mr8kae8h__;!!PtGJab4!vNdSUWS…> 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

UPDATED TIME | Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 18 January 2022 at 16:30 UTC
by Devan Reed Jan. 13, 2022

Jan. 13, 2022

**Updated time to avoid conflict with SSAD ODP Webinar Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 18 January 2022 at 16:30 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/bYHOCg * Check your time zone: https://tinyurl.com/mr8kae8h 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

Transfer Policy Review PDP WG
by ICANN Policy Calendar Jan. 13, 2022

Jan. 13, 2022

**Updated time to avoid conflict with SSAD ODP Webinar Meeting: Transfer Policy Review PDP WG Date/Time: Tuesday 18 January 2022 at 16:30 UTC for 90 minutes Join the Zoom Webinar: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 Passcode: @TP/^*4wg# 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> Wiki Agenda meeting pages 2021: https://community.icann.org/x/Z4HOCg Check your time zone: https://tinyurl.com/sb3srr8b ONLY for Members & Alternates: * Please join via the above Zoom Webinar link and staff will promote you to Panelist * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form<https://docs.google.com/forms/d/e/1FAIpQLScXP3-H595xH4EFgaR3ydOr-1o9BLAVGUI…> to communicate who the alternate is replacing and for which period. This information will be posted to the Alternate Log-Transfer Policy Review PDP wiki page<https://community.icann.org/x/V4aUCQ>. * Members and alternates replacing members, please select Panelists and Attendees, or Everyone when posting to the chat in order for everyone to see and to be captured afterwards. * Alternates (not replacing a member): Please rename your line in Zoom by adding THREE Zs “zzz” before your name, and 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. For 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

1 0

Transfer Policy Review PDP WG
by ICANN Policy Calendar Jan. 13, 2022

Jan. 13, 2022

**Updated time to avoid conflict with SSAD ODP Webinar Meeting: Transfer Policy Review PDP WG Date/Time: Recurring every Tuesday at 16:00 UTC for 90 minutes, 04 January 2022 through 22 February 2022 Join the Zoom Webinar: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 Passcode: @TP/^*4wg# 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> Wiki Agenda meeting pages 2021: https://community.icann.org/x/Z4HOCg Check your time zone: https://tinyurl.com/sb3srr8b ONLY for Members & Alternates: * Please join via the above Zoom Webinar link and staff will promote you to Panelist * Alternate replacement confirmations – In order to keep track of alternate replacements, use the google form<https://docs.google.com/forms/d/e/1FAIpQLScXP3-H595xH4EFgaR3ydOr-1o9BLAVGUI…> to communicate who the alternate is replacing and for which period. This information will be posted to the Alternate Log-Transfer Policy Review PDP wiki page<https://community.icann.org/x/V4aUCQ>. * Members and alternates replacing members, please select Panelists and Attendees, or Everyone when posting to the chat in order for everyone to see and to be captured afterwards. * Alternates (not replacing a member): Please rename your line in Zoom by adding THREE Zs “zzz” before your name, and 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. For 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

1 0

Proposed agenda for meeting #32 on Tuesday 18 January 2022 at 16:30 UTC
by Emily Barabas Jan. 13, 2022

Jan. 13, 2022

Dear Working Group members, Please find below the proposed agenda for the meeting scheduled to take place on Tuesday 18 January 2022 at 16:30 UTC. Kind regards, Julie, Caitlin, Berry, and Emily Transfer Policy Review Phase 1 - Meeting #32 Proposed Agenda 1. Roll Call & SOI updates (5 minutes) 2. Welcome & Chair updates (5 minutes) 1. Second reading: TAC and FOA (15 minutes) * Losing FOA Working Document <https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> (beginning on p. 14) * Gaining FOA Working Document<https://docs.google.com/document/d/1QOCzbLh7w4hdijpAsg6_lybddr0nlsFDcWjdz5e…> (beginning on p. 16) 2. Overview of swimlane diagram for inter-registrar transfer process (60 minutes) * Document will be shared after the call 3. AOB (5 minutes) * Next call: Tuesday 25 January 2022 at 16:00 UTC

1 0

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 18 January 2022 at 16:00 UTC
by Julie Bisland Jan. 13, 2022

Jan. 13, 2022

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 18 January 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/bYHOCg * Check your time zone: https://tinyurl.com/d63u3rek 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

4 4

Notes and action items - TPR WG Meeting #31 - 11 Jan 2022
by Julie Hedlund Jan. 11, 2022

Jan. 11, 2022

Dear TPR WG Members, Please find below the notes and action items from today’s call. The next TPR WG meeting will be on Tuesday, 18 January 2022 at 16:00 UTC. Best regards, Emily, Julie, Berry, and Caitlin Action Items: 1. TAC Working Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1O9PAnxWFUuPo…> (beginning on p. 15) Recommendation #5: ACTION ITEM: Delete Recommendation #5. Recommendation #10: ACTION ITEM: Change the first sentence to: “The Working Group confirms that the Transfer Policy should continue to require Registrars to [set the TAC at the Registry] and….” Insert new text in brackets. Recommendation #11.1: ACTION ITEM: Revise the language to be more precise, as in “11. 1: A standard Time to Live (TTL) for the TAC be [14 calendar days from the time it is [set] at the Registry]…” Insert new text in brackets. 2. Losing FOA Working Document <https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> (beginning on p. 14) Recommendation 13: ACTION ITEMS: 1. 13.2: Delete it. 2. 13.3: Add two new bullet points: -- Date and time that the TAC was generated and information about when the TAC will expire. -- If the TAC has not been provided via another method, this communication will include the TAC. Recommendation #14: ACTION ITEMS: 1. Use “Losing Registrar” instead (with footnote explaining that we mean the Registrar of Record at the time of the transfer request). 2. Use 24 hours as the timing. Transfer Policy Review Phase 1 - Meeting #31 Tuesday 11 January 2022 at 16:00 UTC 1. Roll Call & SOI Updates: No updates provided. 2. Welcome & Chair updates (5 minutes): No updates provided. 3. Second reading: TAC and FOA (45 minutes) TAC Working Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1O9PAnxWFUuPo…> (beginning on p. 15) Recommendation #3: Removed “from time-to-time”. Recommendation #5: * Last week talked about removing recommendation #5. Assume that it is no longer valid and remove it. * ACTION ITEM: Delete Recommendation #5. Additional Candidate Recommendation xx: Keep as a placeholder for now. Recommendation #6: Continue with the new version. Recommendation #9: * A couple of edits to make it more clear that the TAC is only used once. * Revisit when we talk about bulk transfers. Recommendation #10: ACTION ITEM: Change the first sentence to: “The Working Group confirms that the Transfer Policy should continue to require Registrars to [set the TAC at the Registry] and….” Insert new text in brackets. Recommendation #11.1: * 11.1 is okay and keep the 14 calendar days – consider whether hours makes more sense. From when it is provisioned at the registry. But the registry isn’t actually doing it – it’s the registrar. The registry is only accepting the TAC. It is when the registry hashes and saves it to the record when the 14 days start. Could say, “set at the registry” and make the change in recommendation 10 as in 6.2. TTL starts when it is set at the registry. * ACTION ITEM: Revise the language to be more precise, as in “11. 1: A standard Time to Live (TTL) for the TAC be [14 calendar days from the time it is [set] at the Registry]…” Insert new text in brackets. Recommendation 11.2: * 11.2 there was a lot of discussion around the purpose. Leave it as is for now. * For 11.2, second bullet “After a period of less than 14 days by agreement by the Registrar of Record and the RNH?” Is it possible to specify what the agreement might be? * Not sure why we have 11.2. Think we are trying to codify what can happen today and we want to continue the ability to set the TAC to null. * Think we want to set out rules around resetting the TAC so that a registrar can't reset it so often it becomes impossible to transfer the domain. * That agreement could be part of your registration policy, indicating pre-determined reasons to reset a TAC. * Sections 3.7 and 3.8 of current policy set out why a transfer can be denied. Could be reasons to enable a reset of the TAC. Useful to review when we talk about NACKing. * If we leave it with just the first bullet, is that sufficient? Let’s keep both now and revisit in the NACK discussion. Think we need it in case of evidence of fraud. * Is the RNH and Registrar agreement a case where a circumstance arises and then it has to be agreed to at that time? It would need to be prior to being set to null. It should be that the RNH can ask for it at any time. Losing FOA Working Document <https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> (beginning on p. 14) Recommendation 12: We are good with the current language with the footnote. Recommendation 13: * The Registrar of Record will have to maintain who that was at that point in time. * No objections to “10 minutes” for the timing. Recommendations 13.2 and 13.3: * Should we had a TTL? * We don’t say that the TAC is provided, but we assume it? * See 6.3: When the Registrar of Record provides the TAC to the RNH or their designated representative, the Registrar of Record MUST also provide information about when the TAC will expire.]. Makes sense then to also include this in 13.3. * Reseller could be the designated representative. * If it’s a combined communication, is it necessary to say when the TAC was provided? * It’s almost always available via control panel. * There are registrars that only use the Registry interface. How will this work for these? * If registrars use a registry interface for transfers the question pops up how do they send the FOA? As the registry does not trigger such a process.] * Do we care if the Registrar of Record is providing the TAC via control panel? Either way we have to send an email. * Maybe “control panel” isn’t the right terminology since it could be via other methods. * What if we just say that the Registrar of Record…has to include the TAC if it has not be provided by another method, in the Notification of TAC Provision. * Maybe delete the first sentence in 13.2: “[If the Registrar of Record provides the TAC viais provided in the control panel, this notification must be provided to the RNH using a separate method of communication other than the control panel.] * Consider for bullet 3 under 13.3, perhaps include a timeframe? * Should we get rid of 13.2? Not sure we need it. Seems to be generate agreement to delete it. * ACTION ITEMS: * In 13.2: Delete it. * In 13.3: Add two new bullet points: * Date and time that the TAC was generated and information about when the TAC will expire. * If the TAC has not been provided via another method, this communication will include the TAC. Recommendation #14: ACTION ITEMS: 1. Use “Losing Registrar” instead (with footnote explaining that we mean the Registrar of Record at the time of the transfer request. 2. Use 24 hours as the timing. Recommendation #14.1, 14.2, 14.3: * On 14.3, first bullet: Waiting to hear from the RySG on the feasibility of providing the IANA ID. * Not sure that the benefit of including the IANA ID or Rr name outweighs the work to do so. 4. AOB (5 minutes) * Next call: Tuesday 18 January 2021 at 16:00 UTC

1 0

Post Call | Transfer Policy Review PDP WG | Tuesday, 11 January 2022
by Julie Bisland Jan. 11, 2022

Jan. 11, 2022

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Tuesday, 11 January 2022 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/a4HOCg> (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 (please let me know if your name has been left off the attendance list) * 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

**On in 13 minutes** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 11 January 2022 at 16:00 UTC
by Julie Bisland Jan. 11, 2022

Jan. 11, 2022

**On in 13 minutes** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 11 January 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/a4HOCg * Check your time zone: https://tinyurl.com/4crnxp8v [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/4crnxp8v__;!!PtGJab4!uFNSMBa…> 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, 11 January 2022 at 16:00 UTC
by Julie Bisland Jan. 10, 2022

Jan. 10, 2022

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 11 January 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/a4HOCg * Check your time zone: https://tinyurl.com/4crnxp8v [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/4crnxp8v__;!!PtGJab4!uFNSMBa…> 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

Proposed agenda for meeting #31 on Tuesday 11 January 2021 at 16:00 UTC
by Emily Barabas Jan. 7, 2022

Jan. 7, 2022

Dear Working Group members, Please find below the proposed agenda for the meeting scheduled to take place on Tuesday 11 January 2021 at 16:00 UTC. Kind regards, Julie, Caitlin, Berry, and Emily Transfer Policy Review Phase 1 - Meeting #31 Proposed Agenda 1. Roll Call & SOI updates (5 minutes) 2. Welcome & Chair updates (5 minutes) 1. Second reading: TAC and FOA (45 minutes) * TAC Working Document<https://docs.google.com/document/d/1O9PAnxWFUuPofLQCWIQXz8lT7KEj1HgH3b_obh0…> (beginning on p. 15) * Losing FOA Working Document <https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> (beginning on p. 14) * Gaining FOA Working Document<https://docs.google.com/document/d/1QOCzbLh7w4hdijpAsg6_lybddr0nlsFDcWjdz5e…> (beginning on p. 16) 2. 60-day post domain registration lock and post domain transfer lock (30 minutes) * See Parking Lot<https://docs.google.com/document/d/1e4hwyxKTx2JFROQ0qpqm_KREHIuZqIugRlzl_gY…> document for high-level notes from previous WG discussions on this topic 3. AOB (5 minutes) * Next call: Tuesday 18 January 2021 at 16:00 UTC

1 0