[174239] in North American Network Operators' Group
Re: Prefix hijacking, how to prevent and fix currently
daemon@ATHENA.MIT.EDU (Saku Ytti)
Mon Sep 1 05:59:03 2014
X-Original-To: nanog@nanog.org
Date: Mon, 1 Sep 2014 12:58:51 +0300
From: Saku Ytti <saku@ytti.fi>
To: nanog@nanog.org
In-Reply-To: <CAAjbWEquXmz5V2e9ADg2DsqJB--njf+FAnmkA6xRgwDYbPfF6g@mail.gmail.com>
Errors-To: nanog-bounces@nanog.org
On (2014-09-01 14:58 +0530), Tarun Dua wrote:
Hi,
> Would it not help if RIPE un-publishes these ASN's from their whois database ?
>
> I filed the abuse report at RIPE but haven't heard back from them. We
> are NOT a RIPE member but an APNIC member.
Not sure against what RIPE rule it would be and what kind of leverage RIPE
could have here, even if we know they are intentionally evil.
However if I'd be supporting my family with this type of business model, I
would simply appear to be very bad at it, not evil. So I would claim that we
didn't do anything bad here, it was one of our customer (as they do have
different origin AS), and when pointed out, that this ASN has never been your
customer and cannot be, as completely different physical location, I'd simply
say we seeme to have verify-first-as turned off, so it could have been anyone,
and we're hard at work resolving it.
All of this with appropriate delay in answering to queries so you can keep on
doing it years before it's even clear you're evil not just really bad in your
job.
--
++ytti
