nanog mailing list archives
Re: CIDR Report
From: "Peter Galbavy" <peter.galbavy () knowledge com>
Date: Mon, 15 May 2000 11:28:54 +0100
Of course, note that the real problem isn't the memory space, it's the CPU time to calculate the routing table updates. Note, too, that the more unaggregated prefixes in the net, the more changes will need to be propagated to every other router in the default-free zone, implying the need for more instances of a more expensive calculation.
Not trying to teach a mailing-list full of grandmother's to suck eggs, but IFF all 2^32 (-1?) addresses were routed as hosts, then there is no index, and a linear lookup cost. Stupid thing to do, but a 2^32 * 1 or 2 bytes of linear address -> interface table. Peter
Current thread:
- Re: CIDR Report, (continued)
- Re: CIDR Report ww (May 13)
- Re: CIDR Report Joe Provo - Network Architect (May 14)
- Re: CIDR Report Chris Williams (May 15)
- Re: CIDR Report Adrian Chadd (May 15)
- Re: CIDR Report Chris Williams (May 15)
- RE: CIDR Report Bradly Walters (May 15)
- Re: CIDR Report Chris Williams (May 15)
- RE: CIDR Report Roeland M.J. Meyer (May 14)
- Re: CIDR Report Peter Galbavy (May 15)
- Test Roeland Meyer (E-mail) (May 14)
- Re: CIDR Report Chris Williams (May 15)
- Re: CIDR Report brett watson (May 15)
- Re: CIDR Report Chris Williams (May 15)
- Re: CIDR Report Valdis . Kletnieks (May 15)
- Re: CIDR Report Rodney L Caston (May 15)
- Inter-Provider Latency Measurements Lloyd Taylor (May 15)
- "Simple" Multi-Homing ? (was Re: CIDR Report) Todd Sandor (May 15)