May 2023 - GNSO-TPR - lists.icann.org

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 23 May 2023
by Julie Bisland May 16, 2023

May 16, 2023

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 23 May 2023 at 16:00 UTC for 90 minutes. * If unable to attend, members must communicate their alternate replacement using this google form<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…>. To join - Zoom Information: Main Zoom Webinar link: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/95363727469?pwd=N3A3OWFS…> Passcode: @TP/^*4wg# If you are joining via audio only: One tap mobile: US: +19294362866,,95363727469#,,,,*7490739013# or +13017158592,,95363727469#,,,,*7490739013# Telephone: Dial (for higher quality, dial a number based on your current location): US: +1 929 436 2866 or +1 301 715 8592 or +1 312 626 6799 or +1 669 900 6833 or +1 253 215 8782 or +1 346 248 7799 or 888 788 0099 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 953 6372 7469 Passcode: 7490739013 International numbers available: https://icann.zoom.us/u/acdLFXPLp6 <https://urldefense.com/v3/__https:/icann.zoom.us/u/acdLFXPLp6__;!!PtGJab4!v…> Members, alternates, and observers all have different access and participation directions, please read below! ALL: Before joining the call: * Please send apologies and dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> * Visit the Wiki Agenda meeting page: https://community.icann.org/x/_4LKDQ * Time conversion link: https://tinyurl.com/3769xau8 ONLY FOR MEMBERS & ALTERNATES: * Staff will promote members and alternates to panelist once joined. * Chat: Please select Everyone so everyone can see your chat, and so it’s captured in the recording. * If unable to attend, members must communicate their alternate replacement using this google form<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…>. * Alternate assignments will be publicly posted to the Alternate Log-Transfer Policy Review PDP<https://community.icann.org/x/V4aUCQ> wiki page. * Alternates (not replacing a member): Rename your line by adding 3 Zs (zzz) before your name and add, your affiliation - alternate after your name. * Alternates (not replacing a member) are not allowed to engage in the chat or use any of the other zoom room functionalities such as raising hands or agreeing/disagreeing. ONLY FOR OBSERVERS: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Julie

1 0

**STARTING IN 15 MINUTES** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 16 May 2023
by Julie Bisland May 16, 2023

May 16, 2023

**STARTING IN 15 MINUTES** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 16 May 2023 at 16:00 UTC for 90 minutes. * If unable to attend, members must communicate their alternate replacement using this google form<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…>. To join - Zoom Information: Main Zoom Webinar link: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/95363727469?pwd=N3A3OWFS…> Passcode: @TP/^*4wg# If you are joining via audio only: One tap mobile: US: +19294362866,,95363727469#,,,,*7490739013# or +13017158592,,95363727469#,,,,*7490739013# Telephone: Dial (for higher quality, dial a number based on your current location): US: +1 929 436 2866 or +1 301 715 8592 or +1 312 626 6799 or +1 669 900 6833 or +1 253 215 8782 or +1 346 248 7799 or 888 788 0099 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 953 6372 7469 Passcode: 7490739013 International numbers available: https://icann.zoom.us/u/acdLFXPLp6 <https://urldefense.com/v3/__https:/icann.zoom.us/u/acdLFXPLp6__;!!PtGJab4!v…> Members, alternates, and observers all have different access and participation directions, please read below! ALL: Before joining the call: * Please send apologies and dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> * Visit the Wiki Agenda meeting page: https://community.icann.org/x/_YLKDQ * Time conversion link: https://tinyurl.com/y7rk82za [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/y7rk82za__;!!PtGJab4!7SfBBbx…> 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, Devan

1 0

ICANN77 prep week schedule is now published / How to Create your Prep Week Schedule
by Julie Bisland May 16, 2023

May 16, 2023

