IP renumbering timeframe

Marshall Eubanks tme at multicasttech.com
Thu May 30 14:15:50 UTC 2002


On Thu, 30 May 2002 09:48:50 -0400
 Valdis.Kletnieks at vt.edu wrote:
> On Thu, 30 May 2002 09:20:17 EDT, Leo Bicknell <bicknell at ufp.org>  said:
> 
> > Since you have to connect to two or more providers to get an ASN,
> > and since the whole reason to have an ASN is to inject things into
> > the DFZ it doesn't seem like it would increase routing table size
> > by a huge amount.  It would eliminate one whole paperwork/justification
> > step (for your first address allocation).  For subsequent allocations
> > there is an example (that /24) of how efficiently the ISP uses the
> > space.
> 
> Unless I'm missing something, it will double the size of it, since that
> /24 out of that /8 won't aggregate with their other address space.
> (Hint - our AS has 198.82/16 and 128.173/16 and some other small blocks -
> how many routes do YOU see for us?)

Dear Valdis;

If you mean AS   1312  VA-TECH-AS , we see 4 routes :

*  63.164.28.0/22   160.81.38.225            9             0 1239 7066 1312 i
*                   166.61.8.89                            0 145 11537 7066 1312
i
*                   157.130.46.53                        300 701 1239 7066 1312
i
*>                  216.177.55.5                         500 15076 1239 7066
1312 i
*  128.173.0.0      157.130.46.53                        300 701 1239 7066 1312
i
*                   166.61.8.89                            0 145 11537 7066 1312
i
*>                  216.177.55.5                         500 15076 1239 7066
1312 i
*                   160.81.38.225            9             0 1239 7066 1312 i
*  192.70.187.0     157.130.46.53                        300 701 1239 7066 1312
i
*                   166.61.8.89                            0 145 11537 7066 1312
i
*>                  216.177.55.5                         500 15076 1239 7066
1312 i
*                   160.81.38.225            9             0 1239 7066 1312 i
*  198.82.0.0/16    157.130.46.53                        300 701 1239 7066 1312
i
*                   166.61.8.89                            0 145 11537 7066 1312
i
*>                  216.177.55.5                         500 15076 1239 7066
1312 i
*                   160.81.38.225            9             0 1239 7066 1312 i


If you mean  AS  13546  VT-RICHMOND-AS, only one in BGP from 
AS 16517 : 208.16.73.0/24

In MBGP, we only see two of these routes.
Two others are aggregated into Sprint address blocks :

63.164.28.0 
208.16.73.0

while 192.70.187.0 does not appear at all and is not MBGP routable from us.

Regards
Marshall
> 
> Also, there's no real reason to think that address space usage in that
> bootstrap /24 will accurately reflect usage in a /20 allocated to them,
> since THAT /20 will probably be sub-allocated to users/customers.  Heck,
> in our AS, the nameservers and mailservers and the like would probably
> fit into a /27 (maybe a /26), and wouldn't tell you anything about
> the /20 that covers Torgeson Hall....
> -- 
> 				Valdis Kletnieks
> 				Computer Systems Senior Engineer
> 				Virginia Tech
> 
> 
> 




More information about the NANOG mailing list