July 2023 - GNSO-TPR - lists.icann.org

**REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 01 August 2023
by Julie Bisland July 31, 2023

July 31, 2023

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

1 0

Proposed agenda - TPR Meeting #98 - 1 August 2023 at 1600 UTC
by ICANN Policy Calendar July 28, 2023

July 28, 2023

Dear Working Group Members, Please find below the draft agenda for the next meeting on Tuesday, 1 August at 16:00 UTC. Thank you. Best regards, Emily, Julie, Berry, and Caitlin -- Transfer Policy Review - Meeting #98 Proposed Agenda 1 August 2023 1. Welcome and Chair updates 2. Continue discussion of Charter Question i1 ICANN-Approved Transfer (Bulk Transfers): i1) In light of these challenges described in section 3.1.7.2 of the Final Issue Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/final-iss…>, should the required fee in Section I.B.2 of the Transfer Policy<https://www.icann.org/resources/pages/transfer-policy-2016-06-01-en> be revisited or removed in certain circumstances? a. Recap of overarching themes from last call * The WG noted that in the case of an ICANN-approved bulk transfer, the involved registry/ies MAY charge a fee for executing the bulk transfer. (Some noted that there may be instances where the registry chooses to waive the fee, so it should not be mandatory as it currently is in the policy.) * The WG noted the entity requesting the voluntary bulk transfer (typically the current registrar of record) should be responsible for any fee charged by the Registry. * In the case of an involuntary bulk transfer resulting from an involuntary RAA or RRA termination, the WG recommends that the relevant registry/ies must waive any required fee. [This is in recognition of the difficulty in procuring a gaining registrar to take on a failing or unresponsive registrar’s domain name portfolio.] * To enhance the predictability around the fees for bulk transfers, some working group members noted that the Registry should publish fees associated with bulk transfers. * The WG expressed concern with a cost recovery model for bulk transfer fees, but the WG noted that there should be an upper bound on a registry’s mandatory fee (if any) for the sake of predictability. 1. Continued discussion of preliminary agreements and proposals 3. Introduction to Charter Question i2 i2) Should the scope of voluntary bulk transfers, including partial bulk transfers, be expanded and/or made uniform across all registry operators? If so, what types of rules and considerations should govern voluntary bulk transfers and partial bulk transfers? 1. Recap of question origin 2. Discussion 4. AOB

1 0

August, September and October 2023 calls | Transfer Policy Review PDP WG
by Terri Agnew July 28, 2023

July 28, 2023

**We are sending in advance to get dates on everyone’s calendar. Dear all, The calls for August, September and October 2023 for the Transfer Policy Review PDP WG are listed below. The calls take place on Tuesdays at 16:00 UTC for 90 minutes., please be sure to download them as “recurring” vs. a one-time event to ensure all the dates show up on your calendar. * Tuesday, 01 August 2023 – see attached .ics for the August calls * Tuesday, 08 August 2023 * Tuesday, 15 August 2023 * Tuesday, 22 August 2023 * Tuesday, 29 August 2023 * Tuesday, 12 September 2023– see attached .ics for the Sept & Oct calls * Tuesday, 19 September 2023 * Tuesday, 26 September 2023 * Tuesday, 03 October 2023 * Tuesday, 10 October 2023 Future invitations will be sent out closer to the date of the call. Thank you. With kind regards, Terri

1 0

Transfer Policy Review PDP WG
by ICANN Policy Calendar July 28, 2023

July 28, 2023

Meeting: Transfer Policy Review PDP WG Pattern: Weekly on Tuesday’s: 12 September – 10 October 2023 at 16:00 UTC for 90 minutes Alternate replacement confirmations – Members who are unable to attend, please complete the google form<https://docs.google.com/forms/d/e/1FAIpQLScXP3-H595xH4EFgaR3ydOr-1o9BLAVGUI…> to communicate who the alternate is replacing you. 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 page (2023): https://community.icann.org/x/Gow-DQ * Time conversion link: https://tinyurl.com/2y6945sz ONLY for Members & Alternates: * Please join via the above Zoom Webinar link and staff will promote you to Panelist * Alternate assignments 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. * 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# Webinar ID: 953 6372 7469 Passcode: 7490739013 International numbers available: https://icann.zoom.us/u/acdLFXPLp6

1 0

ALAC Input on Transfer Policy PDP Charter Recommendations Phase 2 G3
by Steinar Grøtterød July 26, 2023

July 26, 2023

