Maureen Hilyard maureen.hilyard at gmail.com
Mon Aug 26 23:35:25 UTC 2019

---------- Forwarded message ---------
From: Mary Wong <mary.wong at icann.org>
Date: Mon, 26 Aug 2019, 1:34 PM
Subject: FOLLOWING UP: ICANN66 & DNS Abuse
To: jrobinson at afilias.info <jrobinson at afilias.info>, Manal Ismail <
manal at tra.gov.eg>, Steve DelBianco <sdelbianco at netchoice.org>, Cathrin
Bauer-Bulst <Cathrin.BAUER-BULST at ec.europa.eu>, Kapin, Laureen <
LKAPIN at ftc.gov>, Maureen Hilyard <maureen.hilyard at gmail.com>, Mark
Svancarek (CELA) <marksv at microsoft.com>, Romero, Gonzalo <
gonzalo at cointernet.com.co>, Rod Rasmussen <rod at rodrasmussen.com>, Julie
Hammer @Bigpond <julie.hammer at bigpond.com>, Brian Winterfeldt
<Brian at winterfeldt.law>, gbunton at tucows.com <gbunton at tucows.com>
Cc: Keith Drazek <kdrazek at verisign.com>, Austin, Donna
<Donna.Austin at team.neustar>, Alejandra Reynoso <alejandra.reynoso at cctld.gt>,
Carlos Reyes <carlos.reyes at icann.org>, Tanzanica S. King <
tanzanica.king at icann.org>, Zoe Bonython <secretariat at icannregistrars.org>,
secretariat at rysg.info <secretariat at rysg.info>, Steve Sheng <
steve.sheng at icann.org>, Joke Braeken <joke.braeken at icann.org>, Chantelle
Doerksen <chantelle.doerksen at icann.org>, Fabien Betremieux <
fabien.betremieux at icann.org>, Robert Hoggarth <robert.hoggarth at icann.org>,
Heidi Ullrich <Heidi.Ullrich at icann.org>

Dear all,

I write in relation to the agreed pre-ICANN66 informational webinar (to be
scheduled during Prep Week, which runs from 14-17 October) and the plenary
session to be held during the ICANN66 Meeting itself, on DNS Abuse. I’ve
included those who staff recalls from the ALAC, BC, ccNSO, GAC, IPC, RrSG,
RySG and SSAC had expressed interest in participating in and/or supporting
these sessions, but please let me know if I have missed anyone (or added
anyone who doesn’t wish to be part of the planning process!)

As this is the first time that we will be doing a pre-Meeting informational
webinar, followed by the actual plenary session, and as we have multiple
community groups involved in planning and executing these sessions, I hope
it will be helpful to suggest that this group begin to discuss the
following points:

   1. *What should the pre-Meeting informational webinar cover, and what
   should the Montreal plenary session cover?*

   - You can find the topic descriptions as submitted here:

   - As submitted by the GAC: *“This session approaches the topic of DNS
   Abuse by first looking at the key practical issues followed by a
   facilitated community discussion. DNS Abuse takes a variety of forms, and
   the session will explore – using definitions and examples – what type of
   conduct has traditionally been labelled “DNS Abuse”, an important precursor
   to arriving at a joint definition of DNS Abuse. In a second step, the
   session will explore how registry and registrar operators mitigate and
   address DNS Abuse/security threats, by looking at examples of prevention
   and mitigation measures. Following that, the session will provide a gap
   analysis of issues left to address – including possible challenges to
   prevention and mitigation measures. This session will include discussion of
   how evolving legal and regulatory frameworks put DNS Abuse investigations
   and mitigations performed by 3rd parties at risk, how aware lawmakers and
   regulators of these risks, how governments are working together to bring
   clarity to these issues, and actions the ICANN community can take based on
   the experience it has accumulated on this matter over time and most
   recently through several processes including the CCT Review, the Domain
   Abuse Activity Reporting and the DNS Infrastructure Abuse Audits.*”
   - As submitted by the RySG: *“This session approaches the currently "hot
   topic" of DNS Abuse by first looking at the key practical issues followed
   by a facilitated community discussion. First, we'll take a focused look at
   ICANN's bylaws and remit and next, explore how registry and registrar
   operators mitigate and address DNS Abuse/security threats in that context.
   Third, the community will be invited to discuss issues arising and proposed

   1. *Assuming that all the interested groups will wish to be involved in
   both the webinar and plenary session, how shall we proceed in terms of who
   will do what for both, and in light of the recent open letter to the ICANN
   community from the RySG (reattached for your convenience)?*

Staff will be happy to organize a call to discuss these preliminary
matters; we just thought it may be helpful to kickstart the discussions by
connecting everyone via email.

For your information, and as has been the practice with previous
cross-community and high-interest topics, an ICANN Org Senior Executive
will be tasked with assisting you with your planning, with relevant
Meetings and Policy team staff to help manage logistics and overall session
management (including a proposed date and time for the pre-Meeting
webinar). I will get back to you with further details very shortly. Thank


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://atlarge-lists.icann.org/pipermail/gtld-wg/attachments/20190826/e18d1656/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 20190819 RYSG open letter to community re security threats.pdf
Type: application/pdf
Size: 328658 bytes
Desc: not available
URL: <http://atlarge-lists.icann.org/pipermail/gtld-wg/attachments/20190826/e18d1656/20190819RYSGopenlettertocommunityresecuritythreats-0001.pdf>
-------------- next part --------------
CPWG mailing list
CPWG at icann.org

By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

More information about the GTLD-WG mailing list