November 2021 - GNSO-TPR - lists.icann.org

Post Call | Transfer Policy Review PDP WG | Tuesday, 30 November 2021
by Devan Reed Nov. 30, 2021

Nov. 30, 2021

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Tuesday, 30 November 2021 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/fQiHCg> (attendance included) and the GNSO Master calendar<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, Devan

1 0

With ical attached | Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 07 December 2021 at 16:00 UTC
by Devan Reed Nov. 30, 2021

Nov. 30, 2021

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 07 December 2021 at 16:00 UTC for 90 minutes. Zoom Room Information: Main Zoom Webinar link: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 [icann.zoom.us]<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 [icann.zoom.us]<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/fwiHCg * Check your time zone: https://tinyurl.com/2p83v35x [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2p83v35x__;!!PtGJab4!pfyUo3b…> ONLY FOR MEMBERS & ALTERNATES: * Please join via the Main Zoom Webinar link above and 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, Devan

1 0

Notes and action items - TPR WG Meeting #26 - 30 Nov 2021
by Julie Hedlund Nov. 30, 2021

Nov. 30, 2021

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, 07 December at 16:00 UTC. Best regards, Emily, Julie, Berry, and Caitlin Action Items 1. Losing FOA Candidate Recommendations – see: Losing FOA Working Document <https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> (beginning on p. 14) and Transfer Steps and Notifications [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/17ADMRTYx…> Candidate Recommendation #12: ACTION ITEM: Staff to amend footnote 1 as follows: “The Working Group recommends notes that, in place of the Losing FOA, notifications are sent to the RNH [in relation to an inter-registrar transfer] when key changes take place with their account in relation to a transfer, as detailed in recommendations 13-15.” Candidate Recommendations #13 and #14: ACTION ITEM: Staff to determine whether footnotes 2 and 3 need to be duplicates or if they can be combined. Candidate Recommendation #14: ACTION ITEM: Replace with new text suggested with clarification. ACTION ITEM: Jim Galvin to take the question to the Registries Stakeholder Group as to the feasibility of providing the IANA ID and/or name of the Gaining Registrar. Leave in the requirement in the candidate recommendation until we get a response. 2. Rationale for Elimination of the Gaining FOA – see: Gaining FOA Working Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1QOCzbLh7w4hd…> (beginning on p. 16) ACTION ITEM: WG members should review the rationale for eliminating the Gaining FOA in preparation for next week’s meeting. Transfer Policy Review Phase 1 - Meeting #26 Tuesday 30 November 2021 at 16:00 UTC 1. Roll Call & SOI Updates * No updates provided. 2. Welcome & Chair updates * Reminder we are pulling forward from Phase 2 the NACKing section (section H of the charter) into Phase 1a. * Owen Smigelski re: Registrar Stakeholder Group survey regarding domain creation/transfer locks; see results at: https://docs.google.com/document/d/1-64Z4RqJB2sxR2aFbjt-YakafsjIrYixonfbHcC…. * Got 21 responses out of about 100 members. * There was a wide selection of respondents and regions. * Survey results seem to represent a wide range of opinion. * Question: Did you provide context such as proposed changes that would improve security? Answer: No, just want lock you would prefer and length. There was a comments section where some respondents provided rationale. * Question: Any talk about the opt in/opt out feature? Answer: No, that wasn’t included. * Question: In terms of responses received, can you correlate responses from older registrars versus newer ones? Answer: Do know how each registrar responded, but not sure how much detail I can provide and still keep the data anonymous. * Re: this poll and the AT-Large poll – the background information/context is crucial. Think about putting together a webinar with thoughts and perspectives on this. * Project Plan (see attached document): * WP Meeting #25: Losing FOA; Gaining FOA TPR WG 11/30/21 * WP Meeting #27: Gaining FOA; Revisit TAC TPR WG 12/07/21 * WP Meeting #28: Second reading of FOA/TAC; 60 day lock TPR WG 12/14/21 * WP Meeting #29: 60 day lock; NACK TPR WG 12/21/21 * WP Meeting #30: NACK TPR WG 01/04/22 * WP Meeting #31: Review recommendations package - Phase 1A TPR WG 01/11/22 * WP Meeting #32: Start bulk discussion TPR WG 01/18/22 3. Losing FOA Candidate Recommendations – see: Losing FOA Working Document <https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> (beginning on p. 14) and Transfer Steps and Notifications [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/17ADMRTYx…> Candidate Recommendation #12: * Question re: footnote 1: Why is this written as a recommendation? See “The Working Group recommends that, in place of the Losing FOA, notifications are sent to the RNH when key changes take place with their account in relation to a transfer, as detailed in recommendations 13-15.” * Useful to clarify “losing registrar” is the pre-transfer registrar? Should consistently use “losing registrar” since that is in the policy. * Confirm that several members raised concerns with recommendation #12 that the context needs to be provided, which is the intention of the footnote. * Concerned that “when key changes take place with their account in relation to a transfer” isn’t clear. Leave that out and add the text in brackets: “[in relation to an inter-registrar transfer]” * Not sure resellers can be compliant with this recommendation. * The footnote is only supposed to say that we have decided to remove Losing FOA and do notifications instead as detailed in recommendations #13-#15. The footnote is not a recommendation itself. * ACTION ITEM: Staff to amend footnote 1 as follows: “The Working Group recommends notes that, in place of the Losing FOA, notifications are sent to the RNH [in relation to an inter-registrar transfer] when key changes take place with their account in relation to a transfer, as detailed in recommendations 13-15.” Candidate Recommendation #13: * Re: “The Working Group recommends that the Registrar of Record MUST send a notification [specify method of sending?] to the RNH (as listed in the Registration Data at the time of the TAC request) without undue delay but no later than [10 minutesperiod of time] after the Registrar of Record provides the TAC.” 10-minute time period seems too short. * Possible alternative approach to recommendations 13 & 15 -- Notification of TAC provision is always required when TAC is provided immediately upon request. Notification of TAC request is always required when there is period of time between TAC request and TAC provision. Could provide a conditional statement – different notifications depending on whether instant transfer or asynchronous. * For the moment #13 seems fine, but we may want to come back to it when we discuss bulk transfers. * ACTION ITEM: Staff to determine whether footnotes 2 and 3 need to be duplicates or if they can be combined. Candidate Recommendation #14: * Question: There is one bit of ambiguity: We start out talking about the transfer request and then jump to notification of transfer completion – which is it? Answer: This is about completion of transfer. * Requiring the IANA ID is a new requirement; not sure it is feasible. But this seems like good information to have, so we should require it and figure out now to do it? It could be a lot of work, but maybe the benefit outweighs the impact. * Is it really that useful? Is this really a likely scenario? * It is quite valuable information to have – where the domain name is going. From a registrant perspective it seems like an obviously good thing to know. If you have the IANA ID you can then look up the contact information. We should make this more user friendly. * If we're making a change to what's in the poll response, maybe we should focus on getting the Registrar name rather than IANA ID? RNH will find Registrar name more useful. * Jim Galvin said that they will ask this question of registries to understand the work that might be involved. * Staff working on diagraming the process flow based on the candidate recommendations and also will look at RFC 5731 “Extensible Provisioning Protocol (EPP) Domain Name Mapping”. * ACTION ITEM: Replace with new text suggested with clarification. * ACTION ITEM: Jim Galvin to take the question to the Registries Stakeholder Group as to the feasibility of providing the IANA ID and/or name of the Gaining Registrar. Leave in the requirement in the candidate recommendation until we get a response. Candidate Recommendation #15: * No changes needed as revised. Candidate Recommendation #16: * The WG determined that this was no longer needed so it has been deleted. Re: Record Keeping: * Are there recommendations for each topic area? Or in general? * Don’t most businesses already keep data? Do we have to require it? * If we do make recommendation concerning logs and data retention we could start with requirements to keep records of transfers but as required in the EPDP policy. * It could help to spell out the requirements. There is already current wording that we can look at about keeping logs and best practices. * Do we create global recommendations for transfer policy, or more precise recommendations for each area (TAC, etc.). 4. Rationale for Elimination of the Gaining FOA – see: Gaining FOA Working Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1QOCzbLh7w4hd…> (beginning on p. 16) * ACTION ITEM: WG members should review the rationale for eliminating the Gaining FOA in preparation for next week’s meeting. 5. AOB: Next call Tuesday 7 December 2021 at 16:00 UTC.

1 0

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 07 December 2021 at 16:00 UTC
by Devan Reed Nov. 30, 2021

Nov. 30, 2021

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 07 December 2021 at 16:00 UTC for 90 minutes. Zoom Room Information: Main Zoom Webinar link: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 [icann.zoom.us]<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 [icann.zoom.us]<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/fwiHCg * Check your time zone: https://tinyurl.com/2p83v35x ONLY FOR MEMBERS & ALTERNATES: * Please join via the Main Zoom Webinar link above and 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, Devan

1 0

15 MINUTES **REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 30 November 2021 at 16:00 UTC
by Devan Reed Nov. 30, 2021

Nov. 30, 2021

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 30 November 2021 at 16:00 UTC for 90 minutes. Zoom Room Information: Main Zoom Webinar link: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 [icann.zoom.us]<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 [icann.zoom.us]<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/fQiHCg * Check your time zone: https://tinyurl.com/ksddfsss [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/ksddfsss__;!!PtGJab4!rdyxa_D…> ONLY FOR MEMBERS & ALTERNATES: * Please join via the Main Zoom Webinar link above and 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, Devan

1 0

**REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 30 November 2021 at 16:00 UTC
by Julie Bisland Nov. 29, 2021

Nov. 29, 2021

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 30 November 2021 at 16:00 UTC for 90 minutes. Zoom Room Information: Main Zoom Webinar link: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 [icann.zoom.us]<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 [icann.zoom.us]<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/fQiHCg * Check your time zone: https://tinyurl.com/ksddfsss [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/ksddfsss__;!!PtGJab4!rdyxa_D…> ONLY FOR MEMBERS & ALTERNATES: * Please join via the Main Zoom Webinar link above and 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 #26 on Tuesday 30 November 2021 at 16:00 UTC
by Emily Barabas Nov. 29, 2021

Nov. 29, 2021

Dear Working Group members, Please find below the proposed agenda for the meeting scheduled to take place on Tuesday 30 November 2021 at 16:00 UTC. Prior to the call, please take a few minutes to review draft revisions to the recommendations on Losing FOA based on discussion during last week’s call (see Losing FOA Working Document <https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> beginning on p. 14). Kind regards, Julie, Caitlin, Berry, and Emily Transfer Policy Review Phase 1 - Meeting #26 Proposed Agenda Tuesday 30 November 2021 at 16:00 UTC 1. Roll Call & SOI Updates (5 minutes) 2. Welcome & Chair updates (5 minutes) 3. Losing FOA Candidate Recommendations (45 minutes) * Losing FOA Working Document <https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> (beginning on p. 14); Transfer Steps and Notifications<https://docs.google.com/spreadsheets/d/17ADMRTYxN5sA-e3WoEI96KxlH5YRALBsxgw…> 1. Rationale for Elimination of the Gaining FOA (30 minutes) * Gaining FOA Working Document<https://docs.google.com/document/d/1QOCzbLh7w4hdijpAsg6_lybddr0nlsFDcWjdz5e…> (beginning on p. 16) 2. AOB (5 minutes) * Next call: Tuesday 7 December 2021 at 16:00 UTC

1 0

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 30 November 2021 at 16:00 UTC
by Julie Bisland Nov. 23, 2021

Nov. 23, 2021

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 30 November 2021 at 16:00 UTC for 90 minutes. Zoom Room Information: Main Zoom Webinar link: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 [icann.zoom.us]<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 [icann.zoom.us]<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/fQiHCg * Check your time zone: https://tinyurl.com/ksddfsss ONLY FOR MEMBERS & ALTERNATES: * Please join via the Main Zoom Webinar link above and 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, 23 November 2021
by Julie Bisland Nov. 23, 2021

Nov. 23, 2021

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Tuesday, 23 November 2021 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/ewiHCg> (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 #25 - 23 Nov 2021
by Julie Hedlund Nov. 23, 2021

Nov. 23, 2021

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, 30 November at 16:00 UTC. Best regards, Emily, Julie, Berry, and Caitlin Action Items Losing FOA Candidate Recommendations – see: Losing FOA Working Document <https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> (beginning on p. 14); Transfer Steps and Notifications [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/17ADMRTYx…> Candidate Recommendation #13: ACTION ITEMS: Staff to suggest working to replace “using email”, and concerning the timing/order and language of the notification and TAC presentation/provision. Need to make sure the RNH is notified no matter how the TAC is presented. Candidate Recommendation #14: ACTION ITEM: Ask if there are volunteers for a small team that delves into whether it’s possible to provide the Gaining Registrar name, or if the IANA ID is okay – looking at making IANA ID mandatory and the name of the Gaining Registrar optional. Also update the wording so that multiple notifications can go out regardless of different Gaining Registrars. Candidate Recommendation #15: ACTION ITEM: Make the same changes to the language to be consistent with previous related candidate recommendations. Candidate Recommendation #16: ACTION ITEM: Eliminate this candidate recommendation. Transfer Policy Review Phase 1 - Meeting #25 Tuesday 23 November 2021 at 16:00 UTC 1. Roll Call & SOI Updates * No updates provided. 2. Welcome & Chair updates * Submitting a Project Change Request to move NACKing from Phase 2 to consideration under Phase 1a as it is related to other topics in Phase 1a. * Schedule of Upcoming TPR Meetings – see attached. * Update from Steiner from CCWG members – informal poll on 60-day lock – see: https://mm.icann.org/pipermail/gnso-tpr/. Ended up with some tendencies: * Majority not it favor of the 60-day lock as policy; some agreed to keep it. * Did not agree on whether 60 days was the right timing. * Agreed that there should be some kind of consensus for registrars to treat these types of locks consistently. * Once the WG reaches consensus it would be helpful to have a presentation on the WG’s final decisions to understand the rationale. 3. Losing FOA Candidate Recommendations (60 minutes) – see: Losing FOA Working Document <https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> (beginning on p. 14); Transfer Steps and Notifications [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/17ADMRTYx…> Candidate Recommendation #12: * Staff suggested the following language: “ The Working Group recommends that, in place of the Losing FOA, notifications are sent to the RNH when key changes take place with their account in relation to a transfer, as detailed in recommendations 13-16.” Candidate Recommendation #13: * New language based on the discussion at the last meeting: “If the Registrar of Record provides the TAC by email, and the Registrar of Record also notifies the RNH of the TAC request using email, the two messages may be combined in a single email., the email containing the TAC and the message notifying the RNH of the TAC request must be two distinct communications.” * Owen Smigelski suggested timing for the notification in an email to the list. See: https://mm.icann.org/pipermail/gnso-tpr/. * Question: Do we really need to call out email here – “using email”? Answer: We can come up with different wording for that. * Happy for the mention of the language of the registration agreement, but it is not mandatory. Think this is a MUST. Staff will check the language in the policy concerning language. * Language from the UDRP rules: “Paragraph 11 of the UDRP provides requirements with respect to the Language of Proceedings, “(a) Unless otherwise agreed by the Parties, or specified otherwise in the Registration Agreement, the language of the administrative proceeding shall be the language of the Registration Agreement, subject to the authority of the Panel to determine otherwise, having regard to the circumstances of the administrative proceeding.” And as suggested in the working document: “This notification MUST be written in the language of the registration agreement and MAY also be provided in English or other language.” * ERRP provides that expiry notifications may be presented in one or more languages, but must be provided in the language of the registration agreement. * If there is a timeline it would have to be very short. * Consider reversing the order of the notifications – the goal is to make sure the registrant does get notified. * Not sure there is agreement on the timing of the notification beyond “without undue delay.” * Current Transfer Policy Requirement:” 5.2 Registrars must provide the Registered Name Holder with the unique "AuthInfo" code and remove the "ClientTransferProhibited" within five (5) calendar days of the Registered Name Holder's initial request if the Registrar does not provide facilities for the Registered Name Holder to generate and manage their own unique "AuthInfo" code and to remove the "ClientTransferProhibited" status.” * Change the language that the timing should be first or together for the notifications. * Restructure so that it is in a more chronological order. Might be helpful to go back to the transfer/notification spreadsheet. Notification of TAC request could be mandatory and maybe eliminating other notification. * Think the notification can be combined and most registrars would send one notice. * There is a difference between the notification of the transfer request, and the TAC presentation. If the TAC is only presented in a certain way then the registrant/RNH may not know about it. The request is separate from the TAC presentation. We want to make sure the RNH is aware of when the TAC went out. * If it’s presented in the account then a notice should be sent to the RNH. Whoever made the request, the notification has to go to the RNH. * If the registrant is requesting, then there’s only one notification. If the requester and RNH are different then there has to be a separate notification to the RNH from the TAC presentation. * Presenting the TAC does not have to be in the form of a notification. * Timing: Providing the TAC synchronous with the request, or asynchronous. If asynchronous then two notifications. * ACTION ITEMS: Staff to suggest working to replace “using email”, and concerning the timing/order and language of the notification and TAC presentation/provision. Need to make sure the RNH is notified no matter how the TAC is presented. Candidate Recommendation #14: * On the language of the notification, make it consistent with the text in Candidate Recommendation #14. * How does the Losing Registrar know the name of the Gaining Registrar? Currently we don’t, so a method would have to be created, or to provide the IANA ID, or a link to the database. * Where does the registrant go to complain when the domain name has been transferred without authorization? How can the registrant learn the name of the Gaining Registrar. And the IANA ID is not going to give the registrant the name of the reseller. * But if you have the ID of the Gaining Registrar you have a place to go. * IANA ID: Could be solved with a reference to https://www.icann.org/en/accredited-registrars?filter-letter=a&sort-directi… or similar. * Perhaps the default is to make it mandatory to provide the IANA ID of the Gaining Registrar, unless there is interest in a small team to look at the technical feasibility to provide the Gaining Registrar. * Thoughts on changing to one notification per transfer transaction, which might be different Gaining Registrars? Is this a use case that wouldn’t come up? Should the policy allow for this aggregation? Don’t see a reason not to allow it. * ACTION ITEM: Ask if there are volunteers for a small team that delves into whether it’s possible to provide the Gaining Registrar name, or if the IANA ID is okay – looking at making IANA ID mandatory and the name of the Gaining Registrar optional. Also update the wording so that multiple notifications can go out regardless of different Gaining Registrars. Candidate Recommendation #15: * Important to keep this optional since it won’t happen all of the time. * Just a notification to the RNH that the TAC has been requested (but not provided). * ACTION ITEM: Make the same changes to the language to be consistent with previous related candidate recommendations. Candidate Recommendation #16: * This was the second optional notification. * Should there be this separate notification or can it be combined with others? * Seems that this overlaps with the notification of TAC provision. Don’t think we need it. * Maybe change it sending an alert? * Question: Does this serve a purpose separate from the purposes of previous recommendations and in particular candidate recommendation #13? Answer: Maybe, since it isn’t mandatory it doesn’t hurt to have it. * Maybe there is value in indicating what is included in the optional message. * If we don’t think there is a purpose for it we shouldn’t keep it. * Registrars can always send extra communication to the registrant, but don’t see a need to put that in the policy. * Don't think we need both a Notification of TAC Provision and also a Notification of Pending Transfer. Especially if the transfer is done almost instantaneously after the TAC is provided to the Gaining Registrar. * ACTION ITEM: Eliminate this candidate recommendation. 4. Rationale for Elimination of the Gaining FOA (15 minutes – time permitting) – see: Gaining FOA Working Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1QOCzbLh7w4hd…> (beginning on p. 16) * Take this up at the next meeting. 5. AOB (5 minutes): Next call: Tuesday 30 November 2021 at 16:00 UTC

1 0