[143886] in North American Network Operators' Group
Re: Prefix hijacking by Michael Lindsay via Internap
daemon@ATHENA.MIT.EDU (Denis Spirin)
Sat Aug 20 23:33:30 2011
In-Reply-To: <CAArzuovMZ9jgsdSor09AJCd86m7yEEL6r6uPVOkVFsHUfurs+Q@mail.gmail.com>
Date: Sun, 21 Aug 2011 05:32:54 +0200
From: Denis Spirin <noc@link-telecom.net>
To: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
RIPE NCC can't withdraw any prefixes. They can do de-registration. In this
case it will not lead to withdraw, as it is announced without any honor to
RIPE Database, like Routing Registry. So it will be changed from hijacked
company prefix to hijacked unused prefix, with the same result - mass
spamming from it.
2011/8/21 Suresh Ramasubramanian <ops.lists@gmail.com>
> You could ask that they withdraw the prefixes and see if that works?
>
> On Sun, Aug 21, 2011 at 8:45 AM, Denis Spirin <noc@link-telecom.net>
> wrote:
> > RIPE NCC staff is already doing its investigation.
> >
> > And RIPE NCC can't stop the routing at all.
>
>
>
> --
> Suresh Ramasubramanian (ops.lists@gmail.com)
>
