[arin-ppml] Legacy number resources in the ARIN region (was: Re: Draft Policy ARIN-2021-8: Deprecation of the 'Autonomous System Originations' Field)

[John Curran]

Owen -

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.

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.

Thanks,
/John

John Curran
President and CEO
American Registry for Internet Numbers


On 27 Apr 2022, at 10:49 AM, Owen DeLong <owen at delong.com<mailto:owen at delong.com>> wrote:

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.

This is, by far, the most liberal and most respectful of legacy holders policy of any of the 5 RIRs at this time.

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.

Owen


On Apr 27, 2022, at 04:52 , John Curran <jcurran at arin.net<mailto:jcurran at arin.net>> wrote:

Folks -

It’s important to note that these references shared below are _not_ based on a common definition of “legacy number resource"  –

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.

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.

This is done in recognition that these legacy resource holders were involved in the earliest days of the Internet.

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.

FYI,
/John

John Curran
President and CEO
American Registry for Internet Numbers


On 26 Apr 2022, at 10:24 PM, Andrew Dul <andrew.dul at quark.net<mailto:andrew.dul at quark.net>> wrote:
...

Ripe's published services to legacy holders is documented here

https://www.ripe.net/manage-ips-and-asns/legacy-resources/ripe-ncc-services-to-legacy-internet-resource-holders

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.

https://help.apnic.net/s/article/Historical-resources

https://blog.apnic.net/2021/03/26/rpki-services-now-available-to-apnic-historical-resource-holders/

_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML at arin.net<mailto:ARIN-PPML at arin.net>).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact info at arin.net<mailto:info at arin.net> if you experience any issues.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20220427/bf710b5d/attachment.htm>