February 2024 - GNSO-TPR - lists.icann.org

ICANN79 Presentation Slides
by Christian Wheeler Feb. 28, 2024

Feb. 28, 2024

Dear TPR WG members, Please find attached the slides we will use for our ICANN79 sessions this Saturday (2 March, 1:15pm and 3:00pm AST). We recommend familiarizing yourselves with these slides ahead of our two sessions. Our focus will be on slides 1-28. Thank you to our volunteers who will introduce slides 7-17. In the meantime, WG members please assist our volunteers by adding more rationale to the CORD Preliminary Recommendations + Rationale<https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr…> Google Doc. Thank you all again and we look forward to seeing you virtually and in person in San Juan. Safe travels! Kind regards, Caitlin, Berry, Julie, Feodora, and Christian

1 0

FW: Notes and action items: TPR WG on 27 February 1600 UTC
by Feodora Hamza Feb. 28, 2024

Feb. 28, 2024

Dear TPR WG members, Please find below the brief notes and action items from yesterday’s meeting. The next meetings will be Saturday, 02 March at ICANN79: Session 1 at 13:15-14:30 and Session 2 at 1500-1600 San Juan (UTC-4). Kind regards, Christian, Caitlin, Berry, Julie and Feodora ============================================================================================ 2024-02-27 Transfer Policy Review PDP WG Call<https://community.icann.org/display/TPRPDP/2024-02-27+Transfer+Policy+Revie…> Main discussion and action items 1. Welcome and Chair Updates * Link to the slides: https://docs.google.com/presentation/d/1JIYvzbYHJxK5srf2qbdKr_qslCl-TOcv9iQ… * Members are encouraged to take a look at the rationale document (https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr…) and add input where possible 2. ICANN79 TPR sessions Agenda * Two sessions during ICANN79 Saturday 2nd of March (link) * Links to wiki page agenda of ICANN79 sessions: * Session 1: Focus on Recommendations * https://community.icann.org/display/TPRPDP/2024-03-02+ICANN79+Transfer+Poli… * Session 2: Focus on Established Relationships: https://community.icann.org/display/TPRPDP/2024-03-02+ICANN79+Transfer+Poli… * 4 Members are encouraged to serve as volunteers to present during ICANN79 to present/read out recommendations * Volunteers: Rec 1: Prudence Rec 2: Theo Rec 3: Owen Rec 4: Sarah * Will rationale document be presented? Focus will be on recommendations document as rationale document is still work in progress. 1. CORD Prelim Recs & Rationale (& volunteers) * Link to doc: https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr…. * Rec 1.3. change included revised language to clarify if P/P is involved. * Rec 2 the order has been updated based on previous call. Clarifies what to keep Section II from the transfer policy. * Current Section II needs it own policy. * Recs should be taken into consideration as a whole and not in isolation. * Rec 2.1 includes changes that clarifies that the “designated agent” is not used properly and new wording has been added. “Designated agent”should be eliminated from “future standalone Change of Registrant Data Policy”. * “Designated Agent” removed from transfer policy, but it could be used elsewhere if need be for other processes. * Rec 2.2 Eliminate Section II b “Availability of Change of Registrant” from future standalone policy. It not necessary to include here. * Rec 2.4 Eliminiate 60-day lock from future policy. * Perception could arise that this Rec 2.4 might take away security measured. Hence, more rationale could be needed in the rational document? * Members referred also to other options for registrants to increase security for their domains. * Rec 3 group is adding that Registrars have to provide instructions how registrants can take action if the change was invalid. * Rec 3.4 wording changed from MUST to MAY send CORD notification to new Email address. * Rec 4 Registrars must provide an opt out for Change of Registrant Data notifications. * Rec 4.1. Registrars MUST enable Change of Registrant Data notifications by default when a domain name is initially registered. Registrars MAY disable Change of Registrant Data notifications if the Registered Name Holder elects to opt out of these notifications. * Discussion on is this a security feature and is this hapering security or enhancing it? Opt out as part of data protection option? * Email verification process is in place and could pose an overlap with Rec 4.1? Verification Email only goes to updated Email not existing Email. 2. Recap “Established Relationship” topic * Link to slides: https://docs.google.com/presentation/d/1JIYvzbYHJxK5srf2qbdKr_qslCl-TOcv9iQ… * TPR Swimlane Overview included in the slides. Two yellow boxes are included for the established relationship procedure: * Initiation * Transfer * Refresher on NACK-ing recommendations (Prelim Rec 16 and Prelim Rec 17). How does this affect registration data? * Small group redlined Rec 17 where registrars MUST apply 30-day post change lock and included that they may unlock earlier if an established relationship exists. * Rationale will be further explained and presented during ICANN79 and group should be prepared to speak for or against it during ICANN79. * Does the group believe that an “Established Relationship” role/procedure should be created? If so, what exemptions should customers be provided with? How do these exemptions impact TPR? 1. AOB * No comment

