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

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

Aug. 22, 2023

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 22 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/_YSZDg * Time conversion link: https://tinyurl.com/ys4acauj [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/ys4acauj__;!!PtGJab4!-5IfCJX…> 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

REMINDER | Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 22 August 2023
by Terri Agnew Aug. 21, 2023

Aug. 21, 2023

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 22 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/_YSZDg * Time conversion link: https://tinyurl.com/ys4acauj [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/ys4acauj__;!!PtGJab4!-5IfCJX…> 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 and homework for TPR WG Meeting #101 - 22 August 2023
by Caitlin Tubergen Aug. 17, 2023

Aug. 17, 2023

Dear TPR Working Group Members, Please find below the proposed agenda for the next TPR Working Group meeting. Thank you again to Rick, Owen, Steinar, and Sarah for already putting comments into the Working Document<https://docs.google.com/document/d/1gX1N8d3qoktbniRmfGE4-8Un9dPavIKQ3IZYaoe…>. Please review the updated comments, as well as Support Staff’s proposed responses and edits based on the comments received. Additionally, Support Staff has added some concepts based on the discussion from the last meeting. For ease of reference, we have included the concepts in the body of this email. 🚨🚨 ACTION ITEM 🚨🚨 Working Group members have until Monday, 21 August to note edits, comments, concerns, etc. with the proposed preliminary agreements and concepts. The comments from WG members will make up the agenda for our upcoming meeting. As a reminder, the preliminary agreements and proposed updated language can be found in the orange box beginning on p. 3 of the Working Document<https://docs.google.com/document/d/1gX1N8d3qoktbniRmfGE4-8Un9dPavIKQ3IZYaoe…>. Proposed concepts based on last meeting of WG: Concept 1: The Working Group recognizes that a fee may be involved in a full portfolio transfer but believes flexibility is necessary, and the number should not be explicitly prescribed in the Transfer Policy. Concept 2: The Working Group also recognizes, however, that a price ceiling is helpful to include in the policy language to avoid abusive pricing. Concept 3: In light of Concept 2, the Working Group believes the fee for a full portfolio transfer must not exceed [$50,000 or $1.00 per domain name transferred]. Concept 4: If the full portfolio transfer involves multiple registries, the affected registries must ensure the collective fee does not exceed the recommended ceiling, and the fee should be apportioned based on number of domain names. By way of example, if a registrar has 60,000 domains under management under two TLDs, e.g., 40,000 names under .ABC, and 20,000 names under .DEF, the combined fee cannot exceed $50,000 USD (per concept 3). Since two thirds of the names under management are registered to .ABC, .ABC registry may bill the registrar for 66.66% of the fee, e.g., $33,333.33, and .DEF may bill the registrar for the remaining 33.33% of the fee, e.g., $16,666.67. Concept 4(a): [Following the completion of the transfer, the Registry Operator(s) MUST provide notice to ICANN that the transfer is complete, and the notice to ICANN MUST include the number of domain names transferred. Following receipt of notices from all involved registries, ICANN will send a notice to affected Registry Operators with the reported numbers and corresponding percentages of domain names involved in the bulk transfer, e.g., 26% of names for .ABC and 74% of names for .DEF. The Registry Operators MAY then charge the registrar a fee according to their schedule.] Concept 5: The Working Group notes the Registry Operator should have flexibility to establish and waive fees associated with full portfolio transfers and accordingly, does not recommend a required price floor. So long as the Registry Operator’s fee is below the maximum ceiling, the Registry Operator may establish its price schedule as it chooses, provided the price schedule is communicated transparently to the requesting registrar [(see Rec. x, currently Proposed Preliminary Agreement #4)]. If you have comments or proposed edits to these concepts, please provide them in the Working Document<https://docs.google.com/document/d/1gX1N8d3qoktbniRmfGE4-8Un9dPavIKQ3IZYaoe…> on ICANN-approved Transfers (beginning on p. 3). You may also provide comments via the list. Thank you. Best regards, Julie, Christian, Berry, and Caitlin -- Transfer Policy Review - Meeting #101 Proposed Agenda 22 August 2023 1. Welcome and Chair updates 2. Continue discussion of Preliminary Agreements<https://docs.google.com/document/d/1gX1N8d3qoktbniRmfGE4-8Un9dPavIKQ3IZYaoe…> from Charter Question i1 (Full Portfolio Transfers AKA Bulk Transfers) and Charter Question i2 (Change of Sponsorship AKA Partial 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? 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? 3. AOB

1 0

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

