<div dir="ltr"><div>Dear All,</div><div>I opened the URL and I read</div><div>Quote</div><div>'"</div><div>(i.e. those with direct operational or service relationships with the <abbr title="Internet Assigned Numbers Authority">IANA</abbr> functions operator, in connection with names, numbers, or protocol parameters). " </div><div>Unquote</div><div>This is not correct as the beginning should be : including BUT NOT i.e.</div><div>Such language restrict the proposals other than those three operational communities involved in the process</div><div>Pls check the language that we have included in the DRAFT RFP</div><div>Regards</div><div>Kavouss <strong></strong></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-09-05 9:54 GMT+02:00 Milton L Mueller <span dir="ltr"><<a href="mailto:mueller@syr.edu" target="_blank">mueller@syr.edu</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">These corrections are good, but confusion about the RFP and its status is a Bad Thing.<br>
I would suggest that the same ICANN staff who sent the announcement should send a retraction to the same lists to which it was sent, saying very simply and clearly that the transmission was premature, the RFP is still a draft, and the ICG will formally issue the final RFP on September 8<br>
<div class="HOEnZb"><div class="h5"><br>
> -----Original Message-----<br>
> From: <a href="mailto:internal-cg-bounces@icann.org">internal-cg-bounces@icann.org</a> [mailto:<a href="mailto:internal-cg-bounces@icann.org">internal-cg-bounces@icann.org</a>]<br>
> On Behalf Of joseph alhadeff<br>
> Sent: Friday, September 5, 2014 3:34 AM<br>
> To: <a href="mailto:internal-cg@icann.org">internal-cg@icann.org</a><br>
> Subject: Re: [Internal-cg] Posting of draft RFP<br>
><br>
> I have made a similar statement on the IANA transition panel at IGF, in my own<br>
> capacity, as my understanding of the draft with the intention of providing<br>
> communities working on proposals the substantive elements of the RFP as soon<br>
> as possible.<br>
> On 9/5/2014 3:21 AM, Daniel Karrenberg wrote:<br>
> > On 5.09.14 9:01 , Patrik Fältström wrote:<br>
> >> All,<br>
> >><br>
> >> As you have noticed ICANN posted an announcement as a result of a request<br>
> to have the draft RFP posted, for transparency reasons. I am working with<br>
> ICANN on coming up with issues that makes this clear.<br>
> ><br>
> ><br>
> > On my own initiative I have just sent the following to<br>
> > <a href="mailto:ianatransition@icann.org">ianatransition@icann.org</a> where I saw the announcement:<br>
> ><br>
> > "Be aware that this text has not been formally agreed by the ICG yet.<br>
> > It is a very very stable draft, but changes may still occur before it<br>
> > is agreed.<br>
> ><br>
> > Daniel"<br>
> ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Internal-cg mailing list<br>
> > <a href="mailto:Internal-cg@icann.org">Internal-cg@icann.org</a><br>
> > <a href="https://mm.icann.org/mailman/listinfo/internal-cg" target="_blank">https://mm.icann.org/mailman/listinfo/internal-cg</a><br>
><br>
> _______________________________________________<br>
> Internal-cg mailing list<br>
> <a href="mailto:Internal-cg@icann.org">Internal-cg@icann.org</a><br>
> <a href="https://mm.icann.org/mailman/listinfo/internal-cg" target="_blank">https://mm.icann.org/mailman/listinfo/internal-cg</a><br>
_______________________________________________<br>
Internal-cg mailing list<br>
<a href="mailto:Internal-cg@icann.org">Internal-cg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/internal-cg" target="_blank">https://mm.icann.org/mailman/listinfo/internal-cg</a><br>
</div></div></blockquote></div><br></div>