Dear all, Attached is the ALAC Input on Transfer Policy PDP Charter Recommendations Phase 2 G3. Regards, Steinar Grøtterød At-Large

1 0

Post Call | Transfer Policy Review PDP WG | Tuesday, 25 July 2023
by Julie Bisland July 25, 2023

July 25, 2023

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

1 0

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 01 August 2023
by Julie Bisland July 25, 2023

July 25, 2023

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

1 0

Notes and action items: TPR WG Meeting #97 on 25 July at 1600 UTC
by Julie Hedlund July 25, 2023

July 25, 2023

Dear TPR WG members, Please find below the brief notes and action items from today’s meeting. The next meeting will be on Tuesday, 01 August at 1600 UTC. Best regards, Emily, Julie, Berry, and Caitlin ACTION ITEMS/HOMEWORK: Re: Charter Question i1 ICANN-Approved Transfer (Bulk Transfers) -- Staff will create a working document in Google for WG members to provide comments/suggestions. Re: 1.B proposed updates: Staff will create a working document in Google for WG members to provide comments/suggestions. Transfer Policy Review - Meeting #97 Proposed Agenda 25 July 2023 1. Welcome and Chair updates * Reminder that we do plan on continuing our work through August. * Steve Crocker, SSAC: Issue of smooth transfer of signed zones, raised but it was out of scope. SSAC is working on DS automation and glitch-free transfer – will send the wording to you and will brief groups when the report comes out. * Jothan: We shall always make best efforts on transfer of DNSSEC related _stuff_, but we frequently find this rather challenging when 3rd party DNS Providers are used. * Steinar: ALAC INPUT ON TRANSFER POLICY PDP CHARTER RECOMMENDATIONS PHASE 2 G3 will be distributed to the GNSO-TPR mailing list later this week. Apologies for being delayed a few days. 2. Discussion of Charter Question i1 ICANN-Approved Transfer (Bulk Transfers): See attached slides, starting with slide 17. i1) In light of these challenges described in section 3.1.7.2 of the Final Issue Report [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…>, should the required fee in Section I.B.2 of the Transfer Policy<https://www.icann.org/resources/pages/transfer-policy-2016-06-01-en> be revisited or removed in certain circumstances? 1. Recap of overarching themes from last call * The WG seemed to agree that in the event of an involuntary termination involving a bulk transfer, the mandatory bulk transfer fee should be waived. * Further discussion needed on future of mandatory bulk transfer fee * Language in Section I.B needs rethinking Discussion: * Any discussion of gaming? That you could break them up into tranches of fewer than 50K to avoid a fee? Probably wouldn’t apply for portfolio transfers --- but will come up in other discussions. * Could also be voluntary registrar transfers. We need to be clear there. * Do we need clarity on what we mean by “bulk transfer”? We could think about whether there is better/more clear term? * Curious – it is the registry that loses $50K; are they willing to take these on? For involuntary is happens really infrequently. * In terms of the number of involuntary transfers over the last 5 years there were only two of them, but they do happen. The $50K fee is also for voluntary transfers as between registrars. In a voluntary setting, should there still be a $50K fee. See questions below. ACTION ITEM: Re: Charter Question i1 ICANN-Approved Transfer (Bulk Transfers) -- Staff will create a working document in Google for WG members to provide comments/suggestions. 1. Potential options for mandatory fee * Should the mandatory fee be removed from the policy and left between Ry/Rr? * Should the mandatory fee be tiered based on volume rather than one lump sum? * Should the mandatory fee language remain as is? * Other options? Discussion: * Not in favor of Rr/Ry agreements. * Comment: Agree with the notion that the fee was added to mitigate overuse seems odd. Looking at this as an overarching principle – why not come at this from the point of view there’s work for everyone involved, so if there’s a fee who should pay? Could be paid by whoever is motivating it? Separately, we could consider what that fee would look like. * When we talk about cost-recovery then the registrar would cover it as a flat fee. But registrar may also incur costs. * Two scenarios – voluntary and involuntary. Involuntary is good for the ecosystem. Who initiates an involuntary transfer? If it’s initiated by someone going out of business you won’t get a payment from that entity. Whatever scenario, registries and registrars will incur costs. * Maybe it isn’t fair for ICANN to pay if it is a problem that ICANN has discovered (involuntary scenario). * Even in an involuntary scenario you charge the registrar going out of business but you might not get anything. * Maybe the involuntary scenario is an exception. * Voluntary scenario: probably makes sense to include a fee paid by the registrar – flat fee, cost recovery? What does this language look like and how specific it should be. * Tiered approach: we don’t even know if that is even reasonable for a registry. Should be an option to bring a complaint about fees to ICANN Compliance. * By volume there is economy of scale – 10K isn’t 10 times the effort compared to 1K. * Cost recovery has concerns because registrars don’t know what to expect – whose checking this and how do you know it’s a reasonable fee? * Cost recovery policies are inherently troublesome. The U.S. government has imposed cost recovery policies on the operation of university computer centers. The results are terrible. The party asking for cost recovery has to justify the costs, which leads to both a lot of gaming and a lot of intrusive auditing. * This should be up front. It should be a process that the registry has figured out and knows what the cost is. * Should the policy say that registries should publish their fees? Why not? * So registries include in their RRAs for domain names – include bulk transfer fees? But how is this enforced? Do you have to tell ICANN your fee? * There needs to be a check and balance somewhere. * Starting to see some registries not putting fees in their RRAs, instead in web portals. Urge to have one fee structure across all gTLDs. * Registries and registrar will have different cost models. * Wonder if we can come up with a model, but that doesn’t have specific numbers? * Does the bulk transfer fee have to be mandatory – maybe build in exceptions? * Multiple TLDS – could be good if the transfer could be by organization on the registry services side. Also there are registrar families – could the fee be for the transfer process rather than by name/TLD? * Should the fee be left to the registry/registrar. Or could set a maximum. * It needs to be accountable. ICANN Compliance should be able to enforce. * Think we are focusing too much on a single registry operator. How this plays out across a number of TLDs. * Seems like we still want to be able to have flexibility in the fee assessment/amount and control an upper bound. 1. 1.B proposed updates – see suggested language in brackets in slide 23. Discussion: * The way that 1.B is currently worded is confusing. * On slide 22 – should be a 5th bubble/bucket were the bulk is performed under standard EPP circumstances. * Currently the above scenario is not prohibited but might want to put parameters around it. * Not sure what you would achieve by including it in the policy. ACTION ITEM: Re: 1.B proposed updates: Staff will create a working document in Google for WG members to provide comments/suggestions. 3. AOB