Dear all, The ICANN77 prep week schedule is now published! Please take a moment to read the information below to help create your prep week schedule and add sessions to your calendar. For the prep week schedule, go here: https://icann77.sched.com/ [icann77.sched.com]<https://urldefense.com/v3/__https:/icann77.sched.com/__;!!PtGJab4!_E5j-hi3y…> * Click Sign up or Log in and enter your information (email address and create password) * Once you “Join Event”, the schedule shows up with blank circular buttons to the left of each session. Hover over each button and click “ADD TO MY SCHEDULE” (see screenshot below) or just click in each circle to add the checkmark. [zH2S7YhPBpH+xAAAAAElFTkSuQmCC] * 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. [UYF4B+Gah4wAAAAASUVORK5CYII=] Or [iZO0AAAAASUVORK5CYII=] * You will see this message, “A copy of your schedule has been sent to your(a)email.com<mailto:your@email.com>.” To export the schedule, click the Phone icon: [wOqHIHPNJbGoQAAAABJRU5ErkJggg==] * On the page that appears, scroll down to the section Calendar Sync for Google Calendar, Outlook & Apple Calendar -> Export Calendar, and click the link next to “My Schedule”. When the .ics is exported, add it to the appropriate calendar (see screenshots below). Or, after exporting, drag and drop the .ics file directly into your calendar.. [sPtvZbES15QAAAABJRU5ErkJggg==] [wEIEk8JZn0NCQAAAABJRU5ErkJggg==] The ICANN77 Schedule<https://meetings.icann.org/en/icann77> will be posted 22 May 2023. Please email questions to us at: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, 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…>

1 0

GNSO_TPR // 31 March 2023 Project Package
by Berry Cobb May 16, 2023

May 16, 2023

Dear WG, Please find a link below to project package for the GNSO_TPR PDP (31 March 2023). 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, Project SitRep, and Activity Metrics 2. Page 02 – Meeting metrics, Roster, & Group Attendance 3. Page 03,04 – Project Plan, Gantt chart 4. Page 05 – Workplan Key points: * None for this period. 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 1

REMINDER - Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 16 May 2023
by Julie Bisland May 15, 2023

May 15, 2023

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 16 May 2023 at 16:00 UTC for 90 minutes. * If unable to attend, members must communicate their alternate replacement using this google form<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLScXP3-H…>. To join - Zoom Information: Main Zoom Webinar link: https://icann.zoom.us/j/95363727469?pwd=N3A3OWFSaTlUME9wZzlGajk5VUI3QT09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/95363727469?pwd=N3A3OWFS…> Passcode: @TP/^*4wg# If you are joining via audio only: One tap mobile: US: +19294362866,,95363727469#,,,,*7490739013# or +13017158592,,95363727469#,,,,*7490739013# Telephone: Dial (for higher quality, dial a number based on your current location): US: +1 929 436 2866 or +1 301 715 8592 or +1 312 626 6799 or +1 669 900 6833 or +1 253 215 8782 or +1 346 248 7799 or 888 788 0099 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 953 6372 7469 Passcode: 7490739013 International numbers available: https://icann.zoom.us/u/acdLFXPLp6 <https://urldefense.com/v3/__https:/icann.zoom.us/u/acdLFXPLp6__;!!PtGJab4!v…> Members, alternates, and observers all have different access and participation directions, please read below! ALL: Before joining the call: * Please send apologies and dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> * Visit the Wiki Agenda meeting page: https://community.icann.org/x/_YLKDQ * Time conversion link: https://tinyurl.com/y7rk82za [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/y7rk82za__;!!PtGJab4!7SfBBbx…> 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, Devan

1 0

Proposed agenda for meeting #91 on Tuesday 16 May 2023 at 16:00 UTC
by Emily Barabas May 12, 2023

May 12, 2023

Dear Working Group members, Please find below the proposed agenda for the next meeting scheduled to take place on Tuesday 16 May at 16:00 UTC. Before the call, please review sections Section 3.1 and 3.2.1 of the Transfer Dispute Resolution policy in preparation for discussion of Charter Question G2: https://www.icann.org/resources/pages/tdrp-2016-06-01-en. Kind regards, Caitlin, Berry, Julie, and Emily Transfer Policy Review - Meeting #91 Proposed Agenda 16 May 2023 1. Welcome and Chair updates 2. Review Draft Preliminary Recommendations on TEAC 3. Consider outstanding questions on TEAC 4. Charter Question G1 and G2 on TDRP (time permitting) 5. AOB

