[77447] in North American Network Operators' Group
Re: Please Check Filters - BOGON Filtering IP Space 72.14.128.0/19
daemon@ATHENA.MIT.EDU (Vicky Rode)
Thu Jan 20 12:35:25 2005
Date: Thu, 20 Jan 2005 09:34:24 -0800
From: Vicky Rode <vickyr@socal.rr.com>
Reply-To: vickyr@socal.rr.com
To: Jared Mauch <jared@puck.nether.net>
Cc: Suresh Ramasubramanian <ops.lists@gmail.com>,
thegameiam@yahoo.com, rsears@adnc.com, kurt@amnh.org, nanog@merit.edu
In-Reply-To: <20050120142934.GC19380@puck.nether.net>
Errors-To: owner-nanog-outgoing@merit.edu
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
in-line:
Jared Mauch wrote:
| On Thu, Jan 20, 2005 at 06:26:15PM +0530, Suresh Ramasubramanian wrote:
|
|>David Barak <thegameiam@yahoo.com> wrote:
|>
|>>While it says that bogon filters change, and provides
|>>a URL to check it, what percentage of folks who would
|>>use a feature like "autosecure" would ever update
|>>their filters?
|>>
|>
|>What do they do to update that bogon list anyway - push a new IOS image?
|
|
| Actually, my assumption is anyone with autosecure gets
| free software upgrades for life, as this is a flexible list that
| will change over time. Each time a change is made they
| need to release new software, and notify their installed
| customer base.
- -------------------
i understand bogon filters and reasoning behind it and i'm all for it.
but why does one think (maybe i missing something) this approach
(autosecure) is scalable and acceptable to update your ios or even
constantly updating your acls every time one has to update their bogon
filters? yet another think to look out for? i like to see the network
availability for aol, google, nasdaq, every time they update their bogons.
why can't this somehow be dynamically updated and /or linked to a
master file as opposed to upgrading the ios?
like to hear more thoughts on it.
regards,
/vicky
|
| - jared
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB7+ugpbZvCIJx1bcRApL0AJ0T2xb1ZHkxDSg0Ne3UwXqQ8z7xogCaA4rc
/An79+f9qmCKqfqkDsMH1wU=
=Sv6E
-----END PGP SIGNATURE-----
