Re: [Internal-cg] Posting of draft RFP
I understood this was going out for comment. Saying it is 'subject to change' is not the same as 'does your community consider this form of words will adequately capture the input you need to give?'. It's an RFC on the RFP. -- Narelle Clark Daniel Karrenberg <daniel.karrenberg@ripe.net> wrote: On 5.09.14 9:01 , Patrik Fältström wrote:
All,
As you have noticed ICANN posted an announcement as a result of a request to have the draft RFP posted, for transparency reasons. I am working with ICANN on coming up with issues that makes this clear.
On my own initiative I have just sent the following to ianatransition@icann.org where I saw the announcement: "Be aware that this text has not been formally agreed by the ICG yet. It is a very very stable draft, but changes may still occur before it is agreed. Daniel" _______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
The message that went out gave the impression that this is the final version, not a draft. Mistakes happen, we sometimes do something similar in various IETF official announcements. We then ask the secretariat to send a new message that reads “CORRECTION: …” We should simply do the same here. No problem... Jari
I am still digging out from my email backlog from last week, and wanted to make one note about this. I realize that all has been resolved (thanks to those who took care of it), but I thought it was important to provide my perspective. Alice and Ergys did sent the first 3 September 2014 RFP announcement to me for review before it got posted, and it being a busy IGF day I failed to review it or send them comments prior to its posting. So I take the blame for the original language going out as it did. They were doing their jobs well as they have done all along and this mishap was not their fault. Alissa On 9/5/14, 12:04 PM, "Jari Arkko" <jari.arkko@piuha.net> wrote:
The message that went out gave the impression that this is the final version, not a draft.
Mistakes happen, we sometimes do something similar in various IETF official announcements. We then ask the secretariat to send a new message that reads “CORRECTION: …” We should simply do the same here. No problem...
Jari
_______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
participants (3)
-
Alissa Cooper -
Jari Arkko -
Narelle Clark