1 0

Reminder: Please share availability for August TPR meetings - Deadline Friday, 19 May
by Emily Barabas May 12, 2023

May 12, 2023

Dear working group members, As a reminder, please fill out this brief poll by Friday, 19 May: https://forms.gle/c7d1Aduo5YLct4ST7 Kind regards, Caitlin, Julie, Berry, and Emily From: Emily Barabas <emily.barabas(a)icann.org> Date: Wednesday, 10 May 2023 at 09:44 To: "gnso-tpr(a)icann.org" <gnso-tpr(a)icann.org> Subject: Action Item: Please share availability for August TPR meetings - Deadline Friday, 19 May Dear working group members, Please take a moment to share your availability for working group meetings in August by completing this brief poll: https://forms.gle/c7d1Aduo5YLct4ST7 This poll will close on Friday, 19 May. Kind regards, Caitlin, Julie, Berry, and Emily Emily Barabas Policy Development Support Senior Manager Internet Corporation for Assigned Names and Numbers (ICANN) Phone: +31 (0)6 84507976 www.icann.org<http://www.icann.org/>

1 0

Action Item: Please share availability for August TPR meetings - Deadline Friday, 19 May
by Emily Barabas May 10, 2023

May 10, 2023

Dear working group members, Please take a moment to share your availability for working group meetings in August by completing this brief poll: https://forms.gle/c7d1Aduo5YLct4ST7 This poll will close on Friday, 19 May. Kind regards, Caitlin, Julie, Berry, and Emily Emily Barabas Policy Development Support Senior Manager Internet Corporation for Assigned Names and Numbers (ICANN) Phone: +31 (0)6 84507976 www.icann.org<http://www.icann.org/>

1 0

Post Call | Transfer Policy Review PDP WG | Tuesday, 09 May 2023
by Devan Reed May 9, 2023

May 9, 2023

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Tuesday, 09 May 2023 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/94LKDQ> (attendance included) and the GNSO Master calendar<https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…>. These include: * Attendance * Audio recording * Zoom recording (including audio, visual, rough transcript, and chat.) * Transcript * Agenda and Notes/Action Items As a reminder only members and alternates can join the call as a Panelist, observers can join as an Attendee to listen. For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-tpr/> and the main wiki page<https://community.icann.org/x/P4aUCQ>. Thank you. With kind regards, Devan

1 0

Notes and action items: TPR WG Meeting #90 - 09 May at 1600 UTC
by Julie Hedlund May 9, 2023

May 9, 2023

