<HTML><FONT FACE=arial,helvetica><FONT SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">Adam (ajp@glocom.ac.jp) wrote:<BR>
<<Key fault of the Evolution and Reform Committee is that they have not <BR>
considered the role of staff and counsel. Like wondering why Enron <BR>
failed without looking at Arthur Andersen.<BR>
Anyway, could you explain [proposed resolution text]<BR>
>The ICANN Board should take immediate steps to adopt a policy<BR>
>which requires that no staff or counsel of ICANN who is engaged in policy<BR>
>or legal recommendations or reports shall directly or indirectly represent (as<BR>
>a legal matter) or directly or indirectly benefit (as a financial matter) from<BR>
>individuals or entities who participate in any of the ICANN constituencies<BR>
>or in any ICANN process.<BR>
>><BR>
<BR>
Adam:<BR>
I've noticed that Hans Klein has not had a chance to respond to this important email. I hope you don't mind if I take a stab... As you point out, the Reform Committee does not address issues of staff and counsel. This is a major oversight because staff and counsel play such a critical role in the ICANN process. <BR>
<BR>
Staff and counsel generally do the vast majority of the research, analysis, interaction with the public via comments, presentation to the Board, and recommendations for final action. The .ORG process was a good example of this process. Ultimately, the staff and counsel made the final, single, recommendation to the Board. <BR>
<BR>
Despite this broad authority, the ICANN conflicts of interest policy does not apply to staff and counsel. It applies to Board members, officers (such as Stuart Lynn) and supporting organization leaders, but not to ICANN's own counsel (including general counsel) or senior staff. <BR>
<BR>
What the resolution says in plain English is that the same rules must apply across the Board - to senior staff, to senior counsel, to officers and to Board members. If you are being paid, or someone in your company is being paid, by an individual or entity who have a vested interested in the outcome of an ICANN process, you shouldn't be the person advising the ICANN Board about it. It is a matter of basic fairness. regards, kathy (kleiman, acm-igp)<BR>
<BR>
</FONT></HTML>