<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;">
On Feb 17, 2014, at 4:08 PM, Steve Noble <<a href="mailto:snoble@sonn.com">snoble@sonn.com</a>> wrote:<br>
<div><br class="Apple-interchange-newline">
<blockquote type="cite">
<div bgcolor="#FFFFFF" text="#000000" style="font-family: Helvetica; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
As a holder of both legacy and non-legacy ARIN objects, I have been subject to ARIN's registry update blocks on _non-legacy_ objects that I rightfully control and use. </div>
</blockquote>
<br>
</div>
<div>Steve - </div>
<div> </div>
<div> I'll be the first to admit you suffered needlessly, and appreciate your diligence in </div>
<div> pursuing the correction with ARIN (as it led to us finding an end case for ASN-</div>
<div> only resource records.) For those who might not remember the issue, read </div>
<div> <<a href="http://lists.arin.net/pipermail/arin-ppml/2012-September/026100.html">http://lists.arin.net/pipermail/arin-ppml/2012-September/026100.html</a>> </div>
<div> At this time, you should not longer have any problem updating your ASN records,</div>
<div> and I will apologize again that we did not recognize the issue as a fallout from our</div>
<div> migration any sooner than we did.</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>
</div>
</body>
</html>