> On 13 Apr 2022, at 13:47, John Curran <jcur...@arin.net> wrote:
>
>>
>> On 13 Apr 2022, at 5:16 AM, Alex Band <a...@nlnetlabs.nl> wrote:
>>
>> In case people would like to compare notes to the way this is arranged in
>> the RIPE NCC service region, here is the Resource Certification for non-RIPE
>> NCC Members policy which has been in place since 2013:
>>
>> https://www.ripe.net/publications/docs/ripe-596
>>
>> This resulted in the implementation documented here:
>>
>> https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/resource-certification-rpki-for-provider-independent-end-users
>>
>> It essentially means that Provider Independent End Users and Legacy End
>> Users can log into the RIPE NCC equivalent of ARIN Online and *only* manage
>> RPKI, without having access to any other options.
>
> Alex -
>
> Could you also include the definition of “legacy resource holders” in the
> RIPE region? In the ARIN region it’s quite clear – organizations (or their
> legal successors) who were part of the early Internet and obtained their
> number resources before ARIN’s formation are extended the courtesy of
> specific benefits for those number resources (i.e. basic registry services
> without any fee or contract and a favorable cap on total fees for those who
> bring their resources under registry agreement)
>
> As I understand it in the RIPE region, legacy number resources have little to
> do with parties that were issued them, and is instead some sort of magic
> property that is inherent to the address block itself and transfers along
> with the address block - is this correct?
I think this page gives the best overview of all the puzzle pieces at play:
https://www.ripe.net/manage-ips-and-asns/legacy-resources/ripe-ncc-services-to-legacy-internet-resource-holders
-Alex
