<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 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: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:"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.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:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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">Good points David. Don’t you think also that architecture will have to happen later as well.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></a></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> gnso-rds-pdp-wg-bounces@icann.org [mailto:gnso-rds-pdp-wg-bounces@icann.org]
<b>On Behalf Of </b>David Cake<br>
<b>Sent:</b> Wednesday, March 22, 2017 1:28 PM<br>
<b>To:</b> Chen, Tim <tim@domaintools.com><br>
<b>Cc:</b> RDS PDP WG <gnso-rds-pdp-wg@icann.org><br>
<b>Subject:</b> [EXTERNAL] Re: [gnso-rds-pdp-wg] a suggestion for "purpose in detail"<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It is certainly my strong intention that security and stability and trust issues are addressed thoroughly. <o:p></o:p></p>
<div>
<p class="MsoNormal">However, I think many of those issues are going to be hard to address properly in Phase 1, which deals with fundamental requirements. We can, of course, specify that security and stability and resiliency etc are among the fundamental requirements
(and please, if you feel there are additional specific requirements there do bring them up). But for the most part, it is hard to fully address those issues until we have answered some fairly basic design questions (e.g. centralised or federated, cached or
uncached, etc) that we will not discuss until phase 2. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I also agree that whatever we produce will not be perfect. But I think if we carefully articulate the principles we have been working on and the architecture behind it, and create an architecture that allows for more flexibility in its
operation than whois, then a new RDS may be far more amenable to useful ongoing analysis and incremental improvement than whois. With careful design, we may be able to produce a system that is not just less broken than whois, but also easier to fix by future
policy processes. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">(even just the switch to RDAP goes a long way in this direction for some classes of problem) <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">David<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On 22 Mar 2017, at 12:26 pm, Chen, Tim <<a href="mailto:tim@domaintools.com">tim@domaintools.com</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">+1<o:p></o:p></p>
<div>
<p class="MsoNormal">whois is imperfect, like any system. like RDS will be if it comes to pass. RDS will just be imperfect in a different way. i don't agree with some of the rhetoric here on Whois being totally useless or horribly broken. but that ship
may have sailed. we'll need to understand and consider the unintended consequences of any new system, in our design process. as a member of the Business Constituency, there are RDS-related issues related to security and stability and trust in the DNS, issues
built into the Mission of ICANN, that are important to me and to other members of the BC, that are beyond the privacy issues that in my initial read seem to dominate the conversation of this working group. I look forward to bringing those to bear as I have
the time and attention to do so. <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Tue, Mar 21, 2017 at 6:15 PM, John Bambenek via gnso-rds-pdp-wg <<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">I think gating or stopping whois won't impede criminals one iota. It will impede researchers, defenders and those who try to make the internet safe and will be rife with unintended consequences.<br>
<br>
Sent from my iPhone<br>
<br>
On Mar 21, 2017, at 20:03, Rob Golding <<a href="mailto:rob.golding@astutium.com">rob.golding@astutium.com</a>> wrote:<br>
<br>
>> If access to whois is going to be closed off from the general public,<br>
>> there isn't going to be any point in charging money for whois privacy<br>
>> anyways.<br>
><br>
> You think spammers and scammers wont find a way to get access to the data and illegally share it just because it becomes gated ?<br>
><br>
> Rob<br>
> _______________________________________________<br>
> gnso-rds-pdp-wg mailing list<br>
> <a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
> <a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">
https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><br>
<br>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>