- GNSO-TPR - lists.icann.org

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