<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Sep 25, 2012, at 3:23 AM, "Salanieta T. Tamanikaiwaimaro" <<a href="mailto:salanieta.tamanikaiwaimaro@gmail.com">salanieta.tamanikaiwaimaro@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><br><br><div class="gmail_quote">On Tue, Sep 25, 2012 at 12:19 PM, Kerry Brown <span dir="ltr"><<a href="mailto:kerry@kdbsystems.com" target="_blank">kerry@kdbsystems.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
My understanding is they redirected "took control" of several subdomains of the second level domain <a href="http://3322.org/" target="_blank">3322.org</a>. This would make them third level domains. I agree that theoretically the US courts could try to compel ICANN to do something like this at the root level. I don't think that would happen for reasons both technical and political. I could very well be wrong.<br>
<div class="im HOEnZb"><br>
Kerry Brown<br>
<br></div></blockquote><div><span style="background-color:rgb(255,255,255)">That in itself would threaten the security and stability of the Internet.</span></div></div></blockquote><br></div><div>According to whois, the domain <a href="http://3322.org">3322.org</a> is resolved by two servers, apparently property of Microsoft. It seems that Microsoft has cloned the <a href="http://3322.org">3322.org</a> zone and is selectively editing out any subdomain they do not like. So much about 'sophisticated' technology.</div><div><br></div><div>Such ideas and even provisions exist with TLDs. gTLDs are contractually obliged to provide their zone data (and more) to ICANN or "trusted third party". While not contractually obliged to do so, I believe many ccTLDs are subject to the same policy (even worse, data is copied without their consent). The general idea is that ICANN should be able to "restore the service" if the TLD operator fails. Not much different than what happened with <a href="http://3322.org">3322.org</a>, if you think of it.</div><div><br></div><div>The road to hell is paved with good intentions.</div><div><br></div><div>Daniel</div></body></html>