[members-discuss] [ncc-services-wg] Update of RIPE NCC Procedural Document

On Thu, 4 Apr 2019, Nikolay Gorstkin wrote:

(...)
> 
> It could be funny if it were not so sad, right now we are seeing the RIPE NCC becoming the REGULATOR instead of the COORDINATOR.
> Considering the latest offers from the RIPE NCC about BGP hijacks,

Hello,

Just a small clarification:
2019-03 is merely a proposal currently under discussion.

Perhaps i missed that, but within the 350+ messages during the 
discussion i'm still to see someone argue that persistent intentional 
hijacks are something tolerable.

The NCC's Coordination work is very useful (can't really live without 
stat.ripe.net nowadays), but part of that great job is being 
continuously descredited when some people *persistently* annouce address 
space (or ASNs) that belongs to others -- it doesn't only disrupts 
legitimate owners communications but also networks that receive such 
ilegitimate announcements.

In the same way there are consequences for people which persistently 
falsify documents, maybe those consequences should also be applied to 
those falsifying route announcements. And one very important detail: it 
shouldn't be the NCC's role to determine if any specific persistent 
intentional hijack has happenned.

While several types of Abuse can't be considered as such in the full 
extent of RIPE NCC's service region, i think Hijacks are a minimum common 
denominator that can be agreed by everyone as untolerable.


(...)
>
> regards,
> Nikolay Gorstkin
>


Best Regards,
Carlos