July 2025 - gnso-dnsabuse-smallteam

Update: Draft Documents: 24 July 2025 Meeting Notes
by Feodora Hamza July 25, 2025

July 25, 2025

Dear DNS Abuse Small Team, In addition to below, please find the updated documents for your review prior to the next of the Small Team. Please provide your comments directly into the document by 30 July. * Draft Motion: https://docs.google.com/document/d/1QUEuJuxG9tyA0k-qKV_UR_FwDNnRsix2/edit?u… * Updated Draft Report: https://docs.google.com/document/d/18AMsedMhKEox1196No0yS6ktqFbcTs2l/edit?u… (main changes are highlighted in the document) Kind regards, Feodora on behalf of the support team From: Steve Chan via gnso-dnsabuse-smallteam <gnso-dnsabuse-smallteam(a)icann.org> Reply to: Steve Chan <steve.chan(a)icann.org> Date: Thursday, 24 July 2025 at 19:10 To: "gnso-dnsabuse-smallteam(a)icann.org" <gnso-dnsabuse-smallteam(a)icann.org> Subject: [gnso-dnsabuse-smallteam] 24 July 2025 Meeting Notes Dear DNS Abuse Small Team, Please see below the meeting notes and action items from our 24 July meeting of the DNS Abuse Small Team. Best, Steve Action Items: 1. Leadership and staff to propose a way to include the secondary priorities. This will likely include a table, an additional recommendation, and an explanatory paragraph about methodology. 2. Clarify the text in the report that the prioritized issues might not all warrant policy development. Notes: 1. Welcome * Hopefully wrapping up on recommendations today. 2. Final Input on Gaps Matrix * Streamlined gap IDs and associated them to the Phases/Lifecycle Category. Kept, but hid the original gap IDs since the stakeholder comments sometimes referenced them. * Hopefully close the matrix today. Try and limit to “can’t live with” type concerns, if any. 3. Review Update Draft Report * Added recommendations 2 and 3, which suggest focusing on limited topics for the first PDP coming out of the Issue Report, as well as which topics to concentrate on. * What is the proper terminology in respect of “bulk registrations”? Settled on just referencing domain names. 3.a Main Gaps for Issue Report * The various groups have provided input about which gaps should be prioritized, generally as comments in draft report. * The NCSG’s priority is for a dispute resolution mechanism/access to remedy. * If there is a difference in opinion on the priorities, how should we reconcile? Specifically, how should the additional topics be captured (e.g., NCSG and CSG gaps). * What is currently included is where there seems to be convergence. Are the additional gaps points of convergence? * Validation seems more appropriate for Council level discussion. * Confirmation: the prioritized gaps will not result in the additional gaps being dropped. * Is it better to determine priority once the Issue Report is completed, since part of the Issue Report determines whether the gap is within ICANN’s remit and GNSO policy making? * The Council could change course on the prioritized topics once the Issue Report is delivered. * The prioritized topics facilitate staff’s ability prepare the draft charter. * Could parallel work continue on determining the prioritizing for future work? May result in resourcing issues. And probably should wait for the completion of the Issue Report. Could add a point in the small team’s report to note that this additional work could carry on. * Request for a visualization of the priorities of the various groups. May make sense to include as text. Options to consider include: * Add a recommendation 4 that includes topics for a subsequent PDP * And/or include a description of methodology for identifying the top three priorities. * No objections from NCSG to focus on 3 gaps identified. * Unclear whether DGA topic requires policy work. The Issue Report will likely uncover whether or not this is well suited for a PDP or perhaps another mechanism. The CPH has some text that helps justify why policy work might be warranted. Action Item: Leadership and staff to propose a way to include the secondary priorities. This will likely include a table, an additional recommendation, and an explanatory paragraph about methodology. Action Item: Clarify the text in the report that the prioritized issues might not all warrant policy development. 4. Review Draft Motion * The text might need to be adjusted (e.g., if there is another gap to include, or if the small team wants to identify that policy development might not be appropriate for all topics). * Question about Whereas 3, which references reaching out to GAC. Might be more accurate to reference the GAC Advice. Could also include mention of coordination through the GNSO’s liaison to the GAC. 5. AOB * FYI - GNSO support staff has reached out to SSAC support staff to provide an update on the small team and to note that the SSAC will have an opportunity to provide public comment on the Issue Report. Steven Chan  VP, Policy Development Support & GNSO Relations Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org<mailto:steve.chan@icann.org> Skype: steve.chan55 Mobile: +1.310.339.4410 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

