<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=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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;}
/* List Definitions */
@list l0
{mso-list-id:526719390;
mso-list-template-ids:-376304468;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:1221745462;
mso-list-type:hybrid;
mso-list-template-ids:883991028 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l2
{mso-list-id:1763138898;
mso-list-template-ids:-1642017274;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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">TXVB,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","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">Here is the second paragraph of the Mission & Scope section of the charter:<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" style="background:white;vertical-align:middle"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">“<i>During Phase 1,the PDP WG should, at a minimum, attempt to reach consensus recommendations
<o:p></o:p></i></span></p>
<p class="MsoNormal" style="background:white;vertical-align:middle"><i><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">regarding the following questions:<o:p></o:p></span></i></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo4;background:white;vertical-align:middle">
<![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><i><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">What are the fundamental requirements for gTLD registration data? When addressing this question, the PDP WG should consider, at a minimum, users
and purposes and associated access, accuracy, data element, and privacy requirements.<o:p></o:p></span></i></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo4;background:white;vertical-align:middle">
<![if !supportLists]><span style="font-size:11.0pt;font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><i><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Is a new policy framework and next-generation RDS needed to address these requirements?<o:p></o:p></span></i></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 lfo4;background:white;vertical-align:middle">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Courier New";color:black"><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><i><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">If yes, what cross-cutting requirements must a next-generation RDS address, including coexistence, compliance, system model, and cost, benefit, and
risk analysis requirements?<o:p></o:p></span></i></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 lfo4;background:white;vertical-align:middle">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Courier New";color:black"><span style="mso-list:Ignore">o<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><i><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">If no, does the current WHOIS policy framework sufficiently address these requirements? If not, what revisions are recommended to the current WHOIS
policy framework to do so?</span></i><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">”</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="background:white;vertical-align:middle"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="background:white;vertical-align:middle"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">The first primary bullet above references the first five areas for which the WG is supposed to develop requirements
(i.e., questions 1-5): users and purposes and associated access, accuracy, data element, and privacy requirements. The second primary bullet asks the fundamental question you highlight. That is why deliberation on the first five questions precedes a decision
on the fundamental question in the work plan. So the proposed work plan simply follows the terms of the charter.<o:p></o:p></span></p>
<p class="MsoNormal" style="background:white;vertical-align:middle"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="background:white;vertical-align:middle"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Do you suggest that we request a change to the charter from the GNSO Council?<o:p></o:p></span></p>
<p class="MsoNormal" style="background:white;vertical-align:middle"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="background:white;vertical-align:middle"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">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""> Gomes, Chuck
<br>
<b>Sent:</b> Wednesday, May 11, 2016 6:22 PM<br>
<b>To:</b> 'TXVB'; lisa@corecom.com; gnso-rds-pdp-wg@icann.org<br>
<b>Subject:</b> RE: [gnso-rds-pdp-wg] Work Plan for Approval - updated per RDS PDP WG 10 May meeting<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Here is a little more detail to add to my initial response to this message. I am on a second flight for the day and do not have access to the charter at the
moment so will possibly refer to the terms of the charter later.<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">Note that step 12(e) tasks us with doing what you suggest: “</span>Deliberate on Fundamental Question: Is a new next-gen RDS needed or can the existing WHOIS
system be modified to satisfy requirements for questions 1-5?<span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">” Am I correct in concluding that you think we should try to answer that question before deliberating on any of the
11 questions in the charter?<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>
<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"">
<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a> [<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>TXVB<br>
<b>Sent:</b> Wednesday, May 11, 2016 7:17 AM<br>
<b>To:</b> <a href="mailto:lisa@corecom.com">lisa@corecom.com</a>; <a href="mailto:gnso-rds-pdp-wg@icann.org">
gnso-rds-pdp-wg@icann.org</a><br>
<b>Subject:</b> Re: [gnso-rds-pdp-wg] Work Plan for Approval - updated per RDS PDP WG 10 May meeting<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><br>
I strongly object to this work plan. Per the charter we c are first to determine *if* a new RDS is needed. Everyone in this group seems to have accepted the idea of a new RDS as fait accompli, and hastely rushing ahead.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
-------- Original Message --------<br>
On May 10, 2016, 9:32 PM, Lisa Phifer wrote:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Dear all, <br>
<br>
Attached please find an updated draft of the RDS PDP WG Phase 1 Work Plan for WG approval.
<br>
<br>
Change marks in this update reflect edits to address feedback (below) from today's WG call.
<br>
<br>
During today's WG call, WG members on the call approved publishing this work plan, with the understanding that work plan details are dynamic and will continue to evolve.
<br>
<br>
<b>As indicated in Action Item #3 below, WG members not on today's call are now asked to review this work plan and raise any serious objections to this email list by COB Friday 13 May.<br>
<br>
</b>If no serious objections are raised, this work plan will be published on the WG's wiki. The WG will then continue on to the next tasks identified in this work plan.
<br>
<br>
Best regards, <br>
Lisa <br>
<br>
<br>
At 11:50 AM 5/10/2016, Marika Konings wrote: <o:p></o:p></p>
<p class="MsoNormal"><b><i>3. Discuss updated Phase 1 Work Plan - RDS PDP WG </i>
</b><o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
See latest draft distributed on the mailing list (dated 5 May) <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
Adjust date for 7e based on actual circulation date of SO/AC/SG/C outreach message
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
Item 8 - any and all requirements could be identified here, does not only need to relate to purpose. Possible list of requirements, no substance or analysis yet - will happen as part of the deliberations.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
How to avoid mixing process with substances? <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
Helsinki meeting could be used to get input from others, also should additional materials and/or webinars be prepared to facilitate the preparation of SO/AC/SG/Cs
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
Are the timeframes realistic for item 8c - what is expected from the WG? At this stage, the WG is not asked to express their opinion on the requirements on the list, but only to add any that are missing which will be added without discussion. Following that,
the document will be reviewed for possible duplication and re-grouping. <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
Need to differentiate between what Registrars collect as part of their business practices and what ICANN requires Registrars to collect them as part of accreditation and contractual requirements. This makes ICANN a data controller according to some. Others
note that the people or bodies that collect and manage personal data are called 'data controllers'.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
The list is POSSIBLE requirements - whether they will become requirements will be determined by the WG after deliberation.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
Step 9 to be refined after step 8 - will need to determine whether further outreach will be needed and in what form. Need to update dates as the current ones are not realistic.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
Leadership team will aim to keep the WG moving forward, but cannot overrush it either.
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
Update in step 13 reference to 12e, not 12d <o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo3">
Is there anything in this work plan that anyone seriously objects to? Is this work plan, understanding that it is dynamic and it will change, sufficiently good enough for the WG to consider it final and for the community to see? Note, dates will be updated
as concerns have been expressed in relation to some of the dates that do not reflect the current timeline. No objecctions expressed by those on the call - draft work plan considered good enough to move forward.
<o:p></o:p></li></ul>
<p class="MsoNormal"><b>Action item #2</b> - make sure that dates in work plan are realistic (see for example item 9, item 10)
<br>
<b>Action item #3</b> - Those that were not able to attend the meeting are requested to provide their input on is there anything in this work plan that anyone seriously objects to? Is this work plan, understanding that it is dynamic and it will change, sufficiently
good enough for the WG to consider it final and for the community to see? Deadline: by the end of this week (Friday COB wherever you are).
<o:p></o:p></p>
</div>
</body>
</html>