1 0

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 19 March 2024
by Julie Bisland Feb. 27, 2024

Feb. 27, 2024

NOTE: The next meetings take place during ICANN79; see session 1<https://icann79.sched.com/event/1a15v/gnso-transfer-policy-review-pdp-worki…> and session 2<https://icann79.sched.com/event/1a15y/gnso-transfer-policy-review-pdp-worki…> schedule pages (Zoom participation links will be published 24 hours before the session starts.) Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 19 March 2024 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…>. 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/vwDFE * Time conversion link: https://tinyurl.com/axdbpsdb 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 Policy Team Supporting the GNSO

1 0

Post Call | Transfer Policy Review PDP WG | Tuesday, 27 February 2024
by Julie Bisland Feb. 27, 2024

Feb. 27, 2024

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Tuesday, 27 February 2024 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/uADFE> (attendance included) and the GNSO Master calendar [gnso.icann.org]<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

**3 MINUTES** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 27 February 2024
by Julie Bisland Feb. 27, 2024

Feb. 27, 2024

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 27 February 2024 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/uADFE * Time conversion link: https://tinyurl.com/yvc2jvx2 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/yvc2jvx2__;!!PtGJab4!_u4wkHO…> 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, Terri Policy Team Supporting the GNSO

1 0

GNSO_TPR // 25 February 2024 Project Package
by Berry Cobb Feb. 27, 2024

Feb. 27, 2024

Dear WG, Please find a link below to project package for the GNSO_TPR PDP (25 FEB 2024). 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,4 – Project Plan, Gantt chart 4. Page 05 – Workplan Key points: * Aspirations of releasing the Initial Report for public comment May 2024. 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

**15-MINUTE REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 27 February 2024
by Julie Bisland Feb. 27, 2024

Feb. 27, 2024

**15-MINUTE REMINDER** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 27 February 2024 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/uADFE * Time conversion link: https://tinyurl.com/yvc2jvx2 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/yvc2jvx2__;!!PtGJab4!_u4wkHO…> 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, Terri Policy Team Supporting the GNSO

1 0

Action Item: Prelim Recs + Rationale Document
by Christian Wheeler Feb. 26, 2024

Feb. 26, 2024

Dear TPR WG members, In lieu of the WG call on 20 February (which has been cancelled), all members are tasked to complete the WG’s standing Action Item: to submit Rationale for the WG’s preliminary recommendations. Support staff have updated the existing Rationale Document<https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr…>, adding the WG’s preliminary CORD recommendations (with red text indicating updated language following the 13 Feb call). Please use this document<https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr…> to redline/refine the WG’s preliminary recommendations as necessary, and provide rationale for why the WG is proposing these recommendations. NOTE: It is these materials that will be used to set the stage for the WG’s ICANN79 sessions, so it is important we have this well-grounded. Similar to the TPR session at ICANN77 in DC, the leadership team will be seeking volunteers to speak to blocks of the preliminary recommendations. Please feel free to note your interest now as a side-bar comment. All WG members are expected to contribute substantive rationale to this document<https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr…> by EOD, 27 February. NOTE: If input is not received by the deadline, as a last resort, staff will extract attributed statements from prior transcripts and meeting notes. Thank you all, and we look forward to reviewing your inputs during our next call, scheduled for 27 February at 16:00 UTC. If you have any questions, please do not hesitate to reach out on the list or leave a comment in the document. Best regards, Christian, Caitlin, Berry, and Julie