Aug. 15, 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, 22 August at 1600 UTC. Best regards, Berry, Caitlin, and Julie ACTION ITEMS/HOMEWORK: 1. Re: Preliminary Recommendation #1 – Staff to tighten the language including taking out the examples and putting them into the rationale. 2. Re: Preliminary Agreement #5 -- WG members to consider suggesting a floor and ceiling or other fee structure, whether fees should be included in the policy or elsewhere, and impacts on Preliminary Agreement #1, and put these suggestions in the Working Document at: Preliminary Agreements [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1gX1N8d3qoktb…>. Transfer Policy Review - Meeting #100 Proposed Agenda 15 August 2023 1. Welcome and Chair updates * Reminder that we have three meetings to conclude the discussions on bulk transfers. * Quite a few comments in the working document. Thanks to all who reviewed. 2. Continue discussion of Preliminary Agreements [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1gX1N8d3qoktb…> from Charter Question i1 (Full Portfolio Transfers AKA Bulk Transfers) and Charter Question i2 (Change of Sponsorship AKA Partial Bulk Transfers) – See also attached slides, starting at #36 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? 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? Preliminary Agreement #1: The Working Group recommends that Registry Operators MAY charge a fee to implement a full domain name portfolio transfer* from one ICANN-accredited registrar to another ICANN-accredited registrar. The Working Group recognizes that there may be instances where the Registry chooses to waive this fee, such as cases where [a registrar is involuntarily terminated by ICANN org due to a compliance breach, non-responsiveness to renewal notices, etc.] Discussion: * Highlighted text relates to comment received. * First question, is highlighted text clear enough? * Language is clear, but not who would invoice whom. That’s covered in another recommendation. * Would be more clear if we change ROs to RO (plural to singular). * Perhaps “portfolio” could be replaced by “the holdings of that registrar”. * Staff will endeavor to tighten the language. * Question: No indication of numbers. Is that on purpose? Answer: This is talking about the entire portfolio – could be any number but it doesn’t matter. * Simply second sentence to change the comma to a period and strike the rest (delete examples). * Is it useful to provide the examples? Maybe in a footnote? * Best if we don’t mention involuntary (or voluntary) termination. * This applies to both voluntary and involuntary. * The chances of gaming are limited because there are three parties involved. ACTION ITEM: Re: Preliminary Agreement #1 – Staff to tighten the language including taking out the examples and putting them into the rationale. Preliminary Agreement #4: Due to the variable nature of the fee associated with full portfolio transfers, the Working Group recommends that Registry Operators MUST provide notice to registrars of any fees associated with full portfolio transfers upon request and prior to the completion initiation of the full portfolio transfer. How Registry Operators choose to provide notice of fees will be up to the Registry to decide, i.e., password protected portal, website, written notice, etc. Discussion: * Suggested change: Removing “completion” and changing it to “initiation”. [WG agrees] * Keep this separate from partial transfers. * But if we have similar wording make sure the language is consistent. Preliminary Agreement #5: In the event a registry establishes a mandatory fee for full portfolio transfers, the Working Group recommends [the fee MUST NOT exceed $50,000 or $1 per domain name, whichever is less.] Questions: * Do we want to consider/anticipate portfolio transfers that cover multiple registries? For example, how to coordinate (separately? individually?), how are fees determined, etc? Suggestions? * One option for the fee would be to ensure that that all ROs are made whole, plus some type of administrative fee per RO for processing the change of sponsorship? Discussion: * Bracketed language is a suggestion from staff and not agreed to by the WG. * WG should discuss whether fees should be included in the policy. Concern was about abuse if fee is not mentioned. * Is there a maximum? * It shouldn’t be prohibitively expensive; cost recovery should be a goal, but this is a non-zero effort. * There are a lot more registries, a lot more registrars, a lot more domains in circulation now. This is looking at setting the cap. 10,000 names is a lot different than 10 million names. You know that the practical registry work may not be extremely big technically but you know they still have to go through and make sure. * The fees right now in real life don’t happen that much. Most of these registrars don't have portfolios that involve more than 50,000 names at a particular TLD. * There could be 100K but it never reaches the threshold because it is split over 6 TLDs so there is no fee. When you transfer 40,000 names it's free. But when you transfer 50,000 it's all of a sudden $50,000. It seems arbitrary that there's a cut off that jumps from $0 to $50,000. * These portfolio changes happen a lot. The only blocker here within the gTLD space is the huge fees and not a standardized process that is applicable to all the TLDs. This is about making sure the full portfolio transfer doesn’t get abused. * History tells us this hasn’t really happened – is it more likely to? What about from the idea that there are 10 separate TLDs? There is another dimension here. Maybe talking about a flat fee at all isn’t right, maybe $1 per X [domain name, etc.]. * One of the other variable is a RO could be a 100 TLDs – could be a lot of different variables today. Need to worry about the ceiling, not the floor. * Floor might be good to have – this is a non-trivial effort for a RO. Like the idea of a minimum and ceiling – minimum price and not to exceed price. * Agreement #1 allows the RO to set a floor. Sounds like people agree a ceiling makes sense but not on how to determine the ceiling. * May be some that are more complicated – such as .bank, .pharmacy, etc. * There are fees outside of the Registry too. * Think about it in terms of a $1 per domain name; have a fee based on the registrar’s portfolio size. * The WG likes the ceiling idea, but how to set the bound on the ceiling. How do we make this fair and equitable? Don’t know how you calculate a ceiling without setting numbers. * Have both a floor and ceiling – if registrar’s portfolio is 50K names, then there is a charge of $1 per domain name spread across TLD operators but no more than $50K. * Is there a domain number threshold? * How do you invoice that? Does ICANN get involved? Do we have to think about implementation. * Do we base the fee on the volume irrespective of the number of TLD operators. * Fee is based on the whole portfolio. * How do you divide $50K between X TLD operators? Issue is who does the billing? ICANN? * If the fee is based on the registrar’s portfolio, this is a different orientation than we’ve considered. There’s going to have to be a coordinating body – ICANN. * Makes sense for involuntary transfers – but don’t know we have to require ICANN to be involved for voluntary transfers. * Exploring some good scenarios. It does get very complex. One thing that is lost is to project manage this – to think about it wholistically; would have to be ICANN. * Sounds like the WG is agreeing that a ceiling is a good idea and Jim has a suggestion for how to consider this differently. ACTION ITEM: Re: Preliminary Agreement #5 -- WG members to consider suggesting a floor and ceiling or other fee structure, whether fees should be included in the policy or elsewhere, and impacts on Preliminary Agreement #1, and put these suggestions in the Working Document at: Preliminary Agreements [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1gX1N8d3qoktb…>.

