<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Dear <span
        style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;"><span
style="background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-attachment:initial;background-origin:initial;background-clip:initial;">R.R.
            KRISHNAA,<br>
            <br>
            Thank you for the detailed response. I want to be clear that
            my analysis concerns the functional process of the ICANN
            complaint system which is now shown to be exploitable and
            exploited. It is exploited because neither the original
            policy nor the created process accept the complexity of the
            real world. The system as such is focused on ticket
            processing and not issue resolution. No one is served here
            except the criminal.<br>
            <br>
            Respectfully, Garth<br>
          </span></span></span><br>
      <br>
      On 3/13/17 10:40 PM, Legal wrote:<br>
    </div>
    <blockquote
cite="mid:1489411162.S.6699.1489.pro-236-175.1489441232.14372@webmail.rediffmail.com"
      type="cite"><span style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;">Dear Mr. Garth Bruen</span></span><br>
      <br>
      <span style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;">All domain registration agreements
          contain provisions for taking action on domains if it contains
          incomplete whois details or does any illegal activities.</span></span><br>
      <br>
      <span style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;">I read the WHOIS DATA PROBLEM
          REPORTING SYSTEM (WDPRS). </span></span><br>
      <br>
      <span style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;">The WHOIS INACCURACY COMPLAINT FORM
          provides below:-</span></span><br>
      <br>
      <span style="background:yellow;"><span
          style="font-family:trebuchet ms,sans-serif;"><span
            style="font-size:10.5pt;">This form allows Internet users to
            submit a complaint to</span></span></span> <span
        style="background:yellow;"><span style="font-family:trebuchet
          ms,sans-serif;"><span style="font-size:10.5pt;">ICANN</span></span></span> <span
        style="background:yellow;"><span style="font-family:trebuchet
          ms,sans-serif;"><span style="font-size:10.5pt;">regarding
            incomplete or incorrect Whois data, including privacy or
            proxy contact information. The complaint is then forwarded
            to the sponsoring registrar, who must take reasonable steps
            to investigate and correct inaccurate data.</span></span></span><br>
      <br>
      <span style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;">On receipt of a complaint ICANN
          forwards the complaint to the registrar to investigate the
          matter.  The complaint may be incorrect or invalid whois
          details or involved in any cyber crime activity.  On receipt
          of the complaint the registrar:-</span></span>
      <ol style="list-style-type:lower-alpha;">
        <li style="text-align:justify;"><span
            style="font-family:trebuchet ms,sans-serif;"><span
              style="font-size:10.5pt;">may not allow any change to the
              domain or allow transfer of domain to another registrar
              by  placing the domain on (registrar) locks (4 locks -
              update, transfer, renew and delete) so that change or
              transfer does not take place (this is a preliminary step).
            </span></span></li>
        <li style="text-align:justify;"><span
            style="font-family:trebuchet ms,sans-serif;"><span
              style="font-size:10.5pt;">After this the registrar may
              seek commence investigation on the issue by seeking the
              registrant to clarify the whois details and call upon the
              registrant why the domain should not be suspended for
              incorrect whois details or for involvement in criminal
              activities which is contrary to the domain registration
              policy. </span></span></li>
        <li style="text-align:justify;"><span
            style="font-family:trebuchet ms,sans-serif;"><span
              style="font-size:10.5pt;">the registrar may perform (a)
              and (b) with notice to the registry (registry will be kept
              in of the email) so that registry is aware of the
              incidents and take necessary action when required.  </span></span></li>
      </ol>
      <span style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;">(Kind Note:  Once locks are placed
          the registrant himself may come up and ask the registrar why
          the domain is placed on locks; this may help LEA (law
          enforcement agencies) to identify the  registrant and his
          location to investigate the crime).</span></span><br>
      <br>
      <span style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;">Selling of Opioids may be crime or
          illegal in certain jurisdictions.   In matters where cyber
          crime is also involved along with incorrect details the
          requester may also include the law enforcement agencies in cc
          of his complaint filed before ICANN.   Or else ICANN may
          forward the complaint to relevant cyber crime unit (national
          or international).  Example:  CERT, FDA or INTERPOL.</span></span><br>
      <br>
      <span style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;">On the whole when a complaint is
          filed the complaint (which has cyber crime element in it) may
          also be marked to the registry, law enforcement agencies so
          that parallel investigations can be done by the law
          enforcement agencies simultaneously to ensure that complaint
          is resolved at the earliest.  </span></span><br>
      <br>
      <span style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;">Coming again to the core issue of
          incorrect details – the registrar will be the first person to
          take action on the domain by placing the domain on
          suspension.  Registry will take action if the registrar does
          not take action.  The registrar and the registry have powers
          to put the domain on HOLD (the domain will not be deleted or
          transferred and will be completely controlled i.,e the domain
          will not resolve).  </span></span><br>
      <br>
      <span style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;">By placing the domain on locks as an
          initial step the transfer of domain from one registrar to
          another registrar can be avoided.   </span></span><br>
      <br>
      <span style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;">In the INDRP process (.IN domain
          dispute resolution process) which is similar to UDRP process –
          all 4 server locks are placed by the .IN Registry and all the
          4 locks are placed by the .IN Registrar to ensure that the
          domain is not transferred or changed till the dispute
          resolution process is completed.  </span></span><br>
      <br>
      <span style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;">I humbly submit that at the outset
          ICANN may not take cognizance of this matter.  It is a matter
          which has to be resolved by the registrar and the registry. 
          (Kind note: If criminal activities are involved the requester
          can involve the LEAs also as stated supra).  </span></span><br>
      <br>
      <span style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;">The points highlighted by the Mr.
          Garth are noteworthy (in respect of WDPRS).</span></span><br>
      <br>
      <span style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;">I feel that the main reason WDPRS
          could not keep track of the complaint is because the domain is
          not placed on locks (hence the domain changes from registrar
          to registrar).   But if the locks are placed (as suggested
          above) such things can be prevented.  </span></span><br>
      <br>
      <span style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;">In this case ICANN could not
          actually follow up the ticket and had to close the ticket
          (because the domain can be transferred or changed any moment
          from one registrar to another).  To circumvent this issue the
          above method of placing the domain on locks is suggested.</span></span><br>
      <br>
      <span style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;">In my humble opinion the
          jurisdiction to handle issue relating to incorrect whois
          details lies with the registrar and the registry in ccTLDs; I
          hope the same theory applies for gTLDs also.  As such filing
          complaints before ICANN under WDPRS only overlaps the rights
          of registrar and registry.</span></span><br>
      <br>
      <span style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;"><strong>Suggestion:</strong>   The
          WHOIS INACCURACY COMPLAINT FORM ICANN can also mention that if
          the complaint involves issues relating to any cyber crime
          (drugs, pornography, terrorism or any other cyber crime) in
          addition to incorrect whois details, the relevant law
          enforcement agencies of the requester’s jurisdiction or the
          international law enforcement agnecies may be kept in cc of
          the email.</span></span><br>
      <br>
      <span style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;">Looking forward to hear from others.</span></span><br>
      <br>
      <span