5 7

**REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 27 February 2024
by Julie Bisland Feb. 26, 2024

Feb. 26, 2024

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 27 February 2024 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/uADFE * Time conversion link: https://tinyurl.com/yvc2jvx2 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, Terri Policy Team Supporting the GNSO

1 0

Proposed Agenda - Meeting #121 Tuesday, 27 February 2024 at 1600 UTC
by Christian Wheeler Feb. 22, 2024

Feb. 22, 2024

Dear TPR WG members, Please find below the proposed agenda for our next call, taking place on Tuesday, 27 February 2024 at 16:00 UTC. As a reminder, your current Action Item is to provide Rationale input to the CORD Preliminary Recommendations & Rationale Google Doc<https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr…>, due by 27 February. Thank you and we look forward to reviewing your inputs and seeing you all virtually. Kind regards, Caitlin, Berry, Julie, and Christian ---------- Transfer Policy Review - Meeting #121 Proposed Agenda 27 February 2024 Proposed Agenda: 1. Welcome and Chair Updates 2. ICANN79 TPR sessions Agenda 3. CORD Prelim Recs & Rationale (& volunteers) 4. Recap “Established Relationship” topic 5. AOB

1 0

ICANN79 Policy Outlook Report / ICANN79 GNSO Policy Briefing
by Julie Bisland Feb. 21, 2024

Feb. 21, 2024

Dear All, On behalf of the GNSO Team, I am happy to report that the GNSO Policy Briefing for ICANN79 is now available for download at http://go.icann.org/gnsobriefing [go.icann.org]<https://urldefense.com/v3/__http:/go.icann.org/gnsobriefing__;!!PtGJab4!-Yi…>. In addition, the ICANN79 Policy Outlook Report is available: https://go.icann.org/outlook79 [go.icann.org]<https://urldefense.com/v3/__https:/go.icann.org/outlook79__;!!PtGJab4!-Yii5…>. Happy reading! Best Regards, Julie -- 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…> [signature_2510144026]

1 0

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 27 February 2024
by Terri Agnew Feb. 15, 2024

Feb. 15, 2024

**Reminder, 20 February has been cancelled, please remove it from your calendars. See information below for next scheduled meeting. Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 27 February 2024 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/tQDFE * Time conversion link: https://tinyurl.com/dperyxxz [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/dperyxxz__;!!PtGJab4!4RC8O5p…> 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, Terri Policy Team Supporting the GNSO

1 0

Canceled: Transfer Policy Review PDP WG
by ICANN Policy Calendar Feb. 15, 2024

Feb. 15, 2024

Meeting: Transfer Policy Review PDP WG Date/time: Occurs every Tuesday at 16:00 UTC for 90 minutes, 16 January – 26 March 2024 (note: 05 March and 12 March are cancelled and will take place during ICANN79 scheduled dates/times) Alternate replacement confirmations – Members who are unable to attend, please complete the google form<https://docs.google.com/forms/d/e/1FAIpQLScXP3-H595xH4EFgaR3ydOr-1o9BLAVGUI…> to communicate who the alternate is replacing you. Join the Zoom Webinar: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 Passcode: @TP/^*4wg# 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> * 2024 Wiki page: https://community.icann.org/x/S4BFE ONLY for Members & Alternates: * Please join via the above Zoom Webinar link and staff will promote you to Panelist * Alternate assignments will be posted to the Alternate Log-Transfer Policy Review PDP wiki page<https://community.icann.org/x/V4aUCQ>. * Chat: Please select Everyone when posting to the chat in order for everyone to see and to be captured afterwards. * Alternates (not replacing a member): Please rename your line in Zoom by adding THREE Zs “zzz” before your name, and in parentheses, (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. For Audio only: One tap mobile: US: +19294362866,,95363727469#,,,,*7490739013# or +13017158592,,95363727469#,,,,*7490739013# Webinar ID: 953 6372 7469 Passcode: 7490739013 International numbers available: https://icann.zoom.us/u/acdLFXPLp6

