March 2020 - GNSO-TPRST - lists.icann.org

For your review: draft scoping paper
by Caitlin Tubergen April 2, 2020

April 2, 2020

Dear Scoping Team Members: Further to Support Staff’s action to circulate a clean version of the Scoping Paper to the Team by COB today, please find the link: https://docs.google.com/document/d/1sXxp5TsUskcrW444D6lYCLy6YX99Wyus/edit#. As a reminder, please provide additional and final edits by COB Thursday, 2 April. Support Staff will then incorporate the proposed edits and send the paper to the GNSO Council by Monday, 6 April. In addition, please remember to keep the your RrSG GNSO Councilors colleagues apprised of the Scoping Team's progress. Thank you. Best regards, Berry and Caitlin

7 8

Post call / Transfer Policy Review Scoping Team call on Thursday, 26 March 2020 at 16:00 UTC
by Michelle DeSmyter March 26, 2020

March 26, 2020

Dear all, All recordings for the Transfer Policy Review Scoping Team call held on Thursday, 26 March 2020 at 16:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/2CmJBw> (attendance included). These include: * Attendance (please let me know if your name has been left off the attendance list) * Audio recording * Zoom chat archive * Zoom recording (including audio, visual, rough transcript) For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-tprst/> and the main wiki page<https://community.icann.org/x/OoElBw>. Thank you. Kind regards, Michelle

1 0

Proposed agenda: Transfer Policy Review Scoping Team Meeting #7
by Caitlin Tubergen March 24, 2020

March 24, 2020

Dear All: Please find below the proposed agenda for the next meeting on Thursday, 26 March at 16:00 UTC. As a reminder, please find the action items from our last meeting: Transfer Policy Scoping Team Members to continue working on the Scoping Document for the GNSO Council and provide additional comments by COB Wednesday, 25 March. Please provide all comments in suggestion mode only. Specifically, please review the highlighted topics in the document and provide a clear rationale as to why this topic should be considered in a future PDP. Highlighted topics include: i. Overarching priority statement on how the GNSO Council should consider this topic in the context of its upcoming work ii. Confusion around when inter-registrar transfers can be NACKed iii. Reversing Transfers/Clawback provision iv. Required Data for Review of Policy If there are topics in the paper that have no rationale, the Scoping Team will discuss the removal of the topics during its next meeting on Thursday, 26 March. Thank you. Best regards, Berry and Caitlin -- Transfer Policy Review Scoping Team Meeting #7 Thursday, 26 March 2020 16:00 UTC Proposed Agenda Roll Call & SOI Updates Review Transfer Scoping Doc (link [docs.google.com] Review additional input received on highlighted areas Agree on next steps (submit doc by 6 April, Council motion and docs deadline) Review draft GNSO Council resolution, which would acknowledge the Scoping Team’s proposal to the Council and authorize ICANN org staff to start an Issues Report Wrap up Confirm action items Confirm no additional meetings necessary

1 0

Post call | Transfer Policy Review Scoping Team call | Thursday, 19 March 2020 at 16:00 UTC
by Julie Bisland March 20, 2020

March 20, 2020

Dear all, All recordings for the Transfer Policy Review Scoping Team call held on Thursday, 19 March 2020 at 16:00 UTC can be found on the agenda wiki page<https://community.icann.org/x/rB_JBw> (attendance included). These include: * Attendance (please let me know if your name has been left off the attendance list) * Audio recording * Zoom chat archive * Zoom recording (including audio, visual, rough transcript) For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-tprst/> and the main wiki page<https://community.icann.org/x/OoElBw>. Thank you. Kind regards, Julie -- Julie Bisland GNSO SO/AC Support coordinator 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

Action items - Transfer Policy Scoping Team Meeting - 19 March 2020
by Caitlin Tubergen March 19, 2020

March 19, 2020

