- GNSO-TPR - lists.icann.org

**REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 03 October 2023
by Julie Bisland Oct. 2, 2023

Oct. 2, 2023

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 03 October 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/g4jxDg * Time conversion link: https://tinyurl.com/2rz29rxj [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2rz29rxj__;!!PtGJab4!4Zvjh8P…> 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 #106 - 3 Oct 2023
by Caitlin Tubergen Sept. 29, 2023

Sept. 29, 2023

Dear TPR WG members, Please find below the proposed agenda for the next call on Tuesday, 3 October 2023 at 16:00 UTC. Kind regards, Christian, Julie, Berry, and Caitlin ---------- Transfer Policy Review - Meeting #106 Proposed Agenda 3 October 2023 1. Welcome and Chair updates 2. Continued discussion of 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 [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? * Final thoughts on options for fees<https://docs.google.com/document/d/1b0KIvhRyyO5QSEI4DB4vP78muKvqHneaXOZTcvI…> * Next steps 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? Should proposed BTAPPA updates apply to: 1. all registry operators (via an update to the Transfer Policy), OR 2. all registry operators who offer the BTAPPA (via recommended updates to the BTAPPA) 3. Outstanding question re: EPDP Phase 1, Rec. 27 Wave 1 Report<https://mm.icann.org/pipermail/council/2020-February/023534.html> – Transfer Dispute Resolution Policy * Draft amended TDRP<https://docs.google.com/document/d/12ncsCc_sYiBs2cRZVOPCrBes92aV0p-6S-7hNBk…> (with Rec. 27 updates) for discussion * Questions? 4. AOB

1 0

ICANN78 prep week schedule is now published / How to Create your Prep Week Schedule
by Julie Bisland Sept. 26, 2023

Sept. 26, 2023

Dear all, The ICANN78 prep week schedule is now published! Please take a moment to read the information below to help create your prep week schedule and add sessions to your calendar. For the prep week schedule, go here: https://icann78.sched.com/ [icann78.sched.com]<https://urldefense.com/v3/__https:/icann78.sched.com/__;!!PtGJab4!5PS-FK-94…> * Click Sign up or Log in and enter your information (email address and create password) * Once you “Join Event”, the schedule shows up with blank circular buttons to the left of each session. Hover over each button and click “ADD TO MY SCHEDULE” (see screenshot below) or just click in each circle to add the checkmark. [cid:image001.png@01D9F088.CE8A2A00] * Once you’ve selected all sessions, click the My Schedule link in the lower left corner or hover over your profile and select My Schedule. [cid:image002.png@01D9F088.CE8A2A00] Or [cid:image003.png@01D9F088.CE8A2A00] * You will see this message, “A copy of your schedule has been sent to your(a)email.com<mailto:your@email.com>.” To export the schedule, click the Phone icon: [cid:image004.png@01D9F088.CE8A2A00] * On the page that appears, notice the sections “Mobile” and “Calendar Sync for Google Calendar, Outlook & Apple Calendar”. In the “Calendar Sync …” section, select Export Calendar, and click the link next to “My Schedule”. When the .ics is exported, add it to the appropriate calendar (see screenshots below). Or, after exporting, drag and drop the .ics file directly into your calendar.. [cid:image005.png@01D9F088.CE8A2A00] [cid:image006.png@01D9F088.CE8A2A00] The ICANN78 Schedule<https://meetings.icann.org/en/icann78> will be posted 02 October 2023. Please email questions to us at: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, Policy Team Supporting the GNSO -- Julie Bisland Policy Operations Sr. Coordinator (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

Notes and action items: TPR WG Meeting #105 on 26 Sept at 1600 UTC
by Julie Hedlund Sept. 26, 2023