1 0

Cancelled: 20 Feb TPR WG Call
by Christian Wheeler Feb. 15, 2024

Feb. 15, 2024

Dear TPR WG members, Considering the concurrent Contractual Compliance session during ICANN79 Prep Week, we have met with WG leadership today and determined it will be best to cancel the next TPR WG call (originally scheduled for 20 Feb). We will follow up tomorrow with homework for the TPR WG to complete by its next meeting, scheduled for 27 February, 16:00 UTC. Kind regards, Christian, Caitlin, Berry, and Julie

1 0

Notes and action items: TPR WG on 13 February at 1600 UTC
by Julie Hedlund Feb. 13, 2024

Feb. 13, 2024

Dear TPR WG members, Please find below the brief notes and action items from today’s meeting. The next meeting will be Tuesday, 20 February 2024 at 1600 UTC. Kind regards, Christian, Caitlin, Berry and Julie ACTION ITEMS/HOMEWORK: WG to complete the COR Reduction Rationale document at: https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1DpDO2BYTl6TA…> Transfer Policy Review - Meeting #118 Proposed Agenda 13 February 2024 1. Welcome and Chair Updates * Three sessions with this one before ICANN79. * Two sessions scheduled for ICANN79 – COR and impacts. See TPR agendas at: agenda:(https://community.icann.org/display/TPRPDP/2024-03-02+ICANN79+Trans…. It is currently a rolling agenda for both sessions, part 1 being discussion of the draft COR recommendations, and part 2 being discussion of the Group 1(a) 30-day transfer restriction (and whether the existing recs need to be updated in light of the CORD recs). * ALAC will be meeting at ICANN79 to discuss COR on Saturday, 02 March; open to the public. Follows the TPR sessions. * Still no rationale in the document at: COR Reduction Rationale document at: https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1DpDO2BYTl6TA…> * WG Self-Assessment Survey is still open – 9 responses so far. Closes 21 February. 2. CORD Availability discussion – See attached slides, starting at slide 3. Discussion: * Numbers 2 and 3 can go away completely. No longer relevant. * 2.3 is probably duplicate policy language. * Don’t know what harm there is in allowing someone to update their data – would be less harmful to allow (2.1). * If there is a domain name for which you could update the registrant data would think there would be a contract between the registrar and registrant. * Unless there is disagreement it seems we could simplify the policy by eliminating 2 and 3. * Does 2.2 still make sense if authorization is not required? We now have a notification-only policy so you don’t need it. 3. Preliminary Recommendations – See attached slides. Discussion Prelim Recs 1.1 and 1.2, slide 5: * This is impossible to code for – hard to define a typo or not. * Original language assumed some manual processes. * Think about how this would work in the real world. No notion of typo. * Nothing to prevent a registrar from treating any change as material. Discussion Prelim Rec 1.3, slide 6: * Make sure we are talking about the underlying customer data. * Question: Why do we care about this and how does it tie into change of registrant data? Answer: To clarify in response to charter questions. * If a registrant applies a privacy proxy service, that’s not a material change. * But there is underlying customer data and if that changes there is a notification. Changing the name would trigger notification because it’s out there. * We're getting into a discussion that no longer has anything to do with a change of registrant data in combination with the privacy proxy service. * We had a couple of charter questions on privacy proxy that needed to be addressed. * Do we eliminate it? * It may have been important when we wrote the charter but we can say it’s no longer applicable. Discussion Prelim Rec 2, slide 7: * It’s redundant language. Discussion Prelim Rec 3, slide 8: * Question: Should we change “registrant data” to “registration data”? * Why would we change anything? This section is no longer relevant. There is no confirmation process anymore. There's only notification. Just remove it. Discussion Prelim Rec 4.1, slide 9: * No comments. Discussion Prelim Rec 4.2, slide 10: * Question: Send to the previous or only the new RNH? Answer: We discussed getting rid of the prior and sticking with just RNH. I don’t think we decided that you couldn’t send to both of them if you chose to. * Since this is framed as a change of data the only time it would make sense to notify both is if email changes, which is addressed in 4.4. Discussion Prelim Rec 4.3, slide 11: * No comments. Discussion Prelim Rec 4.4, slide 12: * Question: What are we trying to achieve? Answer: When you are changing the email address the registrar is required by contract to verify that email address -- the new one. So there is work that goes into that. So it's not like it's just changed. Getting a positive notification that email is updated. * Don’t see any good reasons from a policy perspective. * From a registrant perspective see the benefit but if already done by WHOIS verification then that is the complete solution. * Could think about turning the MUST into a MAY? * Notifications might typically go to the account control panel. Discussion Prelim Rec 4.5, slide 13: * No comments. Discussion Prelim Rec 4.6, slide 14: * No comments. Discussion Prelim Rec 4.7, slide 15: * Wonder if we need to be that specific. Discussion Prelim Rec 5.1, slide 16: * Concerns with this: when it comes to a new RNH that is out of the registrar’s control if there is a new agreement. * Question: Maybe we could incorporate more about the decision to be informed and when can an opt out be reversed. Answer: See slide 17. * Question: When a domain name changes hands is there anything that needs to be done about the opt out continuing? Answer: Talked about whether to opt out every time you make a change. * It can be a permanent flag not an every time flag. * Change MUST to MAY? We kept MUST for consistency across registrars. Discussion Prelim Rec 5.2, slide 17: * Question: If a registrant makes a CORD and prior to that opts out there still would be a verification email – any concern about fraud in opting out? * Continue discussion at the next meeting. 4. AOB: None.

