[1172] in North American Network Operators' Group
Re: CIDR Aggregation Tool
daemon@ATHENA.MIT.EDU (Jon Zeeff)
Mon Nov 27 13:02:19 1995
From: jon@branch.com (Jon Zeeff)
To: freedman@netaxs.com (Avi Freedman)
Date: Mon, 27 Nov 1995 12:52:45 -0500 (EST)
Cc: jon@branch.com, big-internet@munnari.OZ.AU, cidrd@iepg.org,
nanog@merit.edu
In-Reply-To: <199511271644.LAA10333@netaxs.com> from "Avi Freedman" at Nov 27, 95 11:44:12 am
> Our route table has:
> *> 198.111.252.0 192.41.177.145 <--- agis
> *> 198.111.252.0/22 192.41.177.181 <--- mci
> *> 198.111.253.0 192.41.177.145 <--- agis
> *> 198.111.255.0 192.41.177.145 <--- agis
This isn't what agis is supposed to be announcing, I'll have to
ask them again to announce 198.111.252/22. There's a couple less
routes already :-).
Once that is fixed, further aggregation of 198.111.252.0 (say into
198.111/16, as a non real example) would change our routing (in
ways we don't want it changed), even with your "next hop the same"
criteria because of the additional meaning that specifics have in
terms of priority.
I agree that your tool is usefull in identifying _potential_ savings.
