<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="">
<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 27 Apr 2022, at 8:22 PM, Owen DeLong <<a href="mailto:owen@delong.com" class="">owen@delong.com</a>> wrote:</div>
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<br class="">
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">On Apr 27, 2022, at 11:23, John Curran <<a href="mailto:jcurran@arin.net" class="">jcurran@arin.net</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Owen -
<div class=""><br class="">
</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class="">
<div class="">Yes, apparently RIPE makes the address blocks themselves somehow “magical” in nature for perpetuity regardless of who is the address holder - certainly an interesting approach when one considers the implications. ...</div>
</blockquote>
</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
Point is that if you hold space that was issued by a predecessor to the current 5 RIRs and you wish to migrate that space out of the ARIN policy regime, it can be easily transferred to RIPE-NCC under the “No Contract” status and RIPE-NCC will leave you alone
to use your space in peace.</div>
</div>
</div>
</blockquote>
<br class="">
</div>
<div>Owen - </div>
<div><br class="">
</div>
<div>Yes, you’ve noted such on multiple occasions, and RIPE is of course free to decide its services and applicable conditions as it sees fit. </div>
<div><br class="">
</div>
<div>In this case, that includes RIPE having a significantly different treatment for legacy number resources than ARIN – one which is associated with the number blocks themselves and without respect to the party to whom it was issued. Martin specifically
asked for the differences on how other RIRs handle legacy resources, and I was noting that not only can a legacy resource holder transfer the administration of their early issued block to RIPE, they can then transfer that block to another party – who will
effectively become a legacy resource holder even if they were never issued resources or even existed before the RIR system. That is a fairly significant difference, and hence why I pointed it out. </div>
<div><br class="">
</div>
<div>Thanks,</div>
<div>/John</div>
<div><br class="">
</div>
<div>
<div>John Curran</div>
<div>President and CEO</div>
<div>American Registry for Internet Numbers</div>
<div><br class="">
</div>
</div>
<div><br class="">
</div>
</body>
</html>