Dear Team: Please find below the action items from today’s Transfer Policy Review Scoping Team meeting. Action Items Transfer Policy Scoping Team Members to continue working on the Scoping Document for the GNSO Council and provide additional comments by COB Wednesday, 25 March. Please provide all comments in suggestion mode only. Specifically, please review the highlighted topics in the document and provide a clear rationale as to why this topic should be considered in a future PDP. Highlighted topics include: i. Overarching priority statement on how the GNSO Council should consider this topic in the context of its upcoming work ii. Confusion around when inter-registrar transfers can be NACKed iii. Reversing Transfers/Clawback provision iv. Required Data for Review of Policy If there are topics in the paper that have no rationale, the Scoping Team will discuss the removal of the topics during its next meeting on Thursday, 26 March. Transfer Policy Scoping Support Staff to prepare draft GNSO Council resolution, which would acknowledge the Scoping Team’s proposal to the Council and authorize ICANN org staff to start an Issues Report to be shared with the Team at its next meeting on Thursday, 26 March. The next meeting will be Thursday, 26 March at 16:00 UTC. Best regards, Berry and Caitlin

1 0

FW: [Ext] Proposed Agenda: Transfer Policy Review Scoping Team Meeting - 19 Mar 2020 - 16:00 UTC
by Caitlin Tubergen March 19, 2020

March 19, 2020

Dear TPSRT: Please find below the proposed agenda for this week’s call. Transfer Policy Review Scoping Team Meeting #6 Thursday, 19 March 2020 16:00 UTC Proposed Agenda Roll Call & SOI Updates Review Transfer Scoping Doc (link [docs.google.com] Solicit input on highlighted areas Request to consolidate topics by T. Keller Agree on next steps (submit doc by 6 April, Council motion and docs deadline) o Discussion on level of priority given change in urgency due to compliance forbearance (add to TPRST scoping doc?) Wrap and confirm next meeting Confirm action items Next TPRST Meeting will be Thursday, 26 March 2020 at 16:00 UTC. Thank you. B Berry Cobb @berrycobb GNSO Policy Consultant

2 1

FW: Proposed Agenda: Transfer Policy Review Scoping Team Meeting - 19 Mar 2020 - 16:00 UTC
by policy＠bacinblack.com March 19, 2020

March 19, 2020

My apologies, I failed to send this agenda to the full list and only to Caitlin. Berry Cobb @berrycobb GNSO Policy Consultant From: policy(a)bacinblack.com <policy(a)bacinblack.com> Sent: Tuesday, March 17, 2020 14:22 To: 'Caitlin Tubergen' <caitlin.tubergen(a)icann.org> Subject: Proposed Agenda: Transfer Policy Review Scoping Team Meeting - 19 Mar 2020 - 16:00 UTC Dear All, Please find below the proposed agenda for this week’s call. Transfer Policy Review Scoping Team Meeting #6 Thursday, 19 March 2020 16:00 UTC Proposed Agenda 1. Roll Call & SOI Updates 2. Review Transfer Scoping Doc (link <https://docs.google.com/document/d/1sXxp5TsUskcrW444D6lYCLy6YX99Wyus/edit> ) a. Solicit input on highlighted areas b. Request to consolidate topics by T. Keller c. Agree on next steps (submit doc by 6 April, Council motion and docs deadline) * Discussion on level of priority given change in urgency due to compliance forbearance (add to TPRST scoping doc?) 3. Wrap and confirm next meeting a. Confirm action items b. Next TPRST Meeting will be Thursday, 26 March 2020 at 16:00 UTC. Thank you. B Berry Cobb @berrycobb GNSO Policy Consultant

1 0

ICANN Community Excellence Award - Nomination Closes 27 March 2020
by Andrea Glandon March 17, 2020

March 17, 2020

https://www.icann.org/news/announcement-2-2020-03-16-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ICANN Community Excellence Award: Nomination Closes 27 March 2020 LOS ANGELES – 16 March 2020 – The Internet Corporation for Assigned Names and Numbers (ICANN) reminds community members that the nomination period for ICANN's Community Excellence Award is open until 27 March 2020 23:59 Universal Coordinated Time (UTC). The ICANN Community Excellence Award recognizes community members who have significantly invested in consensus-based solutions and have contributed substantively to the ICANN multistakeholder model. The ideal recipient(s) will have: · Participated in the ICANN community for a minimum of five years. · Served in multiple ICANN working groups or committees. · Collaborated significantly with more than one Supporting Organization (SO) and/or Advisory Committee (AC). Candidates will be evaluated by a panel of community members appointed by the SO/AC chairs using a merit-based point system evaluated against three criteria: 1. Demonstrates an ability to work across community lines with both familiar and unfamiliar ICANN stakeholders with the aim of building consensus. 2. Facilitates dialogue and open discussion in a fair and collegial manner through the spirit of collaboration, showing empathy and demonstrating a sincere desire to engage with people from other backgrounds, cultures, and interests. 3. Demonstrates additional support for ICANN multistakeholder model and its overall effectiveness through volunteer service via working groups or committees. Please submit nominations via this nomination form [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_forms_…> and include detailed information outlining why the nominee meets the award criteria. Any additional information in support of nominations and/or questions about the award process may be submitted to exellenceaward2020(a)icann.org<mailto:excellenceaward2020@icann.org>. Award recipient(s) will be announced in June 2020 at ICANN68 in Kuala Lumpur. For more information on the award program, please refer to the ICANN Community Wiki.<https://community.icann.org/x/YyOAAw>

