- GNSO-TPR - lists.icann.org

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

**REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 25 July 2023
by Julie Bisland July 24, 2023

July 24, 2023

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

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

July 11, 2023

Dear TPR WG members, Please find below the brief notes and action items from today’s meeting. The next meeting will be in two weeks on Tuesday, 25 July at 1600 UTC. Best regards, Emily, Julie, Berry, and Caitlin ACTION ITEMS/HOMEWORK: None captured. Transfer Policy Review - Meeting #96 Proposed Agenda 11 July 2023 1. Welcome and Chair updates * Thanks to the group for the review of the TEAC and TDRP documents. We received one suggested change from Sarah that we can discuss as a group. * This morning, Berry notified the WG that the monthly project package has been submitted the Council, and we are currently "on target" and 57% of the way through our work. * Per the agenda, we are dedicating today's call to the first charter question under ICANN-approved transfers - Charter Question i1, which references the required fee for bulk transfers. Staff will provide some requested numbers on the bulk transfers, and then we will dive into some targeted questions, based on some of the group's initial feedback from last week. * Project Plan: Where we are today (see above); map out subsequent meeting based on today’s discussion. Will come back to the topic of change of registrants. Question from Sarah Wyld: 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 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. Question: Was our intent specifically to have these updates happen only every 72 hours/3 days, or was that the maximum time that could pass before an update is given? Are we intending to restrict against more prompt/frequent updates (e.g. after two days)? I do think that would be an effect of this current text. If we’re saying that 72 hours/3 days is the maximum time that can pass between updates which could also be more frequent, we could just add in “at least” (“updates by email to the Losing Registrar at least every 72 hours / 3 calendar days”) Discussion: * Sarah: What if there is a useful update prior to 72 hours? We don’t what to restrict this. * Roger: I think this is a good catch. I think we were trying to say within 3 days. If any comments respond to Sarah’s email on the list. Update from Steinar: For info: At-Large has discussed the draft recommendation for Phase 2 charter question G3 and will submit a request to make it possible for a Registrant to initiate a TDRP. The wording will be completed at the CPWG meeting on July 12, 2023. 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 [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. Overview of numbers related to ICANN-approved Bulk Transfers from 2018 – 2022 – see attached slides, #15 * There were 9 ICANN-Approved Bulk Transfers involving 50K or more names * Of the 9 approved transfers involving 50K or more names, 2 were involuntary, and ICANN org sent out an application for the names * 141 ICANN-approved transfers resulting from voluntary/involuntary terminations or voluntary assignments 1. Questions for consideration based on initial reactions from Working Group * The $50,000 fee is a requirement from BTAPPAs that existed in a pre-New gTLD world? Accordingly, what fee considerations (if any) should be made now that bulk transfers could involve multiple TLDs? * Are there instances where the $50,000 fee(s) should be waived? (Examples could include involuntary bulk transfer arising from involuntary bulk transfer resulting from RAA terminations). * Should tiered fees depending on volume be considered in ICANN-approved bulk transfers? * Should additional carve-outs be considered for involuntary transfers - for example - premium names? Discussion: * Jothan: The data on involuntary would be helpful to get data all the way back to the beginning - it is infrequent but quite the harrowing experience for all parties involved. As the registrars mentioned in their comments they really take on a lot of headaches. So, should there be a fee for the gainers since they really are providing a service. * Roger: Maybe for the voluntary ones its more of a business decision. * Volker: We volunteered to take on a registrar known for abuse but stalled when we didn’t pay the transfer fees. Wise to propose that in the case of involuntary bulk transfers the gaining registrar should be exempt from the fees. * Roger: Think also about the path for voluntary bulk transfers. * Jody: We took over a large registrar that went offline and it was a great deal of effort. This is not a money-making situation. A lot of registrants will transfer from the registrar taking them over. * Theo: Most registrars don’t want the bulk transfers from problematic registrars. * Volker: The voluntary bulk transfers need help too. * Steinar: Where did the $50K come from? * Roger: It does get complicated. There is some cost associated with it. Is there a way to do this on a cost basis? * Jothan: This 50k was, I think, arbitrarily set at a time when the landscape was really fundamentally different. I seem to recall it was set as an amount that would cause an appropriate level of friction to dissuade over-use. * Roger: Not a total fee – per 50K or more. Each backend provider would get the $50K fee. * Jothan: Can we drill down to the scenarios where it is voluntary? Do we want to look at whether the registration term is affected? * Roger: Should we remove the idea of fees from the policy and let the registries and registrars to work it out, or is it helpful to leave it there? * Catherine: Should we look at the definition of ICANN-Approved Transfers in the Policy? This is limited. * Jothan: The early version of this was an ad-hoc process. Helpful if we could prescribe that the gaining registrar can handle all of the bulk transfers. * Catherine: Think the above is handled by the policy – except in the case of acquisitions. * Caitlin: Catherine is correct that a gaining registrar applicant will be asked to confirm they are accredited in all relevant TLDs. * Roger: Seems like there’s support for removing the fee on involuntary transfers – but also could be multiple paths. Can we get more details on that voluntary bucket. * Caitlin: In some recent years there has been consolidation of registrars that resulted in bulk transfers. Also this section of the policy could be worded better, particularly with respect to subject/verb agreement. * Catherine: Does this policy and the registry services BTAPPAs overlap? * Roger: This applies to charter question #2. * Jothan: Should vertically integrated registries be excluded from the process -- so should vertical integration be a factor in the scenario of multiple-party involuntary transfer scenarios. * Roger: If someone voluntarily stops supporting a TLD should any or all of the fees be waived or do we not talk about fees at all? There is a cost – how should it be accounted. Hearing that $50K fee should be applied for an involuntary transfer. * Volker: Number 50K always seemed arbitrary – free to 49K but then $50K for 50K domain names. Also would like to see where this fee is coming from and have tiered fees. * Jim: On the question of involuntary transfers: seems likely we could get support from the registries to waive the fees. On the voluntary side I think we need to consider what problem we are trying to solve. Need to discuss this more. Need to understand what was behind the charter question. * Jothan: One reason to look at this closely: As it is today a lot of the automated bulk will change post our changes to the policy especially re: via the access to Auth codes. * Volker: What problem are we solving with the Transfer Policy? If we can’t answer that, then the fee should go. * Roger: When you look at what the Policy is trying to achieve is cost recovery because there is cost to moving these. * Caitlin: “In preparing this report, ICANN org Policy staff consulted with other departments within ICANN org. Colleagues from Global Domains and Strategy (GDS), who manage the De-Accredited Registrar Transition Procedure, have noted that the requirements in Section I.B.2 of the Transfer Policy have * caused challenges in certain instances of de-accreditation. Specifically, the requirement for a gaining registrar to pay a one-time flat fee of $50,000 can make it difficult to secure a gaining registrar. By way of example, when the pool of potential gaining registrars perceive the value of a domain portfolio to be minimal, where the terminating registrar’s domains are known or suspected to have a significant portion of abusive registrations, data escrow issues (the data in escrow is outdated or incomplete), * Jothan Frakes, RrSG Alt to Everyone (1:05 PM) * hopefully I was clear - I think there's a significant amount of inter-registrar "bulk" transfers that happen which work because they can flow through EPP via some level of automation... but once we'd alter the TAC "stuff" those would be affected and perhaps need voluntary bulk solutions * Caitlin Tubergen – From Final Issues Report: “In preparing this report, ICANN org Policy staff consulted with other departments within ICANN org. Colleagues from Global Domains and Strategy (GDS), who manage the De-Accredited Registrar Transition Procedure, have noted that the requirements in Section I.B.2 of the Transfer Policy have caused challenges in certain instances of de-accreditation. Specifically, the requirement for a gaining registrar to pay a one-time flat fee of $50,000 can make it difficult to secure a gaining registrar. By way of example, when the pool of potential gaining registrars perceive the value of a domain portfolio to be minimal, where the terminating registrar’s domains are known or suspected to have a significant portion of abusive registrations, data escrow issues (the data in escrow is outdated or incomplete)” and “expectations of renewal rates are low (in the case of aggressive promotions), the requirement for a gaining registrar to pay a one-time flat fee of $50,000 USD to the registry operator makes it difficult to secure a gaining registrar to accept the domains. This, in turn, poses a risk to the registrants who have utilized the services of the terminating registrar. Furthermore, ICANN has limited ability to determine the quality of the domains or make representations to potential gaining registrars as to the value of the domains.” * Jothan: I would not want vertically integrated registrars to not be able to offer to take involuntary transfers, but then would encourage that it would be the entirety of the registrants. * Jothan: Can this be a multiple TLD type of fee? Poll questions: (approximate with raised hands) 1. If there is an involuntary termination resulting in a bulk transfer, should the required $50,000 fee be waived (no fee in the policy)? (yes: 2 no: 7) 2. Should there be a tiered approach to the fee? (6 yes / want to consider) 3. Leave fee as is? (0 yes) 3. AOB

