nanog mailing list archives
RE: GRC rides again...
From: Roeland Meyer <rmeyer () mhsc com>
Date: Mon, 2 Jul 2001 22:10:49 -0700
From: Ron Buchalski [mailto:rbuchals () hotmail com] Sent: Monday, July 02, 2001 7:52 AM
It may be possible for the features of qos to help limit the extent of the attack, but with no predictability of where the attack sources or attack destinations are, you'd either need to apply qos when the attack occurs (reactive), or deploy it EVERYWHERE, on ALL provider's networks (intensely proactive). I doubt that anyone has the time or effort to deploy worldwide qos in order to stop random (and small, compared to overall traffic) dos attacks.
This WAS the idea, thanks for pointing out the weakness. Basically, yet another means to filter. But, too much work to implement. According to this, it wouldn't scale.
Current thread:
- RE: GRC rides again..., (continued)
- RE: GRC rides again... Dave Israel (Jul 02)
- Re: GRC rides again... David Howe (Jul 02)
- RE: GRC rides again... Roeland Meyer (Jul 02)
- RE: GRC rides again... Ron Buchalski (Jul 02)
- Re: GRC rides again... Ron Buchalski (Jul 02)
- Re: GRC rides again... Stephen Kowalchuk (Jul 02)
- Re: GRC rides again... David Howe (Jul 02)
- RE: GRC rides again... Benny Fischer (Jul 05)
- Re: GRC rides again... auto261850 (Jul 02)
- Re: GRC rides again... Owen DeLong (Jul 02)
- RE: GRC rides again... Roeland Meyer (Jul 02)
- RE: GRC rides again... Roeland Meyer (Jul 02)