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

Feb - June 2023 calls | Transfer Policy Review PDP WG
by Terri Agnew Feb. 17, 2023

Feb. 17, 2023

**We are sending in advance to get dates on everyone’s calendar. Dear all, The calls for February, March, April, May, and June 2023 for the Transfer Policy Review PDP WG are listed below. The calls take place at 16:00 UTC for 90 minutes., please be sure to download them as “recurring” vs. a one-time event to ensure all the dates show up on your calendar. The attached ics is for the recurring meetings March – June 2023. * Tuesday, 21 February 2023 (invite sent out already) * Tuesday, 28 February 2023 * Tuesday, 07 March 2023 * Tuesday, 28 March 2023 * Tuesday, 04 April 2023 * Tuesday, 11 April 2023 * Tuesday, 18 April 2023 * Tuesday, 25 April 2023 * Tuesday, 02 May 2023 * Tuesday, 09 May 20223 * Tuesday, 16 May 2023 * Tuesday, 23 May 2023 * Tuesday, 30 May 2023 * Tuesday, 06 June 2023 Future invitations will be sent out closer to the date of the call. Thank you. With kind regards, Terri

1 0

Transfer Policy Review PDP WG
by ICANN Policy Calendar Feb. 17, 2023

Feb. 17, 2023

Meeting: Transfer Policy Review PDP WG Date/Time: Every Tuesday at 16:00 UTC for 90 minutes, 28 March – 06 June 2023 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> * Wiki agenda page (2023): https://community.icann.org/x/Gow-DQ * Time conversion link: https://tinyurl.com/2p95cn6r 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>. * Members and alternates replacing members, 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

ICANN76 prep week scheduled is now published / How to Create your Prep Week Schedule
by Julie Bisland Feb. 15, 2023

Feb. 15, 2023

Dear all, The ICANN76 prep week scheduled 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://icann76.sched.com/ [icann76.sched.com]<https://urldefense.com/v3/__https:/icann76.sched.com/__;!!PtGJab4!-WtbJjGY_…> * Click Sign up and enter your information (email address and create password) * Once you “Join Event”, the schedule shows up with blank radial buttons to the left of each session. Hover over the radial button and click “ADD TO MY SCHEDULE” (see screen shot below) or just click to add the checkmark. [cid:image001.png@01D94151.1DE98560] * 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. [cid:image002.png@01D94151.1DE98560] Or [cid:image003.png@01D94151.1DE98560] * Click the Phone icon [cid:image004.png@01D94151.1DE98560] * In the bottom section, “Export Calendar”, click the link next to “My Schedule”. When the .ics is exported, add it to the appropriate calendar. [cid:image005.png@01D94151.1DE98560] [cid:image006.png@01D94151.1DE98560] The ICANN76 Schedule<https://76.schedule.icann.org/> will be posted 17 February 2023.Please email questions to us at: gnso-secs(a)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

For Review: Latest Redline of Phase 1A Initial Report & Recommendations
by Emily Barabas Feb. 15, 2023

Feb. 15, 2023

Dear working group members, As discussed on our recent calls, staff had an action item to provide an updated redline revision of the Phase 1A Initial Report to the working group for review. The updated redline is attached and includes: * New edits supported by the working group after reviewing public comments and considering small group outputs. * Updated responses to charter questions and rationales to more fully provide context and reasoning for the WG’s recommendations. * Updates for consistency in terminology, the way that timeframes are referenced, etc. * Discussion of items that the NCSG and SSAC asked the working group to consider, but that the working group determined were out of scope. Please make sure to review the following, with a particular focus on edits that are new since the 21 December redline. New edits are highlighted in yellow. * Section 3 of the report (pages 11-50) * Annex D (pages 58-63) Highlights in blue are to assist staff in tracking areas of the report that will need to updated in the future. Working group members can ignore these highlights for now. Please carefully review this document in coordination with the groups you represent. If you feel that there are items that need to be revised, please enter them here<https://docs.google.com/document/d/1eRM4mFGDNYhb0tiD5V_PE4zxnIKfD46esX6EtHe…>. For each item, please include: * Report version (the date listed in the header of the document) and applicable line numbers ( these are listed along the left margin of the document). * Name and group you represent: If multiple WG members represent a group, input should be in coordination with these other members. * Rationale: please provide a clear explanation for why you are proposing the revision. * Specific proposed revision: Provide the language you would like to see added/removed/edited. The inputs will be reviewed when the working group returns to considering Phase 1(a) items. Additional information about the timeline for returning to Phase 1(a) will be provided as we progress through discussion of Phase 2 topics. Please do not hesitate to reach out with any questions about the review process. Kind regards, Caitlin, Julie, Berry, and Emily Emily Barabas Policy Development Support Senior Manager Internet Corporation for Assigned Names and Numbers (ICANN) Phone: +31 (0)6 84507976 www.icann.org<http://www.icann.org/>

