December 2022 - GNSO-TPR - lists.icann.org

Meeting Invitation | Transfer Policy Review PDP WG call | Thursday, 08 December 2022
by Devan Reed Dec. 6, 2022

Dec. 6, 2022

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Thursday, 08 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/b4IFDQ * For other places see: https://tinyurl.com/3htvzzad 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

15 MINUTES REMINDER | Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 06 December 2022
by Devan Reed Dec. 6, 2022

Dec. 6, 2022

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 06 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/9wnVD * For other places see: https://tinyurl.com/2ysbxuu7<https://urldefense.com/v3/__https:/tinyurl.com/2ysbxuu7__;!!PtGJab4!6Zuy0-u…> 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, Julie

1 0

Process changes and outstanding questions following public comment review
by Emily Barabas Dec. 6, 2022

Dec. 6, 2022

Dear WG members, On our last call, staff took an action item to review the latest redline version of the recommendations alongside the public comment review documents to identify any changes to the overall transfer process that would result from agreed upon updates to the recommendations. Staff was also asked to identify outstanding questions and open items that the group is working on. Here is the summary: Process updates * Rec 2 – Addition of Losing FOA * Rec xx – Registry Operator provides Gaining Rr’s IANA ID to Losing Rr in the notification of pending transfer request, to be included in Losing FOA and Notification of Transfer Completion Open Items * Rec 6 – RrSG reps may suggest further clarifications regarding the designated representative * Rec 11 – RySG reps may suggest further clarifications regarding when the TAC is considered “used” and is reset to null, relationship to TTL, and/or interaction with Ry Lock * Rec 13 – Small team is working on a proposal regarding TTL enforcement * Rec 16 & 17 – Small team is working on a proposal for exceptions to post-create and post-transfer restrictions on transfer * General – Small group is working on developing a list of threat vectors that the proposed security model is and is not intended to address We’ll go through these items on today’s call and welcome input from the group about whether there are additional updates we missed that may have a substantive impact on the transfer process. Kind regards, Caitlin, Julie, Berry, 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

TPR-P1 // 30 November 2022 Project Package
by Berry Cobb Dec. 5, 2022

Dec. 5, 2022

