<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Chuck,<br>
I hope you are having (had) an easy trip. I have respectfully
submitted that the order in which we evaluate key questions will
matter a lot in our process ahead. While the Charter lists a number
of of questions, I assume we have some ability to determine the best
order for evaluating them. The data protection construct gives us a
good order for this evaluation -- and I appreciate our discussion
regarding it. <br>
<br>
Tx for circulating a proposed approach to a work plan and receiving
comments. <br>
<br>
Best regards,<br>
Kathy<br>
<br>
<br>
On 2/27/2016 5:47 PM, Gomes, Chuck wrote:<br>
<blockquote
cite="mid:6DCFB66DEEF3CF4D98FA55BCC43F152E4A415394@BRN1WNEXMBX02.vcorp.ad.vrsn.com"
type="cite">
<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: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
{mso-style-priority:1;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
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";
color:black;}
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";
color:black;}
.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:1729954243;
mso-list-template-ids:-2128441168;}
@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:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@list l1
{mso-list-id:1878664647;
mso-list-template-ids:-99701074;}
@list l1: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 l1: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 l1: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 l1: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 l1: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 l1: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 l1: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 l1: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 l1: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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Kathy,<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">I
want to point out that a draft work plan has not been
provided yet. We just provided a proposed approach to a
work plan. The Leadership Team has a draft work plan just
about ready to send but we wanted to get feedback on the
approach first. With that understanding, I added some
additional responses below.<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";color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
Kathy Kleiman [<a class="moz-txt-link-freetext" href="mailto:kathy@kathykleiman.com">mailto:kathy@kathykleiman.com</a>]
<br>
<b>Sent:</b> Friday, February 26, 2016 2:34 PM<br>
<b>To:</b> Gomes, Chuck; <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> Re: [gnso-rds-pdp-wg] Notes and action
items from Next-Generation RDS PDP WG Meeting - deep
concerns<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Chuck, <br>
If I understand your responses to my responses correctly, the
first step of the draft work plan approach will now be:<br>
<br>
- what domain name registration data is collected and for what
purpose?<br>
<b><i><span style="color:#1F497D">[Chuck Gomes] </span></i></b><span
style="color:#1F497D"> First area of deliberation<br>
=> if I understand your response, adding this bullet
point to our work plan and starting here will work well.
Starting with this question seems quite consistent with the
mandate the Board assigned to our WG: "to define the purpose
of collecting, maintaining and providing access to generic
Top-Level Domain (gTLD) registration data" (Final Report on
Next-Generation gTLD Registration Service (RDS) to replace
WHOIS, page 1, paragraph 1)</span><span
style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[Chuck
Gomes] Let’s consider this after we send out the draft
work plan.<o:p></o:p></span></i></b></p>
<p class="MsoNormal"><span style="color:#1F497D"><br>
<br>
</span>- what specific laws and restrictions limit the re-use
or secondary use of this domain name registration data? (data
gathering, legal analysis section)<b><i><span
style="color:#1F497D"><br>
[Chuck Gomes] </span></i></b><span
style="color:#1F497D"> This will happen in our deliberation
on each possible requirement.<br>
==> Chuck, if we are collecting data about laws and
their restrictions for each possible secondary use, then
aren't we creating a large amount of duplication of effort?
As we know, many registrars and an increasing number of
registries operate in countries and with registrants in
countries with data protection laws (EU, Japan, S. Korea, to
name a few). The data protection laws impose frameworks for
evaluating the re-use and secondary use of information.
Understanding these laws and their limitations and
restrictions
<i>upfront </i>will enable us to better analyze and
approach the overall issue of secondary uses ("possible
requirements") -- create a prism for analysis of additional
proposes uses -- and avoid a lot of duplication of effort.</span><span
style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[Chuck
Gomes] I sure hope not. As chair I hope we can minimize
duplication of efforts except where more work is needed.<o:p></o:p></span></i></b></p>
<p class="MsoNormal"><span style="color:#1F497D"><br>
</span><br>
<span style="color:#1F497D">- what additional uses would
people like to use the domain name registration data and
why?<b><i><br>
[Chuck Gomes] </i></b> First area of deliberation.<br>
==> Now we are onto the issues of additional and
secondary uses of the registration data - not by the
registrars who collect it, but by many others.
<i>This is certainly an area to which the EWG devoted a huge
amount of time and resources.</i> And I think when we get
to this point, their analysis of the worldwide community and
how it would like to use Registrars' data will be very
valuable. But this is a step that requires understanding
other parts of the 11 "complex and inter-related questions"
of the Draft Charter that you pointed out to me (top of page
70 of the "Final Issue Report on a Next-Generation gTLD
Registration Directory Service (RDS) to replace WHOIS").
Thanks for pointing that out - and I am glad we are having
this conversation of the order we might address these
issues. I think it will save a lot of time in the end...
<br>
<br>
In addition, we will need to allocate time (a new bullet in
our work plan?) to analyze the risks to data collectors and
data subjects (registrars and registrants) of making this
data available to the users and for the purposes that
secondary users would like. That's an entire risk analysis
that the EWG did not have time or opportunity to undertake
and to us falls this critical process.
</span><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[Chuck
Gomes] One of the 11 questions specifically addresses
risk; I think it is the next to last one but do not have
them in front of me at the moment as I am in an airport
as I write this.<o:p></o:p></span></i></b></p>
<p class="MsoNormal"><span style="color:#1F497D"><br>
</span><br>
<span style="color:#1F497D">- Outreach to the Supporting
Organizations, Advisory Committees and outreach to the
greater Internet Community<b><i><br>
[Chuck Gomes] </i></b> We will do this multiple times
during our work.<br>
==> Great! Our work plan for phase 1 does not expressly
include the broader community outreach at this pivotal early
stage of our work (which is one to which broad input will
provide important insight and information). A small edit to
our work plan to add? Tx!<br>
<br>
==> <i>Overall, I trust it is OK to add a few more
points to our draft work plan to better reflect the
"complex and inter-related questions" in our Draft
Charter, and to ensure that we don't leave out valuable
steps in our planning or work. I think that was the
purpose of the "call to comments" on this early section of
our work, and thank you for the opportunity to comment.
</i><br>
<br>
==> Regarding wording, I would again respectfully request
that we leave the term <b>
"potential requirements"</b> for a later time. As the EWG
pointed out, there are legitimate and illegitimate secondary
uses of Whois data, legal and illegal ones. Lumping them all
under "potential requirements" this early in our work seems
both premature and misleading. As commenters said - it's
loose wording, and with all of our work ahead, it's better
not to be loose now. The EWG talked about "Users and
Purposes" and that may be a good time for us to use that
term as well.
<b>"Potential Users and Potential Purposes" </b>might work
too. </span><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><b><i><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[Chuck
Gomes] Let’s address this when we discuss the draft work
plan.<o:p></o:p></span></i></b></p>
<p class="MsoNormal"><span style="color:#1F497D"><br>
<br>
Best regards,<br>
Kathy<br>
<br>
</span>On 2/26/2016 5:14 AM, Gomes, Chuck wrote:<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Kathy,</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Let
me make sure I understand what you are suggesting. Are you
recommending that we add the responses that I made (the blue
text below)? If so, that would be fine assuming the rest of
the WG supports that.</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Chuck</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></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";color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
Kathy Kleiman [<a moz-do-not-send="true"
href="mailto:kathy@kathykleiman.com">mailto:kathy@kathykleiman.com</a>]
<br>
<b>Sent:</b> Thursday, February 25, 2016 10:55 PM<br>
<b>To:</b> Gomes, Chuck; <a moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<b>Subject:</b> RE: [gnso-rds-pdp-wg] Notes and action
items from Next-Generation RDS PDP WG Meeting - deep
concerns</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi Chuck,<br>
While I am pondering your other questions, let me send
thoughts back on the bullet points below. We seem to be in
agreement, and have received support on the list. Can we go
ahead and add these bullet points to the start "3. Review and
discuss draft work plan"? It will continue our process of
clarifying and defining our work ahead.<br>
<br>
To the outreach bullet point, it's a small but significant
change to the bullet point to include not only the SOs and ACs
of ICANN, but the larger Internet Community. If that's not
controversial (and I don't see why it would be as it's a good
idea and a past recommendation of the Whois Review Team), is
there any problem in expressly including it?
<br>
<br>
Best, Kathy<o:p></o:p></p>
<div>
<p class="MsoNormal">On 2/25/2016 8:27 PM, Gomes, Chuck wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><br>
For the draft work plan, section 3 below ("Review and
discuss draft work plan"), I would start with these opening
bullet points:<br>
- what domain name registration data is collected and for
what purpose? <b><i><span style="color:#1F497D">[Chuck
Gomes]
</span></i></b><span style="color:#1F497D"> First area
of deliberation.</span><br>
- what specific laws and restrictions limit the re-use or
secondary use of this domain name registration data? (data
gathering, legal analysis section)<b><i><span
style="color:#1F497D">[Chuck Gomes]
</span></i></b><span style="color:#1F497D"> This will
happen in our deliberation on each possible requirement.</span><br>
- what additional uses would people like to use the domain
name registration data and why?<b><i><span
style="color:#1F497D">[Chuck Gomes]
</span></i></b><span style="color:#1F497D"> First area
of deliberation.</span><br>
- Outreach to the Supporting Organizations, Advisory
Committees and outreach to the greater Internet Community<b><i><span
style="color:#1F497D">[Chuck Gomes]
</span></i></b><span style="color:#1F497D"> We will do
this multiple times during our work.</span><br>
- Deliberations as to whether these additional uses are
legal, possible, optional -- and what the costs and benefits
are of providing this data for the secondary purposes that
people are seeking it.
<o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><br>
-----------------------------------------------------------------------<br>
<br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><i>3.
Review and discuss draft work plan approach</i><o:p></o:p></p>
</div>
<ul type="disc">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
level1 lfo3">
Bulk of work in phase 1 relates to recommending requirements
for Registration Directory Services<o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
level1 lfo3">
Use EWG Final Report as starting point, as instructed by the
ICANN Board. Substantial public input was provided and
incorporated by this effort. Not restricted to the EWG Final
Report, but an important starting point. <o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
level1 lfo3">
Develop a comprehensive list of possible requirement
(without a debate) as a first step. Deliberations on each
possible requirement will be the next step after developing
this comprehensive list, including reaching consensus on
whether requirements should be included or not.<o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1
level1 lfo3">
Outreach to SO/ACs is expected during various stages of the
PDP, periodically as needed. This outreach may take various
forms, formal, informal. There is a requirement for formal
input at the early phase of the process. ....<o:p></o:p></li>
</ul>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
<br>
</body>
</html>