Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Routing, Forwarding, and the Legacy Internet

  • From: Chrisy Luke
  • Date: Sun Sep 13 18:22:05 1998

Jim Fleming wrote (on Sep 13):
>                         Let's also imagine that your
> forwarder (not router) could have up to 256 interfaces.
> With 24 bits and a 1 byte wide table, you would need
> 16,777,216 bytes to describe all possible /24s and
> the interface a packet should be forwarded on.

This is a very naieve way of looking at how a forwarding table should
be stored, particularly since it doesn't address many issues related
to internal network topology, imbalance of routes across interfaces,
statistics gathered about use of each entry - including it's age, where
it learnt it from, other sources (and next-hops) for the same destination,
metrics, load-balancing in the case of multipath capable routers etc etc,
not to mention the burden of physically transferring this data to the 
router in the first place.

Even in your simplistic view, you would have to transfer 16meg of data
over a network to get a complete table. Large portions of the world
still use T/E-1's etc on BGP speaking lines. 16mbytes over that will take
a looong time.  And then you have all the BGP metrics to consider - AS path,
MEDs and so forth.

> is not a lot of memory in this day and age. Also, once
> the table was filled in, the lookup would be very fast.

Only because you assume "all networks are equal". They aren't.

== Systems Manager for Easynet, part of Easynet Group PLC.

Discussion Communities

About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home

Merit Network, Inc.