style="background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-attachment:initial;background-origin:initial;background-clip:initial;"><span
          style="font-family:trebuchet ms,sans-serif;"><span
            style="font-size:10.5pt;">Regards</span></span></span><br>
      <br>
      <span style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;"><span
style="background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-attachment:initial;background-origin:initial;background-clip:initial;">R.R.
            KRISHNAA</span><br>
          <span
style="background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-attachment:initial;background-origin:initial;background-clip:initial;">Legal
            Officer</span><br>
          <span
style="background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-attachment:initial;background-origin:initial;background-clip:initial;">National
            Internet Exchange of India</span><br>
          <span
style="background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-attachment:initial;background-origin:initial;background-clip:initial;">Regd.
            Office: Flat No. 6B, 6th Floor,</span><br>
          <span
style="background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-attachment:initial;background-origin:initial;background-clip:initial;">Uppals
            M6 Plaza, </span><br>
          <span
style="background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-attachment:initial;background-origin:initial;background-clip:initial;">Jasola
            District Centre, </span><br>
          <span
style="background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-attachment:initial;background-origin:initial;background-clip:initial;">New
            Delhi </span></span></span><span
style="background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-attachment:initial;background-origin:initial;background-clip:initial;"><span
          style="font-family:trebuchet ms,sans-serif;"><span
            style="font-size:10.5pt;">-</span></span></span><span
