<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 14, 2011, at 12:32 PM, Benson Schliesser wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 14, 2011, at 2:23 PM, Owen DeLong wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Legacy and other addresses returned should be treated the same.<br><br>Once an address is returned to ARIN, it is no longer a legacy address.<br><br>This policy does not make sense so long as it singles out legacy addresses.<font class="Apple-style-span"><font class="Apple-style-span" color="#144FAE"><br></font></font></div></blockquote><br></div><div>I agree with Owen on this.</div><div><br></div><div>ARIN should only accept returned legacy addresses from holders in the ARIN region. But, once accepted, that address space has been effectively transferred to ARIN. It is up to ARIN policy to decide whether to return that block to IANA, reallocate to new requests, etc. And there are no technical reasons to treat address blocks differently, as far as I'm aware.</div><div><br></div><div>Cheers,</div><div>-Benson</div><div><br></div><br></div></blockquote></div>Small nuance here...<div><br></div><div>ARIN should accept return of legacy resources currently served by ARIN (in-addr, whois), regardless of the</div><div>actual current location of the legacy holder. ARIN probably should not accept return of legacy resources</div><div>served by the 4 other RIRs unless ARIN coordinates such an acceptance with the applicable RIR.</div><div><br></div><div>Owen</div><div><br></div></body></html>