<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 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
{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.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";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Courier New";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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:"Courier New";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><p class=MsoNormal><strong><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>If you register a domain name, you are becoming part of the network infrastructure</span></strong><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'> - and that requires that you be contactable.</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'>[Milton L Mueller] <o:p></o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'><o:p> </o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'>This is a point that I have heard repeated endlessly by some people in the technical community. I don’t accept the logic here (indeed, I am not sure there is any logic). A domain name registration is not part of the “network infrastructure” by most scientific/economic definitions of “infrastructure.” DNS is an application. The infrastructure is the physical servers and lines that resolve domain names. Indeed, as you have pointed out in earlier messages, the DNS is not even required to maintain connectivity.<o:p></o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'><o:p> </o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'>But so what if it is part of the “infrastructure”? Everything connected to the Internet (by this logic) could be considered a “part of the network infrastructure.” Including this PC or my mobile phone.<o:p></o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'><o:p> </o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'>The idea that being connected to the internet, or having facilities connected to the internet, requires you to be “contactable” is not as simple as you make it out to be. Contactable by whom? Contactable when? Under what conditions? <o:p></o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'><o:p> </o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'>When you say that contactability is “required” you are again using words and concepts in a very imprecise way. Required by whom? By what? What kind of a “requirement” is this? A legal one? No. A contractual one? Maybe - but that is precisely what we are debating, whether ICANN contracts should require it or be amended, so in effect you are just begging the question. <o:p></o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'><o:p> </o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'>A lot depends on what we mean by “contactable.”<o:p></o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'><o:p> </o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'>In some sense, no one believes that domain registrants should not be contactable. Let me repeat that, because it’s vitally important that anyone participating in this debate understand this. NO ONE WANTS TO INSULATE DOMAIN REGISTRANTS FROM ALL CONTACT. The issue is what method that contact takes and what conditions are attached to it, and who controls the type of contact. <o:p></o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'><o:p> </o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'>You are advocating that unconditional, unrestricted contact, at all times, globally, for any and every purpose, including bad ones. Be brave and admit that. <o:p></o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'><o:p> </o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'>Others are arguing for applying some conditions and restrictions to access; perhaps the same that apply to, e.g., drivers license information, telephone numbers, school records, and so on. Burden of proof is on you, I think, to explain why having a domain name creates such an enormous, unmoderated obligation, such that your name, address, email should be open to global, unrestricted access, while having a telecom access line or a telephone number does not impose the same requirement. <o:p></o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'><o:p> </o:p></span></i></b></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>Perhaps it's that your domain name isn't resolvable from some part of the world - or has invalid signatures that cause web browsing to fail, is supplying poisoned cache records, or is supporting a DDOS attack. Or your mail server is generating spam. Whether you personally operate those servers, or contract someone else to do so for your domain - once you register a domain name, you are responsible for having them operate responsibly. And "responsibly" isn't subjective - it's the subject of the RFCs and standards that make the nework function. This is <strong><span style='font-family:"Arial","sans-serif"'>not</span></strong> religion, politics, morality or personal hygiene. If you register a domain name and do not live up to your responsbilities, the privilege of having a domain name, like that of driving, can be revoked. That doesn't prevent you from using the internet without one - or using postal mail or the telephone. </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'>[Milton L Mueller] <o:p></o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'><o:p> </o:p></span></i></b></p><p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'>I am afraid you are vastly overstating the value of having a Whois record that points to my name and email address. Having that record there does not guarantee that I will respond, does not guarantee that the info is accurate, and does not guarantee that you or anyone else will be able to fix any and every problem that happens. Furthermore, most of the contacting that takes place these days has nothing to do with the technical functioning of the domain – it has to do with what came to be known in earlier debates as “other purposes” – i.e., the desire of law enforcement and trademark lawyers to regulate conduct on the net. An exchange of whois data limited exclusively to registrars/registries and, after meeting a certain threshold, law enforcement, can meet most of those legitimate needs.</span></i></b><span style='font-size:11.0pt;font-family:"Courier New";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal> <o:p></o:p></p></div></div></body></html>