ICM's Initial response to Report of Possible Process Options
<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>I enclose below the Text of a letter sent to Rod Beckstrom at ICANN today, together with a PDF copy of same.</div><div><br></div><div><!--StartFragment--><p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none; text-autospace:none"><span style="mso-bidi-font-size:10.0pt;mso-bidi-font-family: Arial">ICM and its counsel have reviewed the “options” presented to the Board by ICANN staff, and are dismayed to note that several of the options are in many respects substantively and procedurally inconsistent with the IRP declaration. <span style="mso-spacerun: yes"> </span>In fact, only one option (expedited due diligence to confirm financial and technical capabilities) appears to offer the current ICANN Board a path to avoid new and ongoing violations of the organization's Articles of Incorporation and Bylaws. This is, to put it plainly, unacceptable.<span style="mso-spacerun: yes"> </span><o:p></o:p></span></p><p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none; text-autospace:none"><span style="mso-bidi-font-size:10.0pt;mso-bidi-font-family: Arial"><o:p> </o:p></span></p><p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none; text-autospace:none"><span style="mso-bidi-font-size:10.0pt;mso-bidi-font-family: Arial">While we appreciate that this is the first time that the Board has had to consider implementation of an IRP declaration, and in this regard may well believe that all options must be studied, it would be inappropriate, illegal and inconsistent with ICANN’s core values and model of self governance for ICANN to set up an evaluative process that is lacking in objectivity and that does not affirmatively give effect to the underlying IRP declaration. <span style="mso-spacerun: yes"> </span>In our view, ICANN staff’s options paper would appear to have not been conceived with the objective of affirmatively giving full effect to the IRP declaration.<span style="mso-spacerun: yes"> </span><o:p></o:p></span></p><p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none; text-autospace:none"><span style="mso-bidi-font-size:10.0pt;mso-bidi-font-family: Arial"><o:p> </o:p></span></p><p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none; text-autospace:none"><span style="mso-bidi-font-size:10.0pt;mso-bidi-font-family: Arial">The ICANN community clearly called on the Board in Nairobi to honor the IRP declaration and move promptly to right its discriminatory, unfair and bad faith treatment of ICM. <span style="mso-spacerun: yes"> </span>It would indeed be a disservice to urge the Board to follow a path that breaks faith with the community and threatens to prolong this costly and distracting legal dispute. <o:p></o:p></span></p><p class="MsoNormal" style="mso-pagination:none;mso-layout-grid-align:none; text-autospace:none"><span style="mso-bidi-font-size:10.0pt;mso-bidi-font-family: Arial"><o:p> </o:p></span></p> <font class="Apple-style-span" face="'Times New Roman'" size="4"><span class="Apple-style-span" style="font-size: 14px;">ICM and its counsel are studying the options paper and will be submitting an analysis which we trust will be given due and careful consideration by the Board. We remain committed to working constructively and in good faith to resolve this matter, and hope that ICANN and its advisors are similarly committed</span></font><!--EndFragment--> </div><div><br></div><div><br></div><div><br></div><div><br></div><br><div> <div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Stuart Lawley</div><div><br></div><div>ICM Registry LLC</div><div><a href="http://www.icmregistry.com">www.icmregistry.com</a></div></div> </div> </body></html> Attachment:
Letter to ICANN March 28 2010.pdf <html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "></body></html> |