<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 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;}
@font-face
{font-family:Verdana;
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: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;}
span.gmail-
{mso-style-name:gmail-;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@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";color:#1F497D">You are getting way ahead of where we are at.<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>
<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""> gnso-rds-pdp-wg-bounces@icann.org [mailto:gnso-rds-pdp-wg-bounces@icann.org]
<b>On Behalf Of </b>Sivasubramanian M<br>
<b>Sent:</b> Monday, July 25, 2016 5:30 PM<br>
<b>To:</b> Andrew Sullivan<br>
<b>Cc:</b> gnso-rds-pdp-wg@icann.org<br>
<b>Subject:</b> Re: [gnso-rds-pdp-wg] OT Re: An important technical consideration about nature of the service (was Re: The overflowing list )<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:#333333"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Mon, Jul 25, 2016 at 11:40 PM, Andrew Sullivan <<a href="mailto:ajs@anvilwalrusden.com" target="_blank">ajs@anvilwalrusden.com</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal"><span class="gmail-">On Mon, Jul 25, 2016 at 08:04:17PM +0530, Sivasubramanian M wrote:</span><br>
<br>
<span class="gmail-">> ICANN Coordinates the allocation of Names and Numbers, by policies and</span><br>
<span class="gmail-">> programs. "Rule" may be a strong word here, slipped in from the question</span><br>
<span class="gmail-">> that I was answering, it is coordination, and the coordination happens by</span><br>
<span class="gmail-">> agreements. If it coordinates the allocation, it ought to consider itself</span><br>
<span class="gmail-">> responsible for all aspects concerning how fairly these resources are</span><br>
<span class="gmail-">> allocated, and ICANN especially ought to pay attention to the aspects</span><br>
<span class="gmail-">> related to DNS data.</span><br>
<br>
I think you will discover that quite a few of us spent a lot of time<br>
during the CCWG-Accountability work ensuring that the Mission was<br>
quite clear that ICANN does not "coordinate" the DNS beyond the root<br>
zone and certain subordinate policies in zones delegated according to<br>
contracts with ICANN. ICANN most definitely does not coordinate the<br>
allocation of names worldwide. <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:#333333"></span><span style="font-family:"Verdana","sans-serif";color:#333333">It does. Indirectly. By allocation of Top Level Domains for worldwide registration of names.</span><span style="font-family:"Arial","sans-serif";color:#333333"></span><span style="font-family:"Verdana","sans-serif";color:#333333"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<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">The _whole point_ of the DNS is to<br>
prevent such centralization in the interests of ensuring<br>
administration is local (loosely speaking, network topologically) to<br>
the affected parties.<o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";color:#333333"></span><span style="font-family:"Verdana","sans-serif";color:#333333">I have suggested nothing here to imply that ICANN's coordination of Names, on the commercial side, should
get any more detailed than decisions on TLDs and their delegation. But ICANN being the allocating body for Names on a Top Level, becomes responsible for the decision of allocation of the TLD, and (notionally) becomes responsible for ensuring that the Registry
in turn ensures fairness worldwide. The Registrant Data, as the point discussed here, becomes ICANN's responsibility. If anything goes wrong, as a Registrant, I would be right in asking ICANN "my .com registration data has been abused. Why didn't you ensure
that the .com Registry would keep my data safe with itself and with its Registrars?" ICANN can not possibly say, "we didn't do it, a reseller under a Registrar under the Registry did it, don't ask us"</span><span style="font-family:"Arial","sans-serif";color:#333333"></span><span style="font-family:"Verdana","sans-serif";color:#333333">. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:#333333"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:#333333">One that occurred to me is to harmonize the method of collecting Registrant data and harmonize policies for release of data to Law and Order agencies, and in a way empower the
DNS community to say "No" where they consider the request or directive excessive. This I have posted in a different thread. The initial thought was to centralize Registrant Data, which could be modified to be that of a system of keeping the sensitive elements
of the Registrant data decentralized with the Registries, but with uniform policies across the world. Agreed, we need to make sure that any changes to the process of handling and storing Registrant data does not alter the decentralized model. There are apparent
conflicts, but reconcilable. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:#333333"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:#333333"><o:p> </o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:#333333"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:#333333">Sivasubramanian M<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<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"><br>
<span class="gmail-">> By your question, "what rules does ICANN make about DNS", are you implying</span><br>
<span class="gmail-">> that DNS is free for all, in a commercial sense?</span><br>
<br>
Yes, actually, it is, and that's a feature and not a bug.<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
A<br>
<br>
--<br>
Andrew Sullivan<br>
<a href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><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>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>