- GNSO-TPR - lists.icann.org

**AT THE TOP OF THE HOUR** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 10 January 2023
by Julie Bisland Jan. 10, 2023

Jan. 10, 2023

**AT THE TOP OF THE HOUR** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 10 January 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/HIw-DQ * For other places see: https://tinyurl.com/2b9x28mt [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2b9x28mt__;!!PtGJab4!51dhvwz…> 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. * 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 meeting #76 on Tuesday 10 January 2023 at 16:00 UTC
by Emily Barabas Jan. 10, 2023

Jan. 10, 2023

Dear Working Group members, Please find below the proposed agenda for the next meeting scheduled to take place on Tuesday 10 January at 16:00 UTC. Kind regards, Caitlin, Berry, Julie, and Emily ________________________________________________________________________________________________ Transfer Policy Review - Meeting #76 Proposed Agenda 10 January 2023 1. Roll Call & SOI updates 2. Welcome and Chair Updates 3. Proposed Work Plan Update & Project Change Request 4. Proposed Redline from Small Group on Exemption for Recommendation 16 and 17 5. Rationale for Recommendation 13 - Registry Enforcement of TTL 6. AOB

2 1

TPR-P1 // 31 December 2022 Project Package
by Berry Cobb Jan. 9, 2023

Jan. 9, 2023

Dear WG, Please find a link below to project package for the TPR-P1 PDP (31 December 2022). This package is a snap-shot at the close of each month 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 and project SitRep 2. Page 02 – Activity metrics 3. Page 03 – Meeting metrics, Roster, & Group attendance 4. Page 04 – Project Plan, Gantt chart 5. Page 05 – Workplan Key points: * The WG Status is Behind Schedule and Health is At-Risk due to substantive review of the public comments for Phase 1A that in turn impacts restarting deliberations on Phase 1B. 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, 10 January 2023
by Devan Reed Jan. 9, 2023

Jan. 9, 2023

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 10 January 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/HIw-DQ * For other places see: https://tinyurl.com/2b9x28mt [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2b9x28mt__;!!PtGJab4!51dhvwz…> 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. * 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

New GNSO Council Liaison to the GNSO Transfer Policy Review PDP WG
by Nathalie Peregrine Dec. 22, 2022

Dec. 22, 2022

Dear Roger and members of the GNSO Transfer Policy Review PDP WG, During the GNSO Council Strategic Planning Session held last week, Osvaldo Novoa, ISPCP, councilor kindly offered to replace Greg DiBiase, outgoing GNSO Council Liaison to the Transfer Policy Review PDP WG, in his role. The GNSO Council thanks Greg for taking on this role until today, and wishes Osvaldo all the best in this new effort. Osvaldo will be signed up to the TRP PDP WG mailing list shortly. Thank you, Kind regards, Nathalie

2 1

Input Due 16 January: Draft Revisions to Recommendations 10-22
by Emily Barabas Dec. 21, 2022

Dec. 21, 2022

Dear working group members, As discussed on yesterday’s call, staff had an action item to provide an updated redline revision of the Initial Report reflecting agreed updates to Recommendations 10-22 (see pages 26-39), as well as revisions resulting from the last round of input on the previous redline and strawman (see highlighted text on pages 17-19, 21, and 24). The document is attached. Please carefully review this document in coordination with the groups you represent. If you feel that there are items that need to be revised, please enter them here<https://docs.google.com/document/d/1Zoh8D2GuulpIDbyqwYsfRCSJkiGpa19k02eiEE-…>. For each item, please include: * Report version (the date listed in the header of the document) and applicable line numbers ( these are listed along the left margin of the document). * Name and group you represent: If multiple WG members represent a group, input should be in coordination with these other members. * Rationale: please provide a clear explanation for why you are proposing the revision. * Specific proposed revision: Provide the language you would like to see added/removed/edited. The deadline for submitting input is 16 January 2023. After the deadline, the working group will discuss the items submitted in the input document. Following review of those items, the text will be considered stable. Please do not hesitate to reach out with any questions about the review process. Kind regards, Caitlin, Julie, Berry, and Emily Emily Barabas Policy Development Support Senior Manager Internet Corporation for Assigned Names and Numbers (ICANN) Phone: +31 (0)6 84507976 www.icann.org<http://www.icann.org/>

1 0

Notes and action items - TPR WG Meeting #74 - 20 December 2022 at 16:00 UTC
by Julie Hedlund Dec. 20, 2022

Dec. 20, 2022

