Is there an RFC or other standards document that clearly states that static bogon filter lists are a bad idea? While this seems like common sense, there was just an RFC published on why IP addresses for specific purposes (like NTP) shouldn't be encoded into hardware.
Using a dynamic feed needs to be codified so that it finds its way into training classes, documentation, etc. Otherwise, this problem will recur indefinitely. - Dan On 1/20/05 10:18 AM, "Fergie (Paul Ferguson)" <[EMAIL PROTECTED]> wrote: > > > > ...and it's not like ARIN, etc., does not announce to the > Internet community when it allocates from address space > which may have previously been listed in various operational > places as "bogon" or "unalloacted" -- they do. > > I recall seeing similar announcements on the list from time > to time, suggesting due diligence on ARIN's behalf to notifying > people to modify their filtering. *plonk* > > Scanning the archives, an example: > > http://www.merit.edu/mail.archives/nanog/2004-01/msg00374.html > > - ferg > > > -- Jared Mauch <[EMAIL PROTECTED]> wrote: > > This hurts Ciscos reputation that they are causing > pockets of the internet to not work. Next subnets to get allocated > will increase the size of those pockets and so on. Then the internet > will become less reliable as an end-to-end transport medium, hurting > *everyone*. > > -- > "Fergie", a.k.a. Paul Ferguson > Engineering Architecture for the Internet > [EMAIL PROTECTED] or > [EMAIL PROTECTED]