[arin-ppml] Legacy number resources in the ARIN region (was: Re: Inter-RIR transfer Policy reciprocity with Afrinic_Resource Transfer Policy proposal)
jcurran at arin.net
Mon Oct 12 14:34:56 EDT 2020
On 12 Oct 2020, at 1:37 PM, JORDI PALET MARTINEZ <jordi.palet at consulintel.es<mailto:jordi.palet at consulintel.es>> wrote:
For example, I can’t imposse the condition to legacy resources transfered from AFRINIC to ARIN to lose the legacy status, because that’s against ARIN policy.
It’s probably worth elaborating a bit on this, because I do not know the origin of this statement and may have to quibble a bit with the stated reasoning.
ARIN’s number resource policy applies to all resources under our administration – and in general doesn’t reference “legacy status” (i.e. the only section of ARIN’s policy manual which references legacy number resources is NRPM Section 12 / Resource Review, and that's solely to make plain that Resource Review doesn’t create any authority with respect to legacy number resources that ARIN doesn’t already have.)
ARIN defines legacy number resources with some precision: "number resources issued to the resource holder or its predecessor in interest prior to ARIN’s inception on December 22, 1997’. This is done in the ARIN Registration Services Agreement (RSA) because, per direction of the ARIN Board of Trustees, ARIN has provided reduced fees for legacy resource holders and slightly different exit provision on termination for cause.
Number resources are considered “legacy number resources” in the ARIN region is if they are held by original registrant (or its legal successor), and so it is highly unlikely that any resources transferred in from another region would be treated as legacy number resources (i.e. unless being brought into the region via merger/acquisition activity.) Similarly, it probably wouldn’t make sense for resources transferred to another party outside the region to be treated as “legacy number resources” (again, aside from M&A activity), but I should note that we leave it to other RIRs to define their terms and conditions of their registration services as they see fit.
I understand that some regions may treat “legacy status” as an innate property of the number resource block, but that certainly is not the case in the ARIN region - again, the only way number resources can be consider "legacy number resources” is while held by the original registrant or their legal successor, so the idea of “legacy status” for the number block itself independent of the resource holder is meaningless in the ARIN region.
ARIN wouldn’t find a policy proposal that required (or prohibited) “legacy status” treatment for transferred resources to be compatible, but not due to policy conflict but rather because it would could create a conflict with the very specific definition of “legacy number resources” in our registration services agreement.
President and CEO
American Registry for Internet Numbers
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ARIN-PPML