Hi Ariel: Thanks for this. I am sorry I did not get back to you yesterday. I think this is the right approach, to publish the entire document. To address the concerns voiced earlier about the questions we have not yet discussed, you could either: State in the RFP text that questions a, b and c had been honed to a certain point by the group where questions x, y, and z had not yet been discussed and therefore are in rougher form, Break the form into two sections, identifying the questions in the first section that have been discussed by the group and were closer to final and identifying questions in the second group, which have not yet been discussed and are expected to change more. If the table goes out without this clarification question, it will be fine as the RFP is meant to garner candidates with whom you will be able to have detailed discussions. Again, thanks for this work. Best regards, Kurt
On Jan 24, 2018, at 2:15 PM, Ariel Liang <ariel.liang@icann.org> wrote:
Hello everyone,
Staff preparation for the RFP is close to completion, and ICANN is in position to launch the RFP next week, ahead of the original schedule.
To provide vendors with better understanding of the project scope and survey task, as well as to ensure that community-developed guidance is incorporated into the RFP process, the Data Sub Team has agreed to the inclusion of the Data Request Table in the RFP document. Please see attached.
Since the document is currently in draft form and still under discussion within the Sub Team, please be assured that there is clarifying note in the RFP document describing the draft status of the Data Request Table. As per direction from the Data Sub Team, staff has generated this clean version that incorporates edits, comments, and instructions provided by the Sub Team.
To be accessible to all interested vendors, and for purposes of transparency, the attached Data Request Table will be published on icann.org <http://icann.org/> along with other RFP public documents.
The launch of the RFP will not affect the Data Sub Team’s ability to continue working toward the completion of the Data Request Table. There will be a period where ICANN staff answer questions from responding vendors and provide additional information and resources. The final agreed Data Request Table can therefore be included at this stage of the RFP, superseding the earlier draft, and being referenced by respondents in their final RFP responses. We will advise the Data Sub Team of the final internal deadline to finalize the Data Request Table (this is typically about one week before ICANN finalizes responses to send to RFP participants).
We greatly appreciate the time and contributions from the Data Sub Team members and the PDP WG Co-Chairs in the development of the document. The inclusion of the document would be very helpful to get suitable vendors and targeted proposal, while meeting the goal of launching the RFP as soon as possible. We will keep the WG apprised of the status of the RFP process.
Best Regards, Mary, Julie, Berry, and Ariel
<RPMs Data Request Table (Data & Anecdotal Question) - 24 January 2018.pdf>_______________________________________________ gnso-rpm-wg mailing list gnso-rpm-wg@icann.org <mailto:gnso-rpm-wg@icann.org> https://mm.icann.org/mailman/listinfo/gnso-rpm-wg <https://mm.icann.org/mailman/listinfo/gnso-rpm-wg>