[50629] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Deaggregating for emergency purposes

daemon@ATHENA.MIT.EDU (Jared Mauch)
Tue Aug 6 13:39:08 2002

Date: Tue, 6 Aug 2002 13:38:29 -0400
From: Jared Mauch <jared@puck.Nether.net>
To: Phil Rosenthal <pr@isprime.com>
Cc: "'Omachonu Ogali'" <nanog@missnglnk.com>, nanog@merit.edu
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA/zNkI7d3EEmn3+v5DgN/l8KAAAAQAAAAQ0pFih5ztk+XJh+PzcrjwgEAAAAA@isprime.com>
Errors-To: owner-nanog-outgoing@merit.edu


	You should check that your upstream router vendor can handle
the increased config size.

	You are lucky to have as much as 512k config mem on a router
let alone 2M+ as is necessary for some people that do IRR based filtering.

	This is something everyone should keep in mind doing vendor
selection these days...

	- Jared

On Tue, Aug 06, 2002 at 01:29:58PM -0400, Phil Rosenthal wrote:
> 
> Most ISPs that build off of the IRR's do it nightly.  I am talking about
> 10 /24's out of /19, and I'm not announcing any of the /24's -- and wont
> unless there is an emergency, and only then would it be temporary.
> 

-- 
Jared Mauch  | pgp key available via finger from jared@puck.nether.net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.

home help back first fref pref prev next nref lref last post