5 8

Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 21 February 2023
by Julie Bisland Feb. 14, 2023

Feb. 14, 2023

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 21 February 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/KIw-DQ * Time conversion link: https://tinyurl.com/2b9x28mt ONLY FOR MEMBERS & ALTERNATES: * Staff will promote members and alternates to panelist once joined. * Chat: Please select Everyone so everyone can see your chat, and so it’s captured in the recording. * 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

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

Feb. 14, 2023

Dear all, All recordings for the Transfer Policy Review PDP WG call held on Tuesday, 14 February 2023 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/JYw-DQ> (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 As a reminder only members and alternates can join the call as a Panelist, observers can join as an Attendee to listen. For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-tpr/> and the main wiki page<https://community.icann.org/x/P4aUCQ>. Thank you. With kind regards, Julie

1 0

Notes and action items - TPR WG Meeting #80 - 14 February 2023 at 16:00 UTC
by Julie Hedlund Feb. 14, 2023

Feb. 14, 2023

Dear TPR WG members, Please find below the notes and action items from today’s meeting. The next meeting will be on Tuesday, 21 February 2023 at 16:00 UTC. Best regards, Emily, Julie, Berry, and Caitlin ACTION ITEMS/HOMEWORK: Actions from Meeting on 14 February: None identified. Notes: Transfer Policy Review - Meeting #80 Proposed Agenda 14 February 2023 1. Roll Call & SOI updates * See Steinar Grøtterød SOI<https://community.icann.org/pages/viewpage.action?pageId=162890286>. 2. Welcome and Chair Updates * Starting our Phase 2 discussions this week and circle back to our Phase 1b discussions next meeting. * As we move into Phase 2 we’ll send out a request for early input on the charter questions to all the SOs and ACS; we’ll be sending that to you for review. * Update from Steinar/ALAC: Circulated to the CPWG the proposal from Rick on having a shorter TTL for registries – lively discussion but no consensus. 3. Introduction to Phase 2 topics: Transfer Emergency Action Contact (TEAC), Transfer Dispute Resolution Policy (TDRP), and Fast Undo – see the attached slides. * For more reading on the TEAC, please see page 33 of the Final Issue Report: https://gnso.icann.org/sites/default/files/file/field-file-attach/final-iss…. * For details about the ETRP proposal, see pages 49-54 here: https://gnso.icann.org/sites/default/files/filefield_12531/irtp-b-initial-r…. * See also: Public comments on the IRTP-B Initial Report. You can find the comments here: https://forum.icann.org/lists/irtp-b-initial-report/ 4. Time permitting, begin discussion of fast undo -- what is different since the rejection of the Expedited Transfer Reverse Policy (ETRP) proposal? See TDRP decisions at: https://www.adndrc.org/decisions/tdrp and https://www.adrforum.com/domain-dispute/search-decisions Discussion: * Useful to discuss some type of rollback. * Think we should look at the TEAC process first and the changes that might be required, then look at the dispute process, followed by the undo feature. * It is a question whether the recommendations we have established in Phase 1a - in particular the proposed security improvement, will make the ETRP less complexed. * Wonder if we'll need a fast-undo separate from the TDRP... depends on what the TDRP looks like -- do like my idea of figuring out the components of any dispute process and then thinking about how to put it all together. * It is difficult to create a policy to solve a problem when we don’t know what the problem is. * So do we need two timeframes (fast undo and normal undo) or do we need one process that lets us indicate urgency (as you just said)? * Move into a discussion of pain points relating to the TEAC. Discussion of Pain Points Relating to the TEAC: * Not much data, easy to game. * Since TEAC contacts are via phone hard for registries to capture timelines. * I do think some type of expedited transfer issue channel is needed, but not the current version of TEAC. * If this mechanism is going to be maintained ICANN could provide a list of authoritative contacts to the registries. * What does the group think about the idea of making a list of components for a transfer undo process, which we can then turn into a policy? Does that seem like a useful path? am I getting ahead of myself since we decided to look at the TEAC first? * Re data: We found that it is not something ICANN org tracks – when the TEAC is being used. But there is a summary of inputs, including answers to survey questions, that is in the Policy Status Report. * Initial thought is that unless there is a new concept that can be raised to possibly solve the known issues in principle, then it may not be worth-while embarking on that. * What is the problem we are targeting – is it hijacking for the purpose of abuse? * When you are looking at the dispute mechanism you are trying to correct something that occurred erroneously for whatever reason – maybe there are specific paths for why that occurred. * We should have a way to address a transfer that occurred because the bad actor accessed the RNH's account or email and did the transfer. * See various scenarios involving high-value names, including fake court orders. * i’m just reacting to this frequent use of “hijack” in the discussion. I understand that it’s a transfer dispute. the reason doesn’t matter. the complicating factor is whether or not there’s an urgency factor, which only the RNH can answer I would think. or am I oversimplifying? * It’s broader than hijacking – it’s about any transfer that shouldn’t have occurred. * It doesn’t matter why the dispute over the transfer is occurring, just whether it’s urgent or not. * We should start by looking at the concerns that came in from the public comment period. * Once we work through the TEAC and TDRP we may eliminate the need for a roll back, or identify a gap where it is needed. * One of the intention of including the proposal from IRTP (ETRP) and comments is to have that information in the background. If it’s useful to clarify the points previously raised we can do that, but it is meant as background information. * The TEAC came out of IRTP Part B, the same one that considered and rejected the ETRP. The group was looking at these things as part of a dispute process. Charter Questions: Is additional data needed to support evaluation of the effectiveness of the TEAC? * Helpful for the WG to consider what, if any, data might be available. Is there merit to concerns that the requirement disproportionately impacts certain registrars, namely: * Registrars located in regions outside of the Americas and Europe? * Small and medium-sized registrars, which may not have a sufficiently large team to have 24x7 staff coverage with the necessary competency? Registrars in countries where English is not the primary language? 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? Discussion: * Need to consider guidance for responsiveness and what is a reasonable period of time. * There is a lack of window of when this should be done – maybe that should be bounded. * The 4-hour window is a loop hole to do damage. * So we should consider if the timeframes achieve what we want to achieve. * Have seen hijacks timed to occur at the start of a holiday to take advantage of the timeframe when no one might notice. * Would a longer response time result in fewer problems? Not sure, but open to discussions. * Important to think about the degree of impact – does it have to be a complete reversal of ownership; think there are degrees of transfer and criticality. Something to consider with timelines. Is additional guidance needed to define a “reasonable period of time” after which registrars should be expected to use a standard dispute resolution process? Discussion: * Impact defines reasonable – could be an hour, could be 10 days. It depends. * If someone doesn’t notice the transfer, seems like the TEAC might not be appropriate. * Do think the policy should be changed to include a notification to the registrar. * The TEAC isn’t a dispute mechanism, it's a point of contact -- so I think we need one policy (not two) which contains emergency and non-emergency requirements. * It feels like the requests for disclosure process in the EPDP with two sections (urgent and not urgent). * May need guidance on what might be an emergency. * If it is an emergency, need to define “reasonable” and “actionable.” 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? Discussion: * Should the requirement for communication by phone be eliminated? * May have seemed like phone was the quickest method of communication, but not the best for an audit trail. * Does the communication have to be specified? * Issues of accuracy and privacy – phone numbers often are wrong and due to privacy we can’t monitor those calls. Several factors make a Registry Operator’s obligation to “undo” a transfer under Section 6.4 of the Transfer Policy challenging – are updates needed? 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? Discussion: * These charter questions are fairly specific, but can be helpful to take a broader view of what problems we are trying to solve. Helpful to find the pain points. 5. AOB

1 0

**AT THE TOP OF THE HOUR** Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 14 February 2023
by Julie Bisland Feb. 14, 2023

Feb. 14, 2023

**AT THE TOP OF THE HOUR** Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 14 February 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/JYw-DQ * For other places see: https://tinyurl.com/bddt8ucr [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/bddt8ucr__;!!PtGJab4!9WsEuWm…> 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

REMINDER | Meeting Invitation | Transfer Policy Review PDP WG call | Tuesday, 14 February 2023
by Devan Reed Feb. 13, 2023

Feb. 13, 2023

Dear all, The next Transfer Policy Review PDP WG call is scheduled for Tuesday, 14 February 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/JYw-DQ * For other places see: https://tinyurl.com/bddt8ucr [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/bddt8ucr__;!!PtGJab4!9WsEuWm…> 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 #80 on Tuesday 14 February 2023 at 16:00 UTC
by Emily Barabas Feb. 13, 2023

Feb. 13, 2023

Dear Working Group members, Please find below the proposed agenda for the next meeting scheduled to take place on Tuesday 14 February at 16:00 UTC. To prepare for the discussion, please re-review the following on the fast undo mechanism called Expedited Transfer Reverse Policy (ETRP) that was proposed, but ultimately discarded in IRTP-B: * Initial Report – IRTP Part B<https://gnso.icann.org/sites/default/files/filefield_12531/irtp-b-initial-r…>: pages 49-54 * Proposed Final Report – IRTP Part B<https://gnso.icann.org/sites/default/files/filefield_22303/irtp-b-proposed-…>: pages 14-19 Kind regards, Caitlin, Berry, Julie, and Emily Transfer Policy Review - Meeting #80 Proposed Agenda 14 February 2023 1. Roll Call & SOI updates 2. Welcome and Chair Updates 3. Introduction to Phase 2 topics: Transfer Emergency Action Contact (TEAC), Transfer Dispute Resolution Policy (TDRP), and Fast Undo 4. Time permitting, begin discussion of fast undo -- what is different since the rejection of the Expedited Transfer Reverse Policy (ETRP) proposal? 5. AOB

1 0