1 0

Post Call | Transfer Policy Review PDP WG | Tuesday, 13 February 2024
by Julie Bisland Feb. 13, 2024

Feb. 13, 2024

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Tuesday, 13 February 2024 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/swDFE> (attendance included) and the GNSO Master calendar [gnso.icann.org]<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, 20 February 2024
by Julie Bisland Feb. 13, 2024

Feb. 13, 2024

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

**15-MINUTE REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 13 February 2024
by Julie Bisland Feb. 13, 2024

Feb. 13, 2024

**15-MINUTE REMINDER** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 13 February 2024 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/swDFE * Time conversion link: https://tinyurl.com/2ekrey4n [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2ekrey4n__;!!PtGJab4!4bnf0Dm…> ONLY FOR MEMBERS & ALTERNATES: * Staff will promote members and alternates to panelist once joined. * Chat: Please select Everyone so everyone can see your chat, and so it’s captured in the recording. * If unable to attend, members must communicate their alternate replacement using this google form<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…>. * Alternate assignments will be publicly posted to the Alternate Log-Transfer Policy Review PDP<https://community.icann.org/x/V4aUCQ> wiki page. * Alternates (not replacing a member): Rename your line by adding 3 Zs (zzz) before your name and add, your affiliation - alternate after your name. * Alternates (not replacing a member) are not allowed to engage in the chat or use any of the other zoom room functionalities such as raising hands or agreeing/disagreeing. ONLY FOR OBSERVERS: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Julie

1 0

At-Large session at ICANN79 discussing CoRD
by Steinar Grøtterød Feb. 13, 2024

