<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 20/12/2011, at 2:28 PM, McTim wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi David,<br><br><div class="gmail_quote">On Tue, Dec 20, 2011 at 8:28 AM, David Cake <span dir="ltr"><<a href="mailto:dave@difference.com.au">dave@difference.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
</div></div> The arguments against are all similar/equivalent.<br>
The arguments for are different, however.<br>
I think the position can be argued that treaties/legislation granting special rights to the IOC and RC have strong arguments against them, they have nevertheless been ratified/passed and it is not ICANNs position to reopen the issue but simply to acknowledge decisions already made.</blockquote>
<div><br></div><div><br></div><div>International treaty rights give special privileges in the DNS?</div></div></blockquote><div><br></div><span class="Apple-tab-span" style="white-space:pre"> </span>No. But international treaty rights may serve as a relatively forceful argument in favour of changes to DNS policy (policy that does, after all, reflect many other forms of international treaty rights). I'm certainly not suggesting that international treaties should be a mechanism for changing DNS policy, merely that rights granted by international treaty may (and probably should) be one of the many factors weighed by the GNSO (and other SO, for that matter) policy creation process. </div><div><span class="Apple-tab-span" style="white-space:pre"> </span>To turn the argument around, I don't think the GNSO policy process should be deliberately excluding international treaties as a factor when making policy decisions. Does anyone want to advance the argument that they should?</div><div><br><blockquote type="cite"><div class="gmail_quote"><div><br></div><div>I thought that was done by RFC?</div></div></blockquote><div><br></div><span class="Apple-tab-span" style="white-space:pre"> </span>RFCs are one path to creating DNS changes, but not the only one. The GNSO makes a LOT of policy decisions that have nothing to do with RFCs. </div><div><br></div><div><br></div><div><blockquote type="cite"><div class="gmail_quote"><div><br></div><div>.example as well as <a href="http://example.org/">example.org</a> for instance.</div></div></blockquote><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Which just goes to show that ICANN as a whole can be somewhat hypocritical. We do a lot of handwringing about excluding things like the Red Cross (which really do have some pretty solid international treaty support for their position), but there is a lot of stuff on the reserved names list via IETF processes on far flimsier justifications. Not that 'example' is particularly problematic.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Cheers</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>David</div><div><br></div></body></html>