Dear TPR WG members, Please find below the notes and action items from today’s meeting. The next meeting will be on Tuesday, 10 January 2023 at 16:00 UTC. Best regards, Emily, Julie, Berry, and Caitlin ACTION ITEMS/HOMEWORK: 1. Jothan Frakes, Jim Galvin, Jody Kolker, and Rick Wilhelm have volunteered to compile a list of attack vectors and how the recommendations solve for them, or where they are out of scope. 2. Staff to circulate the redlines and give the WG until 16 January for review and comment. 3. Small Team on Exemption for Recommendation 16 and 17: to provide language and rationale for discussion at the meeting on 10 January. 4. Small Team on Rec 13 TTL: * Staff to incorporate the suggested text in the redline but without including hours at this point. * Small team will work on the rationale text for discussion at the meeting on 10 January 2023. Notes: Transfer Policy Review - Meeting #74 Proposed Agenda 20 December 2022 1. Roll Call & SOI updates 2. Welcome and Chair Updates * Question: When will the complete review of the Initial report phase 1a be distributed to the WG? * Answer: Have circulated redlines through 13, and remaining redlines should come out 21 December – but not final version. Staff will fill in rationales as a next step, including elements from small teams. Suggest 09 January for comments on the remaining redlines. * Seems like a quick turnaround; would prefer a week later. * 16 Jan is a holiday in the US. * The new revisions are not very extensive. ACTION ITEM: Staff to circulate the redlines and give the WG until 16 January for review and comment. 3. Small Group on Exemption for Recommendation 16 and 17 (proposal<https://mm.icann.org/pipermail/gnso-tpr/2022-December/000714.html>) “Our proposal is to add the option for registrars to opt out of the lock for “Established Customers”. This should reduce the chance of domains transferring to multiple registrars as part of hijacking, while allowing existing registrants to better manage their domains. A draft definition for “Established Customer” is: ‘An established customer is a registrant who has previously received continuing services from a registrar for a period of more than 30 days and has an established relationship with the registrar. This typically refers to a customer who has a history of regular interactions with the registrar and has demonstrated a willingness to continue receiving services from the registrar in the future.’ See: https://mm.icann.org/pipermail/gnso-tpr/2022-December/000714.html Discussion: * Could change to “registrar/reseller” or “reseller” in parentheses, but the obligations of the RAA apply to reseller. * Can this definition of “established” customer also be used for preventing a transfer lock after material change of Registrant? Perhaps. * ALAC would like all processes to be equal, which would change with this policy. * There are already policies that allow opt outs. * ALAC would like to have time to present to the group. * Consider/think ahead to locks on COR – post transfer restriction leveraged for possible changes in COR. * When thinking about Rec 19 and evidence of fraud – would we similarly require evidence of this “Established Customer”? How could Compliance know that? * What is the next step for this proposal? Can this be incorporated into the Recommendations 16 and 17 – also timing. * Helpful to have specific language and a rationale from the small team. Particularly the impact on the consistency across the industry and security elements. * Challenge for Compliance to gather evidence on the “Established Customer”. ACTION ITEM: Small Team on Exemption for Recommendation 16 and 17 (proposal<https://mm.icann.org/pipermail/gnso-tpr/2022-December/000714.html>): to provide language and rationale for discussion at the meeting on 10 January. 4. Small Group on TTL Enforcement (proposal at the bottom of Recommendation 13 Working Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1Wq4dHcIFR5Xo…>) Strawman Revision: Tentative Draft Language proposed by the Small Team – agreed by the RySG and under review by the RrSG: 13.1 A standard Time to Live (TTL) for tThe TAC MUST be valid for 14 calendar days from the time it is set at the Registry, enforced by the Registryies. 13.2 The Registrar of Record MAY set the TAC to NULL: After a period of less than 14 days prior to the end of the 14th calendar day by agreement of the Registrar of Record and the RNH. Discussion: * Removed “maximum” and settled on “14 calendar days” although registrars may suggest also including hours, but others objected. We don’t use hours elsewhere. No objections from the registrars on the change, except the suggestion to include hours. * Probably shouldn’t say “calendar”, just “days”. Trying to move away from calendars. * Think hours could fit here – in the scope of the rationale. * The statement at the end of 13.2 was not intended to unreasonably limit the ability of the Sponsoring Registrar to null the TAC. Might think about rather than specifying reasons in 13.2, might reference other sections in the policy where we specify reasons why the registrar may reject the transfer. * To remove the term “calendar” we have agreement from the RySG and the RrSG. But RySG would like to take the suggestion to go to hours under advisement. Would prefer not to include hours as that raises the compliance obligation. * If we move to “days” from “calendar days” does that create opportunity for confusion? * WG previously discussed including both “calendar days” and “hours”. * “Calendar days” is more precise than “days”. Don’t have to go to 336 hours. * This is the only deadline where the registries have obligations and with a level of specificity great than obligations for registrars. * Rec 12 specifies hours so adding hours to Rec 13 would make it consistent. * Where does the small team stand on the language and rationale – particular comments around registry obligations? * Would be helpful to reference in 13.2 another section on reasons why a registrar could reject a transfer/registrar of record refuses to send a TAC. * Think we are covered elsewhere for the above references. ACTION ITEMS: 1. Staff to incorporate the suggested text in the redline but without including hours at this point. 2. Small team will work on the rationale text for discussion at the meeting on 10 January 2023. 5. AOB: No meeting 22 December and last week in December; first meeting in January is Tuesday, 10 January.

1 0

Post Call | Transfer Policy Review PDP WG | Tuesday, 20 December 2022
by Julie Bisland Dec. 20, 2022

Dec. 20, 2022

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Tuesday, 20 December 2022 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/_wnVD> (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, chat) * Transcript 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, 10 January 2023
by Julie Bisland Dec. 20, 2022

Dec. 20, 2022

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 10 January 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/HIw-DQ * For other places see: https://tinyurl.com/2b9x28mt 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. * 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, 20 December 2022
by Julie Bisland Dec. 20, 2022

Dec. 20, 2022

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 20 December 2022 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/_wnVD * For other places see: https://tinyurl.com/3zvnjw28 <https://urldefense.com/v3/__https:/tinyurl.com/3zvnjw28__;!!PtGJab4!6w9krA_…> 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. * 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 THREE 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, Devan

1 0