<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
{mso-style-priority:99;
mso-style-link:"Body Text Char";
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.BodyTextChar
{mso-style-name:"Body Text Char";
mso-style-priority:99;
mso-style-link:"Body Text";
font-family:"Calibri","sans-serif";}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1949005743;
mso-list-type:hybrid;
mso-list-template-ids:1279531484 -363961640 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;
mso-bidi-font-family:Arial;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I agree to the role of the chair being in charge of organizing
our work and meeting our deadlines without being deprived from participating to
the RT work ..<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I also like Louis' idea of having a backup, I'm equally fine
with a vice-chair or a co-chair ..<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>On the other hand, and as I'm trying to catch up with the
emails, one thing I feel missing is what will we be looking at when evaluating accountability,
transparency & public input .. I believe it's important that we have some
criteria that would help us:<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:36.0pt;text-indent:-18.0pt;
mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>-<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span dir=LTR></span><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>ask the right questions
during the data gathering phase, <o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:36.0pt;text-indent:-18.0pt;
mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>-<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span dir=LTR></span><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>not be driven only by
the data we receive,<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:36.0pt;text-indent:-18.0pt;
mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>-<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span dir=LTR></span><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>make sure we are all evaluating
the same things and that we all have the full picture<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:36.0pt;text-indent:-18.0pt;
mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>-<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span dir=LTR></span><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>document or at least
have a good justification (if needed) on how we have reached our
recommendations in an as transparent way as possible<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>A few things I feel urgent at this point:<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:36.0pt;text-indent:-18.0pt;
mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>-<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span dir=LTR></span><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>agree on what we'll
ask ICANN staff to prepare for our upcoming meeting (and whether we need
specific names to be available) ..<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:36.0pt;text-indent:-18.0pt;
mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>-<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span dir=LTR></span><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>have a single version of
each document or thread we are discussing in order to keep track of all colleagues'
valuable remarks, comments and substance that have been submitted over email and
may be also start using track changes (if not other tools as suggested by
Cheryl) to facilitate further compilation of all feedbacks received ..<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:36.0pt;text-indent:-18.0pt;
mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>-<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span dir=LTR></span><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>In support of Fabio's
suggestion, agree on working definitions for accountability, transparency &
public input .. I fully understand colleagues' concerns not to spend much time
on definitions (which Fabio also mentioned by suggesting that we don't have to
search for universally accepted definitions) but I really think this would help
us start from a common ground and would facilitate break down of those terms into
factors/parameters that we'll be looking at during our evaluation ..<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Looking forward to our discussion later today ..<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Kind Regards<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>--Manal<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
at-review-bounces@icann.org [mailto:at-review-bounces@icann.org] <b>On Behalf
Of </b>Louis Lee<br>
<b>Sent:</b> Monday, April 26, 2010 7:49 AM<br>
<b>To:</b> Brian Cute<br>
<b>Cc:</b> A&T Review Team<br>
<b>Subject:</b> Re: [At-review] Draft of questions in advance of F2Fin Marina
del Rey<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>I agree that our Chair would serve to run our meetings and
encourage work as suggested. The Chair should also serve as the official point
of contact in official messaging, but any of us should be able to ask anyone
relevant questions in the course of conducting the review.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Should we ask our new Chair to appoint a Vice-Chair to serve
as backup?<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Would we like to ask Marco to assign someone to serve the
Chair as our secretariat to take minutes, etc?<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>And as for the review work, Rod has told me in discussions
that his staff changes is a result of the Board's directive to make agressive
improvements in the organization. The Board's reaction, as Rod had put it, was
mixed. Some felt that he was too fast, while others applauded him. Even though
Rod is getting mixed signals now, he felt that he was being hired to make these
very changes.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>This raises some questions for me:<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>1. Were not all the Board members in full agreement in their
choice of Pres. & CEO? (Not critical to answer.)<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>2. What did the Board think their directive was to Rod? What
did Rod understand the directive to be?<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>3. Which of Rod's changes were made to further which goals
of the directive? <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>The answers may reveal how the Board is directing staff to
address the A&T aspects of the AoC.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Granted, we should not lose sight that the review is of the
Board. We do have the opportunity at the f2f meeting to ask staff some pointed
questions, so it's great that we are taking advantage of that.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Are we requesting that Rod himself be at our f2f in person?
We shouldn't just assume that he'll be there especially since he works out of
an office in a different part of California.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>And while we have the authority to ask Rod's staff some hard
questions, and we may be generating a lot of work for them, it would be nice to
know if Rod has sent a letter to his staff (or at least his key staff for our
review efforts) requesting cooperation.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>And in addition, our work may reveal information relevant to
the other Review Teams. And as much as I would want to share it, I think the
context in how the info was obtained (phrasing of a question, etc) may be lost
if we were to pass on the info. We should be careful to reveal (or NOT!) such
details to our colleagues.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Talk to y'all soon, <br>
<br>
Louie<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
On Apr 25, 2010, at 9:22 AM, "Brian Cute" <<a
href="mailto:briancute@afilias.info">briancute@afilias.info</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Janis,<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Yes,
that should have been the 5<sup>th</sup> and 6<sup>th</sup> date in the
document. Thanks for catching that.<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Best,<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Brian<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>From:</b>
Janis Karklins [mailto:janis.karklins@icann.org] <br>
<b>Sent:</b> Sunday, April 25, 2010 12:11 PM<br>
<b>To:</b> <a href="mailto:at-review@icann.org">at-review@icann.org</a><br>
<b>Subject:</b> Re: [At-review] Draft of questions in advance of F2F in Marina
del Rey<o:p></o:p></p>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Brian<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I
believe that we agreed that the RT meeting is taking place on 5 and 6 May, not
on 4 May you are referring into your note.<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On
the question of the Chair, I fully agree. The role of the Chair is to
coordinate and encourage the work, but he/she should possess the same rights as
other members of the RT.<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Best
regards<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>JK<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>From:</b>
<a href="mailto:at-review-bounces@icann.org">at-review-bounces@icann.org</a>
[mailto:at-review-bounces@icann.org] <b>On Behalf Of </b>Brian Cute<br>
<b>Sent:</b> svētdiena, 2010. gada 25. aprīlī 17:34<br>
<b>To:</b> <a href="mailto:wadelman@godaddy.com">wadelman@godaddy.com</a>;
'Burr,Becky'; <a href="mailto:at-review@icann.org">at-review@icann.org</a><br>
<b>Subject:</b> Re: [At-review] Draft of questions in advance of F2F in Marina
del Rey<o:p></o:p></p>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>RT
team,<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I
have created a document that tries to track Warren’s useful outline and borrows
much of Becky’s work. Please review and make edits. A few thoughts
about the questions and document requests. <o:p></o:p></p>
<p class=MsoListParagraph> <o:p></o:p></p>
<p class=MsoListParagraph>-
The RT will have the ability to ask follow on questions and to ask for
documents from the staff after May 4. It is important that the RT ask for
a complete presentation from ICANN staff on May 4 so we can structure our work
in a timely manner, but this is not an “all or nothing exercise.”<o:p></o:p></p>
<p class=MsoListParagraph>-
Emphasis should be placed on a careful tracking Paragraph 9.1 of the AoC.
I have put direct quotes, partial quotes and paraphrasing of AoC elements in
the document so please carefully scrutinize those points to ensure accuracy.<o:p></o:p></p>
<p class=MsoListParagraph>-
ICANN’s performance regarding Accountability and Transparency prior to the AoC
is informative to the RT’s work but not the central focus. The “General
Questions” in the document are designed to elicit Staff input on pre-AoC
Accountability and Transparency for background purposes. I have also
removed reference to some specific documents and processes. Not because I
believe they are not relevant. Rather, because I believe Staff’s
responses to open ended questions can be more revealing.<o:p></o:p></p>
<p class=MsoListParagraph>-
What is critical for the May 4 exchange is that all key ICANN staff be
available.<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>With
regard to which ICANN staff should be made available, I believe that is a decision
ultimately for Rod. In terms of one key staffer to be a point person, I
would suggest Doug Brent given his role and length of service. Other than
that, it is up to Staff to organize its response.<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>With
regard to the Chair for the RT, we need to resolve whether the Chair will be
one that must recuse his or herself to ensure neutrality or whether the Chair
can participate/advocate in the work and deliberations of the RT. My view
is that, given the relatively small size of the group, and the fact that each
participant was selected for their respective experience and expertise, it
would be short sighted to insist that the Chair be recused from the RT
work. I would recommend that the Chair’s primary functions be to ensure
that the organization of the RT’s work be well managed – essentially that the
“trains run on time” and that the Chair should otherwise participate in the
RT’s work. I am interested to hear other views on this question.<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Regards,<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Brian<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>From:</b>
<a href="mailto:wadelman@godaddy.com">wadelman@godaddy.com</a>
[mailto:wadelman@godaddy.com] <br>
<b>Sent:</b> Friday, April 23, 2010 5:38 PM<br>
<b>To:</b> Burr,Becky; <a href="mailto:at-review@icann.org">at-review@icann.org</a><br>
<b>Subject:</b> Re: [At-review] Draft of questions in advance of F2F in Marina
del Rey<o:p></o:p></p>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Regarding
Becky's suggested questions, I recommend a simpler approach that clarifies what
we'll be asking Staff to provide, while ensuring that the focus of the review
remains on the ICANN Board.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>First,
we should track the road map expressed in Sec. 9.1 of the AoC, and ask Staff to
comment on items (a) through (e) as they apply to this RT. Their comments
should include any topics or open questions that were outlined in the December
document, along with a summary analysis of public feedback received during the
February comment period. Each topic would end with a brief Q&A before
proceeding to the next.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br>
Secondly, Staff would compile and present any documents resulting from recent
review efforts, internal and external, and include an update on the status of
their implementation. We would allow some time for discussion and
Q&A, and post the list and supporting documents to the RT Wiki.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Finally,
we would allocate time for a discussion of General Topics, where we can raise
questions put forward on the mailing list or omitted from Staff's presentation.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>What
are the group's thoughts on this approach? <o:p></o:p></p>
</div>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Warren<br>
<br>
Warren Adelman<br>
President & COO<br>
<a href="http://GoDaddy.com">GoDaddy.com</a><br>
<a href="mailto:warren@godaddy.com">warren@godaddy.com</a><br>
tel. (480)505-8835<br>
fax. (480)275-3990<br>
mobile.(480)882-8876<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>twitter:
<a href="http://twitter.com/asocialcontract">http://twitter.com/asocialcontract</a><br>
<a href="http://www.godaddy.com">http://www.godaddy.com</a><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt' id=replyBlockquote>
<div id=wmQuoteWrapper>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>--------
Original Message --------<br>
Subject: Re: [At-review] Draft of questions in advance of F2F in Marina<br>
del Rey<br>
From: "Burr, Becky" <<a href="mailto:Becky.Burr@wilmerhale.com">Becky.Burr@wilmerhale.com</a>><br>
Date: Fri, April 23, 2010 8:51 am<br>
To: "Burr, Becky" <<a href="mailto:Becky.Burr@wilmerhale.com">Becky.Burr@wilmerhale.com</a>>,
<<a href="mailto:at-review@icann.org">at-review@icann.org</a>><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>By
the way, I think we should set the AoC as the start date for this discussion on
the "what have you improved" questions, and avoid discussions about
ancient, or not so ancient, history. I also think that
we may want to acknowledge upfront that the AoC is a fairly recent
event, that there has been a lot of change in the period since the AoC was
signed, and that we have a realistic view about what progress could have been
made during that period. Accordingly, I would expect a significant part
of the discussion to be about establishing a baseline for measuring future
improvements and about getting the staff to tell us about their plans for those
future improvements. <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Thoughts?<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>From:</b>
<a href="mailto:at-review-bounces@icann.org">at-review-bounces@icann.org</a> [<a
href="mailto:at-review-bounces@icann.org">mailto:at-review-bounces@icann.org</a>]
<b>On Behalf Of </b>Burr, Becky<br>
<b>Sent:</b> Tuesday, April 20, 2010 11:56 AM<br>
<b>To:</b> <a href="mailto:at-review@icann.org">at-review@icann.org</a><br>
<b>Subject:</b> [At-review] Draft of questions in advance of F2F in Marina del
Rey<o:p></o:p></p>
<p class=MsoBodyText>I have attached as a Word document and pasted below, a
first cut at questions/issues for staff in Marina del Rey. I suspect that
we could profitably spend a lot of time on just a subset of these, but tried to
be more rather than less complete. Also, I think that there are some pretty
important questions we need to answer soon regarding structure and
participation. In particular:<o:p></o:p></p>
<p class=MsoBodyText>* <b><i>What ICANN staff will be participating in our
discussions in Marina del Rey</i></b><i>? Some of the new hires are not
listed on the staff directory – some key folks located outside of California.</i>
<o:p></o:p></p>
<p class=MsoBodyText>* Another key issue is how we would like to interact with
staff. As a large group? Broken out by department/role? Any
that we want to meet with individually, either now or later? What ground
rules do we need to ensure an open dialogue? <o:p></o:p></p>
<p class=MsoBodyText>Comments please!<o:p></o:p></p>
<p class=MsoBodyText><u>Questions in Preparation for F2F in Marina del Rey</u><o:p></o:p></p>
<p class=MsoBodyText>1. Provide and discuss the ICANN staff org chart –
who does what? What is the reporting structure? Where (in the
world) do people sit? How do key staff members spend their time?
While this seems basic, it is not well understood by members of the ICANN
community. Moreover, there have been significant staffing changes in the
last few months that it would be helpful to understand. <o:p></o:p></p>
<p class=MsoBodyText>2. What does the staff view as its key tasks with
respect to A&T, and how is responsibility for those tasks allocated? <o:p></o:p></p>
<p class=MsoBodyText>3. In addition to the Bylaws and Articles of
Incorporation, what documents do staff rely on to fulfill ICANN’s
accountability and transparency obligations. Where do the 2008 Management
Operating Principles, the PSC report, other documents fit in? Are there
internal policies or procedures in place for ensuring that accountability and
transparency issues are considered at appropriate junctures? How are accountability
and transparency issues included/considered in strategic planning and budgeting?<o:p></o:p></p>
<p class=MsoBodyText>4. <a name=91></a>One of the challenges for the AT
Review Team is to identify metrics for measuring improvement under the AoC
tasks. What does the staff suggest? What should we focus on,
what should our priorities be? For this first review, what realistically
can we measure as accomplishments, what should we look at as “works in
progress”? With respect to those works in progress, how should they be
measured going forward?<o:p></o:p></p>
<p class=MsoBodyText>5. We have reviewed the various comments submitted
on the AoC review process, as well as the staff summary of those comments.
Which points seem most important/relevant to staff?<o:p></o:p></p>
<p class=MsoBodyText>6. What observations can ICANN staff make with
respect to progress the AoC commitment to maintain and improve robust
mechanisms for public input, accountability, and transparency so as to ensure
that the outcomes of its decision-making will reflect the public interest and
be accountable to all stakeholders by? Any improvements we should pay
particular attention to? <o:p></o:p></p>
<p class=MsoBodyText>In addition to general reflections on these issues, the
Team seeks staff views on progress and plans with respect to the following: <o:p></o:p></p>
<p class=MsoBodyText>(a) Assessing and improving ICANN Board of Directors
(Board). Have steps been taken to improve Board performance that may not
be apparent to the community (e.g., training for members). Are there
changes in the Board selection process, and is sufficient attention given to
the ways in which Board composition meets ICANN's present and future needs?<o:p></o:p></p>
<p class=MsoBodyText>- Observations on the ways in which staff interacts with
Board – has that changed, is it improving, are there ways in which it can be
improved?<o:p></o:p></p>
<p class=MsoBodyText>(b) What are the staff views on the way the current
accountability mechanisms work – ombuds, reconsideration, IRP? What about
the various institutional review processes? How are consultants selected,
terms of reference set, etc.? How does staff use the information in these
reviews?<o:p></o:p></p>
<p class=MsoBodyText>(c) What are the staff observations about the role and
effectiveness of the GAC and its interaction with the Board? What
improvements have been/are being implemented, and how is that working?
How does staff communicate with the GAC when it seeks public policy input
from the GAC? <o:p></o:p></p>
<p class=MsoBodyText>(d) What are the staff’s observations about the processes
by which ICANN receives public input? In general, how would the staff
rate public input? What improvements have been/are being implemented?
Who synthesizes, and how is input summarized/communicated to the Board?
There are many sets of public comments that are listed as “awaiting
summary/analysis.” Is that due to a resource issue, to the fact that the
issues have been overtaken by events? Is there a better way to do this? <o:p></o:p></p>
<p class=MsoBodyText>(e) What are the staff’s observations about the
degree to which ICANN's decisions are embraced, supported and accepted by the
public and the Internet community? <o:p></o:p></p>
<p class=MsoBodyText>(f) Does the staff have views, suggestions of ways
in which the policy development process can facilitate enhanced cross community
deliberations and effective and timely policy development? What kind of
support does staff provide to the PDP, and how effective is it? Are there
enough resources to provide necessary support?<o:p></o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>_______________________________________________<br>
At-review mailing list<br>
<a href="mailto:At-review@icann.org">At-review@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/at-review">https://mm.icann.org/mailman/listinfo/at-review</a><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='background:white'><o:p> </o:p></span></p>
<p align=center style='text-align:center'><span style='background:white'>Click <a
href="https://www.mailcontrol.com/sr/CxKGMmCJreTTndxI!oX7Uj80y4Ou3Kxpfu5qa9YhQ2EqJ4pxADcVu35EcnE4+!LmaWl9hNA2pe+FfmYpsSvVwQ==">here</a>
to report this email as spam.<o:p></o:p></span></p>
</div>
</blockquote>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>
<div>
<p class=MsoNormal><ATT00001..txt><o:p></o:p></p>
</div>
</blockquote>
</div>
</body>
</html>