<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Jovan,<div><br><div><div>On Dec 9, 2013, at 7:07 AM, Jovan Kurbalija <<a href="mailto:jovank@diplomacy.edu">jovank@diplomacy.edu</a>> wrote:</div><blockquote type="cite"><div bgcolor="#FFFFFF" text="#000000"><p class="MsoNormal"><span style="color: rgb(34, 34, 34); font-family: Helvetica; font-size: 12pt; background-color: white;">David clarified that ICANN does
not host the root server.</span></p></div></blockquote></div><div><div><br></div>To clarify my clarification (:)):</div><div><br></div><div>ICANN operates the "Whois" database for the root. However that database is not particularly an operational concern (yes, it would be annoying if you couldn't look up the contact information for the administrators for a TLD, but it wouldn't have immediate operational impact). Verisign operates the root zone database. This database is probably what most people consider to be "the root server".</div><div><br></div><div><blockquote type="cite"><div bgcolor="#FFFFFF" text="#000000"><p class="MsoNormal" style="background-color: white; position: static; z-index: auto;"><span style="color: rgb(34, 34, 34); font-family: Helvetica; font-size: 12pt;">The US
'deletion’
move is almost as improbable as the chance that the Higgs Boson
experiment in
CERN will create anti-matter field which can siphon the Earth
through a black
hole.</span></p></div></blockquote><div><br></div><div><div>An interesting thought experiment would be what would happen if the UN asked (and the US government complied) with such a request. Assuming both ICANN and Verisign abided by the US government request:</div><div><br></div><div>First, the root server operators would need to accept the removal. They ultimately control the DNS data they serve. If they do nothing special, they will serve the updated zone. If the change removing the TLD was initiated using the regular process (that is, through the IANA), I suspect there would be a high likelihood most if not all of the root servers would comply. However, if the change came outside of normal processes (which is almost certainly the case since the normal process would require the country in question to agree to be removed), I believe at least some of the root servers would refuse to accept the modified zone.</div><div><br></div><div>But let's assume the root servers accepted the change. Next, the world's resolver operators would need to accept the removal. If they disagreed and were sufficiently motivated, there are a variety of mechanisms by which they could choose to serve the unmodified zone. It is important to note that since DNSSEC validation is typically done at the resolver, DNSSEC protections do not necessarily apply.</div><div><br></div><div>The implication of all of this is that any action to remove a TLD without general agreement/acceptance of the root server operators and resolver operators (who are generally every ISP in the world), will likely result in a reasonable facsimile of chaos, a fracturing of the "One Internet", and, more to the point, unlikely to be particularly successful. This is why I've never really thought this was a realistic scenario, particularly given we're talking about _names_ that make it easy for people to get to the resources, not the resources in question. It would be like removing <insert bad person's name> from the telephone directory as opposed to canceling their credit cards or arresting them. </div><div><br><blockquote type="cite"><div bgcolor="#FFFFFF" text="#000000"></div></blockquote></div><div>Regards,</div><div>-drc</div><div><br></div></div></div></div><link rel="File-List" href="x-msg://52/Jovan%20Kurbalija_files/filelist.xml"><style>
<!--
/* Font Definitions */
@font-face
{font-family:Arial;
panose-1:2 11 6 4 2 2 2 2 2 4;
mso-font-charset:0;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:3 0 0 0 1 0;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;
mso-font-charset:0;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:3 0 0 0 1 0;}
@font-face
{font-family:"Lucida Calligraphy";
panose-1:3 1 1 1 1 1 1 1 1 1;
mso-font-charset:0;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:3 0 0 0 1 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-ascii-font-family:Cambria;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:Cambria;
mso-fareast-theme-font:minor-latin;
mso-hansi-font-family:Cambria;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;
mso-ansi-language:EN-US;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;
text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;
text-underline:single;}
<a href="http://span.il">span.il</a>
{mso-style-name:il;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.SpellE
{mso-style-name:"";
mso-spl-e:yes;}
span.GramE
{mso-style-name:"";
mso-gram-e:yes;}
@page Section1
{size:595.0pt 842.0pt;
margin:1.0in 1.25in 1.0in 1.25in;
mso-header-margin:.5in;
mso-footer-margin:.5in;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
</style></body></html>