[anti-abuse-wg] Russian carding... no, Islandic carding... no Belizian carding!

On Thu, Aug 11, 2016 at 06:01:55AM -0700, Ronald F. Guilmette
wrote:
>
>In message <08CBCEE4-B5B5-4B1A-8110-3508A025642C at gmail.com>,
>Suresh wrote:
>
>>H. Recovering resources assigned to non-existing entities
>>
>>http://www.ripe.net/ripe/meetings/ripe-59/presentations/rasmussen-recovering-resources.pdf
>
>That is a *very* interesting document Suresh!  Thanks for
>posting about it.

This presentation is making the same mistake that you are
consistently making. 
RIPE NCC *does NOT assign resources to end-users* (except in the
edge case of independent resource-holders who have a direct
contract with NCC)

PA resources, such as the /29 you're banging on about, are
*assigned* to the end user by a LIR from larger space *allocated*
to the LIR by the RIR (RIPE NCC in this case)

Any fraud, if such it is, is perpetrated on the *LIR*, not on RIPE
NCC. The NCC does not know, nor does it have to, know every
customer of every LIR. (Nor can the NCC "repossess" a /29 out of a
larger allocation - this is not possible for routing reasons
alone.)

FWIW, if a LIR is consistently and wilfully creates fraudulent
records in the ripedb you can make a complaint and the NCC has
sanctions available up to and including closure of the offending
LIR. I sincerely hope that this requires a better standard of
evidence than 
"It is self evident that they are evil criminals!!111!"

It is important to understand the distinction between
allocation and assignment and the process that leads to an
assignment of resources to an end-user before making wild
accusations. 

rgds,
Sascha Luck