[anti-abuse-wg] New on RIPE Labs: How We Will Be Validating abuse-c

Hi,


On Thu, 11 Oct 2018, Ronald F. Guilmette wrote:

>
> In message <DB5PR06MB1590D86126B81C0E1845FB3B94E10 at DB5PR06MB1590.eurprd06.prod.
> outlook.com>, Brian Nisbet <brian.nisbet at heanet.ie> wrote:
>
>> To address one point; Legacy resources are excluded because that is the way
>> that RIPE Policy works.
>
> That's rather like saying that the reason we have hurricanes is because
> God works in mysterious ways.

RIPE policies tend NOT to apply to address space issued *before* the RIPE 
NCC was created.


> Maybe you should elaborate and explain.  I would appreciate it if you did.
>
> I'm sure that will be enlightening and educational, at least for me, as
> I'm still not even sure that I fully grasp or understand the concept of
> "legacy" resources within the RIPE region.  (Up till now I had always
> been told that "legacy" resources only existed as such within the ARIN
> region.)

It emerged from the ARIN region, yes.

But in the "pre-RIR era" Jon Postel and others handing out IPv4 address 
space also distributed to orgs outside the (current) ARIN service 
region.

Some years ago, the RIRs agreed on a process to "transfer" those records 
from the ARIN database to the other RIR's databases, depending on where 
the resource holder was based.

Some of those transferred records are maintained in the "destination
databases", but part of them are simply frozen...

I'm aware about this because we also have some legacy space, and i 
also helped some of our Universities to recover control over their legacy 
space objects.


Regards,
Carlos


> Regards,
> rfg
>