Routing Vs. Forwarding:
-Routing Algorithms:
Vectors can be huge. Vector size = O(N)
N : the number of networks.
Link-State Packet size = O(1) (Because packet contains only
information about its direct neighbors within its network)
Number of Link-State Packets= O(N)
(Because packets must besent throughout the network – reliable flooding).
-Forwarding:
Choosing right output port given routing information.
Intra-domain routing:
within an ASIs a distance vector algorithm. Works well for small domains.
Is a link-State algorithm. Better for larger domains.
Inter-domain routing:
Is harder. Why?
1.
Each router in an AS has to keep all information? Scalability?
Key router in an AS keeping track of all information?
Failure of centralized node?
2.
Different metrics on different ASs.
3.
Peering agreements between ASs? Security? How much flow can go from
an AS to another? Economics and bandwidth considerations.
4.
Obfuscation. Network providers do not want to advertise their AS topology.
5.
Decentralized administration? Who is responsible for managing all this?
Fixing problems? (e.g. routers misbehaving)
Ran by border routers; so they can communicate with each other even the ones
on the border of same AS.
Network reachability info.
Peering relationships.
Initially: routers know the networks inside their AS and advertise ASs that
they are directly connected to. Works like link-state.
One speaker for an AS – maintains routing tables and transmitted information.
Problem is that the BGP table is huge.
(Same administration is a requirement)
Landmark hierarchy:
Node has radius i. All nodes within that radius View this landmark.
Routing tables are smaller and the number of forwarded measures is near optimal.
The radius distribution is heavy tailed (A small number of routers have a large radius).