I read it every week. It's a finger on the pulse of a system on which I am totally dependent... Geoff Huston <gih@apnic.net> wrote:
Does anyone give a s**t about this any more?
From what I learned at the latest NANOG it's very clear that nobody reads this any more.
Is there any good reason to persist in spamming the nanog list with this report?
thanks, Geoff
those who read it and follow routing best practicez will continue to do those, those who havent yet given a shit wont get a sudden dose of exlax after seeing their asn in it. --srs (iPad) On 16-Oct-2011, at 5:47, "Joelja@bogus.com" <joelja@bogus.com> wrote:
I read it every week. It's a finger on the pulse of a system on which I am totally dependent...
Geoff Huston <gih@apnic.net> wrote:
Does anyone give a s**t about this any more?
From what I learned at the latest NANOG it's very clear that nobody reads this any more.
Is there any good reason to persist in spamming the nanog list with this report?
thanks, Geoff
I read it every week. It's a finger on the pulse of a system on which I am totally dependent...
the email i want to see here is "i wuz a polluter, but i read the cidr report, i haz seen the light, and i'm gonna stop polluting." no, i am not holding my breath. randy
Randy, yes, our ASN landed on polluter list once and we fixed it. I think there is nothing wrong in sharing that. Me and few bunch of self acclaimed geeks of our region read it and have done our level best to remove few polluters but with very less success. Seems like those who should be reading it are either too busy polluting or using hushmail. Geof, this is very useful stuff for many. so how many uniqe hits you get on the website? On Sunday, October 16, 2011, Randy Bush <randy@psg.com> wrote:
I read it every week. It's a finger on the pulse of a system on which I am totally dependent...
the email i want to see here is "i wuz a polluter, but i read the cidr report, i haz seen the light, and i'm gonna stop polluting."
no, i am not holding my breath.
randy
-- Regards, Aftab A. Siddiqui
aftab,
yes, our ASN landed on polluter list once and we fixed it. I think there is nothing wrong in sharing that.
thank you, thank you.
Me and few bunch of self acclaimed geeks of our region read it and have done our level best to remove few polluters but with very less success.
what would help? randy
Me and few bunch of self acclaimed geeks of our region read it and have done our level best to remove few polluters but with very less success.
what would help?
I guess rpki would help and a banner during every NOG/RIR meeting showing top polluters. I seriously don't understand that why an RIR can't send atleast a notice to those announcing bogus prefixes. A letter in RED mailed to the business address would help. m2c of bad geekness -- Regards, Aftab A. Siddiqui
Me and few bunch of self acclaimed geeks of our region read it and have done our level best to remove few polluters but with very less success. what would help? I guess rpki would help
working on it. it will lessen the perceived security benefit of fragging.
and a banner during every NOG/RIR meeting showing top polluters.
NOGs could do that for the polluting operators their region. this may actually be implementable! hey EOF, if you have not been completely digested by the NCC, perhaps this would be good in wien.
I seriously don't understand that why an RIR can't send atleast a notice to those announcing bogus prefixes. A letter in RED mailed to the business address would help.
RIRs claimed in the past that they have nothing to do with routing. of course, rpki-based origin validation changes this. but i suspect that they may still want to keep as distant as possible. randy
I seriously don't understand that why an RIR can't send atleast a notice to those announcing bogus prefixes. A letter in RED mailed to the business address would help.
RIRs claimed in the past that they have nothing to do with routing. of course, rpki-based origin validation changes this. but i suspect that they may still want to keep as distant as possible.
well IMHO, that's "stealing of resource." Yes if they have nothing to do with routing than atleast they should do somethin to safe guard what they are providing to thr members. So, any chance of putting a banner of top polluters in next APRICOT. :) -- Regards, Aftab A. Siddiqui
On Sun, 16 Oct 2011, Aftab Siddiqui wrote:
success.
what would help?
I guess rpki would help and a banner during every NOG/RIR meeting showing top polluters.
A similar thing was done at a USENIX in Monterey over a decade ago. The point behind that one was to drive home how bad it was for the attendees to use telnet to their boxes at the mothership. Nothing like seeing people watch their passwords put up on two screens to teach them about SSH. Granted, placing the CIDR report up on a screen may not have the same effect, but as NANOGs get video recorded, it's a lot harder to explain in the future why you were on that list. Somehow the visual is more powerful than pretending an erased email doesn't make it into a web archive.
I seriously don't understand that why an RIR can't send atleast a notice to those announcing bogus prefixes. A letter in RED mailed to the business address would help.
May be a useful angle for the RIRs to pursue - but are RIRs in the routing police business? wfms
On Sun, 16 Oct 2011 10:06:10 EDT, "William F. Maton Sotomayor" said:
A similar thing was done at a USENIX in Monterey over a decade ago. The point behind that one was to drive home how bad it was for the attendees to use telnet to their boxes at the mothership. Nothing like seeing people watch their passwords put up on two screens to teach them about SSH.
Did something similar at a SANS-EDU class a few years back, maybe 300 or so attendees. The first morning, I ran several carefully crafted tcpdumps on the wireless network to get just the SYN packets for telnet, ssh, rlogin/rsh, and POP in cleartext and over SSL. Then just before class started up after lunch, I announced the counts (was about 1/3 encrypted, 2/3 cleartext). When the slide with the numbers hit the screen, a predictable 2/3 suddenly got outraged "You have no right to grab our passwords/ that's irresponsible behaior for a security professional/ etc". So I joked "See Randy, I *told* you we wouldn't have to map from IP to MAC to conference registration to tell who they were" which didn't help matters much. ;) Then I tell them that yes, it *would* be irresponsible for me to snarf passwords, so I only grabbed SYN packets. The room got quiet, till I added "but those random people sitting out in the atrium aren't security professionals, and we have no control over whether they grab passwords or not, so you probably want to change your passwords." Sudden flurry of typing from 2/3 of the people. "Over a secure channel, of course". Sudden lack of typing and a lot of deer-in-headlights looks, and one voice from the back of the room "Well played" ;)
On Sun, 16 Oct 2011, Aftab Siddiqui wrote:
I seriously don't understand that why an RIR can't send atleast a notice to those announcing bogus prefixes. A letter in RED mailed to the business address would help.
The RIRs have indicated in the past that they don't see this as their job even though we keep asking for it. Instead, the RIRs do other things with our membership dues that we do not ask for. Go figure. -Hank
participants (7)
-
Aftab Siddiqui -
Hank Nussbacher -
Joelja＠bogus.com -
Randy Bush -
Suresh Ramasubramanian -
Valdis.Kletnieks＠vt.edu -
William F. Maton Sotomayor