<div dir="ltr"><div>Alissa, Others,</div><div>I have sent many proposals , suggestions and comments</div><div>No answer was given to any of them except on an occasional basis </div><div>This time I am firm to say that </div>
<div>There is no need nor it is appropriate to rush in providing the final and définitive text of RFP to IGF due to the fact that there are some final tuning and alignments to be made and there is no active consultation process in place before 01 September to do so,</div>
<div>Thus no need to do something in harsh .</div><div>At the maximum ,a preliminary / darft doc. may be provided to IGF clearly indicating that it will be finalized at f2f on 06 September.</div><div>Regards</div><div>Kavouss </div>
<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-08-26 18:08 GMT+02:00 Alissa Cooper <span dir="ltr"><<a href="mailto:alissa@cooperw.in" target="_blank">alissa@cooperw.in</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 8/26/14, 6:35 AM, "Daniel Karrenberg" <<a href="mailto:daniel.karrenberg@ripe.net">daniel.karrenberg@ripe.net</a>><br>
wrote:<br>
<div><br>
><br>
><br>
>[I am sorry but I must have missed the consensus call on publishing the<br>
>RFP before the IGF. Am I the only one?]<br>
><br>
>I was surprised that a lot of you expressed that you want to publish the<br>
>RFP before the IGF even though our call uncovered that the text is not<br>
>final today. So there will be changes. Whatever one might think about<br>
>the substance of those, there will be a new text which we will have to<br>
>agree on.<br>
><br>
>So I must raise the question of how we agree on the final text as a<br>
>group. What will be the mechanism for agreement and the time involved?<br>
>I suggested to do this at the next f2f meeting because it does not seem<br>
>practical to me to achieve agreement by another mechanism before that<br>
>meeting. If we can agree on another mechanism that works faster, all the<br>
>better!<br>
><br>
>Not using a mechanism that clearly establishes agreement is what I meant<br>
>with "On the Fly!".<br>
><br>
>I have no objections against sharing the current draft with anyone,<br>
>including communities and IGF participants. I am not opposed to even<br>
>publishing it as the current draft. But until we agree as a group it has<br>
>to stay "draft". We could even say "Draft scheduled to be agreed on<br>
>September 6th" if we want to stress it is pretty stable.<br>
<br>
</div>This is exactly what I was suggesting — with the hope that we can settle<br>
on some provisional fixes for the issues raised on the call today within<br>
two days, we can publish a stable draft before the IGF, continue to<br>
solicit feedback on the draft from our communities, and finalize it after<br>
the IGF, either on Sept 6, on the list, or whenever we schedule our next<br>
conference call.<br>
<span class="HOEnZb"><font color="#888888"><br>
Alissa<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
><br>
>So how are we going to agree on the final text?<br>
><br>
>Daniel<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>
_______________________________________________<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>