1 0

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

July 11, 2023

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Tuesday, 11 July 2023 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/V4GCDg> (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, 25 July 2023
by Julie Bisland July 11, 2023

July 11, 2023

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 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

**STARTING IN 3 MINUTES** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 11 July 2023
by Julie Bisland July 11, 2023

July 11, 2023

**STARTING IN 3 MINUTES** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 11 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/V4GCDg * Time conversion link: https://tinyurl.com/2eb4cfva [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2eb4cfva__;!!PtGJab4!9-0WPku…> 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

**AT THE TOP OF THE HOUR** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 11 July 2023
by Julie Bisland July 11, 2023

July 11, 2023

**AT THE TOP OF THE HOUR** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 11 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/V4GCDg * Time conversion link: https://tinyurl.com/2eb4cfva [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2eb4cfva__;!!PtGJab4!9-0WPku…> 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

GNSO_TPR // 20 July 2023 Project Package
by Berry Cobb July 11, 2023

July 11, 2023

Dear WG, Please find a link below to project package for the GNSO_TPR PDP (20 July 2023). This package is a snap-shot in time and developed by the leadership team to report on the working group’s activities and status of the project. It is also distributed to the GNSO Council to keep them informed as managers of the PDP. The package is deposited on the wiki so that we can track access statistics. Link: https://community.icann.org/x/MQDQCQ 1. Page 01 – Summary Dashboard, Project SitRep, and Activity Metrics 2. Page 02 – Meeting metrics, Roster, & Group Attendance 3. Page 03 – Project Plan, Gantt chart 4. Page 04 – Workplan Key points: * None for this period. Please let staff know if you have questions. Thank you. B Berry Cobb Policy Development – Senior Program Manager Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 424 443 8960 Phone: +1 202 570 7240 Fax: +1 202 789 0104 Twitter: @berrycobb www.icann.org<https://www.icann.org/>

1 0