<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<base href="x-msg://621/">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>
<div>On Jun 20, 2012, at 11:22 AM, Milton L Mueller wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><span class="Apple-style-span" style="color: rgb(31, 73, 125); font-family: 'Courier New'; font-size: 15px; ">John,</span><span class="Apple-style-span" style="border-collapse: separate; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1" style="page: WordSection1; ">
<div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">
<span style="font-size: 11pt; font-family: 'Courier New'; color: rgb(31, 73, 125); ">We’ve been through this before.<o:p></o:p></span></div>
<div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">
<span style="font-size: 11pt; font-family: 'Courier New'; color: rgb(31, 73, 125); "><o:p> </o:p></span></div>
<div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">
<span style="font-size: 11pt; font-family: 'Courier New'; color: rgb(31, 73, 125); ">ICANN was created by the USG (and is still supervised by it even more directly than ARIN) to manage the root of the DNS. Country code top level domain managers were the DNS
version of “legacy holders.” They were given their TLDs before ICANN existed and thus the new corporation had no contractual authority over them, yet still they relied on ICANN’s management of the IANA database.<o:p></o:p></span></div>
<div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">
<span style="font-size: 11pt; font-family: 'Courier New'; color: rgb(31, 73, 125); "><o:p> </o:p></span></div>
<div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">
<span style="font-size: 11pt; font-family: 'Courier New'; color: rgb(31, 73, 125); ">ICANN tried to unilaterally assert authority over them, in essence attempting to force them to sign contracts by refusing to update their root zone records. That, um, didn’t
go over too well.</span></div>
</div>
</div>
</span></blockquote>
<div><br>
</div>
It's is not directly comparable; in fact, ARIN has encouraged legacy address</div>
<div>holders to update their registration records and has providing registry services </div>
<div>without change since inception. A legacy holder does not have to sign any </div>
<div>agreement, and has their registration and services continue in nearly the same</div>
<div>form as the day of ARIN's inception.</div>
<div><br>
</div>
<div>(In fact, we face a conflict between the community expecting that all address </div>
<div>holders, including legacy, need to be more proactive in updating their registration </div>
<div>data and the desire to minimize burdens on existing registrants)</div>
<div><br>
<blockquote type="cite"><span class="Apple-style-span" style="color: rgb(31, 73, 125); font-family: 'Courier New'; font-size: 15px; ">It amazes me that ARIN would try to repeat the same discredited trick. True, there is, or may be, less risk of creating an
international geopolitical incident because other nation-states are not as involved, but the basics are the same. YOU DON’T HAVE ANY AUTHORITY OVER LEGACY HOLDERS. Get used to it. It’s a historical quirk, it’s messy, but it’s just true. You will need to develop
a way to accommodate yourself to that fact, just as ICANN did.</span></blockquote>
<div><br>
</div>
<div>Your reasoned discourse does not become any more credible due to the </div>
<div>yelling/USE OF CAPS, and in fact may be seen as the refuge for arguments </div>
<div>which otherwise lack support.</div>
<div><br>
</div>
<div>You might also want to consider that the current ongoing process within </div>
<div>ICANN regarding establishment of policy for relegation of country code TLDs... </div>
<div>This does indeed have parallels, in that everyone is coming together to establish </div>
<div>clear policies for situations which were not considered in the past, much like the</div>
<div>formation of new transfer policies for IP addresses.</div>
</div>
<div><br>
</div>
<div>FYI,</div>
<div>/John</div>
<div><br>
</div>
<div>John Curran</div>
<div>President and CEO</div>
<div>ARIN</div>
<div><br>
</div>
</body>
</html>