<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; ">
<div>
<div>On Jun 19, 2013, at 10:48 AM, Mike Burns <<a href="mailto:mike@nationwideinc.com">mike@nationwideinc.com</a>> wrote:<span style="font-size: 12pt; font-family: Calibri; "> </span></div>
<blockquote type="cite">
<div style="WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space" dir="ltr">
<div dir="ltr">
<div style="font-family: Calibri; font-size: 12pt; ">
<div>And yet they route...</div>
</div>
</div>
</div>
</blockquote>
<br>
</div>
<div>
<div>Mike - </div>
<div> </div>
<div> You started by indicating that this was an issue with registry accuracy, but the fact is that </div>
<div> when the purported sale is contrary to the policy, the registry still accurately reflects the </div>
<div> actual party with the rights to the unique registry entry, since the rights only change when</div>
<div> done in accordance with policy set by the community. Whether something is being routed</div>
<div> on the Internet or not is an entirely different matter, as shown operationally from time to time</div>
<div> by the various route leaks that occur.</div>
<div><br>
</div>
<div> The registry is accurate as long as it follows the community-developed policy; if you don't </div>
<div> like the policy, then work to change it. Regardless, the registry accurately reflects what</div>
<div> the community indicates it should under the circumstances.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>/John</div>
<div><br>
</div>
<div>John Curran</div>
<div>President and CEO</div>
<div>ARIN</div>
<div><br>
</div>
</div>
<br>
</body>
</html>