<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=iso-8859-1"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><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-reply;
font-family:"Times New Roman","serif";
color:#1F497D;
font-weight:normal;
font-style:normal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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=WordSection1><p class=MsoNormal><span style='color:#1F497D'>I have some comments on the draft document. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>First, I think the timeframes do not work well when matched against the schedule we face to complete our work by the end of the year. I think any consultant report, to be helpful to the committee, must be submitted to us in final form no later than September 20, the date now proposed for a status report.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Second, I think it is important that the scope of work include benchmarking against other relevant multistakeholder processes. I propose that language be added to include that concept in the last paragraph of the scope of work as follows: “benchmark the ICANN PDP process against other relevant multistakeholder processes.” We can add this phrase after the parenthetical (See Annex) in that bullet point.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Third, notwithstanding that the GAC is one of many stakeholders at ICANN, its positioning vis-ŕ-vis the PDP is complicated by the fact that the bylaws currently contemplate the GAC providing its advice to the Board and not to supporting organizations as they do their work. I strongly agree with Jorgen that some specific mention of at least this aspect of the GAC issue should be included in the RFP and propose a fourth bullet point in the third part of the scope of work headed “provide a critical analysis . . .” as follows: “to what extent the ICANN bylaw process by which the GAC submits advice to the Board prevents or inhibits the participation of the GAC in the PDP and whether the PDP process could be strengthened by encouraging the submission of views and advice from the GAC and governments earlier in the process.”<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Thank you and I hope I am not too late in proposing these changes.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Larry<o:p></o:p></span></p><p class=MsoNormal><span style='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"'> atrt2-bounces@icann.org [mailto:atrt2-bounces@icann.org] <b>On Behalf Of </b>Alan Greenberg<br><b>Sent:</b> Wednesday, June 26, 2013 11:34 PM<br><b>To:</b> ATRT2<br><b>Subject:</b> [atrt2] URGENT: Final Draft RFP<br><b>Importance:</b> High<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>Attached please find the hopefully final RFP. Before disappearing for the next week, Brian made some edits, one of which removed the explicit reference to the GAC under scope of work. Since he is not here to present his rationale, I have temporarily left in his comment about why he felt strongly that the particular reference should not be included in the RFP.<br><br>Partly in response to that, Lise and I, with Avri's agreement included an explicit reference to ICANN ACs and SOs in the Annex description of stakeholders.<br><br>In addition to posting this RFP publicly, staff has identified two potential consultants to explicitly be invited to bid, One World Trust and Ken Bour. <b>With this note</b>, I ask staff to explain why they believe that they could meet our needs.<br><br>If anyone on the RT has additional suggestions for who to invite, please let us know quickly. The list of those submitting proposals to the ATRT1 competition can be found at <br><a href="http://www.icann.org/en/about/aoc-review/atrt/rfp-respondents-evaluation-19jun10-en.pdf">http://www.icann.org/en/about/aoc-review/atrt/rfp-respondents-evaluation-19jun10-en.pdf</a> .<br><br>If we are to meet the target issue date of July 1 (next Monday!), we need to finalize everything quickly, so I ask for all comments and suggestions to arrive no later that 12:00 UTC on Friday, June 28.<br><br>If there are any <u>crucial</u> edits to them RFP itself, please submit them as soon as possible to allow discussion.<br><br>Alan<br><br><br><br><br><br><o:p></o:p></p></div></body></html>