<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 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="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" 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>
<div class=""><br class="">
</div>
<div class="">However, ARIN is the formal successor administrator of its registry with corresponding implications – for example, RIPE hasn't usually consider such registrations within their policy scope, whereas in ARIN’s case, administration of the registry
was specifically transferred to ARIN so that the community could have a voice in the policies by which they are managed. Legacy resource holders don’t have to participate if they don’t wish to, but all of the address blocks are subject to the community-developed
policy. </div></blockquote></div></div></blockquote><div><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><br class=""></div><div>Owen</div><div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class="">
<div class=""><br class="">
</div>
</blockquote>
Thanks,<br class="">
<div class="">/John</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">John Curran</div>
<div class="">President and CEO</div>
<div class="">American Registry for Internet Numbers</div>
</div>
<div class=""><br class="">
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">On 27 Apr 2022, at 10:49 AM, Owen DeLong <<a href="mailto:owen@delong.com" class="">owen@delong.com</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="">
Interestingly, if your resources were issued by an organization that was not one of the current 5 RIRs at the time of issuance, RIPE will consider your resources eligible to be treated as “legacy without contract” when you transfer to RIPE.
<div class=""><br class="">
</div>
<div class="">This is, by far, the most liberal and most respectful of legacy holders policy of any of the 5 RIRs at this time.</div>
<div class=""><br class="">
</div>
<div class="">A simple virtual machine within the EU is sufficient to create the nexus necessary to effect the transfer. Once the resources are transferred, it is no longer necessary to maintain the VM.</div>
<div class=""><br class="">
</div>
<div class="">Owen</div>
<div class=""><br class="">
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">On Apr 27, 2022, at 04:52 , 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="">
Folks -
<div class=""><br class="">
</div>
<div class="">It’s important to note that these references shared below are _not_ based on a common definition of “legacy number resource" –
<div class=""><br class="">
</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class="">
<div class="">ARIN considers a legacy number resource to be one that’s held by the original registrant (or their legal successor, e.g. due to merger) and that was issued by one of ARIN’s predecessor registries (NSI/InterNIC, GSI, SRI, Jon) and thus transferred
to ARIN at the time of our formation. </div>
<div class=""><br class="">
</div>
<div class="">ARIN extends basic registry services w/o fee or contract to legacy resource holders, and offers them the opportunity if they wish to enter into an RSA with ARIN, becoming a member and receiving all the same services as every other customer, ability
to vote in elections etc. only with a special cap on their total registry maintenance fees (currently of $175/year, increasing $25/yr) that’s applied regardless of total size of IPv4 number resource holdings.</div>
<div class=""><br class="">
</div>
<div class="">This is done in recognition that these legacy resource holders were involved in the earliest days of the Internet. </div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">I understand that in other region "legacy number resource” may have other meanings, and in fact may not even be related to the present day party with the rights to the address block. </div>
<div class=""><br class="">
</div>
<div class="">FYI,</div>
<div class="">/John</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">John Curran</div>
<div class="">President and CEO</div>
<div class="">American Registry for Internet Numbers</div>
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On 26 Apr 2022, at 10:24 PM, Andrew Dul <<a href="mailto:andrew.dul@quark.net" class="">andrew.dul@quark.net</a>> wrote:</div>
<div class="">
<div class="">
<div class="moz-cite-prefix">...<br class="">
</div><p class="">Ripe's published services to legacy holders is documented here</p><p class=""><a class="moz-txt-link-freetext" href="https://www.ripe.net/manage-ips-and-asns/legacy-resources/ripe-ncc-services-to-legacy-internet-resource-holders">https://www.ripe.net/manage-ips-and-asns/legacy-resources/ripe-ncc-services-to-legacy-internet-resource-holders</a></p><p class="">APNIC's calls these historical resources and its policies are noted here. APNIC will also require historical resource holders to become members effects Jan 1, 2023.<br class="">
</p><p class=""><a class="moz-txt-link-freetext" href="https://help.apnic.net/s/article/Historical-resources">https://help.apnic.net/s/article/Historical-resources</a></p><p class=""><a class="moz-txt-link-freetext" href="https://blog.apnic.net/2021/03/26/rpki-services-now-available-to-apnic-historical-resource-holders/">https://blog.apnic.net/2021/03/26/rpki-services-now-available-to-apnic-historical-resource-holders/</a><br class="">
</p>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
_______________________________________________<br class="">
ARIN-PPML<br class="">
You are receiving this message because you are subscribed to<br class="">
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" class="">ARIN-PPML@arin.net</a>).<br class="">
Unsubscribe or manage your mailing list subscription at:<br class="">
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" class="">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br class="">
Please contact <a href="mailto:info@arin.net" class="">info@arin.net</a> if you experience any issues.<br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div></blockquote></div><br class=""></body></html>