Dear TPR WG members, Please find below the brief notes and action items from today’s meeting. The next meeting will be on Tuesday, 16 May at 1600 UTC. Best regards, Emily, Julie, Berry, and Caitlin ACTION ITEMS/HOMEWORK: None captured. Notes: Transfer Policy Review - Meeting #90 Proposed Agenda 09 May 2023 1. Roll Call & SOI updates 2. Welcome and Chair Updates * Yesterday was the deadline of policy proposals for requirements related to informal resolution. There do not appear to be any new proposals in the document. Therefore we are going to focus back on the questions in the charter, beginning with TEAC. * Steinar: CPWG/ALAC discussed the proposal for informal resolution and agreed it should be policy, but offered no specific language. * We are trying something different this week -- a more structured approach, including a chair proposal for the path forward based on inputs to date. Perhaps we can take a few mins at the end of the call to collect feedback on the approach and whether folks are comfortable continuing this way for TEAC/TDPR questions. * Project Work Plan: * There were no new policy proposals for requirements related to informal resolution, so we will focus back on the questions in the charter, beginning with TEAC. * Note that there are new meetings on the calendar for June and July. We will send a poll to gauge availability for August. 3. New proposals for policy requirements - non-emergency informal resolution (if any are received) (link to working document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1vP9Q-EyhroHI…>) * No new proposals to discuss. 4. Status and next steps on Charter Questions F1-F7 (see TEAC working document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1ejqMnKrN5Pnq…> and attached slides) Question F1: f1) Is additional data needed to support evaluation of the effectiveness of the TEAC mechanism? If so, what data is needed? Status: In written input RySG, NCSG, and BC have stated that it would be helpful to have additional metrics from registrars to support policymaking. In WG discussion, some support was expressed for requiring registrars to track and report on TEAC activity. Possible Path Recommendation to require registrars to track and report on specific data points related to the TEAC going forward, leveraging lists from RySG, NCSG, and BC. Rationale Metrics will support understanding of how well the TEAC functions and any pain points, which will support future data-driven policy making. To Discuss Specific metrics that would be required. Discussion: * Think the WG agrees that we need additional data and tracking, but need specifics. Confirmed that this is a good idea. * Talk about the things that would be most helpful to track at a high level. * We may be creating pieces of these metrics as we go. * Any thoughts from the WG on specific metrics to collect? Not a lot of discussion about this yet. Questions F2/F3: f2) The time frame (4 hours) for registrars to respond to communications via the TEAC channel has been raised as a concern by the Transfer Policy Review Scoping Team and in survey responses. Some have expressed that registries must, in practice, have 24x7 coverage by staff members with the appropriate competency to meet this requirement and the language skills to respond to communications from around the world. Is there merit to concerns that the requirement disproportionately impacts certain registrars, namely: 1. Registrars located in regions outside of the Americas and Europe, because of significant time zone differences? 2. Small and medium-sized registrars, which may not have a sufficiently large team to have 24x7 staff coverage with the necessary competency? 3. Registrars in countries where English is not the primary language, who may, in practice, need to have English-speaking TEAC contacts to respond to requests in English? f3) To what extent should the 4-hour time frame be revisited in light of these concerns? Are there alternative means to address the underlying concerns other than adjusting the time frame? Status: In initial deliberations, some support was expressed for extending the timeframe for initial contact from 4 hours to 24 hours. Early written input does not seem to contradict this path forward: * RySG: “. . . as a practical matter, the 4-hour timeframe and the telephone-driven nature of the TEAC mechanism can lead to suboptimal outcomes. . . Research of prior RySG comments on the IRTP Part B (March 2011) indicates (at that time) most voicing an opinion within the RySG supported a timeframe of 24 hours.” * RrSG: “While 4 hours may be too short, there should be a minimum response deadline (perhaps 48 hours) to ensure that emergency transfer disputes are addressed in a timely manner.” * NCSG: “The 4-hour time frame should be revisited to, at least, 24 hours.” * BC: depending on the frequency and effectiveness of use, the four-hour time frame seems generally appropriate for emergency situations, though it can perhaps be expanded somewhat to 12 or 24 hours. Possible Path Recommendation to extend the TEAC deadline to 24 hours. Rationale Reduce risk of gaming, reduce burden on registrars (especially smaller companies and those in time zones outside of Europe and the Americas), while still providing a reasonable response timeframe. Currently RAA has a 24 hour SLA for Rrs to provide a non-automated initial response to reports of illegal activity. This may be considered an analogous situation. Discussion: * Heard a lot of support for the 24-hour window. Question F4: f4) Section I.A.4.6.2 of the Transfer Policy states that “Communications to a TEAC must be initiated in a timely manner, within a reasonable period of time following the alleged unauthorized loss of a domain.” The Transfer Policy Review Scoping Team noted that this timeframe should be more clearly defined. Is additional guidance needed to define a “reasonable period of time” after which registrars should be expected to use a standard dispute resolution process? Note: The working group has considered two items related to this charter question: 1. The timeframe for initial contact to the TEAC following the alleged unauthorized loss of a domain. 2. The timeframe for final resolution of an issue raised through the TEAC channel. f4, Item 1: The timeframe for initial contact to the TEAC following the alleged unauthorized loss of a domain. Status: Comments from the RySG, RrSG, NCSG, and BC support providing more guidance around “a reasonable period of time.” While some working group members have favored providing a precise deadline, others have noted that there may be circumstances that require more flexibility. RrSG suggested that the timeframe should be aligned with when the registrar is made aware of the unauthorized transfer. BC suggested the period could be 5 days from the alleged unauthorized loss of a domain. Possible Path Initial contact to a TEAC should generally occur no more than [x days] following the alleged unauthorized loss of a domain. If the initial contact to the TEAC channel occurs more that [x days] following the alleged unauthorized loss of a domain, the registrar must provide a detailed explanation of why this is an emergency situation that must be addressed through the TEAC channel, including why earlier contact to the TEAC was not possible. Rationale The suggested approach puts additional definition around “a reasonable period of time,” while allowing flexibility for exceptional circumstances that may still constitute an emergency. To Discuss Would 30 days be an appropriate time frame, corresponding to the post-transfer lock period? Discussion: * We had discussions around data occurrence versus data reporting – when is it a TEAC/emergency situation? * Not sure how the above would be validated. Better to look at an objective number. 30 days seems more reasonable. Shouldn’t be gauging awareness. f4, Item 2: The timeframe for final resolution of an issue raised through the TEAC channel Status: Some working group members noted that it would be helpful to have defined timeframes, but others raised that each case is different and some cases may take longer to resolve than others. Absent data about the types of cases and resolutions handled through the TEAC channel, it is difficult to define requirements. Possible Path If an issue is raised through the TEAC channel, the registrar receiving the communication must provide updates about the status of the resolution to the party who initiated the TEAC contact no less than every [x period of time], including specific actions taken to work towards resolution. Rationale Introduces additional transparency and accountability without providing strict deadlines that may not be appropriate or feasible to meet, depending on circumstances. To Discuss Time period for periodic updates. Discussion: * This is a complicated thing to write policy around. Not sure how regular these updates need to be. * Timeframe might vary. * Goal is to keep the two parties engaged and working towards resolution. Two or three days seems reasonable. Question F5: f5) According to section I.A.4.6.2 of the Transfer Policy, the TEAC may be designated as a telephone number, and therefore some TEAC communications may take place by phone. The Transfer Policy Review Scoping Team flagged this provision as a potential item for further consideration. Do telephone communications provide a sufficient “paper trail” for registrars who may later wish to request a transfer “undo” based on failure by a TEAC to respond? Such a request would require the registrar to provide evidence that a phone call was made and not answered, or a call back was not received within 4 hours. Noting this requirement, should the option to communicate by phone be eliminated? Is an authoritative “system of record” for TEAC communications warranted? If so, what are the requirements for such a system? Status: There are different views on this question: * RySG supports “exploring integrating a TEAC-like function into the ICANN nSP”, but is “not prepared to recommend that the option for phone communication be eliminated without understanding the proposed option(s) for replacement.” * RrSG does not have a unified position and suggests that It “may be ideal to allow each registrar to choose which form of contact they would prefer.” * NCSG suggests that the use of telephone communication for TEAC may “raise concerns about the ability to provide a sufficient "paper trail"” and suggests that email may be a suitable system of record. * BC notes that “the telephone contact appears to remain an effective means of communications for the initial contact, however there should perhaps be an additional logging mechanism via a written report to ICANN, for example, or even via email correspondence which would have a paper trail.” Possible Path Require that registrars provide an email address for TEAC. First attempt to contact the TEAC must be by email, but can be followed by other forms of communication (for example, phone). The TEAC must respond to that initial email within 24 hours. Rationale Ensures that there is a paper trail associated with each initial TEAC contact without creating complex new requirements for an system of record that may be seldom used. Discussion: * Hard to build requirements when we have very little data at this point. * Don’t think the Registries role to gather evidence. * The 24-hour might stretch this out a little. * Being used so little, does it make sense to create a system of record? * Could add in that ICANN could be pushing the TEACs when then send out contacts – if ICANN knows when contact updates go out it would be helpful if they could send them to the Registries. * Good to keep the phone contact, but the email would be initiating it and moving it forward. Solves a paper-trail/evidence issue. * Seems to be support for the possible path. Questions F6/7: f6/f7) The Transfer Policy Review Scoping Team indicated that there are several factors that make a Registry Operator’s obligation to “undo” a transfer under Section 6.4 of the Transfer Policy challenging: 1. Registry Operators do not have access to the designated TEACs for each Registrar, making validation of an undo request nearly impossible. 2. There is no way for Registry Operators to independently verify that a Registrar did not respond within the required time frame or at all since Registry Operators are not a party to, or copied on, communications between the Registrar TEACs. 3. Transfer “undo” requests associated with the failure of a TEAC to respond are unilateral so there is no validation required prior to a Registry Operator taking action. This has, on occasion, led to a “he said”, “she said” scenario. 4. Follow on to f6 iii., if the policy were to be updated to allow for some level of validation by the Registry Operator prior to taking action, the requirement to “undo” a transfer within 5 calendar days of receiving an TEAC undo request leaves little to no time to attempt to validate the request prior to taking the action. To what extent are changes to the policy needed to address these concerns? Are there other pain points for Registry Operators that need to be considered in the review of the policy in this regard? Issue i Status: * RySG suggests “that ICANN Org include the Rr TEAC in the list of Rr contacts that it regularly supplies to the ROs.” Possible Path Recommendation that ICANN Org include the registrar TEAC in the list of registrar contacts that it regularly supplies to the ROs. Rationale Helps to ensure that registries are aware of updates to TEAC information. Discussion: * What is the issue behind the RySG suggestion: * Registrars are required to keep their TEAC updated in the NsP and also the portal with the RO. * ICANN doesn’t include the TEAC when they send updates to the RO. * Ask that ICANN includes the TEAC update along with the primary Registrar contacts. * Questions: Do registries have access to the NsP? Answer: The primary way we access the TEAC is in our own systems – pretty sure we don’t have access to the registrar’s TEAC in the portal. * Question: It seems like a logistics and operational – rather than policy – issue. Could registries go directly to GDS? Answer: Yes, we have tried to do this but it was decided that because of GDPR this information could no longer be distributed. Issue ii, iii, iv Status: * RySG early input reiterated concerns stated in the charter question. In working group discussion, RySG members have held that the process should work in such a way that the RO doesn’t need to make a decision or conduct any verification. Registries should also not be liable in cases where they undo a transfer because a TEAC did not respond in time. * RrSG early input noted that “some Registrars suggest that the registry should be required to contact both registrars before taking action that could impact the domain in determining whether there is noncompliance.” Further, “Transfer undoes should only occur for TEAC noncompliance when a registry can conclude that the TEAC obligations of the gaining registrar were noncompliant, not in a scenario where evidence from the two registrars is conflicting. The group may benefit from considering requiring the creation of a communication path to pass these TEAC requests back and forth and ensure that the registry and ICANN also have visibility into them.” * NCSG suggested that “one possible solution could be to require Registrar TEACs to copy Registry Operators on all TEAC communications” and noted that an authoritative system is an alternative. * BC notes that in the “. . . absence of much data concerning dissatisfaction with a very infrequently used procedure, would seem to mitigate in favour little change to the current approach.” Question for Input: According to Transfer Policy Section I.A.6.4, “The Registry Operator shall undo a transfer if, after a transfer has occurred, the Registry Operator receives one of the notices as set forth below. . .6.4.4 Documentation provided by the Registrar of Record prior to transfer that the Gaining Registrar has not responded to a message via the TEAC within the timeframe specified in Section I.A.4.6.” Would a requirement that first contact occurs by email sufficiently mitigate registry concerns about “he said, she said” scenarios? Discussion: * No suggested path forward as there are diverging positions. * Good step to go from phone to email, and having RO cc’d on TEAC email – also could be helpful if there was a suggested template for the email to ensure it contains key information. Think about it going to a specific inbox (i.e., teac(a)godaddy.com<mailto:teac@godaddy.com>). * The specific inbox probably can’t be policy, but could be guidance. * Question: What evidence would the RO need to do a rollback? Answer: It is very situationally dependent. Registries have concerns about liability – really look hard before doing a rollback. * Looking at current practices there is a lot of concern about liability. * Extending the timeframe from 4 to 24 hours will help a lot, and having an email paper trail. Could mitigate the issues. Next Steps: * Is this approach useful? * Seems like there is general support for this approach. * Question: Can staff start drafting answers to charter questions? Answer: Yes, and drafting some preliminary recommendations. 5. AOB

1 0