<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
+1 Scott.<br>
<br>
I am adding the recommendation that question #5 be moved to question
#2. Question #2 would then become "What steps are needed to protect
data and privacy" -- really the foundational question of what laws
govern our evaluation of the collection, storage and disclosure of
the data we will be discussing in #1?<br>
<br>
Before moving on to "Who should have access to the gTLD registration
data and why," it would help us to understand the requirements of
law - particularly comprehensive data protection laws -- that
differentiate the data collector/primary use (registrars) from
secondary users who might seek additional access to the data, e.g.,
via the RDS directory. What are data collectors legally allowed to
do with the personal data they collect, and what limits exist? All
seem a foundational understanding before we approach "Who should
have access to the gTLD registration data and why." <br>
<br>
Tx,<br>
Kathy<br>
<br>
<br>
On 3/1/2016 9:08 AM, Hollenbeck, Scott wrote:<br>
<blockquote
cite="mid:831693C2CDA2E849A7D7A712B24E257F4A37B30F@BRN1WNEXMBX02.vcorp.ad.vrsn.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<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:11.0pt;
font-family:"Calibri","sans-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;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;
font-weight:normal;
font-style:normal;}
.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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:12.0pt;color:#1F497D">Only one suggestion,
Chuck. Looking at the questions posed in #12, I wondered if
question #1 (“Who should have access to gTLD registration
data and why?”) is indeed the first question we should ask.
I would find it helpful to understand what “gTLD
registration data” is before I think about who should have
access to it, so I would like to suggest that the current
question #4 (“What data should be collected, stored, and
disclosed?”) be moved to question #1.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;color:#1F497D">When we get around to
asking “What data should be collected, stored, and
disclosed?” it might be helpful to read
<a moz-do-not-send="true"
href="https://www.rfc-editor.org/info/rfc7485">RFC 7485</a>.
It’s an inventory of information that was available via
WHOIS at the time the IETF’s WEIRDS working group wrote the
document. It might not be 100% accurate now, but I believe
it’s still the best summary of current practice.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Scott</span><span
style="font-size:12.0pt;color:#1F497D"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span
style="font-size:12.0pt;color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in
0in 0in 4.0pt">
<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"">
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a>
[<a class="moz-txt-link-freetext" href="mailto:gnso-rds-pdp-wg-bounces@icann.org">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Gomes, Chuck<br>
<b>Sent:</b> Monday, February 29, 2016 4:14 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<b>Subject:</b> [gnso-rds-pdp-wg] DRAFT work plan for
Phase 1<br>
<b>Importance:</b> High<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:black">Thanks to
everyone who responded regarding the approach to a work
plan proposed by the Leadership Team in our meeting last
week and online afterwards. I understand that some of you
may still have concerns about the proposed approach but
the Leadership Team decided that it might be more
effective to deal with any remaining concerns as we
discuss and refine a draft work plan. So we prepared a
DRAFT work plan for Phase 1 and have attached it. An
overview of the plan will be provided in our WG meeting
tomorrow with opportunity for questions and initial
discussion. We will continue to discuss the plan on this
list after tomorrow’s meeting and leading up to our
Marrakech meeting on 9 March, at which time we will try to
finalize it if possible.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Note that
whatever we finalize a work plan will have to be
flexible. It will have to be updated as we go depending
on our actual progress. Also note, that the details for
what are now steps 13 to 15 will have to be developed
after we finalize the results of step 12 and the preceding
steps.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">We encourage
all of you to at least do a quick review of this document
before our meeting tomorrow if possible. Regardless, we
ask everyone to review it in detail after tomorrow’s call.
If you are unable to participate in the WG meeting
tomorrow, in addition to reviewing the draft plan
thoroughly, please listen to the recording of the call.
We strongly request everyone to communicate your questions
and comments on the list so that we can start to refine
the plan online and be try to finalize it in our meeting
on 9 March.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Thanks in
advance for your cooperation and contributions.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gnso-rds-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
</blockquote>
<br>
</body>
</html>