<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hello, Garth.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">I appreciate your frustration, but I do not believe Compliance is doing all these blogs just to distract people.  They do receive "requests" for action on content matters and it is a smaller proportion compared to WHOIS inaccuracy complaints, but apparently the effort and time required to address the content problems are disproportionately higher, especially when the "requests" come from organized and large commercial entities with lots of legal resources.  The blogs are part of the effort to address that problem through education and awareness.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Regarding staffing, specifically the hiring of the Consumer Safeguard Director, which I know you and the At-Large are very concerned about, there needs to be follow-up action from Compliance to draw up a job ToR for the position and to invite ALAC input.  This is an action item stemming from that meeting and the Board will review the status of that action at its May meeting.<br><br><span style="font-size: 13pt;">Best regards,</span><div><span style="font-size: 13pt;"><br></span></div><div><span style="font-size: 13pt;">Rinalia </span></div><div><br></div></div><div><br>On Apr 14, 2016, at 11:04 PM, "<a href="mailto:gbruen@knujon.com">gbruen@knujon.com</a>" <<a href="mailto:gbruen@knujon.com">gbruen@knujon.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
  
    <meta content="text/html; charset=windows-1252" http-equiv="Content-Type">
  
  
    <div class="moz-cite-prefix">Rinalia, <br>
      <br>
      These blogs are a distraction. There are at-least three explaining
      in painful detail why ICANN cannot regulate content. Yet looking
      at compliance's own statistics on the complaints they receive,
      their workload is clearly consumed with contractual items. One
      would think that crowds are banning on ICANN's doors to get
      content pulled down. <br>
      <br>
      As if on cue, whenever the compliance director is asked very
      specific questions about staffing, process, etc. he begins
      discussing "content" when no one has brought it up. This is
      leaning towards a tactic of casting any difficult issue ICANN does
      not want to handle as a "content" issue. It is tiresome. <br>
      <br>
      -Garth<br>
      <br>
      <br>
      On 4/14/16 2:36 PM, Rinalia Abdul Rahim wrote:<br>
    </div>
    <blockquote cite="mid:CANZv7UGDU1d_r8VROPjkgLrevOXoixYTt0XmFna9pWnmVrYZTg@mail.gmail.com" type="cite"><span style="background-color:rgba(255,255,255,0);font-size:small">Blog
        written </span><span style="background-color:rgba(255,255,255,0);font-size:small">by
        Allen Grogan - could </span><span style="background-color:rgba(255,255,255,0);font-size:small">be
        of interest to the ALAC on</span><span style="background-color:rgba(255,255,255,0);font-size:small"> registrant
        issues.</span><br>
      <div>
        <div><font size="2"><span style="background-color:rgba(255,255,255,0)"><br>
            </span></font></div>
        <div><font size="2"><span style="background-color:rgba(255,255,255,0)">See <a moz-do-not-send="true" href="https://www.icann.org/news/blog/icann-is-not-the-internet-content-police" target="_blank"></a><a class="moz-txt-link-freetext" href="https://www.icann.org/news/blog/icann-is-not-the-internet-content-police">https://www.icann.org/news/blog/icann-is-not-the-internet-content-police</a></span></font><br>
        </div>
        <div><font size="2"><br>
          </font></div>
        <div><font size="2">Best regards,</font></div>
        <div><font size="2"><br>
          </font></div>
        <div><font size="2">Rinalia</font></div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
ALAC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a>
<a class="moz-txt-link-freetext" href="https://atlarge-lists.icann.org/mailman/listinfo/alac">https://atlarge-lists.icann.org/mailman/listinfo/alac</a>

At-Large Online: <a class="moz-txt-link-freetext" href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a>
ALAC Working Wiki: <a class="moz-txt-link-freetext" href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a></pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Garth Bruen
<a class="moz-txt-link-abbreviated" href="mailto:gbruen@knujon.com">gbruen@knujon.com</a>

617-947-3805
<a class="moz-txt-link-freetext" href="http://www.knujon.com">http://www.knujon.com</a>
Fisher College, Criminal Justice Division
ICANN At-Large Advisory Council
Author: WHOIS Running the Internet
<a class="moz-txt-link-freetext" href="http://www.wiley.com/WileyCDA/WileyTitle/productCd-1118679555.html">http://www.wiley.com/WileyCDA/WileyTitle/productCd-1118679555.html</a></pre>
  

</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>ALAC mailing list</span><br><span><a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a></span><br><span><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac">https://atlarge-lists.icann.org/mailman/listinfo/alac</a></span><br><span></span><br><span>At-Large Online: <a href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a></span><br><span>ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a></span></div></blockquote></body></html>