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

Notes and action items: TPR WG Meeting #98 on 01 August at 1600 UTC
by Julie Hedlund Aug. 1, 2023

Aug. 1, 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, 07 August at 1600 UTC. Best regards, Emily, Julie, Berry, and Caitlin ACTION ITEMS/HOMEWORK: Re: Charter question i1 staff to create a working document with the preliminary agreements for WG members to review and suggest revisions. Transfer Policy Review - Meeting #98 Proposed Agenda 01 August 2023 1. Welcome and Chair updates * First August meeting and will continue through August. * Work Plan: Currently at meeting #98, first of August. Five more meetings to discuss ICANN-approved transfers followed by a recap; then moving back to change of registrant. * Are their boundaries want to set on bulk transfers? Need more discussion on the first charter question. 2. Continue discussion of Charter Question i1 ICANN-Approved Transfer (Bulk Transfers) – see attached slides, starting at slide #24: 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 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 – start on slide 26 Preliminary Agreement #1 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. Preliminary Agreement #2 The WG noted the entity requesting the voluntary bulk transfer (typically the current registrar of record) MUST be responsible for any fee charged by the Registry. Preliminary Agreement #3 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.] Preliminary Agreement #4 To enhance the predictability around the fees for bulk transfers, the WG noted that the Registry must publish fees associated with bulk transfers within its [Registry Registrar Agreement/conspicuous place within the Registry portal.] Preliminary Agreement #5 In the event a registry establishes a mandatory fee, the fee MUST NOT exceed [$50,000 or $1 per domain name, whichever is less.] Discussion: PA#1: * Under the current language of the policy is multiple RRAs are terminated that exceed 50K names each would need a fee; the language here notes that instead of current language, “will charge” it’s changed to “MAY charge”. * When this was created over a decade ago there were fewer registries that had such large numbers of names, but still most would be under that threshold, so we may need to look at this holistically and also costs. Part of that money is making sure registrars aren’t abusing the system. * Question: what happens if you arrive at the names in aggregate? Perhaps provide the registrar/registry the opportunity to bundle (or not bundle) the TLDs under a given Registry Operator within the RRA. PA#3: * Don’t recall that we agreed to this. Know we were having conversations around the fee, but “MUST” goes to far. * This is one of the first agreements we discussed across a couple of meetings, but perhaps we need to continue to discuss – didn’t get objections when discussed. * When it is voluntary the registrar initiating it pays for it, but involuntary the receiving registrar pays. * One thing that is important is to clearly partition between involuntary and voluntary bulk transfers – hard to keep this straight for these preliminary agreements. * The requirement of a fee schedule would work against the competitive nature of the voluntary bulk transfer services esp. under BTAPPA. * Doesn’t state where to publish – could it be published privately between partners? Could we let registries and registrars come to that agreement so the registrar could know what it would be ahead of time. * What we are talking about in this charter question is a registrar full portfolio move. BTAPPA doesn’t fall into this discussion. * Fees don’t make sense. Break apart into finite pieces – looking at all the preliminary agreements. * Think these agreements are that we won’t have a fee listed in policy and giving the flexibility to set the fees and decide where to publish. * Question: The missing preliminary agreement is that the fee is variable (no longer a flat fee). Answer: Agree that we can clarify that – that we remove the specific fee from the policy language. Re: Charter question i1 staff to create a working document with the preliminary agreements for WG members to review and suggest revisions. 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 * Mentioned differentiating registrar-initiated for partial bulk transfer, some may not realize that it’s not prohibited. As long as the transfer is allowed by the registrar’s terms and conditions and notification to the registrant – we should tease out those types and make sure registrants are informed. * Goes to the BTAPPA, a registrar chooses to get into business with a registry. * When we talk about standardization we can come up with standard practices but not sure about technical requirements. * Voluntary bulk transfers and partial bulk transfers work reasonable well now, but that will change under the new policy changes. * We did add a lot of security features in inter-registrar transfers, could make partial bulk transfers more difficult. * In looking at the fast-track RSEP language for BTAPPA it doesn’t cover a reseller moving from one registrar to another. That is a shortcoming. Providing more flexibility to the BTAPPA boilerplate is important. * We might have to replace BTAPPA with an ICANN-approved process that matches it in some respects but allows it to be expanded. * BTAPPA --- we need something wider ranging; maybe it is okay for what it does. * When we have these partial bulk transfer make sure the expiry date stays intact. * We need to call that out and get agreement on. Questions: * What types of factors should be made uniform across registry operators with respect to bulk transfers? * Required availability of BTAPPA? * Scrap BTAPPA. * Keep it but create something more flexible. * Required criteria needed in order to initiate? * New sponsor/registry to have the bulk mechanism in place. * Need to document as we are building the process. * Question: In some cases the registrant doesn’t know who the registrar is – but for GDPR do they need to know? Answer: Depends on the scenario. * Sarah (from the chat): 'd say yes, the data subject should know who holds their data. Under the GDPR they have the right to know who the Controller is, which may be the Registry, or I guess may not... they also have the right to know the recipients or categories of recipients of data, which is the registry (but maybe gives some room to not name specific registries). * Uniform Timelines? * Transparent pricing with upper bound? * Don’t think it’s avoidable to set a limit – when eligible to do a partial bulk transfer, i.e., number of names. * Complexity of doing a partial move. May be TLDs across registry operators. * Uniform communication requirements? * This is a big one and one that we really need to think about. How is the registrant informed? Are there requirements for notification? * Who is the best entity to do that? Shift the responsibility to the initiator of the bulk transfer and have binding requirements. * Requirements or uniform cure if issue occurs during partial transfers and cancellation is needed? * Need to think about where cancellations can happen, how, when. 4. AOB

1 0

ON NOW | Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 01 August 2023
by Devan Reed Aug. 1, 2023

Aug. 1, 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

15 MINUTE REMINDER | Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 01 August 2023
by Devan Reed Aug. 1, 2023

Aug. 1, 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