<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<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]-->
<title>Re: List of issues that the A&T RT would like to discuss with ICANN
staff on 5 May</title>
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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:0in;
margin-bottom:.0001pt;
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;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle18
{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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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 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'>All,<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'>For your consideration, a draft proposed response to Rod’s
email concerning the meeting on May 5<sup>th</sup>. Please provide edits
or suggestions concerning the most effective way to respond.<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'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Rod,<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'>Thank you for your response to the Review Team’s requests
with respect to our first face-to-face meeting on May 5, 2010 in Marina del Rey.
The RT carefully considered the importance of holding its first meeting in
Marina del Rey at ICANN headquarters and is quite disappointed to hear that you
will not be joining us in person at the meeting. We request confirmation
that other arrangements for your participation, in some form, will be
made. At this meeting, the RT expects to receive verbal responses from
key ICANN staff to the list of questions approved by the RT. <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'>The RT views this initial exchange as an important and
meaningful opportunity to begin the data collection aspect of our exercise and
welcomes the participation of the Advisor to the CEO for Transparency and Accountability
and other ICANN staff you may designate. This face-to-face meeting will
allow the RT to hear directly from ICANN staff regarding the accountability and
transparency mechanisms that are already in place and to begin the work process
that will lead to RT recommendations under the Affirmation of Commitments.
The RT notes that the December 2010 deadline for recommendations to the Board
imposes time constraints that both the RT and ICANN staff share. Therefore,
it is critical that the initial data collection aspect of the RT work commence
so that the RT’s other work streams can begin without delay. <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'>Best regards,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Janis Karklins<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>On behalf of the Accountability and Transparency Review Team<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 0in 0in 0in'>
<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"'> Brian Cute
[mailto:briancute@afilias.info] <br>
<b>Sent:</b> Friday, April 30, 2010 12:49 PM<br>
<b>To:</b> 'Burr, Becky'; at-review@icann.org<br>
<b>Subject:</b> Re: [At-review] FW: List of issues that the A&T RT would like
to discuss with ICANN staff on 5 May<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>If I may, I think that in the moment, the RT members should
reflect on the most constructive way to respond to Rod’s email with
careful clarification that the RT members indeed expect to meet with ICANN
staff next week and to receive verbal answers to the questions we have compiled
and approved at a team and to get some document production. I believe the
initial exchanges with ICANN staff will be critical in achieving meaningful
recommendations from the RT by December as required. While the substance
of Rod’s response raises questions for all of us, the RT need not lose
focus on the important work at hand and the need to get on with it.<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 0in 0in 0in'>
<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"'> Burr, Becky
[mailto:Becky.Burr@wilmerhale.com] <br>
<b>Sent:</b> Friday, April 30, 2010 11:27 AM<br>
<b>To:</b> at-review@icann.org<br>
<b>Subject:</b> [At-review] FW: List of issues that the A&T RT would like
to discuss with ICANN staff on 5 May<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>With the greatest respect, I find this response disturbing.
Apparently, the ICANN staff is not prepared to enter into a dialogue with us
regarding the substance of our work. I would have thought that
conversation was an important "modality for interaction" on the
review points, and I am sorry to see adversarial overtones creep in so early in
the process. </span><o:p></o:p></p>
<p class=MsoNormal><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='margin-bottom:12.0pt'><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>Rod Beckstrom<br>
<b>Sent:</b> Thursday, April 29, 2010 5:32 PM<br>
<b>To:</b> Janis Karklins<br>
<b>Cc:</b> Denise Michel; at-review@icann.org; Donna Austin<br>
<b>Subject:</b> Re: [At-review] List of issues that the A&T RT would like
to discuss with ICANN staff on 5 May</span><o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>Dear Janis, <br>
<br>
Thank you for forwarding the initial list of proposed questions under
consideration from your Accountability and Transparency Review Team. On
behalf of ICANN’s Management Team, we welcome the opportunity to work
with you in your consideration of ICANN’s Accountability and
Transparency. We believe that this process should be a meaningful
opportunity for ICANN to demonstrate the high levels of accountability and
transparency already in place, as well as an opportunity to collaborate in a
constructive manner to develop the means by which to measure effectiveness and
reach an even greater level.<br>
<br>
Thank you also for your clarification and agenda from which we infer that
written answers to the questions are not anticipated and that the purpose of
your sessions in Marina del Rey next week will be focused on: 1) establishing
the framework for review, including the development of standards and
benchmarks, 2) creating modalities for interaction on the review points that
you are intending to consider as part of the overall review, 3) developing the
questions/issues that will need to be considered, and 4) establishing a
methodology to refine requests for information, This agrees with discussions we
have had with Peter Dengate Thrush on the meeting goals. <br>
<br>
In light of the short time period since we have received these questions, and
the somewhat conflicting instructions we received about Staff’s expected
role at the meeting next week, we know that you understand that next
week’s sessions will be limited in terms of our ability to respond and
appreciate your acknowledgement that this is too short a timeline for us to
provide formal responses. Since ICANN Staff will clearly need to provide
complete and full written responses on the record, and noting that those responses
will need to be responsive to the standards for review that have yet to be
established, it is my assumption that Staff will not be expected to provide
oral responses to these questions, during these sessions. Oral responses,
if made during the session, would likely be incomplete, uneven, and could not
be measured against to-be-determined standards. The result would be to retard,
rather than inform, the group’s work. However, I do expect an active
staff role to: a) assist in helping frame the work to be completed in written
responses, b) establish the processes and timelines for providing those written
responses, and c) discuss proposed levels of resource allocation relating to
this review.<br>
<br>
To further this point, my instructions to Denise Michel (who reports directly
to me as Advisor to the CEO for Transparency and Accountability and is tasked
with leading the staff response and substantive support,) is for the ICANN
Staff to focus on how to: i) discuss the various modalities for interaction
regarding the reviews, ii) provide clarification of which questions/issues that
staff can answer in writing, as well as beginning consideration of timelines
for such responses, iii) assist the Review Team in developing a methodology to
refine the questions/issues, and iv) direct or assist the Review Team in
obtaining information from other sources, where the board, advisory committees,
and/or supporting organizations are better sources of information. <br>
<br>
I must emphasize that consideration of the breadth of the anticipated
responses, and the level of resources that will be required to effectively
respond to the questions/issues are important discussion topics for the
interaction with ICANN Staff. Given that ICANN has finite organizational
resources, and that this is one of a number of important reviews, a schedule
will be developed to ensure that ICANN is responsive to this group’s
needs and that overall timelines are met. <br>
<br>
We also note that processes for disclosure of, and methods for dealing with
potential conflicts of interest (including proposed methods for withdrawal from
participation or abstention on some issues of conflict) should be
pre-requisites to substantively starting the review process (i.e., prior to
establishing standards and questions). With that in mind, we think in
more in concert with the ICANN model that the conflicts discussion should be
moved to the front of the agenda.<br>
<br>
Lastly, I have noted from a review of your agenda that you have scheduled a
total of five hours of time with ICANN Management during your first day.
This includes three hours of time with ICANN Staff for an open morning
session, and two hours of time with ICANN Staff in a closed afternoon session.
Given the role of ICANN Staff at this initial meeting described above, I would urge
you to consider whether the agenda reflects the actual time required for ICANN
Staff participation.<br>
<br>
Thank you again for the information and clarifications. Please direct any
responses or questions on the above points to Denise Michel (<a
href="Denise.Michel@ICANN.org">Denise.Michel@ICANN.org</a>). I look
forward to speaking with you and the Review Team next week. We look
forward to participating and assisting your Review Team and thank you for your
significant efforts in moving this process forward.<br>
<br>
Warmly, <br>
<br>
Rod Beckstrom<br>
<span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><br>
<br>
<br>
On 4/27/10 9:15 AM, "Janis Karklins" <<a
href="janis.karklins@icann.org">janis.karklins@icann.org</a>> wrote:</span><o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif"'>Dear Rod,<br>
<br>
On behalf of the A&T RT I would like to submit the list of issues that the
members of the Team would like to discuss with the senior management of ICANN.
The Team leaves at your discretion the decision on which staff members you
would like to take with you or delegate for this interaction. <br>
<br>
I was mistaken yesterday when I was talking with you about written response. I
misunderstood the discussion during the RT meeting where the term “to
start building material/ documental trace of the work of the RT” was
used. My apologies for confusion.<br>
RT is not asking written reply to list of question. They are submitted to allow
better preparation for the discussion.<br>
<br>
As you know, the RT is meeting on 5 and 6 May in Marina del Ray Hotel. The
interaction with staff is scheduled on 5 May. The morning session will be
public. The subsequent session will be held in private. We should work together
to set the modalities of the interaction.<br>
<br>
I stand ready to provide further clarifications.<br>
<br>
Best regards<br>
JK <br>
</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><br>
Warmly,<br>
<br>
Rod<br>
<br>
Rod Beckstrom<br>
President and CEO<br>
ICANN<br>
<br>
<i>One World. One Internet. Everyone Connected.</i></span><o:p></o:p></p>
</div>
</body>
</html>