Why doesn't BGP... -Reply

The route computation is made by the routing protocol and is only made
when a route changes. Maybe you know of a router implementation
where the forwarding code checks the BGP and OSPF paths for every
packet, but I don't know of any that work that way.

If routers were stable, routers would make all of their routing
decisions within minutes of power up and never change those decisions.
Forwarding is then based on the table builtbased on those decisions.

Call setup happens every time a connection is setup. Even as much as
routes flap in the Internet, the load on the routers (ones that
actually work, mythical) only affects mostly stable routes by slowing
their convergence when they make their very rare bounce. That's why
IP routing scales as well as it does and switches using comparable
processors have already exceeded call setup rates in limited

IP routing has an scaling advantage over call setup. Call setup can
take advantage of the lowest loaded path at the time of setup,
providing a better chance to load balance (ala PNNI). The VC table
has a speed forwarding advantage over the IP radix tree. The radix
tree may have a space advantage due to aggregation. That in a
nutshell is the IP vs ATM flamewar (did I miss anything - ommisions
private mail unless it was major). The interest in IP switching
(CSRs, tag switching, IP switching proposal de jour) comes from a
desire to combine the best of the two.