<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:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@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;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 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
{mso-style-priority:99;
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;}
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.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:JA;}
@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;mso-fareast-language:JA">+1<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:JA"><o:p> </o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:JA"><o:p> </o:p></span></a></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<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>Farell Folly<br>
<b>Sent:</b> Wednesday, July 27, 2016 6:42 AM<br>
<b>To:</b> Shane Kerr <shane@time-travellers.org><br>
<b>Cc:</b> RDS PDP WG <gnso-rds-pdp-wg@icann.org><br>
<b>Subject:</b> Re: [gnso-rds-pdp-wg] Use cases: Fundamental, Incidental, and Theoretical<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p>+1 Shane <o:p></o:p></p>
<p>Best Regards<br>
@__f_f__<br>
<a href="https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fabout.me%2ffarell&data=01%7c01%7cmarksv%40microsoft.com%7c8803fe64384b45c6343808d3b623e7df%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=n5cM7an1Vm0hVu2%2fAjB4Nj%2f32BEl%2fCCyxHH3LPHoDwk%3d">about.me/farell</a>
<br>
________________________________.<br>
Mail sent from my mobile phone. Excuse for brievety.<o:p></o:p></p>
<div>
<p class="MsoNormal">Le 27 juil. 2016 13:27, "Shane Kerr" <<a href="mailto:shane@time-travellers.org">shane@time-travellers.org</a>> a écrit :<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">All,<br>
<br>
[ Apologies for the length. I need get back to my actual job, so don't<br>
have time to make this shorter. ]<br>
<br>
I propose that:<br>
<br>
* We should have a way to reject some use cases<br>
* Part of that motivation should be whether it is actually needed for<br>
DNS<br>
<br>
This is not important now, but it will be at some point. It might be<br>
helpful to keep this in mind as we work on use cases.<br>
<br>
---------------------------------------------------------------------<br>
<br>
My thinking is that we have three basic types of use cases:<br>
<br>
Primary<br>
=======<br>
These use cases are necessary to actually be able to use the DNS<br>
itself. There are very few of these - almost all around configuring<br>
data that is needed for the DNS protocol to work.<br>
<br>
For example, you can get a domain in <a href="https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fNL.EU.ORG&data=01%7c01%7cmarksv%40microsoft.com%7c8803fe64384b45c6343808d3b623e7df%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=ZElr58dP2yDpvFLzbd61QAyBeTsU2LULOldb36mp40U%3d" target="_blank">
NL.EU.ORG</a> with only an e-mail<br>
address, and this is not published anywhere. (Even the e-mail address<br>
is not strictly necessary. One could set up a system based strictly on<br>
login to a web page.)<br>
<br>
The recent thought-experiment (aborted because it is not in our<br>
work plan) about finding the minimum set of data needed to run the DNS<br>
would have been a good start for defining these use cases.<br>
<br>
Incidental<br>
==========<br>
The vast majority of use cases that we see today exist only as an<br>
artifact of the way that WHOIS works.<br>
<br>
A long time ago a system was established that publishes certain<br>
information; without much thought about the long-term impact of the<br>
setup. Over the years people have found all kinds of creative, useful,<br>
and nefarious things to do with this information. However, storing or<br>
accessing this information has very little or nothing to do with<br>
actually making DNS work.<br>
<br>
For example, the DNS protocol certainly does not care what my fax<br>
number is, but anyone who looks up my domain name will see it. (Don't<br>
worry, I won't be doxed! I don't have a fax because this isn't 1986.)<br>
Likewise DNS software doesn't care when a domain was created. And so on.<br>
<br>
The use cases here include using RDS to track down criminals, research<br>
trademark disputes, create mass-mailing portfolios, looking for domain<br>
drop dates, and most of what people actually use WHOIS for today.<br>
<br>
Note that I definitely include technical uses that are outside of the<br>
needs of the DNS protocol itself. So, for example, having a way to<br>
contact a DNS operator when something is wrong falls into this category.<br>
<br>
Theoretical<br>
===========<br>
We have seen a couple of proposed use cases that seem to be ideas that<br>
people have for useful or harmful ways that RDS can be used, but that<br>
do not exist today (at least not that anyone can fully document).<br>
<br>
For example, there seems to be a desire to use the RDS as a way to<br>
issue warrants for information about registrants. While this may be<br>
useful, this is not possible today (even with RDAP, I note). Likewise<br>
concerns about using RDS to generate to generate lists of political<br>
enemies probably fits into this category.<br>
<br>
---------------------------------------------------------------------<br>
<br>
Discussion<br>
==========<br>
<br>
I bring this up because eventually we should be able reject certain use<br>
cases. (As an NCUC member, I expect to push back hard against a lot of<br>
use cases defined for business or law-enforcement purposes.)<br>
<br>
I think that what I called "primary" use cases have to be accommodated.<br>
I think there may be some disagreement about the details, but these<br>
should be relatively easy to come to consensus on.<br>
<br>
On the other hand, I think that both what I called "incidental" and<br>
"theoretical" use cases need to be motivated more strongly.<br>
<br>
There will probably be a natural tendency to prioritize existing uses<br>
of WHOIS - what I call "incidental" - because someone has some<br>
existing processes that depend on these. I think that this is wrong,<br>
and that any use of WHOIS outside of what is needed by DNS needs to be<br>
equally-well motivated.<br>
<br>
That's about it.<br>
<br>
Cheers,<br>
<br>
--<br>
Shane<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://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fmm.icann.org%2fmailman%2flistinfo%2fgnso-rds-pdp-wg&data=01%7c01%7cmarksv%40microsoft.com%7c8803fe64384b45c6343808d3b623e7df%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=jpg5JCbmalQRfVEnLKaOK35tjTHQPmTdDOsY2Kj7Clw%3d" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</body>
</html>