1 0

**AT THE TOP OF THE HOUR** Meeting Invitation | TPR PDP WG call | Tuesday, 25 July 2023
by Julie Bisland July 25, 2023

July 25, 2023

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

1 0

Proposed agenda for TRP Meeting #97 on 25 July 2023 - 16:00 UTC
by Caitlin Tubergen July 24, 2023

July 24, 2023

Dear Working Group Members, Please find below the draft agenda for the next meeting on Tuesday, 25 July at 16:00 UTC. As a reminder, Sarah proposed an edit to a preliminary recommendation for TEAC. The proposed update, which is shown below, received no objections, so the preliminary recommendation now reads: Re: Draft Preliminary Recommendation: Once a Gaining Registrar has provided an initial non-automated response to a TEAC communication as described in Section I.A.4.6.3 of the Transfer Policy, the Gaining Registrar must provide additional, substantive updates by email to the Losing Registrar at least every 72 hours / 3 calendar days until work to resolve the issue is complete. These updates must include specific actions taken by the Gaining Registrar to work towards resolution. (emphasis added) Thank you. Best regards, Emily, Julie, Berry, and Caitlin -- Transfer Policy Review - Meeting #97 Proposed Agenda 25 July 2023 1. Welcome and Chair updates 2. Discussion of Charter Question i1 ICANN-Approved Transfer (Bulk Transfers): i1) In light of these challenges described in section 3.1.7.2 of the Final Issue Report<https://gnso.icann.org/sites/default/files/file/field-file-attach/final-iss…>, should the required fee in Section I.B.2 of the Transfer Policy<https://www.icann.org/resources/pages/transfer-policy-2016-06-01-en> be revisited or removed in certain circumstances? 1. Recap of overarching themes from last call * The WG seemed to agree that in the event of an involuntary termination involving a bulk transfer, the mandatory bulk transfer fee should be waived. * Further discussion needed on future of mandatory bulk transfer fee * Language in Section I.B needs rethinking 1. Potential options for mandatory fee * Should the mandatory fee be removed from the policy and left between Ry/Rr? * Should the mandatory fee be tiered based on volume rather than one lump sum? * Should the mandatory fee language remain as is? * Other options? 1. 1.B proposed updates 3. AOB

1 0