24 July 2025 Meeting Notes
by Steve Chan July 24, 2025

July 24, 2025

Dear DNS Abuse Small Team, Please see below the meeting notes and action items from our 24 July meeting of the DNS Abuse Small Team. Best, Steve Action Items: 1. Leadership and staff to propose a way to include the secondary priorities. This will likely include a table, an additional recommendation, and an explanatory paragraph about methodology. 2. Clarify the text in the report that the prioritized issues might not all warrant policy development. Notes: 1. Welcome * Hopefully wrapping up on recommendations today. 2. Final Input on Gaps Matrix * Streamlined gap IDs and associated them to the Phases/Lifecycle Category. Kept, but hid the original gap IDs since the stakeholder comments sometimes referenced them. * Hopefully close the matrix today. Try and limit to “can’t live with” type concerns, if any. 3. Review Update Draft Report * Added recommendations 2 and 3, which suggest focusing on limited topics for the first PDP coming out of the Issue Report, as well as which topics to concentrate on. * What is the proper terminology in respect of “bulk registrations”? Settled on just referencing domain names. 3.a Main Gaps for Issue Report * The various groups have provided input about which gaps should be prioritized, generally as comments in draft report. * The NCSG’s priority is for a dispute resolution mechanism/access to remedy. * If there is a difference in opinion on the priorities, how should we reconcile? Specifically, how should the additional topics be captured (e.g., NCSG and CSG gaps). * What is currently included is where there seems to be convergence. Are the additional gaps points of convergence? * Validation seems more appropriate for Council level discussion. * Confirmation: the prioritized gaps will not result in the additional gaps being dropped. * Is it better to determine priority once the Issue Report is completed, since part of the Issue Report determines whether the gap is within ICANN’s remit and GNSO policy making? * The Council could change course on the prioritized topics once the Issue Report is delivered. * The prioritized topics facilitate staff’s ability prepare the draft charter. * Could parallel work continue on determining the prioritizing for future work? May result in resourcing issues. And probably should wait for the completion of the Issue Report. Could add a point in the small team’s report to note that this additional work could carry on. * Request for a visualization of the priorities of the various groups. May make sense to include as text. Options to consider include: * Add a recommendation 4 that includes topics for a subsequent PDP * And/or include a description of methodology for identifying the top three priorities. * No objections from NCSG to focus on 3 gaps identified. * Unclear whether DGA topic requires policy work. The Issue Report will likely uncover whether or not this is well suited for a PDP or perhaps another mechanism. The CPH has some text that helps justify why policy work might be warranted. Action Item: Leadership and staff to propose a way to include the secondary priorities. This will likely include a table, an additional recommendation, and an explanatory paragraph about methodology. Action Item: Clarify the text in the report that the prioritized issues might not all warrant policy development. 4. Review Draft Motion * The text might need to be adjusted (e.g., if there is another gap to include, or if the small team wants to identify that policy development might not be appropriate for all topics). * Question about Whereas 3, which references reaching out to GAC. Might be more accurate to reference the GAC Advice. Could also include mention of coordination through the GNSO’s liaison to the GAC. 5. AOB * FYI - GNSO support staff has reached out to SSAC support staff to provide an update on the small team and to note that the SSAC will have an opportunity to provide public comment on the Issue Report. Steven Chan  VP, Policy Development Support & GNSO Relations Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org<mailto:steve.chan@icann.org> Skype: steve.chan55 Mobile: +1.310.339.4410 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

Post Call | GNSO Council DNS Abuse Small Team meeting | 24 July 2025
by Devan Reed July 24, 2025

