<div dir="ltr">John,<div><br></div><div>I'll let others closer to the present Board reply about the situation as is at present. I'm sure your advice would be welcome as input for many of the processes ICANN has undertaken. In what I have seen of the board "all of the above" would be my answer if you asked "what have you bumped into and how have you solved it?"</div>
<div><br></div><div>What would make your contribution even more interesting and useful would be examples from other Internet-resource policy coordination organizations. I'm sure you have a treasure chest of those!�</div>
<div><br></div><div>Alejandro Pisanty</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 26, 2014 at 6:27 PM, John Curran <span dir="ltr"><<a href="mailto:jcurran@istaff.org" target="_blank">jcurran@istaff.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Feb 26, 2014, at 3:03 PM, Alejandro Pisanty <<a href="mailto:apisanty@gmail.com">apisanty@gmail.com</a>> wrote:<br>
<br>
> John,<br>
><br>
> in an ideal world you'd do that iteration after iteration until the result is perfectly clear and actionable and the consensus is unequivocally established. But then, in that ideal world, that would be the case from the very beginning.<br>
<br>
� I was not asking about the ideal world, but those specific cases you referenced earlier where the<br>
� "bottom-up advice (wasn't always) clear and precise enough for the ICANN Board to just approve."<br>
� In order to save time, perhaps it would best to just accept such cases at face value, and move on<br>
� to consider its relevance of this discussion on the role of governments, GAC input, and Board<br>
� consideration of same.<br>
<br>
� The discussion on this topic has revealed quite a bit of "Board wisdom" regarding handling of issues<br>
� (e.g. �usefulness of stimulating further discussion and new approached where the community has not<br>
� come up with something sufficiently clear, the Board's vision of a limited role in the course of normal<br>
� policy development efforts, desirability of the Board not serving as its own experts, �use of expert<br>
� working groups when needed, etc.)<br>
<br>
� Perhaps it would be helpful for the Board to enshrine some of this wisdom into a more detailed process<br>
� and criteria than the current GNSO policy development process? �Presently, the entire Board wisdom is<br>
� enshrined in a single line regarding whether "the Board determines that such policy is not in the best<br>
� interests of the ICANN community or ICANN."<br>
<br>
� There is a complete absence of any criteria (even representative) about what might constitute a policy<br>
� being "not in the best interests of the ICANN community or ICANN.", for example -<br>
<br>
� � �- Policy statement is insufficiently clear to allow for implementation<br>
� � �- Policy development did not follow the approved policy development process<br>
� � �- Policy would result in ICANN doing something contrary to prevailing law<br>
� � �- Policy was not clearly supported by the ICANN community<br>
� � �- Policy was strongly opposed by one significant segment of the ICANN community<br>
� � � � � �and there is not documentation that those views have been fully considered.<br>
� � �- Policy could pose significant technical risk<br>
� � �- etc.<br>
<br>
� Obviously having such a set of formal criteria may also be helpful in preparation of the staff report,<br>
� but the main benefit would be in documenting a shared understanding over some of the significant<br>
� types of issues that the Board will weigh in its determination.<br>
<br>
� Clearly, the Board will always retain the freedom to identify other concerns due to its weighty responsibility<br>
� to the mission of the organization, but setting clear expectations about the normal evaluation process and<br>
� criteria (to match what has been discussed on this list) would probably be helpful in dispensing with some<br>
� of the Board perception issues, and certainly help in anchoring accountability aspects of the organization.<br>
<br>
FYI,<br>
/John<br>
<br>
Disclaimer: �My views alone.<br>
<br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>- - - - - - - - - - - - - - - - - - - - - - - - - - -<br>� � �Dr. Alejandro Pisanty<br>Facultad de Qu�mica UNAM<br>Av. Universidad 3000, 04510 Mexico DF Mexico<br>
+52-1-5541444475 FROM ABROAD<br>+525541444475 DESDE M�XICO SMS +525541444475<br>Blog: <a href="http://pisanty.blogspot.com" target="_blank">http://pisanty.blogspot.com</a><br>LinkedIn: <a href="http://www.linkedin.com/in/pisanty" target="_blank">http://www.linkedin.com/in/pisanty</a><br>
Unete al grupo UNAM en LinkedIn, <a href="http://www.linkedin.com/e/gis/22285/4A106C0C8614" target="_blank">http://www.linkedin.com/e/gis/22285/4A106C0C8614</a><br>Twitter: <a href="http://twitter.com/apisanty" target="_blank">http://twitter.com/apisanty</a><br>
---->> Unete a ISOC Mexico, <a href="http://www.isoc.org" target="_blank">http://www.isoc.org</a><br>. �. �. �. �. �. �. �. �. �. �. �. �. �. �. �.
</div>