[I am sorry but I must have missed the consensus call on publishing the RFP before the IGF. Am I the only one?] I was surprised that a lot of you expressed that you want to publish the RFP before the IGF even though our call uncovered that the text is not final today. So there will be changes. Whatever one might think about the substance of those, there will be a new text which we will have to agree on. So I must raise the question of how we agree on the final text as a group. What will be the mechanism for agreement and the time involved? I suggested to do this at the next f2f meeting because it does not seem practical to me to achieve agreement by another mechanism before that meeting. If we can agree on another mechanism that works faster, all the better! Not using a mechanism that clearly establishes agreement is what I meant with "On the Fly!". I have no objections against sharing the current draft with anyone, including communities and IGF participants. I am not opposed to even publishing it as the current draft. But until we agree as a group it has to stay "draft". We could even say "Draft scheduled to be agreed on September 6th" if we want to stress it is pretty stable. So how are we going to agree on the final text? Daniel
On 8/26/14, 6:35 AM, "Daniel Karrenberg" <daniel.karrenberg@ripe.net> wrote:
[I am sorry but I must have missed the consensus call on publishing the RFP before the IGF. Am I the only one?]
I was surprised that a lot of you expressed that you want to publish the RFP before the IGF even though our call uncovered that the text is not final today. So there will be changes. Whatever one might think about the substance of those, there will be a new text which we will have to agree on.
So I must raise the question of how we agree on the final text as a group. What will be the mechanism for agreement and the time involved? I suggested to do this at the next f2f meeting because it does not seem practical to me to achieve agreement by another mechanism before that meeting. If we can agree on another mechanism that works faster, all the better!
Not using a mechanism that clearly establishes agreement is what I meant with "On the Fly!".
I have no objections against sharing the current draft with anyone, including communities and IGF participants. I am not opposed to even publishing it as the current draft. But until we agree as a group it has to stay "draft". We could even say "Draft scheduled to be agreed on September 6th" if we want to stress it is pretty stable.
This is exactly what I was suggesting — with the hope that we can settle on some provisional fixes for the issues raised on the call today within two days, we can publish a stable draft before the IGF, continue to solicit feedback on the draft from our communities, and finalize it after the IGF, either on Sept 6, on the list, or whenever we schedule our next conference call. Alissa
So how are we going to agree on the final text?
Daniel
_______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
Alissa, Others, I have sent many proposals , suggestions and comments No answer was given to any of them except on an occasional basis This time I am firm to say that 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, Thus no need to do something in harsh . At the maximum ,a preliminary / darft doc. may be provided to IGF clearly indicating that it will be finalized at f2f on 06 September. Regards Kavouss 2014-08-26 18:08 GMT+02:00 Alissa Cooper <alissa@cooperw.in>:
On 8/26/14, 6:35 AM, "Daniel Karrenberg" <daniel.karrenberg@ripe.net> wrote:
[I am sorry but I must have missed the consensus call on publishing the RFP before the IGF. Am I the only one?]
I was surprised that a lot of you expressed that you want to publish the RFP before the IGF even though our call uncovered that the text is not final today. So there will be changes. Whatever one might think about the substance of those, there will be a new text which we will have to agree on.
So I must raise the question of how we agree on the final text as a group. What will be the mechanism for agreement and the time involved? I suggested to do this at the next f2f meeting because it does not seem practical to me to achieve agreement by another mechanism before that meeting. If we can agree on another mechanism that works faster, all the better!
Not using a mechanism that clearly establishes agreement is what I meant with "On the Fly!".
I have no objections against sharing the current draft with anyone, including communities and IGF participants. I am not opposed to even publishing it as the current draft. But until we agree as a group it has to stay "draft". We could even say "Draft scheduled to be agreed on September 6th" if we want to stress it is pretty stable.
This is exactly what I was suggesting — with the hope that we can settle on some provisional fixes for the issues raised on the call today within two days, we can publish a stable draft before the IGF, continue to solicit feedback on the draft from our communities, and finalize it after the IGF, either on Sept 6, on the list, or whenever we schedule our next conference call.
Alissa
So how are we going to agree on the final text?
Daniel
_______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
_______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
On 26.08.14 18:08 , Alissa Cooper wrote:
... we can publish a stable draft before the IGF, continue to solicit feedback on the draft from our communities, and finalize it after the IGF, either on Sept 6, on the list, or whenever we schedule our next conference call.
In that case we had a misunderstanding on the call and all is fine as far as I am concerned. Daniel
Yes we should only publish a draft before our f2f meerting Regards Kavouss 2014-08-26 21:02 GMT+02:00 Daniel Karrenberg <daniel.karrenberg@ripe.net>:
On 26.08.14 18:08 , Alissa Cooper wrote:
... we can publish a stable draft before the IGF, continue to solicit feedback on the draft from our communities, and finalize it after the IGF, either on Sept 6, on the list, or whenever we schedule our next conference call.
In that case we had a misunderstanding on the call and all is fine as far as I am concerned.
Daniel
_______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
+1 after taking into account Elise's input. Mary Uduma Sent from my BlackBerry wireless device from MTN -----Original Message----- From: Kavouss Arasteh <kavouss.arasteh@gmail.com> Sender: internal-cg-bounces@icann.org Date: Tue, 26 Aug 2014 21:36:33 To: Daniel Karrenberg<daniel.karrenberg@ripe.net> Cc: IANA etc etc Coordination Group<Internal-cg@icann.org> Subject: Re: [Internal-cg] SUBSTANTIVE: RFP Timing _______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
I agree with this approach as well. Paul. On 27 Aug 2014, at 2:08 am, Alissa Cooper <alissa@cooperw.in> wrote:
On 8/26/14, 6:35 AM, "Daniel Karrenberg" <daniel.karrenberg@ripe.net> wrote:
[I am sorry but I must have missed the consensus call on publishing the RFP before the IGF. Am I the only one?]
I was surprised that a lot of you expressed that you want to publish the RFP before the IGF even though our call uncovered that the text is not final today. So there will be changes. Whatever one might think about the substance of those, there will be a new text which we will have to agree on.
So I must raise the question of how we agree on the final text as a group. What will be the mechanism for agreement and the time involved? I suggested to do this at the next f2f meeting because it does not seem practical to me to achieve agreement by another mechanism before that meeting. If we can agree on another mechanism that works faster, all the better!
Not using a mechanism that clearly establishes agreement is what I meant with "On the Fly!".
I have no objections against sharing the current draft with anyone, including communities and IGF participants. I am not opposed to even publishing it as the current draft. But until we agree as a group it has to stay "draft". We could even say "Draft scheduled to be agreed on September 6th" if we want to stress it is pretty stable.
This is exactly what I was suggesting — with the hope that we can settle on some provisional fixes for the issues raised on the call today within two days, we can publish a stable draft before the IGF, continue to solicit feedback on the draft from our communities, and finalize it after the IGF, either on Sept 6, on the list, or whenever we schedule our next conference call.
Alissa
So how are we going to agree on the final text?
Daniel
_______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
_______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
participants (5)
-
Alissa Cooper -
Daniel Karrenberg -
Kavouss Arasteh -
mnuduma＠yahoo.com -
Paul Wilson