Title: Source Selectable Path Diversity via Routing Deflections
1Source Selectable Path Diversity via Routing
Deflections
-
Presenter Sean - Authors Xiaowei Yang
- University of California, Irvine
- xwy_at_ics.uci.edu
- Sigcomm 2006
David Wetherall University of
Washington djw_at_cs.washington.edu
2Deflections
3Why Routing Deflection
2095
700
856
260
233
639
1295
548
587
366
846
902
1893
1176
4Why Routing Deflection
2095
700
856
260
233
639
1295
548
587
366
846
902
1893
1176
5Outlines
- Introduction
- Deflection Rules
- Tag Architecture
- Inter-domain Rules
- Evaluation
- Conclusion
6Outlines
- Introduction
- Deflection Rules
- Tag Architecture
- Inter-domain Rules
- Evaluation
- Conclusion
7Introduction
- Why source routing
- End-system partially or fully specify the paths
taken by their packets - Goals improve the reliability and performance of
networks - Lower latency
- Greater bandwidth availability
- Failure mask
- How provides path diversity, reduce the
dependence on a single network path with
undesirable characteristics - Problems with source routing
- Map for preferred routes is not ready
- Conflict with the ISP policy based routing today
- Security threat
8Approach
- Using deflection routing to construct diverse
path - Routers forward packets off the shortest path
when it is not available - Three deflection rules enabling routers to
independently deflect packets with loop-free, and
ISP policies compatible - Built on top of shortest path routing machinery
- Incrementally deployable
- Tag routing architecture
- Users use tag to express their routing preferred.
- ISPs make the routing decision using the Tag as
the routing selector
9Outlines
- Introduction
- Deflection Rules
- Tag Architecture
- Inter-domain Rules
- Evaluation
- Conclusion
10Deflection Rules
- Deflection set set of neighbors that a router
can use to reach particular destinations - Two main concerns for deflection
- Correctness of deflection
- A safety condition loop-free
- A liveness condition reach the destination
- Effectiveness through evaluation
- Notions
- ni
- cost(ni, dest) -gt cost(ni) shortest path cost
11Rule 1 (One Hop Down)
2095
700
856
639
260
233
1295
548
587
366
846
902
1893
1176
12Rule 1 (One Hop Down)
- Loop free
- Cost after the first hop strictly decrease
- Generalization of shortest path
- Special case ECMP, Equal Cost Multiple Path
- Implementation need to know the cost of
neighbors - Distance vector protocol directly achieve
- Link-state protocol need multiple round of
computation
13Rule 2 (Two Hops Down)
2095
700
856
639
260
233
1295
548
587
366
846
902
1893
1176
14Rule 2 (Two Hops Down)
- Loop free
- Still a generalization of shortest path
- Cost strictly decrease every two hops
- No two-node sequence can repeat, no link-level
loop - One node can be visited more than once
- Implementation
- Overload is slighter higher than Rule 1.
- Know the costs of neighbors incoming link
information
15Rule 3 (Two Hops Forward)
2095
700
856
639
260
548
233
1295
587
366
846
902
1893
1176
16Rule 3 (Two Hops Forward)
- Loop free
- Eliminate the immediate backtracking.
- More flexible than Rule 2
- Implementation
- Implementation complexity is slight increase
comparing with Rule 2. - Need to compute costs for nodes neighbors in
G\li
17Outlines
- Introduction
- Deflection Rules
- Tag Architecture
- Inter-domain Rules
- Evaluation
- Conclusion
18Tag Architecture
- Each packet carries a tag that determines the
path it takes through the network from the
present location to the destination - Tag properties
- Tags must be consistent in their path selections
to the same extent as existing Internet routes - Tags are opaque and lack global meaning except
that we require a value of zero to correspond to
the default Internet path - Different tags should select a diverse set of
network paths. - Two approach
- Shim encoding
- IP tag encoding
19Shim Encoding
20IP Header and IP Tag Encoding
21IP Tag Encoding
- Use IP identifier to encode the tag
- Use rarely used portion of the TTL space as the
indication to use the tag selection - Internet paths rarely exceed 40 hops
- Common initial TTL values 30, 32, 60, 64, 128,
255 - Rarely used TTL space 128 215
- Modification 160-200-gtuse tag,
- 200 entire path
- gt200 only the end of path
- 160ltTTLlt200 only the beginning of the path
- Other tag selection turn off
- True incremental deployment
- Disadvantages
- Not completely backwards-compatible
- Reroute when TTLs within the tag selection range
- Traceroute cannot be used
- Not compatible with other proposals with IP ID
overloaded
22Mapping Tags to Deflections
- Pick up the selection set S by a rule, S K
- Number pseudo-randomly from 0 to K
- 0 default shortest cost neighbor
- Choose next-hop pseudo-randomly
- Pseudo-randomly choose a small prime number P gt K
- Tag value T
- Selection N (T mod P) mod K
- Outer mod produce a number in the right range
- Inner mod produce further degree of freedom
(valuable)
23Outlines
- Introduction
- Deflection Rules
- Tag Architecture
- Inter-domain Rules
- Evaluation
- Conclusion
24Inter-domain Rules
- Deflection built on top of BGP and IGP
- Cost is decided based on BGP and IGP
- Problems deflection can change the default
egress point and hence cost metric for a dest may
change unexpectedly when the packet is deflected - Solution extending the cost function
- cost(n, dest) -gt cost(n, nexthop(n, dest))
- Benefits
25Outlines
- Introduction
- Deflection Rules
- Tag Architecture
- Inter-domain Rules
- Evaluation
- Conclusion
26Evaluation
- Goal Simulate the tag architecture and
deflection rules to characterize the kinds of
path diversity that they provide - Desirable results a high degree of path
diversity is desirable to increase the ability of
a source to avoid faulty links or nodes on their
default paths - Characterize path diversity in three respects
- The deflection paths that exist between
particular source and destination nodes - The ability to route around particular nodes or
links deemed faulty - The ability to switch peering points
27Methodology
- Custom simulator
- Three input topologies
- Real network (Abilene and GEANT) (small)
- Measured ISP topologies from Rocketfuel (Sprint,
Ebone, Tiscali, Exodus and Abovenet) (larger) - Topologies randomly generated with Brite
power-law, uniform degree distribution - Barabasi Albert (BA)
- Waxman model (Waxman)
- Three output metrics
- The number of neighbors in the deflection set at
each router - The fraction of shortest paths that can be
re-routed to by-pass a faulty link or node - How often a source can arrive at an egress that
is not its lowest-cost exit
28(No Transcript)
29 of Deflection Neighbors
30 of Deflection Path
31Node Difference
32 of Faulty-Avoiding Node Pairs
33Faction of Peer-Switching Nodes
34 of Tags to Bypass A Fault
35Outlines
- Introduction
- Deflection Rules
- Tag Architecture
- Inter-domain Rules
- Evaluation
- Conclusion
36Conclusions
- Present a practical tag-based routing system that
provides the benefits of source-controlled routes
- Scalable, compatible with ISP policies, and
easily incrementally deployable. - Provide a high-level of path diversity
- Results show that a source can avoid most single
node of link faults by trying only a handful of
tags, with better results for larger networks - The most interesting part is defining the routing
deflections rules - Loop-free (safety)
- Destination reachable (liveness)
37Questions
- Make use of BGP Have the disadvantage of BGP?
- Dynamics of BGP
- Loop again?
- Effect of delayed update of the cost?
- Instability?
- Routing oscillations?
- Convergence time?
38Thanks and Questions
sean_at_wayne.edu and visit http//www.cs.wayne.edu/
sean
39 of Deflection Neighbors
40 of Deflection Neighbors
41 of Deflection Neighbors
42 of Deflection Path
43 of Deflection Path
44 of Deflection Path
45Node Difference
46Node Difference
47Node Difference
48 of Faulty-Avoiding Node Pairs
49 of Faulty-Avoiding Node Pairs
50 of Faulty-Avoiding Node Pairs
51Faction of Peer-Switching Nodes
52Faction of Peer-Switching Nodes
53Faction of Peer-Switching Nodes
54 of Tags to Bypass A Fault
55 of Tags to Bypass A Fault
56 of Tags to Bypass A Fault