Feb. 13, 2024

Dear all, As mentioned at the last GNSO-TPR call, At-Large will have a session discussing the CORD. See https://icann79.sched.com/event/1a16J/at-large-policy-discussion for details. Regards, Steinar Grøtterød

1 0

ICANN79 GNSO Sessions - How to Get Organized / Remote Participation Details
by Julie Bisland Feb. 12, 2024

Feb. 12, 2024

Dear all, With ICANN79<https://meetings.icann.org/en/icann79> just around the corner, please take a moment to read the information below for a seamless and successful meeting. REGISTER NOW! DEADLINE TO REGISTER IS 28 February 2024! * Sign into Your ICANN Account or create an account here<https://account.icann.org/login>. * Register by selecting the Meeting Registration tile. * Click on the Registration link. NOTE: There will be no onsite registration facilities this year so you must register in advance. In-person, advance registration will close on 28 February 2024. After that point in time, only virtual participation will be open for continued registration. Walk-up and late registrations will not be accepted after the in-person advance registration closes. All walk-up and late registered attendees will only have access to virtual participation. Before creating your schedule, please read this page carefully: https://meetings.icann.org/en/remote-participation. If participating on-site, please read the Health and Safety page<https://meetings.icann.org/en/79healthandsafety>. CREATE YOUR MEETING SCHEDULE * Access the schedule here<https://icann79.sched.com/>. The schedule shows up with blank circular radial buttons to the left of each session. Hover over the radial button and click “ADD TO MY SCHEDULE” or just click to add the checkmark. * 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. * Click the Phone icon, “Mobile app + iCal” (located on the right side of the page) * In the bottom section, “Export Calendar”, click the link next to “My Schedule”. When the .ics is exported, add it to the appropriate calendar. OR, after exporting, drag and drop the .ics file into your calendar. * Please remember, for security purposes, participation links will be posted 24-hours prior to the session start times. There will be no calendar invitations sent, as the meeting schedule allows you to download all sessions of interest to your individual calendars Review the Participation Tools and update Zoom * All sessions will use Zoom rooms. Access details are available 24hrs prior. * Visit the Participation Tools page<https://meetings.icann.org/en/remote-participation> for links to download the latest version of Zoom for access to the ICANN Meeting sessions. * Please see the ICANN Meeting Virtual Participation How-To Guide for more information on how to get the most out of the virtual meeting tools. Links to Bookmark ICANN79 Meeting Schedule<https://icann79.sched.com/> ICANN79 GNSO Remote Participation Wiki Page<https://community.icann.org/x/XIMYEQ> GNSO Session agendas<https://community.icann.org/x/WYMYEQ> For all GNSO meeting-related queries (RP or others), please email us at: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team -- 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…> [signature_2593744606]

1 0

**REMINDER** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 13 February 2024
by Julie Bisland Feb. 12, 2024

Feb. 12, 2024

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 13 February 2024 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/swDFE * Time conversion link: https://tinyurl.com/2ekrey4n [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2ekrey4n__;!!PtGJab4!4bnf0Dm…> 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 - Meeting #118 Tuesday, 13 February 2024 at 1600 UTC
by Christian Wheeler Feb. 8, 2024

Feb. 8, 2024

Dear TPR WG members, Please find below the proposed agenda for our next call, taking place on Tuesday, 13 February 2024 at 16:00 UTC. As a reminder, your current Action Item is to provide input (which may be expressed in bullet points) in the COR Reduction Rationale Google Doc, found here: https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr… Thank you for sharing your inputs and we look forward to seeing you all virtually. Kind regards, Christian, Caitlin, Berry, and Julie ---------- Transfer Policy Review - Meeting #118 Proposed Agenda 13 February 2024 Proposed Agenda: 1. Welcome and Chair Updates 2. CORD Availability discussion 3. Preliminary Recommendations 4. AOB

1 0

