[159582] in North American Network Operators' Group
Re: Notice: Fradulent RIPE ASNs
daemon@ATHENA.MIT.EDU (Sander Steffann)
Tue Jan 15 17:36:28 2013
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <85415.1358253343@tristatelogic.com>
Date: Tue, 15 Jan 2013 23:36:04 +0100
To: Ronald F. Guilmette <rfg@tristatelogic.com>
Cc: nanog <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Hi,
>> is likely to be following the
>> reporting procedure for the provision of untruthful information to =
the
>> RIPE NCC at http://www.ripe.net/contact/reporting-procedure, which is
>> a well defined procedure. RIPE NCC will investigate any report
>> submitted though this procedure; there is a flowchart at this web
>> address that clearly explains what will happen.
>=20
> See above. I have done a great deal of work on this already. I leave
> it to other interested parties to file wharever additional reports =
they
> might feel are warranted or appropriate.
Sorry, but you post this information on public mailing lists where it =
can be discussed but where no action can be taken, and then refuse to =
post it to the single organisation that actually *can* do something with =
it?
Nobody else will take your research and submit it to a third party. It's =
your research: either you submit it to the RIPE NCC and action will be =
taken where appropriate, or you don't and then your research will be =
forgotten and nothing will be done... It's just one form to fill in.
Thanks,
Sander
