<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 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:11.0pt;
        font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:#0563C1;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:#954F72;
        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;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
span.EmailStyle19
        {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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Thanks for the quick reply Nathalie. Please see my responses below.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Chuck<o:p></o:p></p>
<p class="MsoNormal"><a name="_MailEndCompose"><o:p> </o:p></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>From:</b> nathalie coupet [mailto:nathaliecoupet@yahoo.com]
<br>
<b>Sent:</b> Wednesday, May 31, 2017 2:40 PM<br>
<b>To:</b> Gomes, Chuck <cgomes@verisign.com><br>
<b>Cc:</b> gnso-rds-pdp-wg@icann.org<br>
<b>Subject:</b> [EXTERNAL] Re: Does the principle of proportionality apply to thin data?<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi Chuck,<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">My position was and is to secure unauthenticated access to thin data for all.<o:p></o:p></p>
<p class="MsoNormal"><b><i>[Gomes, Chuck] Wouldn’t ‘all’ include bad actors and consumers?<o:p></o:p></i></b></p>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">I envisioned access to RDS through 3 chock points to weed out bad actors as much as possible: <o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">An end-user would need to check the first box for authenticated/unauthenticated access,<o:p></o:p></p>
<p class="MsoNormal"><b><i>[Gomes, Chuck] For thin data the WG has already tentatively agreed that access would be unauthenticated so why would a box need to be checked for this?<o:p></o:p></i></b></p>
<p class="MsoNormal">then another box for consumer<o:p></o:p></p>
<p class="MsoNormal"><b><i>[Gomes, Chuck] What is a consumer? If someone was a consumer or not, would that determine what thin data they could access?<o:p></o:p></i></b></p>
<p class="MsoNormal">and a third would be to select the purpose or a default purpose would be selected for him (maybe no purpose could also be possible). <o:p></o:p></p>
<p class="MsoNormal"><b><i>[Gomes, Chuck] For thin data the WG has tentatively agreed that access would be granted without identifying a purpose so it appears that you disagree with that conclusion. I confess to being confused.</i></b><o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">Consumers don't need all the thin data to be published for their simple queries, since - in my mind - they want to make sure the website is legitimate or they want to identify the author in case of abuse (such as defamation, abuse or threats). <o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">If the principle of proportionality doesn't apply to most other cases, that's fine. But I think it does apply for simple consumer queries. <o:p></o:p></p>
<p class="MsoNormal"><b><i>[Gomes, Chuck] What is a ‘simple consumer query’? How does the ‘principle of proportionality’ apply to a simple consumer query? What is your understanding of what ‘proportionality’ means?</i></b><o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">This is an interesting debate, but I never thought it would lead to people actually proposing to drop vital data for the functioning of the Internet.<o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">I had in mind the other principle that you do not volunteer data when it is not required. It should be useful. Not because it is PPI, but out of caution.<o:p></o:p></p>
<p class="MsoNormal"><b><i>[Gomes, Chuck] It sounds like you are suggesting that RDS requestors should have to identify a purpose for thin data elements. Am I missing something?</i></b><o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><br>
Sent from my iPhone<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On May 31, 2017, at 2:21 PM, Gomes, Chuck <<a href="mailto:cgomes@verisign.com">cgomes@verisign.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">Nathalie,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Thank you for your suggestion that the principle of proportionality be added. That has generated a very lively discussion.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">As I am sure you have seen, a lot of WG members have stated that they do not believe that the principle of proportionality applies to thin data and have provided what I think is pretty good rationale in support of their position. As the
originator of the suggestion, do you still maintain that the principle applies to thin data? If so, how would you counter the arguments that have been made to the contrary?<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">All – If anyone else thinks that the principle of proportionality applies to think data, please speak up and provide your counters to the arguments that have been made to the contrary.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Chuck<o:p></o:p></p>
</div>
</blockquote>
</div>
</body>
</html>