North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: DoS attacks, NSPs unresponsiveness

  • From: Jeff Workman
  • Date: Wed Nov 08 02:14:30 2000

Stoned koala bears drooled eucalyptus spit in awe as Bill Fumerola exclaimed:

> On Sat, Nov 04, 2000 at 06:00:38AM -0500, Jeff Workman wrote:
<dialog snipped>
> > Customer:  You've got to be kidding!
> > 
> > Me:        Nope, thank you, drive through. *click*
> A large IP provider (and construction/mining company) essentially told
> me the above.  That was after they turned down my circuit to "stop" the
> attack.
This is the point where I would start questioning whether my business
relationship with this provider is such a wise idea, and also whether or
not this behavior is the provider's policy or just the network engineer on
duty's policy.  I pay for bandwith, and for my upstream to at *least* do a
little bit to protect my investment.  I understand that if I need more
than an ACL on my router interface that they will gladly (most
likely) sell me a managed firewall package but even without that, I expect
them to get the garbage off my pipe when I notice it.  I don't even expect
them to take proactive measures to keep it off my wire, but when I see it,
I expect something to be done about it.  If not, then I will let my money
do the talking elsewhere.

Representing me, myself, and I.

"For competitive reasons we can't tell you the location of our fiber."
	-- An anonymous representative of a very large telco
"For competitive reasons we can't tell you the location of our backhoe."
	-- An anonymous representative of a contractor.