Routing as a Service

1
Routing as a Service

• Ion Stoica
• UC Berkeley
• December 17, 2003

2
Problem

• Applications want more flexibility and
  functionality
• Multicast End-system multicast
• Resilience RON
• DoS defense SOS
• Performance Detour
• Applications want efficiency
• Thats why we do 100x100 network!

3
Thesis

• Give end-hosts control on routing
• End-hosts should be able to
• Source route
• Set-up acyclic communication graphs
• Route packets through desired service points
• Stop flows in infrastructure
• Infrastructure still provide
• Data forwarding
• Connectivity, fast recovery

4
How is This Different?
Infrastructure
Host
Data plane
Internet Infrastructure overlays
Control plane
p2p End-host overlays
Data plane
Control plane
Our proposal
Data plane
Control plane
5
Two Examples

• Application Specific Routing
• DoS Defense

6
Application Specific Routing
A
Network measurements
Query/reply routing info.
Setup routes
B
D
C
7
DoS Defense

• Problem attacker floods the incoming link of the
  victim
• Solution stop attacking traffic before it
  arrives at the incoming link
• Today call the ISP to stop the traffic, and hope
  for the best!
• Approach give end-host control on what packets
  to receive
• Enable end-hosts to stop the attacks in the
  network

8
Why End-Hosts (and not Network)?

• End-hosts can better react to an attack
• Aware of semantics of traffic they receive
• Know what traffic they want to protect
• End-hosts may be in a better position to detect
  an attack
• Flash-crowd vs. DoS

9
Many Open Issues

• Security
• Scalability
• Stability
• Initial experience with Internet Indirection
  Infrastructure (i3)
• A trigger is like an entry in a routing table!