<html><head></head><body bgcolor="#FFFFFF" text="#000000" lang="en-US" style="background-color: rgb(255, 255, 255); line-height: initial;">                                                                                      <div style="width: 100%; font-size: initial; font-family: Calibri, 'Slate Pro', sans-serif, sans-serif; color: rgb(31, 73, 125); text-align: initial; background-color: rgb(255, 255, 255);">ā€ˇGarth,</div><div style="width: 100%; font-size: initial; font-family: Calibri, 'Slate Pro', sans-serif, sans-serif; color: rgb(31, 73, 125); text-align: initial; background-color: rgb(255, 255, 255);"><br></div><div style="width: 100%; font-size: initial; font-family: Calibri, 'Slate Pro', sans-serif, sans-serif; color: rgb(31, 73, 125); text-align: initial; background-color: rgb(255, 255, 255);">Well said.</div><div style="width: 100%; font-size: initial; font-family: Calibri, 'Slate Pro', sans-serif, sans-serif; color: rgb(31, 73, 125); text-align: initial; background-color: rgb(255, 255, 255);"><br></div><div style="width: 100%; font-size: initial; font-family: Calibri, 'Slate Pro', sans-serif, sans-serif; color: rgb(31, 73, 125); text-align: initial; background-color: rgb(255, 255, 255);">Murray</div>                                                                                                                                     <div style="width: 100%; font-size: initial; font-family: Calibri, 'Slate Pro', sans-serif, sans-serif; color: rgb(31, 73, 125); text-align: initial; background-color: rgb(255, 255, 255);"><br style="display:initial"></div>                                                                                                                                                                                                   <div style="font-size: initial; font-family: Calibri, 'Slate Pro', sans-serif, sans-serif; color: rgb(31, 73, 125); text-align: initial; background-color: rgb(255, 255, 255);"></div>                                                                                                                                                                                  <table width="100%" style="background-color:white;border-spacing:0px;"> <tbody><tr><td colspan="2" style="font-size: initial; text-align: initial; background-color: rgb(255, 255, 255);">                           <div style="border-style: solid none none; border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding: 3pt 0in 0in; font-family: Tahoma, 'BB Alpha Sans', 'Slate Pro'; font-size: 10pt;">  <div><b>From: </b>gbruen@knujon.com</div><div><b>Sent: </b>Friday, April 15, 2016 08:36</div><div><b>To: </b>rinalia.abdulrahim@gmail.com</div><div><b>Cc: </b>alac@atlarge-lists.icann.org</div><div><b>Subject: </b>Re: [ALAC] Content regulation</div></div></td></tr></tbody></table><div style="border-style: solid none none; border-top-color: rgb(186, 188, 209); border-top-width: 1pt; font-size: initial; text-align: initial; background-color: rgb(255, 255, 255);"></div><br><div id="_originalContent" style="background-color: rgb(255, 255, 255);">
  
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  
  
    <div class="moz-cite-prefix">Rinalia, <br>
      <br>
      It's about a lot more than my frustration, it's about nothing less
      than fair and equal access to the process for all Internet users.
      When ICANN seeks to use inclusion of the "end user" in its goal to
      become the independent Internet steward but then does not fulfill
      its obligation we have to vigorously address that problem. <br>
      <br>
      Not only is this a big issue, it is potentially the biggest issue.
      ICANN says "we don't need government oversight" but has no
      framework or even internal will to protect consumers in the
      absence of government regulation. From the horse's mouth, they
      don't think consumer trust is their obligation, so why would they
      bother to build anything that ensures the consumer trust? <br>
      <br>
      However, your explanation points to an inherent problem within
      ICANN and particularly within compliance. What we see over and
      over is a failure to provide adequate process to manage issues
      (complaints/data) coming into the organization. If they are having
      problems with large commercial entities that is a completely
      separate issue from dealing with pure consumer voices. If they are
      barking at consumer voices in At-Large the same way they do at big
      industry then this is a complete failure to execute the
      multi-stakeholder model. They need to go back to the drawing board
      and start over. <br>
      <br>
      -Garth<br>
      <br>
      <br>
      On 4/15/16 3:32 AM, <a class="moz-txt-link-abbreviated" href="mailto:rinalia.abdulrahim@gmail.com">rinalia.abdulrahim@gmail.com</a> wrote:<br>
    </div>
    <blockquote cite="mid:07CED1CD-309E-44AB-BB1F-05535465E7EA@gmail.com" type="cite">
      <meta http-equiv="content-type" content="text/html; charset=utf-8">
      <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 moz-do-not-send="true" href="mailto:gbruen@knujon.com">gbruen@knujon.com</a>" <<a moz-do-not-send="true" href="mailto:gbruen@knujon.com"></a><a class="moz-txt-link-abbreviated" href="mailto:gbruen@knujon.com">gbruen@knujon.com</a>>
        wrote:<br>
        <br>
      </div>
      <blockquote type="cite">
        <div>
          <meta content="text/html; charset=utf-8" 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" class="moz-txt-link-freetext" href="https://www.icann.org/news/blog/icann-is-not-the-internet-content-police"></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 moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a>
<a moz-do-not-send="true" 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 moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a>
ALAC Working Wiki: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28ALAC%29">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 moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:gbruen@knujon.com">gbruen@knujon.com</a>

617-947-3805
<a moz-do-not-send="true" 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 moz-do-not-send="true" 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 moz-do-not-send="true" href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a></span><br>
          <span><a moz-do-not-send="true" 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 moz-do-not-send="true" href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a></span><br>
          <span>ALAC Working Wiki: <a moz-do-not-send="true" href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28ALAC%29">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a></span></div>
      </blockquote>
    </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>
  

<br><!--end of _originalContent --></div></body></html>