[47614] in North American Network Operators' Group
Re: Effective ways to deal with DDoS attacks?
daemon@ATHENA.MIT.EDU (E.B. Dreger)
Tue May 7 18:43:44 2002
Date: Tue, 7 May 2002 22:43:17 +0000 (GMT)
From: "E.B. Dreger" <eddy+public+spam@noc.everquick.net>
To: vern@ee.lbl.gov
Cc: "Christopher L. Morrow" <chris@UU.NET>,
Scott Francis <darkuncle@darkuncle.net>,
Pete Kruckenberg <pete@kruckenberg.com>, nanog@merit.edu
In-Reply-To: <200205072150.g47LolO07444@yak.icir.org>
Message-ID: <Pine.LNX.4.20.0205072238220.26665-100000@www.everquick.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
> Date: Tue, 07 May 2002 14:50:47 -0700
> From: vern@ee.lbl.gov
>> 2) I'm pretty sure most providers aren't going to let
>> customers determine traffic engineering methods on their
>> networks
> See the above. This is not something done by the customers
> (well they could, but that's not the main idea).
I nominate the trust chain model. Sort of like BGP. If I speak
bad BGP, chances are that higher powers will edit filter-lists
and distribute-lists, and I'll have "set community kick-me" on my
back for the next three years. ;-)
Granted, BGP isn't foolproof. We all can recall some rather, uh,
messy BGP screwups that caused widespread problems. But by and
large, it works rather well.
--
Eddy
Brotsman & Dreger, Inc. - EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@brics.com>
To: blacklist@brics.com
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots.
Do NOT send mail to <blacklist@brics.com>, or you are likely to
be blocked.