style="background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-attachment:initial;background-origin:initial;background-clip:initial;"><span
          style="font-family:trebuchet ms,sans-serif;"><span
            style="font-size:10.5pt;">110025</span></span></span><br>
      <span style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;"><span
style="background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-attachment:initial;background-origin:initial;background-clip:initial;">Tel:
            +91-11-48202010 (Direct) </span><br>
          <span
style="background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-attachment:initial;background-origin:initial;background-clip:initial;">+91-11-48202000</span><br>
          <span
style="background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-attachment:initial;background-origin:initial;background-clip:initial;">Email: </span></span></span><a
        moz-do-not-send="true"><span
style="background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-attachment:initial;background-origin:initial;background-clip:initial;"><span
            style="color:windowtext;"><span style="font-family:trebuchet
              ms,sans-serif;"><span style="font-size:10.5pt;">legal@nixi.in</span></span></span></span></a><br>
      <span style="font-family:trebuchet ms,sans-serif;"><span
          style="font-size:10.5pt;"><span
style="background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-attachment:initial;background-origin:initial;background-clip:initial;">Website: 
          </span></span></span><span
style="background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-attachment:initial;background-origin:initial;background-clip:initial;text-decoration:none;"><span
          style="color:windowtext;"><span style="font-family:trebuchet
            ms,sans-serif;"><span style="font-size:10.5pt;"><a class="moz-txt-link-abbreviated" href="http://www.nixi.in">www.nixi.in</a></span></span></span></span><br>
      <br>
      <br>
      From: <a class="moz-txt-link-rfc2396E" href="mailto:gbruen@knujon.com">&lt;gbruen@knujon.com&gt;</a><br>
      Sent: Mon, 13 Mar 2017 18:49:22 GMT+0530<br>
      To: Rinalia Abdul Rahim <a class="moz-txt-link-rfc2396E" href="mailto:rinalia.abdulrahim@gmail.com">&lt;rinalia.abdulrahim@gmail.com&gt;</a>, Len
      Felipe Snchez Amba <a class="moz-txt-link-rfc2396E" href="mailto:leonfelipe@sanchez.mx">&lt;leonfelipe@sanchez.mx&gt;</a>, Alan Greenberg
      <a class="moz-txt-link-rfc2396E" href="mailto:alan.greenberg@mcgill.ca">&lt;alan.greenberg@mcgill.ca&gt;</a>,
      <a class="moz-txt-link-rfc2396E" href="mailto:at-large@atlarge-lists.icann.org">"at-large@atlarge-lists.icann.org"</a>
      <a class="moz-txt-link-rfc2396E" href="mailto:at-large@atlarge-lists.icann.org">&lt;at-large@atlarge-lists.icann.org&gt;</a>,
      <a class="moz-txt-link-rfc2396E" href="mailto:na-discuss@atlarge-lists.icann.org">"na-discuss@atlarge-lists.icann.org"</a>
      <a class="moz-txt-link-rfc2396E" href="mailto:na-discuss@atlarge-lists.icann.org">&lt;na-discuss@atlarge-lists.icann.org&gt;</a>, ALAC Internal List
      <a class="moz-txt-link-rfc2396E" href="mailto:alac-internal@atlarge-lists.icann.org">&lt;alac-internal@atlarge-lists.icann.org&gt;</a><br>
      Subject: [At-Large] ICANN Complaint System Circumvented<br>
      <br>
      Dear ALAC Leadership and the greater community,<br>
      <br>
      I am submitting the following memorandum for your consideration:<br>
      <a moz-do-not-send="true"