Post Call | Transfer Policy Review PDP WG | Tuesday, 06 February 2024
by Julie Bisland Feb. 6, 2024

Feb. 6, 2024

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Tuesday, 06 February 2024 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/sQDFE> (attendance included) and the GNSO Master calendar [gnso.icann.org]<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, 13 February 2024
by Julie Bisland Feb. 6, 2024

Feb. 6, 2024

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 13 February 2024 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/swDFE * Time conversion link: https://tinyurl.com/2ekrey4n ONLY FOR MEMBERS & ALTERNATES: * Staff will promote members and alternates to panelist once joined. * Chat: Please select Everyone so everyone can see your chat, and so it’s captured in the recording. * If unable to attend, members must communicate their alternate replacement using this google form<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…>. * Alternate assignments will be publicly posted to the Alternate Log-Transfer Policy Review PDP<https://community.icann.org/x/V4aUCQ> wiki page. * Alternates (not replacing a member): Rename your line by adding 3 Zs (zzz) before your name and add, your affiliation - alternate after your name. * Alternates (not replacing a member) are not allowed to engage in the chat or use any of the other zoom room functionalities such as raising hands or agreeing/disagreeing. ONLY FOR OBSERVERS: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Julie

1 0

Notes and action items: TPR WG on 06 February at 1600 UTC
by Julie Hedlund Feb. 6, 2024

Feb. 6, 2024

Dear TPR WG members, Please find below the brief notes and action items from today’s meeting. The next meeting will be Tuesday, 13 February 2024 at 1600 UTC. Kind regards, Christian, Caitlin, Berry and Julie ACTION ITEMS/HOMEWORK: WG to complete the COR Reduction Rationale document at: https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1DpDO2BYTl6TA…> Transfer Policy Review - Meeting #117 Proposed Agenda 06 February 2024 Notes: 1. Welcome and Chair updates * Less than a month from ICANN79 – just four scheduled calls. Get our recommendations in place. * Take self-assessment survey by Feb 21. * COR Reduction Rationale doc still has no input – need to fill that out. See action item above. * Zak, BC: Gave an update to BC – expressed their deep concern to remove all notifications and default locks. If that was a recommendation, would likely be a minority report: * Question – what locks? Answer – Opt out to be accepted on a 60-day lock: BC would like to see a default lock that registrars could opt out, with consistency in application. BC is interested in reducing the lock but against removing it. * That’s why we need the rationale document to be completed, such as the reason to remove the 60-day lock. * Steinar, ALAC: Looks like at ICANN79 will discuss the COR with public participation – will provide info if that is the case. 2. Mandatory Notifications wrap-up – see attached slides, starting at slide #5: Discussion: * Second bullet point, which do we want? Are we saying generic your info was updated? Or confirm specific change? WG needs to decide. * Stay away from the word “contact” – Suggest changing “contact information” to “registrant data”. Need to be clear. * Prefer the message lists field that was updated but not what changed in the field. * Look at the alert you get from a responsible bank as an example and minimize the amount of info provided in case the email was compromised and also avoid being too prescriptive. * Question: Wasn’t there another item re: triggers? Answer: We still need to discuss. * Ask ourselves what security goals we want to achieve if COR is not in the Transfer Policy. * Sounds like the group is okay specifying what fields have changed, but not what in that field changed. Identify known RDDS field but not what. * Question: Change of ownership with registrant data – who will see it (the old/new registrant)? Answer: That’s something that needs to be addressed. It depends, but I don’t think we can say how that would work. Need to get into these things more deeply. Notifications – Opt Out Pros/Cons: See Slide 6 Discussion: * Key point: registrant opt out. * If account is hacked notification goes to fraudulent registrant. If registrant opted out wouldn’t get notifications. * Need to look at what other industries do and why – should be a defensible rationale. It’s not about transfers – it’s about information changing. * Could turn on by default and let registrant opt out. * Uncomfortable with being able to turn off notifications – only the owner and only proactive. * Don’t see the outcry from registrants getting emails. * Could be situations when registrant would want to opt out. * maybe it should be an account setting, but not a registrar default in their terms etc. That seems like a good middle ground. * Agreement on mandatory with/without opt out. * Support for the three minimum fields (name, org, email) as triggers – see #3 below. * If there were a proactive opt out that might be okay if it was an informed decision. * If multiple changes notifications should be able to be combined. * Opt out okay if informed. * If we do have a registrant opt out it should be the same across the board for all registrars. * Note that we are talking about opting out of notifications, not locks. And should be consistently applied. * Agree: Same fields as today; mandatory but registrant can actively choose to opt out. 3. "Change of Registrant Data" discussion -- see attached slides, starting at slide #7: Discussion – slide 8 – Change of Registrant Data: * Need to decide what is that minimum set of triggers. * Prefer to keep the current set of triggers – second row. Ability to combine notifications is really helpful. * Look at what needs to be notified for security purposes. * Can still do verification even if combined. * Support for the three minimum fields (name, org, email) as triggers. Discussion – slide 9 – Material Change: * Need to decide what is that minimum set of trigger. * Include addition of data? That could be a material change if field was blank. * WG supports leaving Material Change as is. Discussion -- slide 10 – Privacy/Proxy/Designated agent * Question: Remove Designated Agent? Answer: WG has decided it won’t be defined in policy. * Registrar wouldn’t know if third-party privacy/proxy; If registrar does know, would a change trigger a notice? If assigned back to the registrant is that a notification? * No matter what: WG is saying, it doesn’t matter if it’s privacy/proxy if any one of those three fields changes it will trigger a notification. Note that the PPSAI process is still being worked out. * One of the important things is that it relates to the registrant data and not the PUBLIC data - so if the real data is redacted (not with P/P service) and is changed then the CORD is triggered. Discussion -- slides 11 & 12 – Prior and New Registrant * These terms are out of date. * Send notification when data changes in those three fields – see above – to prior registrant. * Is the opt out on the person or the domain name? Need to discuss details. * Need to continue discussion at the next meeting. 4. CORD Availability and Placement (time allowing) -- see attached slides, starting at slide #13: * Deferred to next meeting. 5. AOB: None.