1 0

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 22 August 2023
by Julie Bisland Aug. 15, 2023

Aug. 15, 2023

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 22 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/_YSZDg * Time conversion link: https://tinyurl.com/ys4acauj 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

Post Call | Transfer Policy Review PDP WG | Tuesday, 15 August 2023
by Julie Bisland Aug. 15, 2023

Aug. 15, 2023

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

**STARTS IN 15 MINUTES** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 15 August 2023
by Julie Bisland Aug. 15, 2023

Aug. 15, 2023

**STARTS IN 15 MINUTES** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 15 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/94SZDg * Time conversion link: https://tinyurl.com/52b425vs [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/52b425vs__;!!PtGJab4!8aWtu0O…> 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 // 14 August 2023 Project Package
by Berry Cobb Aug. 14, 2023

Aug. 14, 2023

Dear WG, Please find a link below to project package for the GNSO_TPR PDP (14 August 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: * Welcome to WG meeting #100. 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

**REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 15 August 2023
by Julie Bisland Aug. 14, 2023

Aug. 14, 2023

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 15 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/94SZDg * Time conversion link: https://tinyurl.com/52b425vs [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/52b425vs__;!!PtGJab4!8aWtu0O…> 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 WG Meeting #100 - Tuesday, 15 August 2023
by Caitlin Tubergen Aug. 10, 2023

Aug. 10, 2023

Dear TPR Working Group Members, Please find below the proposed agenda for our upcoming 100th meeting of this Working Group. 🚨🚨 ACTION ITEM 🚨🚨 Thank you to Rick, Owen, and Steinar for already putting comments into the Working Document<https://docs.google.com/document/d/1gX1N8d3qoktbniRmfGE4-8Un9dPavIKQ3IZYaoe…>. As a reminder, Working Group members have until Monday, 14 August to note edits, comments, concerns, etc. with the proposed preliminary agreements. If a preliminary agreement has no comments, we will assume it is acceptable to the group and will base our agenda off of the preliminary agreements with comments and concerns. As a reminder, the preliminary agreements and proposed updated language can be found in the orange box beginning on p. 3 of the Working Document<https://docs.google.com/document/d/1gX1N8d3qoktbniRmfGE4-8Un9dPavIKQ3IZYaoe…>. Best regards, Emily, Julie, Berry, and Caitlin -- Transfer Policy Review - Meeting #100 Proposed Agenda 15 August 2023 1. Welcome and Chair updates 2. Continue discussion of Preliminary Agreements<https://docs.google.com/document/d/1gX1N8d3qoktbniRmfGE4-8Un9dPavIKQ3IZYaoe…> from Charter Question i1 (Full Portfolio Transfers AKA Bulk Transfers) and Charter Question i2 (Change of Sponsorship AKA Partial 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? 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? 3. AOB

1 0