NIRA: A New Internet Routing Architecture

1
NIRA A New Internet Routing
Architecture
Offense by Amit
April 19, 2006, Northwestern University
2
Addressing Scheme
-- Hierarchical name space, Strict
provider-rooted addressing -- User will have
multiple address for multiple providers
(Multi-homing) -- suppose your Tier-i ISP on
average is connected with 2 Tier(i-1)
ISPs. Then an user at level n will have O(2n)
address. Exponential growth !!! --
What about peering ? It breaks provider-consumer
semantics. Common in
Internet. -- For non-canonical routing, you don't
even need to change the address scheme. -- AS
moves from ISP-A to ISP-B, all its addresses
change.
3
Topology Information Propagation Protocol
-- Policy based link state protocol -- How it is
better than BGP? BGP is policy based distance
vector protocol? -- Scalability vs.
Convergence -- Link state based TIPP will face
scalability problem as more and more AS start
peering each other? Design flaw! -- Routing
region grows as more and more AS peer with each
other.
4
Name-to-Route Lookup Service
-- Extended DNS -- Where to place NRLS route
servers? Address changes as AS moves from
one provider to another provider. -- Temporary
unavailability of hosts belong to AS moving
from one provider to another. -- Need to
update DNS entry for each hosts as AS changes
its provider. Sudden overload at the route
servers and network.
5
Source Routing
-- Security issues. -- No longer shortest path
routing, both sender and receiver
choose their own up-hill paths independently
and put them together. -- Multiple
redundant paths, but load balancing is not
possible, since paths are decided by
independent sources. -- Traffic
Engineering
6
Misc
-- Give ability to user to choose wide-area ISP
to foster competition, competition gt
innovation, QoS etc. -- Not essentially true ! --
your local ISP is connected to only 1-2 Wide Area
ISPs. So you are constrained by your local
ISP. -- Business Complicacy -- End user need
sign agreement with Wide-area ISPs. -- No
Evaluation, who knows in reality is going to
perform worse than existing one?
7
Conclusion
-- Routing is a functionality, which cannot be
achieved without the help from the
intermediate routers, then why not use them?
There is no point making routers dumb!
-- Network based routing is more adaptive than
source routing. -- It's hard to
incorporate Security/policy in End-to-
End Routing.