<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=us-ascii"><meta name=Generator content="Microsoft Word 12 (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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 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";
color:black;}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
color:black;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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 bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Milton:<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'>I agree in principle, but we are not talking enough about when or how they can comment after a proposal is submitted. I also think they can comment on the RFP as a document and suggest where they think the RFP is not asking the right questions. We can do that outside of the RFP, but this needs to be addressed in a clearer manner somewhere.<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'>Joe<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";color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> Milton L Mueller [mailto:mueller@syr.edu] <br><b>Sent:</b> Friday, August 22, 2014 4:07 PM<br><b>To:</b> joseph alhadeff; internal-cg@icann.org<br><b>Subject:</b> RE: [Internal-cg] FW: Further RFP revision<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'>Joe,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Here I think we need to distinguish between actual proposals, which the RFP solicits and attempts to structure, and public comments on the proposal(s) that we put together. <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'>E.g., when you talk about a group addressing “a specific issue of interest such as accountability”, it sounds to me like you are talking about people reacting to specific proposals that have actually been made. In that case, they can review the proposals and assess the adequacy with which they address, say, the accountability issue, and submit comments during the public comment period accordingly. <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'>What I fear is that your current language will encourage groups to inundate the ICG with comments like “We think accountability is important and ICANN needs more of it” BEFORE any proposals have actually been made – as if WE were the ones developing the proposal. We cannot do anything with such comments. Either people concoct and propose specific institutional, legal and operational changes that enhance accountability (in which case they are helping to develop a proposal) or they are just expressing opinions, which is only helpful to us if these opinions are about specific proposals that we have before us. <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'>Do you understand my concern here?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>--MM<o:p></o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"></a><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext'> <a href="mailto:internal-cg-bounces@icann.org">internal-cg-bounces@icann.org</a> [<a href="mailto:internal-cg-bounces@icann.org">mailto:internal-cg-bounces@icann.org</a>] <b>On Behalf Of </b>joseph alhadeff<br><b>Sent:</b> Friday, August 22, 2014 3:41 PM<br><b>To:</b> <a href="mailto:internal-cg@icann.org">internal-cg@icann.org</a><br><b>Subject:</b> Re: [Internal-cg] FW: Further RFP revision<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Milton:<br><br>I have been a strong proponent of making sure that proposals are developed only in the communities, but I am not convinced that those processes will necessarily be accessible beyond the normal members of and participants to that community. If there is a specific issue of interest, such as accountability, and there is a specific opinion on that I think we need to be open to those comments. We can try to make the timing of more general stakeholder comments coincide with the publication of the proposal for comments, but we need a section that better addresses how we are open to comments outside of the drafting communities and how and when they can participate in our process.<br><br>Joe <o:p></o:p></p><div><p class=MsoNormal>On 8/22/2014 3:19 PM, Alissa Cooper wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>Forwarding on behalf of Milton who is having list email issues ...<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>On 8/22/14, 11:25 AM, "Milton L Mueller" <a href="mailto:mueller@syr.edu"><mueller@syr.edu></a> wrote:<o:p></o:p></pre><pre><o:p> </o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre><o:p> </o:p></pre><pre>-----Original Message-----<o:p></o:p></pre><pre>From: Milton L Mueller<o:p></o:p></pre><pre>Sent: Friday, August 22, 2014 11:04 AM<o:p></o:p></pre><pre>To: 'Alissa Cooper'; <a href="mailto:internal-cg@icann.org">internal-cg@icann.org</a><o:p></o:p></pre><pre>Subject: RE: [Internal-cg] Further RFP revision<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Alas, there are still some unresolved issues here.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I still have to insist that the first and second paragraphs contain<o:p></o:p></pre><pre>language that cover the same topic, but provide different meanings and<o:p></o:p></pre><pre>thus open to door to conflicting interpretations that could cause us<o:p></o:p></pre><pre>trouble. We need to choose one or the other of the meanings and delete<o:p></o:p></pre><pre>the other. <o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Here is an exegesis:<o:p></o:p></pre><pre><o:p> </o:p></pre></blockquote><pre>>From the middle of paragraph 1:<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre><o:p> </o:p></pre><pre>"Other parties may provide comments to the ICG on particular aspects that<o:p></o:p></pre><pre>may be covered by proposals that may be of significant interest to them,<o:p></o:p></pre><pre>for review by the ICG as time and resources permit. The ICG will direct<o:p></o:p></pre><pre>comments received from other parties to the relevant operational<o:p></o:p></pre><pre>communities as appropriate."<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Paragraph 2: <o:p></o:p></pre><pre><o:p> </o:p></pre><pre>"During the development of their proposals, the operational communities<o:p></o:p></pre><pre>are expected to consult and work with other affected parties; likewise,<o:p></o:p></pre><pre>other affected parties are strongly encouraged to participate in<o:p></o:p></pre><pre>community processes, as the ICG is requiring proposals that have<o:p></o:p></pre><pre>consensus support from a broad range of stakeholder groups."<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>My view is that the material from paragraph 1 must be deleted so as to<o:p></o:p></pre><pre>not confuse people and undermine the message in paragraph 2.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>As it is written now, the material in paragraph 1 invites parties to<o:p></o:p></pre><pre>provide "comments" to us on "proposals" (note the _plural_ form) that are<o:p></o:p></pre><pre>being considered by the operational communities. To me, this seems to<o:p></o:p></pre><pre>invite people to provide ongoing commentary on the ideas being considered<o:p></o:p></pre><pre>by the operational communities as they develop a proposal or consider<o:p></o:p></pre><pre>alternatives. That is not what we want. We want finished, agreed<o:p></o:p></pre><pre>proposals. <o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Paragraph 2 is much clearer about what we want. It "strongly encourages"<o:p></o:p></pre><pre>affected parties to participate in the operational community process for<o:p></o:p></pre><pre>the same of "consensus support from a broad range of...groups," but it<o:p></o:p></pre><pre>does not completely close the door to the receipt of finished alternative<o:p></o:p></pre><pre>proposals where consensus is not possible.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I really think that section of paragraph 1 and paragraph 2 are<o:p></o:p></pre><pre>articulating separate models of response and we cannot allow the RFP to<o:p></o:p></pre><pre>be released with such a critical ambiguity in it.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I also made a few minor changes, related to labeling IIA as Policy source<o:p></o:p></pre><pre>and the second bullet point under IIB<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I also responded to Martin's comments about his nervousness. My point is<o:p></o:p></pre><pre>that various proposals might come up with different ways of excluding or<o:p></o:p></pre><pre>separating policy from IANA implementation. Since we can’t use the<o:p></o:p></pre><pre>existing method (NTIA contract) to do so, this section is simply asking<o:p></o:p></pre><pre>them to explain the implications of their changes for existing policy<o:p></o:p></pre><pre>arrangements. However, we may be able to finesse this issue, because it<o:p></o:p></pre><pre>says almost the same thing as bullet point 2 in section II B. So do we<o:p></o:p></pre><pre>need it at all?<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Finally, a word about "testing." I don't know what kind of a parallel<o:p></o:p></pre><pre>universe the rest of you live in, but in the world I have become familiar<o:p></o:p></pre><pre>with as a social scientist, there is no "testing" of legal and<o:p></o:p></pre><pre>institutional accountability arrangements. We can project or estimate<o:p></o:p></pre><pre>based on past experience, but that is all. If there are technical and<o:p></o:p></pre><pre>operational changes called for by a proposal, yes, we can talk about<o:p></o:p></pre><pre>pre-testing them in some kind of laboratory set up. But asking people to<o:p></o:p></pre><pre>"test" what will happen if the NTIA is not there and some other<o:p></o:p></pre><pre>accountability mechanism is, is asking for the impossible. So I have<o:p></o:p></pre><pre>altered the language to deal with this.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>-----Original Message-----<o:p></o:p></pre><pre>From: <a href="mailto:internal-cg-bounces@icann.org">internal-cg-bounces@icann.org</a><o:p></o:p></pre><pre>[<a href="mailto:internal-cg-bounces@icann.org">mailto:internal-cg-bounces@icann.org</a>]<o:p></o:p></pre><pre>On Behalf Of Alissa Cooper<o:p></o:p></pre><pre>Sent: Thursday, August 21, 2014 8:40 PM<o:p></o:p></pre><pre>To: joseph alhadeff; <a href="mailto:internal-cg@icann.org">internal-cg@icann.org</a><o:p></o:p></pre><pre>Subject: Re: [Internal-cg] Further RFP revision<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I took one more stab at this — v10 attached and uploaded.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>There was some new text in v09(jha) about how people should feel free<o:p></o:p></pre><pre>to comment to us about transparency, completeness, etc. I think that<o:p></o:p></pre><pre>is true as a general matter, but that is not what we are asking for<o:p></o:p></pre><pre>specifically in this RFP.<o:p></o:p></pre><pre>That is what we will ask for — from anyone who cares to answer — after<o:p></o:p></pre><pre>we have the proposal components submitted (by December :)).<o:p></o:p></pre><pre>So I removed that text.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I also found the new first paragraph quite confusing — it said we are<o:p></o:p></pre><pre>issuing this RFP “for consideration” by all parties, which makes it<o:p></o:p></pre><pre>sound like we’re asking people to comment on the RFP itself, rather<o:p></o:p></pre><pre>than submit proposals. So, I did some editing on the first two<o:p></o:p></pre><pre>paragraphs, and also tried to work in the good suggestion from Manal<o:p></o:p></pre><pre>that we re-emphasize that we will direct comments to the operational<o:p></o:p></pre><pre>communities where we can. Here is how the first two paragraphs read now:<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>"The IANA Stewardship Transition Coordination Group (ICG) is seeking<o:p></o:p></pre><pre>complete formal responses to this Request for Proposals (RFP) from the<o:p></o:p></pre><pre>“operational communities” of IANA (i.e., those with direct operational<o:p></o:p></pre><pre>or service relationships with IANA; namely names, numbers, protocol<o:p></o:p></pre><pre>parameters). Other interested and affected parties are strongly<o:p></o:p></pre><pre>encouraged to provide their inputs through open processes run by these<o:p></o:p></pre><pre>operational communities. Other parties may provide comments to the<o:p></o:p></pre><pre>ICG on particular aspects that may be covered by proposals that may be<o:p></o:p></pre><pre>of significant interest to them, for review by the ICG as time and<o:p></o:p></pre><pre>resources permit. The ICG will direct comments received from other<o:p></o:p></pre><pre>parties to the relevant operational communities as appropriate.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>During the development of their proposals, the operational communities<o:p></o:p></pre><pre>are expected to consult and work with other affected parties;<o:p></o:p></pre><pre>likewise, other affected parties are strongly encouraged to<o:p></o:p></pre><pre>participate in community processes, as the ICG is requiring proposals<o:p></o:p></pre><pre>that have consensus support from a broad range of stakeholder groups.”<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>In section 0, I edited “change” to “address” in "Identify which<o:p></o:p></pre><pre>category of the IANA functions this submission proposes to change”<o:p></o:p></pre><pre>since some communities might propose no changes.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>In section 4 I still think there are three bullet points that need<o:p></o:p></pre><pre>elaboration, of just one sentence each, because they are not clear on<o:p></o:p></pre><pre>their face:<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>·Continuity of service requirements<o:p></o:p></pre><pre>·Risks<o:p></o:p></pre><pre>·Service integration aspects<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>For example, “Risks” seems so vague that each community could write a<o:p></o:p></pre><pre>novel about them and not be complete. What are we really looking for<o:p></o:p></pre><pre>here?<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Thanks,<o:p></o:p></pre><pre>Alissa<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>On 8/19/14, 8:50 AM, "joseph alhadeff" <a href="mailto:joseph.alhadeff@oracle.com"><joseph.alhadeff@oracle.com></a><o:p></o:p></pre><pre>wrote:<o:p></o:p></pre><pre><o:p> </o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>I have uploaded v9(jha) with a few suggested edits to further clarify<o:p></o:p></pre><pre>the operational vs impacted communities comment process... Also a<o:p></o:p></pre><pre>question of whether testing should be limited to Section III - are<o:p></o:p></pre><pre>those the only changes contemplated that could impact stability and<o:p></o:p></pre><pre>functionality?<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I think we are getting pretty close to a final draft...<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Joe<o:p></o:p></pre><pre>On 8/19/2014 11:05 AM, Milton L Mueller wrote:<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>Paul:<o:p></o:p></pre><pre>Done. It is uploaded as docx as version 09. Also proposed some<o:p></o:p></pre><pre>minor clarity changes to the preamble and added a comment responding<o:p></o:p></pre><pre>to Martin's nervousness. We can't have Martin being nervous.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Milton L Mueller<o:p></o:p></pre><pre>Laura J and L. Douglas Meredith Professor Syracuse University<o:p></o:p></pre><pre>School of Information Studies<o:p></o:p></pre><pre><a href="http://faculty.ischool.syr.edu/mueller/">http://faculty.ischool.syr.edu/mueller/</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>-----Original Message-----<o:p></o:p></pre><pre>From: <a href="mailto:internal-cg-bounces@icann.org">internal-cg-bounces@icann.org</a> [<a href="mailto:internal-cg">mailto:internal-cg</a>-<o:p></o:p></pre><pre><a href="mailto:bounces@icann.org">bounces@icann.org</a>] On Behalf Of Paul Wilson<o:p></o:p></pre><pre>Sent: Tuesday, August 19, 2014 10:05 AM<o:p></o:p></pre><pre>To: ICG<o:p></o:p></pre><pre>Subject: Re: [Internal-cg] Further RFP revision<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Milton, thanks for your comments on the "section 0" part. this<o:p></o:p></pre><pre>adds some needed clarity about the whole orientation of this<o:p></o:p></pre></blockquote></blockquote></blockquote><pre>process.<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre><o:p> </o:p></pre><pre>If you can, please make further edits to the version 8 document<o:p></o:p></pre><pre>linked below.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Paul.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>On 19 Aug 2014, at 9:30 pm, Paul Wilson <a href="mailto:pwilson@apnic.net"><pwilson@apnic.net></a> wrote:<o:p></o:p></pre><pre><o:p> </o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>Apologies for the delay, a new RFP revision is now online:<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre></blockquote><pre><o:p> </o:p></pre></blockquote></blockquote></blockquote><pre><a href="https://www.dropbox.com/s/4d2izh5jobgyu48/IANA%20Transition%20RFP%25">https://www.dropbox.com/s/4d2izh5jobgyu48/IANA%20Transition%20RFP%</a><o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>20v08.docx<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre><o:p> </o:p></pre><pre>Paul<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>On 19 Aug 2014, at 8:52 pm, Paul Wilson <a href="mailto:pwilson@apnic.net"><pwilson@apnic.net></a> wrote:<o:p></o:p></pre><pre><o:p> </o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>Dear all,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I am in the process of reconciling all inputs on the latest RFP<o:p></o:p></pre><pre>document,<o:p></o:p></pre></blockquote></blockquote><pre>and will have a clean version available in Dropbox shortly.<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>My intention is to go run this document sequentially during<o:p></o:p></pre><pre>tonight's<o:p></o:p></pre></blockquote></blockquote><pre>meeting, seeking ICG members' views and suggestions.<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>Thanks,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Paul.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre></blockquote></blockquote><pre>__________________________________________________________<o:p></o:p></pre><pre>______________<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>Paul Wilson, Director-General, APNIC <a href="mailto:dg@apnic.net"><dg@apnic.net></a><o:p></o:p></pre><pre><a href="http://www.apnic.net">http://www.apnic.net</a> +61 7<o:p></o:p></pre></blockquote></blockquote></blockquote></blockquote></blockquote><pre>3858<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>3100<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>See you at APNIC 38!<o:p></o:p></pre><pre><a href="http://conference.apnic.net/38">http://conference.apnic.net/38</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre></blockquote></blockquote><pre>_______________________________________________<o:p></o:p></pre><pre>Internal-cg mailing list<o:p></o:p></pre><pre><a href="mailto:Internal-cg@icann.org">Internal-cg@icann.org</a><o:p></o:p></pre><pre><a href="https://mm.icann.org/mailman/listinfo/internal-cg">https://mm.icann.org/mailman/listinfo/internal-cg</a><o:p></o:p></pre></blockquote><pre>_______________________________________________<o:p></o:p></pre><pre>Internal-cg mailing list<o:p></o:p></pre><pre><a href="mailto:Internal-cg@icann.org">Internal-cg@icann.org</a><o:p></o:p></pre><pre><a href="https://mm.icann.org/mailman/listinfo/internal-cg">https://mm.icann.org/mailman/listinfo/internal-cg</a><o:p></o:p></pre></blockquote><pre><o:p> </o:p></pre><pre>_______________________________________________<o:p></o:p></pre><pre>Internal-cg mailing list<o:p></o:p></pre><pre><a href="mailto:Internal-cg@icann.org">Internal-cg@icann.org</a><o:p></o:p></pre><pre><a href="https://mm.icann.org/mailman/listinfo/internal-cg">https://mm.icann.org/mailman/listinfo/internal-cg</a><o:p></o:p></pre></blockquote></blockquote><pre><o:p> </o:p></pre></blockquote><pre><o:p> </o:p></pre><p class=MsoNormal style='margin-bottom:12.0pt'><br><br><o:p></o:p></p><pre>_______________________________________________<o:p></o:p></pre><pre>Internal-cg mailing list<o:p></o:p></pre><pre><a href="mailto:Internal-cg@icann.org">Internal-cg@icann.org</a><o:p></o:p></pre><pre><a href="https://mm.icann.org/mailman/listinfo/internal-cg">https://mm.icann.org/mailman/listinfo/internal-cg</a><o:p></o:p></pre></blockquote><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>