1 0

**ON IN 6 MINUTES** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 06 February 2024
by Julie Bisland Feb. 6, 2024

Feb. 6, 2024

**ON IN 6 MINUTES** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 06 February 2024 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/sQDFE * Time conversion link: https://tinyurl.com/mpnrptvm [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/mpnrptvm__;!!PtGJab4!-i0w50a…> 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, 06 February 2024
by Julie Bisland Feb. 5, 2024

Feb. 5, 2024

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 06 February 2024 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/sQDFE * Time conversion link: https://tinyurl.com/mpnrptvm [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/mpnrptvm__;!!PtGJab4!-i0w50a…> 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 - Meeting #117 Tuesday, 06 February 2024 at 1600 UTC
by Christian Wheeler Feb. 1, 2024

Feb. 1, 2024

Dear TPR WG members, Please find below the proposed agenda for our next call, taking place on Tuesday, 06 February 2024 at 16:00 UTC. As a reminder, the WG’s current Action Item is to provide input for the COR Reduction Rationale Google Doc, found here: https://docs.google.com/document/d/1DpDO2BYTl6TA7ApfPpG3Hpl13nrv4y4x9B3hImr… Thank you for sharing your inputs and we look forward to seeing you all on Tuesday. Kind regards, Christian, Caitlin, Berry, and Julie ---------- Transfer Policy Review - Meeting #117 Proposed Agenda 06 February 2024 Proposed Agenda: 1. Welcome and Chair Updates 2. Mandatory Notifications wrap-up 3. "Change of Registrant Data" discussion 4. CORD Availability and Placement (time allowing) 5. AOB

1 0