Sept. 26, 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, 03 October at 1600 UTC. Best regards, Berry, Caitlin, and Julie ACTION ITEMS/HOMEWORK: 1. Staff to provide the data on the number of registries that offer BTAPPA services. 2. WG members to provide their feedback/preferences on the 4 options: https://docs.google.com/document/d/1b0KIvhRyyO5QSEI4DB4vP78muKvqHneaXOZTcvI… Transfer Policy Review - Meeting #105 Proposed Agenda 26 September 2023 1. Welcome and Chair updates * Hopefully the survey will help us to get to a better spot. * Just a few weeks to finish up and to ICANN78. 2. Continue discussion of 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 [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? The different options for policy language can be found here: https://docs.google.com/document/d/1b0KIvhRyyO5QSEI4DB4vP78muKvqHneaXOZTcvI… Review Survey [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLSefyrdj…> Responses re: Draft Options o Remove the reference to fees entirely o Remove price ceiling (but allow for reasonable fee) o Retain price ceiling + Include language for apportionment of fees o Remove price ceiling + algorithm based on number of names transferred o Other? Survey Results: * Seems like the most popular option was #3 and overwhelming support for a price ceiling. * Some indicated reluctance for including pricing at all. * No agreement on a number for a price ceiling. * Responses on algorithm price ceiling were also quite split. * Changed language to “Registry MAY charge”. Discussion: * Question: How would premium priced names work if we were to consider the variable algo? Would the standard registration fee be counted for premiums? * Jim Galvin, RySG: With respect to the fee structure the Registries don’t have an opinion but if there is a fee reference would prefer the status quo, but depends on what Registrars decide to do. Preference for apportionment as in option #3. * Option #4 deals with that as well (number of names transferred). * From a non-registry point of view transferring 50k domains is not much more work than 1k names. * Be able to apportion the fee based on what is coming out of the registrar but RySG prefers keeping the current fee. * On BTAPPA we need to think about this more and understand what others (particularly Registrars) think. * We want the registries to discuss this but not wait too long. * Should be able to get a response in a small number of weeks. * Question: Do know how many registries are offering BTAPPA and how many domains are covered? Answer: All of the approved BTAPPAs are published, so we could get that information for the group if helpful. * I think they are listed in the RSEP page, but it may not expand out where providers list multiple TLDs within them. ACTION ITEM: Staff to provide the data on the number of registries that offer BTAPPA services. Q#2: If you preferred Option 2: "Registry MAY charge a reasonable fee to the gaining Registrar", or if the Group ultimately goes with this option, should there be language regarding a general price ceiling? In other words, should the language read: “Registry MAY charge a reasonable fee, but under no circumstances should the fee exceed [x]” * So even with the small with a high, with a registry who has everything automated, and actually, who can do the work, for $500 can still charge $10,000, because we decided that was reasonable. * The ceiling just becomes the standard fee. * We still need a justification for that fee. * We are only talking about a full portfolio move, not partial. * Question: Are we talking about eliminating the cap and substituting reasonable fee? Are we talking about eliminating it altogether? * Everybody's talking about removing the specific fee number and putting reasonable in there, not removing the fee itself. * Not sure why there is a need for a fee for 50K but not <50K. * There is a cost it was decided on 50K. It’s a balance. * WG has already agreed on “Registry MAY charge”. * Registry is getting a better business partner out of this. * INSERT 1255 Could have a situation that no one want to take the transfer. * Seemed like a price ceiling made sense to add to “reasonable”. Q#2a: If you voted YES to including a price ceiling, why do you believe a price ceiling should be included? [Select all that apply] * Support for transparency and concerns about high fees. * Jim Galvin, RySG: Discussion has gotten a lot of play considering how infrequently this is used. * Helpful to have more feedback on this from registries. Q#3: If the Working Group ultimately recommends a price ceiling, what would be an appropriate number? * Current language was favored. * Kind of spread apart. * Big issue is where original fee came from but bigger question is whether “reasonable” option #2 is an improvement? Q#4: Staff presented a new algorithm-based option for consideration during the last meeting on 19 September. Please familiarize yourself with Option 4<https://docs.google.com/document/d/1b0KIvhRyyO5QSEI4DB4vP78muKvqHneaXOZTcvI…> before responding to the next 5 questions (#4-8). As a reminder, one reason an algorithm-based approach was presented was to allow for flexibility over time, predictability, and the removal of specific dollar amounts from the policy. With that in mind, if an algorithm is applied based on the number of domain names, what would be an appropriate percentage? The current example language includes the following: “Registry Operators MAY charge a fee for making the changes only in transfers involving greater than [50,000] total domain names. For qualifying transfers, the affected Registry Operator’s fee must not exceed [0.5%] of the Registry’s wholesale price of the domain name for up to [200,000] domain names.” * This was based on a percent number. * Some discussion on factoring in premium names – expectation was if there was a mix the price would be wholesale. * Not a lot of agreement in the responses. * It is complex and there is no predictability. * Know wholesale prices will be increasing – the variable will change. * On transparency: wholesale prices are not public information. Couldn’t be managed by an independent third party. * As we’ve been talking through this there is less support. Q#9: Who should be responsible for paying the Registry fee (if any)? * The Gaining Registrar (current) – almost 90%. Summary: * Sounds like people are more comfortable with options #3 and #2 based on today’s discussion – if we can get down to two options to take to public comment that would be great. If we could get to one option and not go to public comment that is better, but don’t think we are there. WG members to provide their feedback/preferences on the 4 options: https://docs.google.com/document/d/1b0KIvhRyyO5QSEI4DB4vP78muKvqHneaXOZTcvI… 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? Should proposed BTAPPA updates apply to: 1. all registry operators (via an update to the Transfer Policy), OR 2. all registry operators who offer the BTAPPA (via recommended updates to the BTAPPA) Discussion: * With are new security measures those transfers become more difficult. * How many businesses would these changes affect? * If we don’t come up with a solution and stay with the status quo then we are taking two steps back re: competition among registrars. * With BTAPPA the reason this is crucial is because other work we are doing would dry up opportunity. 3. AOB

