[38249] in North American Network Operators' Group
Re: engineering --> ddos and flooding
daemon@ATHENA.MIT.EDU (Mark Mentovai)
Fri Jun 1 15:13:52 2001
Date: Fri, 1 Jun 2001 15:07:26 -0400 (EDT)
From: Mark Mentovai <mark-list@mentovai.com>
To: Geoff Zinderdine <geoff.zinderdine@mts.mb.ca>
Cc: <lucifer@lightbearer.com>, <nanog@merit.edu>
In-Reply-To: <001901c0eacc$94995a80$0c64a8c0@aegis>
Message-ID: <Pine.GSO.4.33.0106011500270.449-100000@oak.ggn.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
Geoff Zinderdine wrote:
>Why not just advertise the host route with an unreachable next hop from your
>main peering session?
Maybe your upstream sets the NEXT_HOP to your side of the point-to-point for
you, just in case you neglected to do so.
Even if they don't, who's to say what's unreachable? If the NEXT_HOP is
truly unreachable, in that there is no route to it, the BGP path won't be
marked as valid and won't make it to the IP routing table (Loc-RIB.)
I've long felt that IP should have come with a provision for an address that
is never routed. It would be great if we could get something like 127.0.0.2
for this very task.
Mark
