<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mv="http://macVmlSchemaUri" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1027"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1"/>
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Dear All, </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Staff preparation for the RFP is close to completion. ICANN can potentially launch the RFP a week or so earlier than the original date (9 February). Therefore, we would like to provide clarification and get
the Data Sub Team’s input on a couple of crucial items related to the RFP:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">1. Inclusion of the Sub Team’s Data Request Table </span></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">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, staff strongly recommend including
the Sub Team’s Data Request Table in the RFP documents<b>. </b>We understand that the document is currently in draft form and still under discussion within the Sub Team. Please be assured that to the extent the document is still in draft form when published
in the RFP documents, there will be a clarifying note describing the draft status of the document. To be accessible to all interested vendors, and for purposes of transparency, the draft Data Request Table will be published on icann.org along with other RFP
public documents. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">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 becoming the basis upon which respondents will rely on in their final RFP responses.
Depending on the actual RFP launch date and progress, 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).</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Even at its draft stage, the Data Request Table would be very helpful to get suitable vendors and targeted proposals. Since the goal is to launch the RFP as soon as possible, waiting for the Sub Team to finalize
the Data Request Table before launching the RFP would risk further delays. After the RFP is launched, the Data Sub Team still have some time to provide the final agreed document to responding vendors.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><u><span style="font-size:11.0pt">Question from Staff</span></u><span style="font-size:11.0pt">:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Can the Data Request Table, even in draft form, be shared with the full PDP WG no later than <b><u>22 January</u></b>? This will give the Sub Team a couple of more weeks to prepare the draft Data Request Table,
ensure the full WG is also comfortable with releasing the table as part of the RFP, and achieve an earlier RFP launch date.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">2. Potential Vendors </span></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Staff would like to seek your input on potential vendors to reach out to for the RFP. If you have suggestions on potential vendors, <b><u>by Monday, 15 January</u></b>, please provide: 1) legal entity name of
the potential vendor, 2) name of the contact person, and 3) email address of contact person. Due to privacy concerns, please send suggestions directly to </span><a href="mailto:ariel.liang@icann.org"><span style="font-size:11.0pt">ariel.liang@icann.org</span></a><span style="font-size:11.0pt">.
The contact information will be pre-loaded into the ICANN RFP system, which will generate an auto message when the RFP is launched, inviting suggested vendors to submit proposals.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">As advised previously, staff will also be reaching out to the full WG for suggestions of potential vendors.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Thank you for time and input! Happy to discuss these points during the next Sub Team meeting or before.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Best Regards,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Mary, Berry, Julie, and Ariel</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
</body>
</html>