href="//prolinks.rediffmailpro.com/cgi-bin/prored.cgi?red=http%3A%2F%2Fknujon%2Ecom%2FDONT%5Fanalysisoficannwdprs%2Epdf&amp;rediffng=0"
        rel="external" target="_blank">http://knujon.com/DONT_analysisoficannwdprs.pdf</a><br>
      <br>
      What you will find in this document is an analysis of the ICANN<br>
      complaint system (WDPRS). The analysis uses one criminally-used
      domain<br>
      with false WHOIS as an example to better understand the issues
      with<br>
      ICANN policy and procedure. In short, the ICANN WDPRS has been<br>
      effectively circumvented by the owners of this criminal domain.
      The<br>
      domain has had 3 different sets of false WHOIS and simply
      transferred<br>
      their domain each time a complaint was filed. The domain had been<br>
      transferred to 4 different registrars and is currently operating
      selling<br>
      narcotics.<br>
      <br>
      In short, the current system has failed in its intent and the
      criminals<br>
      now know how to get around enforcement. The problem is in the
      contract<br>
      and in the compliance procedures.<br>
      <br>
      This is related to the earlier studies I have released to the
      list. I<br>
      will be presenting at the joint session of the Public Safety
      Working<br>
      Group (PSWG) and the Verified TLD (vTLD) constituency on Tuesday
      14<br>
      March from 18:30 to 19:30 in Hall B4.1. I invite all comments and
      will<br>
      be talking about this in meetings.<br>
      <br>
      Apologies for any cross-posting.<br>
      <br>
      -Garth<br>
      <br>
      <br>
      --<br>
      Garth Bruen<br>
      <a class="moz-txt-link-abbreviated" href="mailto:gbruen@knujon.com">gbruen@knujon.com</a><br>
      <br>
      617-947-3805<br>
      <a moz-do-not-send="true"
href="//prolinks.rediffmailpro.com/cgi-bin/prored.cgi?red=http%3A%2F%2Fwww%2Eknujon%2Ecom&amp;rediffng=0"
        rel="external" target="_blank">http://www.knujon.com</a><br>
      ICANN At-Large Advisory Council<br>
      Author: WHOIS Running the Internet<br>
      <a moz-do-not-send="true"
href="//prolinks.rediffmailpro.com/cgi-bin/prored.cgi?red=http%3A%2F%2Fwww%2Ewiley%2Ecom%2FWileyCDA%2FWileyTitle%2FproductCd%2D1118679555%2Ehtml&amp;rediffng=0"
        rel="external" target="_blank">http://www.wiley.com/WileyCDA/WileyTitle/productCd-1118679555.html</a><br>
      <br>
      _______________________________________________<br>
      At-Large mailing list<br>
      <a class="moz-txt-link-abbreviated" href="mailto:At-Large@atlarge-lists.icann.org">At-Large@atlarge-lists.icann.org</a><br>
      <a moz-do-not-send="true"
href="//prolinks.rediffmailpro.com/cgi-bin/prored.cgi?red=https%3A%2F%2Fatlarge%2Dlists%2Eicann%2Eorg%2Fmailman%2Flistinfo%2Fat%2Dlarge&amp;rediffng=0"
        rel="external" target="_blank">https://atlarge-lists.icann.org/mailman/listinfo/at-large</a><br>
      <br>
      At-Large Official Site: <a moz-do-not-send="true"
href="//prolinks.rediffmailpro.com/cgi-bin/prored.cgi?red=http%3A%2F%2Fatlarge%2Eicann%2Eorg&amp;rediffng=0"
        rel="external" target="_blank">http://atlarge.icann.org</a><br>
      <br>
-------------------------------------------------------------------------------------------------------------------------------<br>
      [NIXI is on Social-Media too. Kindly follow us at:<br>
      Facebook: <a class="moz-txt-link-freetext" href="https://www.facebook.com/nixiindia">https://www.facebook.com/nixiindia</a> &amp; Twitter:
      @inregistry ]<br>
      This e-mail is for the sole use of the intended recipient(s) and
      may<br>
      contain confidential and privileged information. If you are not
      the<br>
      intended recipient, please contact the sender by reply e-mail and
      destroy<br>
      all copies and the original message. Any unauthorized review, use,<br>
      disclosure, dissemination, forwarding, printing or copying of this
      email<br>
      is strictly prohibited and appropriate legal action will be taken.<br>
-------------------------------------------------------------------------------------------------<br>
    </blockquote>
    <br>
    <p><br>
    </p>
    <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>
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>
  </body>
</html>