<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><div class=""><p class="">Noah,</p><p class="">There is an hierarchy regarding the legacy space:<br class="">
</p><p class="">1. Legacy Space as a whole<br class="">
</p></div></div></blockquote><div><br class=""></div>I think the idea of “legacy space” is a mistake. The idea that there is some magical property to addresses which were first issued prior to the existence of RIRs which is preserved in perpetuity is absurd.</div><div><br class=""></div><div>There are legacy registrations which have certain questions about their contractual status and there is a great deal of ambiguity around what obligations the RIRs have towards those registrants and what, if any obligations those registrants have with regard to the RIRs.</div><div><br class=""></div><div>However, once that space is transferred, it should not have any special status. The new registrant should sign a contract with the RIR and should receive the space under the same terms and conditions as if that space was issued today.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><p class="">2. Idle Legacy Space [There are indeed legacy spaces in use, and
not idle]<br class=""></p></div></div></blockquote><div><br class=""></div>This would be legacy registrations where the registrant is not using the space or where the registrant no longer exists and the space has not yet been stolen, hijacked, or otherwise misclaimed.</div><div><br class=""></div><div>In the former case, it is up to the legacy registrant how they wish to handle the situation, through transfer, retaining the space, or returning it to the appropriate RIR.</div><div><br class=""></div><div>In the latter case, ideally, the RIR in question reclaims the space. However, in reality, identifying and sufficiently documenting the situation in order to do a reclamation is very difficult.</div><div><blockquote type="cite" class=""><div class=""><div class=""><p class="">
</p><p class="">3. Hijacked and now recovered Idle legacy Space. [There are some
legacy spaces that can never be reclaimed by their initial
allotees, probably because they are out of business, and there is
no successor organization]<br class=""></p></div></div></blockquote><div><br class=""></div>Other than the fact that it got hijacked at some time, I don’t see much difference between this and the above mentioned cases under 2. I think it is largely a distinction without a difference.</div><div><br class=""></div><div>Owen</div><div><br class=""></div></body></html>