<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="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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="1026" />
</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 lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks for doing this Lisa.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Let me add that I think our original instructions for Outreach #2 suggested that groups review the possible requirements list: “</span>Over the past several
weeks the WG has been working on Work Plan Task 8 to develop a first cut of a ‘Possible Requirements List for gTLD Registration Data and Directory Services’. A copy of that list as of the date of this request is posted on the WG
<a href="https://community.icann.org/x/shOOAw">wiki</a> in <a href="https://community.icann.org/download/attachments/56986791/RDS%20PDP%20List%20of%20Possible%20Requirements%20D3%20-%2010%20June.pdf?version=1&modificationDate=1465652929146&api=v2">
pdf</a> and <a href="https://community.icann.org/download/attachments/56986791/RDS%20PDP%20List%20of%20Possible%20Requirements%20D3%20-%2010%20June.docx?version=1&modificationDate=1465652899541&api=v2">
word</a>. Please review this initial list according to the guidelines below and submit any additional possible requirements that you think should be added.<span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">”<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">We have since realized as a lot of you have that the very large size of the list of possible requirements made it unrealistic for those not in the WG to review
it in responding to Outreach #2 in the short time allowed. They are of course welcome to do that if they have time, but we are now saying that that is not necessary and that groups may suggest possible requirements without doing the list review first. As
Lisa says, if liaisons can readily eliminate duplicates proposed by their respective groups, that would be nice but that also is not a requirement. We will eliminate duplicates after we receive the responses to Outreach #2.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hopefully, this will make it much easier for each group to respond to the request prior to or in the Helsinki WG sessions.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> gnso-rds-pdp-wg-bounces@icann.org [mailto:gnso-rds-pdp-wg-bounces@icann.org]
<b>On Behalf Of </b>Lisa Phifer<br>
<b>Sent:</b> Friday, June 17, 2016 3:07 PM<br>
<b>To:</b> RDS PDP WG<br>
<b>Subject:</b> Re: [gnso-rds-pdp-wg] Outreach #2 / Draft 3<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dear all,<br>
<br>
To answer questions raised by Steve and others on outreach #2, Chuck has asked me to share this clarification -
<b>especially for those of you who volunteered to liaise with your SO/AC/SG/Cs during this informal outreach.<br>
<br>
</b>We are not expecting SO/AC/SG/Cs to review/comment on the initial list of possible requirements. The initial list was attached to outreach message #2 as examples of possible requirements taken from input sources and related to charter questions. However,
this initial list is just a starting point, prior to any WG deliberation.<br>
<br>
To make sure this starting point is inclusive and comprehensive, outreach message #2 informally invited other groups to suggest additions
<i>if they wish</i>. It is okay for groups to opt out of providing additions at this early stage or to simply suggest possible requirements without reviewing the initial list. If WG members serving as liaisons are able to flag any existing list items that are
similar to items suggested by their group, that is appreciated but not required.<br>
<br>
The WG will continue to expand, organize, and refine this on-going list to reflect additional inputs and WG progress, but there is simply not enough time to prepare, review and distribute another draft in advance of Helsinki. As such, the draft 3 attached to
outreach message #2 must suffice as our starting point for cross-community discussion at ICANN56.<br>
<br>
Regards,<br>
Lisa<br>
<br>
At 10:07 AM 6/11/2016, Marika Konings wrote:<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal">Dear All,<br>
<br>
Outreach message #2 has been posted here: <a href="https://community.icann.org/x/pYxlAw">
https://community.icann.org/x/pYxlAw</a>. Those that have volunteered to serve as a lead point of contact for their respective groups (see
<a href="https://community.icann.org/x/Nh_OAw)">https://community.icann.org/x/Nh_OAw)</a> should have received a separate email with instructions. Thank you for your assistance.<br>
<br>
Best regards,<br>
<br>
Marika<br>
<br>
<b>Marika Konings<br>
</b>Senior Policy Director & Team Leader for the GNSO, Internet Corporation for Assigned Names and Numbers (ICANN)
<br>
Email: <a href="mailto:marika.konings@icann.org">marika.konings@icann.org</a> <br>
<i> <br>
Follow the GNSO via Twitter @ICANN_GNSO<br>
Find out more about the GNSO by taking our <a href="http://learn.icann.org/courses/gnso">
interactive courses</a> and visiting the <a href="http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers">
GNSO Newcomer pages</a>.<br>
</i> <br>
<br>
<b>From: </b><<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a>> on behalf of Lisa Phifer <<a href="mailto:lisa@corecom.com">lisa@corecom.com</a>><br>
<b>Date: </b>Saturday 11 June 2016 at 08:23<br>
<b>To: </b>"<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>" <<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>><br>
<b>Subject: </b>[gnso-rds-pdp-wg] Draft 3 of Initial Possible Requirements List<br>
<br>
Dear all,<br>
<br>
Draft 3 of the initial possible requirements list is attached and has been posted on your wiki in DOC and PDF formats, both under Phase 1 documents and on the Sign-Up Sheet.<br>
<br>
Thanks to all of you who worked over these past several weeks to extract possible requirements from key input documents!
<br>
<br>
You should find every assignment that was completed before 10 June incorporated into Draft 3. Note that key input documents and possible requirements were assigned unique numbers as they were reformatted and incorporated into Draft 3; new possible requirements
were simply added to the end of the appropriate section(s) without any attempt to group similar items from different sources. In some cases, where the same exact possible requirement was mapped to multiple questions, this was simply noted to reduce repetition
and simplify review.<br>
<br>
There are still some assignments underway. A brief list of those key input documents have been included at the end of Draft 3 simply to let reviewers know those documents are being worked. You can still find the Sign-Up Sheet itself and links to all original
submissions here: <a href="https://community.icann.org/x/shOOAw">https://community.icann.org/x/shOOAw<br>
<br>
</a><b>Watch for another email to this WG list regarding Outreach Message #2 and further instructions for those of you who volunteered to assist with informal SO/AC/SG/C outreach.<br>
<br>
</b>Best Regards,<br>
Lisa<o:p></o:p></p>
</div>
</body>
</html>