July 24, 2025

Dear all, Please use link below to access the attendance and the recording links on the small team wiki page for the GNSO Council DNS Abuse Small Team meeting held on Thursday, 24 July 2025 at 14:00 UTC. DNS Abuse Small Team Wiki: https://icann-community.atlassian.net/wiki/x/iQCiCg Thank you! Kind regards, Devan Policy Team Supporting the GNSO

1 0

Meeting Invitation | GNSO Council's DNS Abuse Small Team call | Thursday, 31 July 2025
by Devan Reed July 24, 2025

July 24, 2025

Dear all, The next call for the GNSO Council's DNS Abuse Small Team will take place on Thursday, 31 July 2025 at 14:00 UTC for 60 minutes. Join from PC, Mac, iPad, or Android: Zoom Webinar link: https://icann.zoom.us/j/91555564642?pwd=QnlKeXhycVVJdklMUHJTTjlsdnhRQT09 Passcode:4^NT$6A9$. Audio only: Webinar ID: 915 5556 4642 Passcode: 6982547835 International numbers available: https://icann.zoom.us/u/abKXhMNgh Wiki space: https://icann-community.atlassian.net/wiki/x/iQCiCg Thank you. Kind regards, Devan Policy Team Supporting the GNSO

1 0

Input to the DNS Abuse Small Team: ICANN83 CPH DNS Abuse Community Update
by jen＠dot.asia July 24, 2025

July 24, 2025

Dear All, Please find attached the CPH DNS Abuse WG session report and input to further our discussions tomorrow. The report is directed to the GNSO Council, but is relevant to our work. In particular I note that in the last paragraph of the report the CPH DNS Abuse WG has responded to our draft text as follows: "Finally, the CPH DNS Abuse WG encourages the GNSO Council to start a PDP on DNS Abuse Mitigation by requesting an Issues Report that focuses on one of the preventative measures discussed on this session report: 1) A Requirement to Pivot on Actionable Reports of Malicious Registered Domains, 2) Strengthening of API Clauses to address bulk registrations, and 3) Discussing a gTLD-wide operational and policy framework to mitigate Botnet DGAs at scale." Best, Jen -----Original Message----- From: Owen Smigelski <owen.smigelski(a)namecheap.com> Sent: Wednesday, July 23, 2025 7:42 PM To: jen(a)dot.asia Cc: Elizabeth Bacon <beth(a)pir.org>; GNSO-Secs <gnso-secs(a)icann.org> Subject: ICAN83 CPH DNS Abuse Community Update Hi Jen, On behalf of the CPH, attached is the "ICANN 83 Session Report: CPH DNS Abuse Community Update” for consideration by the GNSO Council prior to tomorrow’s meeting. Please let us know if you need anything further regarding this update. Regards, Owen & Beth

2 1

15 MINUTES REMINDER | Meeting Invitation | GNSO Council's DNS Abuse Small Team call | Thursday, 24 July 2025
by Devan Reed July 24, 2025

July 24, 2025

Dear all, The next call for the GNSO Council's DNS Abuse Small Team will take place on Thursday, 24 July 2025 at 14:00 UTC for 60 minutes. Join from PC, Mac, iPad, or Android: Zoom Webinar link: https://icann.zoom.us/j/91555564642?pwd=QnlKeXhycVVJdklMUHJTTjlsdnhRQT09 Passcode:4^NT$6A9$. Audio only: Webinar ID: 915 5556 4642 Passcode: 6982547835 International numbers available: https://icann.zoom.us/u/abKXhMNgh Wiki space: https://icann-community.atlassian.net/wiki/x/iQCiCg Thank you. Kind regards, Julie Policy Team Supporting the GNSO

1 0

Proposed Agenda DNS Abuse Small Team Meeting 24 July 14:00 UTC
by Feodora Hamza July 23, 2025

July 23, 2025

