<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div>Thanks Rubens. The use of "best practices" was in the original version that contracted parties sent around - I was pretty proud that I was able to keep it in! </div><div><br></div><div>Regarding your other comment, I guess I do't know where that leaves us since at least the GAC seems to know what abuses are. How do we solve this?</div><div><br></div><div>Best,</div><div>Paul</div><div><br></div><div><br></div><div><br></div>
<blockquote id="replyBlockquote" webmail="1" style="border-left: 2px solid blue; margin-left: 8px; padding-left: 8px; font-size:10pt; color:black; font-family:verdana;">
<div id="wmQuoteWrapper">
-------- Original Message --------<br>
Subject: Re: [council] For your review - GNSO Review of GAC Communique<br>
Hyderabad<br>
From: Rubens Kuhl <<a href="mailto:rubensk@nic.br">rubensk@nic.br</a>><br>
Date: Mon, December 12, 2016 2:30 pm<br>
To: <a href="mailto:policy@paulmcgrady.com">policy@paulmcgrady.com</a><br>
Cc: Marika Konings <<a href="mailto:marika.konings@icann.org">marika.konings@icann.org</a>>, "<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>"<br>
<<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>><br>
<br>
<div class=""><br class=""></div>Paul,<div class=""><br class=""></div><div class="">Setting apart what the role of ICANN and contracted parties are in this matter, we need to be aware that there are fundamental limitations that would prevent any of such entities to do what is described in the text. </div><div class=""><br class=""></div><div class="">Currently, there is no Computer Science standard to define what is an abuse, its taxonomies or how to report them; it's not much different from the famous obscenity definition: "I know it when I see it.". So even if we somehow put ICANN in the role of making such standards, which would be unprecedented since standards in this area until now came from ISO, IETF, M3AAWG and APWG, it would fail miserably due to lack of a theoretical framework to base such standards on. </div><div class=""><br class=""></div><div class="">That's why most of the work in the Information Security field refer to "practices"; this allow for not hardcoding a phenomena that is always fast evolving and be more effective by being more adaptable. </div><div class="">I would even challenge the use of "best practices" in the context below since it would require a greater level adoption in the field, but this is a confusion that is already widely spread in a number of ICANN documents, unfortunately. </div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Rubens</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">Em 12 de dez de 2016, à(s) 18:10:000, <a target="_blank" href="mailto:policy@paulmcgrady.com" class="">policy@paulmcgrady.com</a> escreveu:</div><br class="Apple-interchange-newline"><div class=""><span style="font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-family: Verdana; font-size: 10pt;" class=""><div class="">Hi All,</div><div class=""><br class=""></div><div class="">The IPC has had a chance to consider the draft language for Section 2 and propose the following (heavily) edited draft response:</div><div class=""><span style="font-size: 10pt;" class=""><br class=""></span></div><div class=""><span style="font-size: 10pt;" class="">___________________________</span></div><div class="MsoNormal" style="font-size:12pt;;"><span lang="EN-GB" class="">The GNSO Council would like to express concern that the list of questions set out in Annex 1 has been categorised as “advice”. <span class="Apple-converted-space"> </span></span><span class="">In this context,<span class="Apple-converted-space"> </span></span><span lang="EN-GB" class="">the term “advice” ought to be given its ordinary dictionary meaning, and a request to the Board to provide various data and information does not<span class="Apple-converted-space"> </span></span><span class="">constitute “GAC Advice”, as this term is used in the ICANN Bylaws. Since GAC Advice<span class="Apple-converted-space"> </span></span><span lang="EN-GB" class="">has a specific status and treatment under the under the ICANN Bylaws, precision of terminology is crucial to avoid any perception that there is an attempt to direct the Board, rather than making a request for information and attempting to impose a reasonable deadline for its provision. That said, t</span><span class="">he GNSO Council looks forward to reviewing ICANN’s responses to the questions listed in Annex 1 to the Communiqué. Some contracted parties to ICANN have or are in the process of developing a number of “best practices” initiatives related to registry and registrar operations. ICANN is responsible for setting standards for abuse reporting and performance when determining compliance with contractual obligations. </span><span class="">The issue of DNS Abuse Mitigation raised by the GAC may also be dealt with by the GNSO in </span><span class="">GNSO PDP Working Groups, producing relevant Consensus Policy recommendations then duly adopted by the Board. Further,<span class="Apple-converted-space"> </span></span><span class="">the issue of DNS Abuse Mitigation raised by the GAC is dealt with by the GNSO as the issue arises, whether it be various active and/or open projects on the <a href="https://gnso.icann.org/en/meetings/projects-list-28nov16-en.pdf" target="_blank" class="">Projects List</a>, or as part of GNSO <a href="https://gnso.icann.org/en/council/policy" target="_blank" class="">Policy Activities</a>. </span></div><div class="MsoNormal" style="font-size:12pt;;"><span class="">___________________________</span></div><div class=""><br class=""></div><div class="">I'm very happy to discuss the rationale for these proposed changes. </div><div class=""><br class=""></div><div class="">Best,</div><div class="">Paul</div><div class=""><br class=""></div><div class=""><br class=""></div><blockquote id="replyBlockquote" webmail="1" style="border-left-width: 2px; border-left-style: solid; border-left-color: blue; margin-left: 8px; padding-left: 8px; font-size: 10pt; font-family: verdana;" class=""><div id="wmQuoteWrapper" class="">-------- Original Message --------<br class="">Subject: [council] For your review - GNSO Review of GAC Communique<br class="">Hyderabad<br class="">From: Marika Konings <<a target="_blank" href="mailto:marika.konings@icann.org" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">marika.konings@icann.org</a>><br class="">Date: Thu, December 08, 2016 11:48 am<br class="">To: "<a target="_blank" href="mailto:council@gnso.icann.org" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">council@gnso.icann.org</a>" <<a target="_blank" href="mailto:council@gnso.icann.org" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">council@gnso.icann.org</a>><br class=""><br class=""><div class="WordSection1" style="page: WordSection1;"><div class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size:12pt;; font-family: Calibri;"><span style="font-size: 11pt;" class="">Dear All,<o:p class=""></o:p></span></div><div class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size:12pt;; font-family: Calibri;"><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size:12pt;; font-family: Calibri;"><span style="font-size: 11pt;" class="">Please find attached for your review the proposed GNSO Review of the GAC Communique. This draft has been developed by the small drafting team that was formed at ICANN57 consisting of Donna Austin, James Bladel, Heather Forrest, Phil Corwin, Michele Neylon, Paul McGrady and Carlos Guttierez. Please share any comments and/or input you may have with the mailing list. Consideration of this document is also on the agenda for the GNSO Council meeting on 15 December.<span class="Apple-converted-space"> </span><o:p class=""></o:p></span></div><div class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size:12pt;; font-family: Calibri;"><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size:12pt;; font-family: Calibri;"><span style="font-size: 11pt;" class="">Best regards,<o:p class=""></o:p></span></div><div class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size:12pt;; font-family: Calibri;"><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size:12pt;; font-family: Calibri;"><span style="font-size: 11pt;" class="">Marika<o:p class=""></o:p></span></div><div class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size:12pt;; font-family: Calibri;"><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size:12pt;; font-family: Calibri;"><b class=""><i class=""><span style="font-size: 11pt;" class="">Marika Konings<o:p class=""></o:p></span></i></b></div><div class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size:12pt;; font-family: Calibri;"><i class=""><span style="font-size: 11pt;" class="">Senior Policy Director & Team Leader for the GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) <o:p class=""></o:p></span></i></div><div class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size:12pt;; font-family: Calibri;"><i class=""><span style="font-size: 11pt;" class="">Email:<span class="Apple-converted-space"> </span><a target="_blank" href="mailto:marika.konings@icann.org" style="color: rgb(149, 79, 114); text-decoration: underline;" class=""><span style="color: rgb(5, 99, 193);" class="">marika.konings@icann.org</span></a> <o:p class=""></o:p></span></i></div><div class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size:12pt;; font-family: Calibri;"><i class=""><span style="font-size: 11pt;" class=""> <o:p class=""></o:p></span></i></div><div class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size:12pt;; font-family: Calibri;"><i class=""><span style="font-size: 11pt;" class="">Follow the GNSO via Twitter @ICANN_GNSO<o:p class=""></o:p></span></i></div><div class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size:12pt;; font-family: Calibri;"><i class=""><span style="font-size: 11pt;" class="">Find out more about the GNSO by taking our <a target="_blank" href="http://learn.icann.org/courses/gnso" style="color: rgb(149, 79, 114); text-decoration: underline;" class=""><span style="color: rgb(5, 99, 193);" class="">interactive courses</span></a> and visiting the <a target="_blank" href="http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers" style="color: rgb(149, 79, 114); text-decoration: underline;" class=""><span style="color: rgb(5, 99, 193);" class="">GNSO Newcomer pages</span></a>. </span></i></div></div></div></blockquote></span></div></blockquote></div><br class=""></div>
</div>
</blockquote></span></body></html>