1 0

Post Call | Transfer Policy Review PDP WG | Tuesday, 26 September 2023
by Julie Bisland Sept. 26, 2023

Sept. 26, 2023

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

Sept. 26, 2023

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

**2 minutes** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 26 September 2023
by Julie Bisland Sept. 26, 2023

Sept. 26, 2023

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 26 September 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/gYjxDg * Time conversion link: https://tinyurl.com/4fkd5zwd [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/4fkd5zwd__;!!PtGJab4!9j6Varo…> 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 15 MINUTES** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 26 September 2023
by Julie Bisland Sept. 26, 2023

Sept. 26, 2023

**STARTING IN 15 MINUTES** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 26 September 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/gYjxDg * Time conversion link: https://tinyurl.com/4fkd5zwd [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/4fkd5zwd__;!!PtGJab4!9j6Varo…> 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

Re: [GNSO-TPR] Proposed Agenda + Assignment - Meeting #105 Tuesday, 26 September 2023
by Caitlin Tubergen Sept. 25, 2023

Sept. 25, 2023

Dear WG members, This is a friendly reminder to please complete the short survey<https://docs.google.com/forms/d/e/1FAIpQLSefyrdjNCnZST_SEe1heUu6oiU1Bx5_rC6…> on ICANN-approved transfers before tomorrow’s meeting. Thank you to those who have already completed the survey. Best regards, Christian, Julie, Berry, and Caitlin From: GNSO-TPR <gnso-tpr-bounces(a)icann.org> on behalf of Christian Wheeler <christian.wheeler(a)icann.org> Date: Thursday, September 21, 2023 at 5:15 PM To: "gnso-tpr(a)icann.org" <gnso-tpr(a)icann.org> Subject: [GNSO-TPR] Proposed Agenda + Assignment - Meeting #105 Tuesday, 26 September 2023 Dear TPR WG members, Please find below the proposed agenda for the next call on Tuesday, 26 September 2023 at 16:00 UTC. In preparation for next week’s call, Support Staff have created a Survey [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLSefyrdj…> with questions aimed at clarifying WG member positions for discussion and conclusion of the ICANN-Approved Transfers topic. Prior to completing this Survey, please review the options laid out in the Draft Options Document<https://urldefense.com/v3/__https:/docs.google.com/document/d/1b0KIvhRyyO5Q…> and read the survey in its entirety. Please complete this Survey [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLSefyrdj…> before our next call on Tuesday, 26 September. Thank you all for your attention to the homework. Kind regards, Christian, Caitlin, Berry, and Julie ---------- Transfer Policy Review - Meeting #105 Proposed Agenda 26 September 2023 1. Welcome and Chair updates 2. Continue discussion of 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 [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? · Review Survey [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLSefyrdj…> Responses re: Draft Options o Remove the reference to fees entirely o Remove price ceiling (but allow for reasonable fee) o Retain price ceiling + Include language for apportionment of fees o Remove price ceiling + algorithm based on number of names transferred o Other? 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? Should proposed BTAPPA updates apply to: 1. all registry operators (via an update to the Transfer Policy), OR 2. all registry operators who offer the BTAPPA (via recommended updates to the BTAPPA) 3. AOB

1 0

**REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 26 September 2023
by Julie Bisland Sept. 25, 2023

Sept. 25, 2023

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 26 September 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/gYjxDg * Time conversion link: https://tinyurl.com/4fkd5zwd [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/4fkd5zwd__;!!PtGJab4!9j6Varo…> 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