Dear DNS Abuse Small Team, Please find below the proposed agenda for tomorrows Small Team call. DNS Abuse Agenda 24 July 2025 14:00 UTC 1) Welcome (5min) 2) Final Input on Gaps Matrix<https://docs.google.com/spreadsheets/d/18PdZnH3OQ65NT9g0lGE6Y2toFaCrtxyf/ed…> (10min) 3) Review Updated Draft Report<https://docs.google.com/document/d/18AMsedMhKEox1196No0yS6ktqFbcTs2l/edit?u…> (30min) a. Main Gaps for Issue Report 4) Review Draft Motion (10min) 5) AOB (5min) Kind regards, Feodora on behalf of the Support Team

1 0

Re: 17 July 2025 Meeting Notes
by Feodora Hamza July 23, 2025

July 23, 2025

Dear DNS Abuse Small Team, Just a kind reminder on the pending action items below. 1. AI: Each group to come up with top 3 priorities for next week’s meeting that are appropriate for policy development. 2. AI: Leadership and staff to provide priorities list for discussion and reaction from input already received. 3. AI: Staff will start preparing the draft motion to present to small team to provide feedback With regards to AI 2, please see the following document for your further review: * Draft Report [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/18AMsedMhKEox…> (Section 2) Kind regards, Feodora on behalf of the Support Team From: John Emery via gnso-dnsabuse-smallteam <gnso-dnsabuse-smallteam(a)icann.org> Reply to: John Emery <john.emery(a)icann.org> Date: Friday, 18 July 2025 at 17:39 To: "gnso-dnsabuse-smallteam(a)icann.org" <gnso-dnsabuse-smallteam(a)icann.org> Subject: [gnso-dnsabuse-smallteam] 17 July 2025 Meeting Notes Dear DNS Abuse Small Team, Please see attached below the meeting notes and action items from our 17 July meeting of the DNS Abuse Small Team. Please look out for an email from Jen later today with the leadership and staff priorities list based on Small Team input thus far for discussion. DNS Abuse Small Team Wiki [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/iQC…> Slides [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/downl…> ACTION ITEMS AI: Each group to come up with top 3 priorities for next week’s meeting that are appropriate for policy development. AI: Leadership and staff to provide priorities list for discussion and reaction from input already received. AI: Staff will start preparing the draft motion to present to small team to provide feedback 1. Welcome 2. Update on Preliminary Recommendations Document * Update on the Draft Report [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/18AMsedMhKEox…> with additional two recommendations for discussion * The chart at the end of the document was removed and the full list of gaps in the matrix [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/18PdZnH3O…> * Updated the list of gaps in the matrix including the phases and merged agreed upon cells and integrated CSG and NCSG input 3. Discussion on Issue Report * Previously 1 issue report resulted in 1 PDP, this Issue report will look more deeply in the list of gaps and will encompass all of that * Result of this one issue report will be a narrowly chartered PDP on one or two topics/gaps to complete the work expeditiously. * Subsequent PDPs could be initiated from this original issue report when the initial PDP completes it work 4. Discussion on “Prioritization” * How would we like to prioritize there have been indications of SGs/Cs for what should be prioritized * Who will decide? This will be a Council decision, the Small Team can recommend from the prioritization exercise. * Good to have priorities here to then make a recommendation to Council and then while Issue report is being worked on there may be other factors to consider * Suggestion to launch next PDP during public comment period going with a single issue report * As PDP is underway the next step can be a chartering team for the next set of work In the Chat: CSG priorities are: 1. Associated domain check. 2. Continual review and update of DNS abuse definitions. 3. Validation of registrant details. 4. Access to bulk / API registrations * Caution prioritization exercise from Council that a continuing small team. A PDP, a charter drafting team, a small team, and another PDP there could be resource constraints * How this Small Team wants to prioritize with the At Large priorities in the slides [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/downl…> * ALAC input based on the matrix and were careful not to go into solutions to provide input on the gap itself. The possible solutions list can be litigated later as it is a raw list based on the matrix. * ALAC list could be revised based on how the inputs will be resolved and the priorities of the other groups * Do we prioritize low hanging fruit? For those items for the first PDP, do they necessarily need to be topics where PDPs are appropriate to address? * Calling for the issue report will lay foundational work for the first and subsequent PDPs. This will be looking at whether the gaps will be fit for PDP. * AI: each group come up with top 3 priorities for next week’s meeting that are appropriate for policy development * Also CPH DNS Abuse working group will have something coming along soon * Determine what is a PDP focus and what is for other parts of the community. We can cover more gaps if some things should just be referred back to ICANN compliance * Intention is to focus on what makes most sense for inclusion in PDP specifically, framing for low hanging fruit. PDP work with topics that are important and impactful, wide agreement, and perhaps easier to implement * Reminder: only two more meetings with this Small Team * AI: Leadership and staff to provide priorities list for discussion and reaction from input already received * There is a time crunch meeting on the 31st need to have finalized recommendation and matrix for the annex for the 4 August deadline * Limiting scope to topics appropriate for policy development and put in writing the low hanging fruit * AI: Staff will start preparing the draft motion 5. AOB- Next Steps John R. Emery, Ph.D. Policy Development Support Senior Specialist Generic Names Supporting Organization (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

REMINDER | Meeting Invitation | GNSO Council's DNS Abuse Small Team call | Thursday, 24 July 2025
by Terri Agnew July 23, 2025

July 23, 2025

Dear all, The next call for the GNSO Council's DNS Abuse Small Team will take place on Thursday, 24 July 2025 at 14:00 UTC for 60 minutes. Join from PC, Mac, iPad, or Android: Zoom Webinar link: https://icann.zoom.us/j/91555564642?pwd=QnlKeXhycVVJdklMUHJTTjlsdnhRQT09 Passcode:4^NT$6A9$. Audio only: Webinar ID: 915 5556 4642 Passcode: 6982547835 International numbers available: https://icann.zoom.us/u/abKXhMNgh Wiki space: https://icann-community.atlassian.net/wiki/x/iQCiCg Thank you. Kind regards, Julie Policy Team Supporting the GNSO

1 0

DNS Abuse Small Team: draft text on prioritization of issues
by jen＠dot.asia July 18, 2025

July 18, 2025

Dear All, Following the notes from our call yesterday, here are the prioritized list of three issues for ST members to bring back to their SG/Cs for reaction, discussion and additional input for our call next week (Thursday August 24). During our call we also discussed context and reframing for this prioritization exercise to limit this to what we have termed “Low Hanging Fruit”: Rationale/Low Hanging Fruit: Limited to topics that seem appropriate for policy development (taking into consideration review of source data, input/priorities received by ST members and Community consultation during ICANN83) * "Low hanging fruit" can mean: * i) important/impactful gap to solve * ii) likely to gain broad consensus * iii) ideally, the potential solution(s) seem uncomplicated. For consideration for input into the Draft report <https://docs.google.com/document/d/18AMsedMhKEox1196No0yS6ktqFbcTs2l/edit> : Recommendation 3: Prioritize the following Three Issues. (rationale/explanation to be further updated for the draft report – pending ST input) Based on data analysis, community consultation, and input from stakeholder groups, the Small Team recommends the following three issues be prioritized for early scoping and possible PDP initiation under the Issue Report: * Unrestricted API access for new customers: The INFERMAL study and other community inputs indicate a strong correlation between abuse and unrestricted API-enabled bulk registrations. * Associated Domain Checks: The CPH update during ICANN83 indicated that there is currently no contractual requirement or best practice standard requiring contracted parties to investigate domains associated with known malicious actors. * Limited coordination on DGA-based abuse: The current system for responding to Domain Generation Algorithm (DGA)-based threats commonly used in botnets and malware campaigns seems to be fragmented. No single trusted platform or protocol for real-time information sharing between registries, registrars, hosting providers, and law enforcement means fragmentation causing delays and inconsistent responses. Best, Jen From: John Emery via gnso-dnsabuse-smallteam <gnso-dnsabuse-smallteam(a)icann.org> Sent: Friday, July 18, 2025 11:39 AM To: gnso-dnsabuse-smallteam(a)icann.org Subject: [gnso-dnsabuse-smallteam] 17 July 2025 Meeting Notes Dear DNS Abuse Small Team, Please see attached below the meeting notes and action items from our 17 July meeting of the DNS Abuse Small Team. Please look out for an email from Jen later today with the leadership and staff priorities list based on Small Team input thus far for discussion. DNS Abuse Small Team Wiki <https://icann-community.atlassian.net/wiki/x/iQCiCg> Slides <https://icann-community.atlassian.net/wiki/download/attachments/178389129/1…> ACTION ITEMS AI: Each group to come up with top 3 priorities for next week’s meeting that are appropriate for policy development. AI: Leadership and staff to provide priorities list for discussion and reaction from input already received. AI: Staff will start preparing the draft motion to present to small team to provide feedback 1. Welcome 2. Update on Preliminary Recommendations Document * Update on the Draft Report <https://docs.google.com/document/d/18AMsedMhKEox1196No0yS6ktqFbcTs2l/edit?u…> with additional two recommendations for discussion * The chart at the end of the document was removed and the full list of gaps in the matrix <https://docs.google.com/spreadsheets/d/18PdZnH3OQ65NT9g0lGE6Y2toFaCrtxyf/ed…> * Updated the list of gaps in the matrix including the phases and merged agreed upon cells and integrated CSG and NCSG input 3. Discussion on Issue Report * Previously 1 issue report resulted in 1 PDP, this Issue report will look more deeply in the list of gaps and will encompass all of that * Result of this one issue report will be a narrowly chartered PDP on one or two topics/gaps to complete the work expeditiously. * Subsequent PDPs could be initiated from this original issue report when the initial PDP completes it work 4. Discussion on “Prioritization” * How would we like to prioritize there have been indications of SGs/Cs for what should be prioritized * Who will decide? This will be a Council decision, the Small Team can recommend from the prioritization exercise. * Good to have priorities here to then make a recommendation to Council and then while Issue report is being worked on there may be other factors to consider * Suggestion to launch next PDP during public comment period going with a single issue report * As PDP is underway the next step can be a chartering team for the next set of work In the Chat: CSG priorities are: 1. Associated domain check. 2. Continual review and update of DNS abuse definitions. 3. Validation of registrant details. 4. Access to bulk / API registrations * Caution prioritization exercise from Council that a continuing small team. A PDP, a charter drafting team, a small team, and another PDP there could be resource constraints * How this Small Team wants to prioritize with the At Large priorities in the slides <https://icann-community.atlassian.net/wiki/download/attachments/178389129/1…> * ALAC input based on the matrix and were careful not to go into solutions to provide input on the gap itself. The possible solutions list can be litigated later as it is a raw list based on the matrix. * ALAC list could be revised based on how the inputs will be resolved and the priorities of the other groups * Do we prioritize low hanging fruit? For those items for the first PDP, do they necessarily need to be topics where PDPs are appropriate to address? * Calling for the issue report will lay foundational work for the first and subsequent PDPs. This will be looking at whether the gaps will be fit for PDP. * AI: each group come up with top 3 priorities for next week’s meeting that are appropriate for policy development * Also CPH DNS Abuse working group will have something coming along soon * Determine what is a PDP focus and what is for other parts of the community. We can cover more gaps if some things should just be referred back to ICANN compliance * Intention is to focus on what makes most sense for inclusion in PDP specifically, framing for low hanging fruit. PDP work with topics that are important and impactful, wide agreement, and perhaps easier to implement * Reminder: only two more meetings with this Small Team * AI: Leadership and staff to provide priorities list for discussion and reaction from input already received * There is a time crunch meeting on the 31st need to have finalized recommendation and matrix for the annex for the 4 August deadline * Limiting scope to topics appropriate for policy development and put in writing the low hanging fruit * AI: Staff will start preparing the draft motion 5. AOB- Next Steps John R. Emery, Ph.D. Policy Development Support Senior Specialist Generic Names Supporting Organization (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org <http://www.icann.org>

1 0