[95137] in North American Network Operators' Group
Re: Where are static bogon filters appropriate? was: 96.2.0.0/16 Bogons
daemon@ATHENA.MIT.EDU (Chris L. Morrow)
Thu Mar 1 14:33:41 2007
Date: Thu, 01 Mar 2007 19:32:49 +0000 (GMT)
From: "Chris L. Morrow" <christopher.morrow@verizonbusiness.com>
In-reply-to: <Pine.LNX.4.61.0703010930400.2752@soloth.lewis.org>
To: Jon Lewis <jlewis@lewis.org>
Cc: Eric Ortega <eric.ortega@midco.net>, nanog@merit.edu
Errors-To: owner-nanog@merit.edu
On Thu, 1 Mar 2007, Jon Lewis wrote:
> On Thu, 1 Mar 2007, Chris L. Morrow wrote:
>
> > So, where are static bogon filters appropriate? (loaded question perhaps)
> > I ask because just about every 'security expert' and 'security whitepaper'
> > or 'security suggestions' has some portion that speaks to "why it's a
> > grand idea to have acl-lines/firewall-policy tp block 'bogon' ip space"
> > (for some definition of 'bogon' of course).
>
> I suppose they're appropriate when done by network security consultants,
> as it guarantees future / repeat business. :)
ah-ha! but seriously, is this something an NSP/ISP should be doing? or is
this an enterprise function? or MSSP function? Are there standard tools
available to notify folks when changes occur? (aside from: "go check
iana.org website" or "golly traffic's not flowing anymore")
-Chris
