nanog mailing list archives
Re: Notice: Fradulent RIPE ASNs
From: Rich Kulawiec <rsk () gsp org>
Date: Wed, 16 Jan 2013 06:26:28 -0500
On Tue, Jan 15, 2013 at 11:36:04PM +0100, Sander Steffann wrote:
Sorry, but you post this information on public mailing lists where it can be discussed but where no action can be taken [...]
That's not exactly correct. Lots of people on this list are perfectly capable of taking a variety of actions (based on this information) should they choose to do so. I have. I do not understand why you're so adamant about sending this information to an organization primarily distinguished by its incompetence and negligence. If they were actually DOING THEIR JOBS in even minimally diligent fashion, then Ron wouldn't needed to write that note or do the research behind it, because this wouldn't be happening. ---rsk
Current thread:
- Notice: Fradulent RIPE ASNs Ronald F. Guilmette (Jan 14)
- Re: Notice: Fradulent RIPE ASNs Eugeniu Patrascu (Jan 14)
- Re: Notice: Fradulent RIPE ASNs Alex Brooks (Jan 15)
- Re: Notice: Fradulent RIPE ASNs Ronald F. Guilmette (Jan 15)
- Re: Notice: Fradulent RIPE ASNs Sander Steffann (Jan 15)
- Re: Notice: Fradulent RIPE ASNs Suresh Ramasubramanian (Jan 15)
- Re: Notice: Fradulent RIPE ASNs Sander Steffann (Jan 15)
- Re: Notice: Fradulent RIPE ASNs Ronald F. Guilmette (Jan 16)
- Re: Notice: Fradulent RIPE ASNs Rich Kulawiec (Jan 16)
- Re: Notice: Fradulent RIPE ASNs Todd Underwood (Jan 16)
- Re: Notice: Fradulent RIPE ASNs Rich Kulawiec (Jan 16)
- Re: Notice: Fradulent RIPE ASNs Todd Underwood (Jan 16)
- Re: Notice: Fradulent RIPE ASNs William Herrin (Jan 16)
- Re: Notice: Fradulent RIPE ASNs Suresh Ramasubramanian (Jan 16)
- Re: Notice: Fradulent RIPE ASNs Rich Kulawiec (Jan 17)
- Re: Notice: Fradulent RIPE ASNs Alex Brooks (Jan 15)
- Re: Notice: Fradulent RIPE ASNs Eugeniu Patrascu (Jan 14)
- Re: Notice: Fradulent RIPE ASNs Matthew Petach (Jan 16)
- Re: Notice: Fradulent RIPE ASNs Carlos M. Martinez (Jan 16)
- Re: Notice: Fradulent RIPE ASNs Steven G. Huter (Jan 16)