1 0

Re: [GNSO-TPRST] Notes and action items: Transfer Policy Review Scoping Team Meeting - 27 Feb 2020
by Thomas Keller March 12, 2020

March 12, 2020

Dear members, I would like to suggest that we incorporate the points Gaining & Losing Registrar Form of Authorization (“FOA”) Confusion around when inter-registrar transfers can be NACKed? Registrant experience/confusion AuthCode handling TechOps Proposed Transfer Process into one topic (aka “The Transfer Process”) as they are all interdependent. The TechOps Proposed Transfer Process should be the starting point for further discussion as it already addresses most of the issues, even though it does not provide final recommendations for all of them. Best tom Von: GNSO-TPRST <gnso-tprst-bounces(a)icann.org> im Auftrag von Caitlin Tubergen <caitlin.tubergen(a)icann.org> Datum: Donnerstag, 12. März 2020 um 05:24 An: "gnso-tprst(a)icann.org" <gnso-tprst(a)icann.org> Betreff: Re: [GNSO-TPRST] Notes and action items: Transfer Policy Review Scoping Team Meeting - 27 Feb 2020 Dear Scoping Team Members: In following up on Support Staff’s action item to update the Draft GNSO Scoping Document by Monday, 9 March, please review the updated version<https://docs.google.com/document/d/1sXxp5TsUskcrW444D6lYCLy6YX99Wyus/edit>, which no longer includes previous references to an EPDP, as the Team is no longer suggesting to move forward with an EPDP on Gaining Registrar FOAs. As you review the draft, please pay particular attention to the highlighted text. Please review the draft by Thursday, 19 March. As always, please only provide edits in suggestion mode. Thank you. Best regards, Berry and Caitlin From: Caitlin Tubergen <caitlin.tubergen(a)icann.org> Date: Thursday, February 27, 2020 at 9:42 AM To: "gnso-tprst(a)icann.org" <gnso-tprst(a)icann.org> Subject: Notes and action items: Transfer Policy Review Scoping Team Meeting - 27 Feb 2020 Dear Colleagues: Please find below the notes and action items from today’s Transfer Policy Review Scoping Team meeting. As a reminder, the next meeting will be Thursday, 19 March at 16:00 UTC. Support Staff will send calendar invites shortly. Best regards, Berry and Caitlin Transfer Policy Review Scoping Team Meeting #5 Thursday, 27 February 2020 16:00 UTC Action Items 1. Team Members to review section 3.11 of the ICANN Org Rec. 27 Wave 1 deliverable<https://gnso.icann.org/en/drafts/epdp-phase-1-recommendation-27-18feb20-en.…> in detail by Thursday, 5 March. Specifically, Team members should provide feedback if they support or do not support section 3.11. 2. In reviewing the Collaborative Issue Scoping Document<https://docs.google.com/document/d/1HXDmFuxSM6smWGga_Kc13bk2NYNsHlcQNm58S-0…>, Team to ensure: (1) the document is comprehensive; (2) relevant dependencies are identified; (3) urgency levels are identified; (4) whether the Team is recommending a “start from scratch” or “update the existing policy using the issues identified” by Thursday, 5 March. 3. Following Team’s updates to the Collaborative Issue Scoping Document<https://docs.google.com/document/d/1HXDmFuxSM6smWGga_Kc13bk2NYNsHlcQNm58S-0…>, Support Staff to update the Draft GNSO Scoping Document<https://docs.google.com/document/d/1sXxp5TsUskcrW444D6lYCLy6YX99Wyus/edit> by Monday, 9 March. Support Staff to remove previous references to EPDP, as the Team is no longer suggesting to move forward with an EPDP on Gaining Registrar FOAs. 4. Support Staff to draft and circulate a draft GNSO Council resolution, which would acknowledge the Scoping Team’s proposal to the Council and authorize ICANN org to start an Issues Report by Thursday, 26 March. 5. Beginning on Monday, 9 March, Team Members to review the Draft GNSO Scoping Document and provide proposed edits (in suggestion mode only) by Thursday, 19 March. Agenda 1. Roll Call & SOI Updates 2. Discussion of ICANN org Rec. 27 deliverable a. Background: this document represents ICANN Org’s Wave 1 deliverable<https://gnso.icann.org/en/drafts/epdp-phase-1-recommendation-27-18feb20-en.…> and identifies elements of Consensus Policies that will be affected as a result of EPDP implementation, e.g., elimination of the administrative field results in a change to the definition of Transfer Contact under the Transfer Policy · The EPDP Phase 1 Team recommended a survey of all existing consensus policies and the Wave 1 deliverable represents ICANN org staff’s in depth review of how the Phase 1 recommendations affect current ICANN consensus policies. · It is important that the TPRST read through this document. · Most issues identified in this report are already identified by this group in its scoping document, but this report dives into more specific detail. · This report also classifies the changes to the the Transfer Policy as HIGH impact, which is helpful for the Council’s prioritization exercise. Specifically, this shows why it is important for future Transfer Policy work to be addressed, as the Temp Spec and New Reg Data policy renders the Transfer Policy a “broken” consensus policy. TPRST reaction: · Action: TPRST to review section 3.11 of the ICANN Org Rec. 27 Wave 1 deliverable<https://gnso.icann.org/en/drafts/epdp-phase-1-recommendation-27-18feb20-en.…> in detail by Thursday, 5 March. Specifically, Team members should provide feedback if they support or do not support section 3.11 · Leadership and Support Staff foresee this Team to meet two more times (19 March and 26 March). b. Agree on next steps 4. Discuss path to completion of recommendation to GNSO Council b. Has the Scoping Team had sufficient time to identify Transfer Policy issues that need further policy work? 3. Reference docs: 1. Collaborative Issue Scoping Document<https://docs.google.com/document/d/1HXDmFuxSM6smWGga_Kc13bk2NYNsHlcQNm58S-0…> 2. Suggested model for how to proceed<https://docs.google.com/spreadsheets/d/1SkPzufLyU0Z8gbJdxsnF76EHanq7DZyt32K…> 3. Draft GNSO Scoping Document<https://docs.google.com/document/d/1sXxp5TsUskcrW444D6lYCLy6YX99Wyus/edit> · It seems that the group sees an advantage in multiple PDPs. · The GNSO Council will ultimately make the decision of how to proceed with the work. · The document still lists EPDP for the FOA issue, so this should be updated based on the group’s previous discussion that in light of the recent board resolution, the FOA issue does not need to go through an EPDP. For a normal PDP, ICANN staff would develop an Issues Report that would be reviewed by the GNSO Council. · As part of this Team’s deliverable to the GNSO Council, Support Staff’s suggestion would be to include a draft resolution, which would acknowledge the Scoping Team’s proposal and authorize ICANN org to start an Issues Report. · As a reminder, even if the group recommends a new PDP or series of PDPs, that work would most likely not start until one of the current PDPs finishes. In parallel, staff can develop the Issue Report. · Following the posting of the draft Issues report, the Final Issues report, which goes to the GNSO Council could include an accompanying document that represents a draft charter. This “draft charter” is not meant to preempt the work of the ultimate charter drafting team. It would, however, be helpful to provide a preliminary sizing on the amount of effort it will take to complete the proposed PDP or series of PDPs. The sizing will be impossible until there is an agreed scope of work to be done. · Once the issue report is finished, the final Issues Report will include a draft charter and a motion to launch a charter drafting team. · The Initial Issues Report would go out for public comment for the standard 40 days before the Final Issues Report goes to the GNSO Council. The core of the charter, such as the delivery schedule or rough sizing would be a section within the Issues Report. Note: The draft Charter should not be included in the public comment proceeding b/c it would be a distraction. c. Group composition preferences (open, experts only, represented) · There may be a compromise b/w an open model and a closed model. · Perhaps groups who do not wish to actively participate could have a representative(s) act in a “super observer capacity”. In other words, the representative(s) are not required to attend and participate in every meeting, but would be responsible for following the work and reporting back to their respective constituencies. The idea behind this is to ensure the PDP work would not “come as a surprise” to any group. General TPRST feedback: · Looking through the Initial Scoping Doc and the issues raised within it - if this goes through a normal PDP - this process seems cumbersome and takes a lot of time. Could these issues be fit into a single PDP or not more than two PDPs? · Burnout effect could be mitigated by multiple PDPs · Until we know what the exact scope is - at least from Staff’s perspective, what would be helpful to inform the Council - should issues be addressed one by one, or should we start from scratch? That is the most important question that the group needs to have a proposed answer on. · Not advocating for starting from scratch; however, that does have its merits d. Agree on next steps 5. Wrap and confirm next meeting o Confirm action items · Support Staff to update the GNSO Scoping Doc letter to remove the reference to EPDP · Support Staff to draft a proposed GNSO Council resolution, which will be submitted to the Council with the Scoping Document · Team Members to review section 3.11 of the ICANN Org Rec. 27 Wave 1 deliverable<https://gnso.icann.org/en/drafts/epdp-phase-1-recommendation-27-18feb20-en.…> in detail by Thursday, 5 March. Specifically, Team members should provide feedback if they support or do not support section 3.11 · Team Members to review the issues chart and ensure it is comprehensive (including urgency level) and include dependencies (if any) by Thursday, 6 March. · The Team needs to wrap by 3 April. · The Team will meet the 19th and 26th - by the 26 March, Support Staff can have the draft resolution. · From 9 March - 19 March, this Team can review the next version of the draft. · Document needs to be delivered to the GNSO Council by 6 April. o Next TPRST Meeting will be Thursday, 19 March 2020 at 16:00 UTC.