Dear WG, Please find a link below to project package for the TPR-P1 PDP (30 November 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-05 – Activity metrics, group attendance for plenary meetings, and roster 3. Page 06 – Project Plan, Gantt chart 4. Page 07 – Workplan Key points: * The WG is behind schedule with review of the public comments for Phase 1A that in turn impacts restarting deliberations on Phase 1B. * Note that some tasks have now been downgraded to “Target will be Missed”, but this has not affected the overall Status/Health of the project…..yet. Please let us 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, 06 December 2022
by Devan Reed Dec. 5, 2022

Dec. 5, 2022

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 06 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/9wnVD * For other places see: https://tinyurl.com/2ysbxuu7<https://urldefense.com/v3/__https:/tinyurl.com/2ysbxuu7__;!!PtGJab4!6Zuy0-u…> 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, Julie

1 0

Proposed agenda for meeting #71 on Tuesday 6 December 2022 at 16:00 UTC
by Emily Barabas Dec. 5, 2022

Dec. 5, 2022

Dear Working Group members, Please find below the proposed agenda for the next meeting scheduled to take place on Tuesday 6 December 2022 at 16:00 UTC. Prior to the call, please review the documents linked in the agenda below. Kind regards, Emily, Julie, Berry, and Caitlin ________________________________________________________________________________________________ Transfer Policy Review - Meeting #71 Proposed Agenda 6 December 2022 1. Roll Call & SOI updates 2. Welcome and Chair Updates 3. Revised Reasons that a Registrar of Record MAY Deny a Transfer – Recommendation 19 (Public Comment Review Tool<https://community.icann.org/display/TPRPDP/Phase+1A+-+Public+Comment+Review…> and Public Comment Working Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1trkihdcP80GA…>) 4. New Reasons that a Registrar a Record MUST Deny a Transfer – Recommendation 20 (Public Comment Review Tool<https://community.icann.org/display/TPRPDP/Phase+1A+-+Public+Comment+Review…> and Public Comment Working Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1VkFtTdlrwDmz…>) 5. Revised Reasons that a Registrar of Record MUST Deny a Transfer – Recommendation 21 (Public Comment Review Tool<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…> and Public Comment Working Document<https://docs.google.com/document/d/1SlBZKawRXBNmk4zHy9E_4wePW-q0z24sbwxFK_N…>) 6. Revised Reasons that a Registrar of Record MUST NOT Deny a Transfer – Recommendation 22 (Public Comment Review Tool<https://community.icann.org/download/attachments/201949311/gnso-TPR-P1A-pcr…> and Public Comment Working Document<https://docs.google.com/document/d/1h8w7bjDYUHnfg8zJGZskF21KcumgE12KvZZDeBt…>) 7. AOB

1 0

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 06 December 2022
by Julie Bisland Dec. 1, 2022

Dec. 1, 2022

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 06 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/9wnVD * For other places see: https://tinyurl.com/2ysbxuu7 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, Julie

1 0

Post Call | Transfer Policy Review PDP WG | Thursday, 01 December 2022
by Julie Bisland Dec. 1, 2022

Dec. 1, 2022

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Thursday, 01 December 2022 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/bYIFDQ> (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

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

Dec. 1, 2022

Dear TPR WG members, Please find below the notes and action items from today’s meeting. The next meeting will be on Tuesday, 06 December at 16:00 UTC. Best regards, Emily, Julie, Berry, and Caitlin ACTION ITEMS/HOMEWORK: Ongoing Action Items: 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. Action Items from 01 December: 1. Recommendation 13: Question to the Community -- Small Team on TTL Enforcement: Send the proposal to the list with rationale. 2. Transfer Process: Staff to provide an updated flow chart of the entire transfer process to reflect the recent agreement from the WG, when all aspects of the process has been agreed to by the WG. 3. Recommendations 2-9: Staff to release revised redline based on WG agreement. Notes: Transfer Policy Review - Meeting #70 Proposed Agenda 01 December 2022 1. Roll Call & SOI updates 2. Welcome and Chair Updates * Small Team on TTL: * AOB from Sarah Wyld: Request a recap of the entire transfer process to view the flow – staff to create a flow chart? Have lost track of what messages happen and when, so good to have a wholistic review. Take an action item to staff. * Small Team on Recommendation 13 on the TTL for the TAC and where the enforcement takes place: Specifically, “13.1: A standard Time to Live (TTL) for the TAC MUST be 14 calendar days from the time it is set at the Registry, enforced by the Registries.” Question to the community: Who is best positioned to manage the standard 14-day TTL – the Registry or the Registrar, and why? Are there specific implications if the TTL is managed by the Losing Registrar? 13.2: The Registrar of Record MAY set the TAC to null after a period of less than 14 days by agreement by the Registrar of Record and the RNH. * Compromise is to do a one-word edit to 13.1 to replace “Registries” with “Registrars” and add “A maximum TTL for the TAC MUST be 21 calendar days from the time it is set at the Registry, enforced by the Registry.” * Discussion: * Think this is making it a lot more complicated to have two solutions to one problem. Could be a lot of places for ambiguity. * This is a compromise because of how long it would take for some registrars to provide the take to RNHs. Downside is that we are changing the TTL to 21 days. * Registrars do feel strongly that this should be enforced by the registries. * Concern that the Losing Registrar could be in breach. * Additionally, the 'cooling period' of TAC existing but not necessarily usable (notice to RnH) that is allegedly replacing the RnH's agency to halt an unintended transfer based upon their notice that the current NACK provides - is also a factor at the front of the 14 days. * The 5-day period starts when it's set and issued, so if there's a delay from request to set/issue that delay is not coming out of the 14-day TTL period. * The 5-day period for the request of the TAC starts when the TAC is requested, not when it's set. * This is not straightforward – there are a lot of pieces involved. ACTION ITEM: Small Team on TTL Enforcement/Recommendation 13: Send the proposal to the list with rationale. ACTION ITEM: Staff to provide an updated flow chart of the entire transfer process to reflect the recent agreement from the WG, when all aspects of the process has been agreed to by the WG. 3. Review of Feedback on Recommendation 2 Strawman Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1e8iG6FmRD0M5…> (feedback document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1d7KwQH6poIxr…>) * Jim Galvin, RySG: IANA ID to the losing registrar. Discussion text had some language, but that was redlined out. Pull detail into the recommendation add: “Preliminary Recommendation xx: The Registry Operator MUST provide the Gaining Registrar’s IANA ID in the notification of a pending transfer request to the Losing Registrar, which will enable the Losing Registrar to provide this information in the [Losing FOA and] Notification of Transfer Completion.” * From Sarah Wyld (see Recommendation 2 Strawman at the link above): * What the process would look like: * 1. RNH unlocks domain and requests TAC from the Registrar of Record (Losing Rr) * 2. Losing Rr sends a TAC ACK email to the RNH saying “Someone requested a TAC; if this wasn’t you, click <NACKlink>. If it was you, you can either do nothing and we’ll provide you the TAC in 5 days or you can click <ACKlink> and we’ll give you the TAC right now” * a. If RNH clicks <NACKlink>, the TAC is never set at the Ry, and other things might happen (e.g. account password reset, etc) * b. If RNH clicks <ACKlink>, the Losing Rr provisions the TAC at the Ry and issues it to the RNH (Rec 3 Notification of TAC Issuance) * c. If no response, Losing Rr waits 5 days and then provisions the TAC at the Ry and issues it to the RNH (Rec 3 Notification of TAC Issuance) * 3. When the RNH receives the TAC, they provide it to the gaining Rr and the transfer is completed (Rec 4 “Notification of Transfer Completion” etc) * Doesn’t solve the problem of the TAC going out in the wild once it’s provisioned. Strawman added the IANA ID, but this doesn’t provide that. Strawman solves both issues. * See other comments, including from ALAC and BC, in the Recommendation 2 strawman document. * TechOps suggests as few changes as possible from the original design. * Might need to be a time for adjustment via the IRT. * There is a re-education aspect as well. * Note that if the WG doesn’t come to agreement, the current policy (Losing FOA) stands. * The agency piece of this is to give the registrant more power, but the difference is the timing – we don’t agree on the timing. * People need to be as concise as possible with their proposals. * Seems that there is general agreement from the WG to go with the strawman proposal. Not full consensus – most agree and some do not. 4. Review of Feedback on Revisions to Recommendations 3-9 (see pages 18-24 attached) (feedback document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1d7KwQH6poIxr…>) * Recommendation 8: Comments from Sarah Wyld – editorial issue. WG accepts the changes – will be incorporated into the next redline. * Comments from RySG: Incorporate into the next redline. ACTION ITEM: Recommendations 2-9: Staff to release revised redline based on WG agreement. 5. Revised Reasons that a Registrar of Record MAY Deny a Transfer – Recommendation 19 (Public Comment Review Tool<https://community.icann.org/display/TPRPDP/Phase+1A+-+Public+Comment+Review…> and Public Comment Working Document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1trkihdcP80GA…>) c) Proposed edits: I.A.3.7.1 Potential next step: Consider whether “violation of registrar’s anti-abuse policies, or evidence of fraud” in the MAY category is an appropriate compromise. In brief, the alternatives presented in the comments: In the MAY category: * Evidence of fraud (status quo) * Violation of the Registrar's domain use or anti-abuse policies or evidence of fraud. OR Evidence of fraud, or violation of the Registrar’s domain use or anti-abuse policies. * Evidence of fraud, illegal activity, phishing, distribution of malware, or to comply with the law. In the MUST category: * The Registrar has knowledge of credible evidence of the domain currently being used for malware, phishing, pharming, or command & control botnets. Additional proposal: Move “Evidence of fraud” to the MUST category and include “violation of the Registrar’s domain use or anti-abuse policies” in the MAY category. WG discussion and agreement: * WG members generally agreed that this item should remain in the MAY category for the reasons summarized above. * Additional proposal from Sarah Wyld (29 Nov): “Evidence of fraud or the domain presents an active or continuing threat.” * The WG recalled that upcoming discussions on potential contract amendments (https://www.icann.org/en/system/files/correspondence/heineman-demetriou-to-…) may interact with discussion of potential edits to I.A.3.7.1. Discussion: * Lots of discussion on the last call. * Seems like there isn’t agreement of adding something beyond evidence of fraud. * What about adding “security” into Sarah’s proposal? Like - Evidence of fraud or the domain presents an active or continuing security threat? * What is a “security threat”? Do like “anti-abuse policies”. * It’s in our contracts that we have to obey the law: RAA 3.7.2 "Registrar shall abide by applicable laws and governmental regulations.” * We’ll never get agreement on exact text but if we can make it better we should try. * Can’t prevent registrars from complying with the law. Could see you blocking because of OFAC, but we also can’t try to interpret local laws. * Registrars will comply with local law regardless of policy. * Think everyone thinks that evidence of fraud is not enough, but don’t agree how defining something beyond that. If we can’t get to agreement it will stay evidence of fraud. * Still seems like keeping it in the “MAY” category makes sense.

1 0

**AT THE TOP OF THE HOUR** Meeting Invitation | Transfer Policy Review PDP WG call | Thursday, 01 December 2022
by Julie Bisland Dec. 1, 2022

Dec. 1, 2022

**AT THE TOP OF THE HOUR** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Thursday, 01 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/bYIFDQ * For other places see: https://tinyurl.com/2p9fx9c4 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2p9fx9c4__;!!PtGJab4!8nzE2yy…> 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, Julie

1 0