1 0

Notes and action items: Transfer Policy Review Scoping Team Meeting - 27 Feb 2020
by Caitlin Tubergen March 12, 2020

March 12, 2020

Dear Colleagues: Please find below the notes and action items from today’s Transfer Policy Review Scoping Team meeting. As a reminder, the next meeting will be Thursday, 19 March at 16:00 UTC. Support Staff will send calendar invites shortly. Best regards, Berry and Caitlin Transfer Policy Review Scoping Team Meeting #5 Thursday, 27 February 2020 16:00 UTC Action Items Team Members to review section 3.11 of the ICANN Org Rec. 27 Wave 1 deliverable in detail by Thursday, 5 March. Specifically, Team members should provide feedback if they support or do not support section 3.11. In reviewing the Collaborative Issue Scoping Document, Team to ensure: (1) the document is comprehensive; (2) relevant dependencies are identified; (3) urgency levels are identified; (4) whether the Team is recommending a “start from scratch” or “update the existing policy using the issues identified” by Thursday, 5 March. Following Team’s updates to the Collaborative Issue Scoping Document, Support Staff to update the Draft GNSO Scoping Document by Monday, 9 March. Support Staff to remove previous references to EPDP, as the Team is no longer suggesting to move forward with an EPDP on Gaining Registrar FOAs. Support Staff to draft and circulate a draft GNSO Council resolution, which would acknowledge the Scoping Team’s proposal to the Council and authorize ICANN org to start an Issues Report by Thursday, 26 March. Beginning on Monday, 9 March, Team Members to review the Draft GNSO Scoping Document and provide proposed edits (in suggestion mode only) by Thursday, 19 March. Agenda Roll Call & SOI Updates Discussion of ICANN org Rec. 27 deliverable Background: this document represents ICANN Org’s Wave 1 deliverable and identifies elements of Consensus Policies that will be affected as a result of EPDP implementation, e.g., elimination of the administrative field results in a change to the definition of Transfer Contact under the Transfer Policy · The EPDP Phase 1 Team recommended a survey of all existing consensus policies and the Wave 1 deliverable represents ICANN org staff’s in depth review of how the Phase 1 recommendations affect current ICANN consensus policies. · It is important that the TPRST read through this document. · Most issues identified in this report are already identified by this group in its scoping document, but this report dives into more specific detail. · This report also classifies the changes to the the Transfer Policy as HIGH impact, which is helpful for the Council’s prioritization exercise. Specifically, this shows why it is important for future Transfer Policy work to be addressed, as the Temp Spec and New Reg Data policy renders the Transfer Policy a “broken” consensus policy. TPRST reaction: Action: TPRST to review section 3.11 of the ICANN Org Rec. 27 Wave 1 deliverable in detail by Thursday, 5 March. Specifically, Team members should provide feedback if they support or do not support section 3.11 Leadership and Support Staff foresee this Team to meet two more times (19 March and 26 March). Agree on next steps 4. Discuss path to completion of recommendation to GNSO Council Has the Scoping Team had sufficient time to identify Transfer Policy issues that need further policy work? c. Reference docs: Collaborative Issue Scoping Document Suggested model for how to proceed Draft GNSO Scoping Document It seems that the group sees an advantage in multiple PDPs. The GNSO Council will ultimately make the decision of how to proceed with the work. The document still lists EPDP for the FOA issue, so this should be updated based on the group’s previous discussion that in light of the recent board resolution, the FOA issue does not need to go through an EPDP. For a normal PDP, ICANN staff would develop an Issues Report that would be reviewed by the GNSO Council. As part of this Team’s deliverable to the GNSO Council, Support Staff’s suggestion would be to include a draft resolution, which would acknowledge the Scoping Team’s proposal and authorize ICANN org to start an Issues Report. As a reminder, even if the group recommends a new PDP or series of PDPs, that work would most likely not start until one of the current PDPs finishes. In parallel, staff can develop the Issue Report. Following the posting of the draft Issues report, the Final Issues report, which goes to the GNSO Council could include an accompanying document that represents a draft charter. This “draft charter” is not meant to preempt the work of the ultimate charter drafting team. It would, however, be helpful to provide a preliminary sizing on the amount of effort it will take to complete the proposed PDP or series of PDPs. The sizing will be impossible until there is an agreed scope of work to be done. Once the issue report is finished, the final Issues Report will include a draft charter and a motion to launch a charter drafting team. The Initial Issues Report would go out for public comment for the standard 40 days before the Final Issues Report goes to the GNSO Council. The core of the charter, such as the delivery schedule or rough sizing would be a section within the Issues Report. Note: The draft Charter should not be included in the public comment proceeding b/c it would be a distraction. Group composition preferences (open, experts only, represented) · There may be a compromise b/w an open model and a closed model. · Perhaps groups who do not wish to actively participate could have a representative(s) act in a “super observer capacity”. In other words, the representative(s) are not required to attend and participate in every meeting, but would be responsible for following the work and reporting back to their respective constituencies. The idea behind this is to ensure the PDP work would not “come as a surprise” to any group. General TPRST feedback: Looking through the Initial Scoping Doc and the issues raised within it - if this goes through a normal PDP - this process seems cumbersome and takes a lot of time. Could these issues be fit into a single PDP or not more than two PDPs? · Burnout effect could be mitigated by multiple PDPs · Until we know what the exact scope is - at least from Staff’s perspective, what would be helpful to inform the Council - should issues be addressed one by one, or should we start from scratch? That is the most important question that the group needs to have a proposed answer on. · Not advocating for starting from scratch; however, that does have its merits Agree on next steps 5. Wrap and confirm next meeting Confirm action items · Support Staff to update the GNSO Scoping Doc letter to remove the reference to EPDP · Support Staff to draft a proposed GNSO Council resolution, which will be submitted to the Council with the Scoping Document · Team Members to review section 3.11 of the ICANN Org Rec. 27 Wave 1 deliverable in detail by Thursday, 5 March. Specifically, Team members should provide feedback if they support or do not support section 3.11 · Team Members to review the issues chart and ensure it is comprehensive (including urgency level) and include dependencies (if any) by Thursday, 6 March. · The Team needs to wrap by 3 April. · The Team will meet the 19th and 26th - by the 26 March, Support Staff can have the draft resolution. · From 9 March - 19 March, this Team can review the next version of the draft. · Document needs to be delivered to the GNSO Council by 6 April. Next TPRST Meeting will be Thursday, 19 March 2020 at 16:00 UTC.

2 2