Title: Drafting Behind Akamai (Travelocity-Based Detouring)
1Drafting Behind Akamai (Travelocity-Based
Detouring)
2Motivation
- Overlay networks
- Build the view of the underlying network
- Passive and active measurements
- To determine overlay paths according to some
metric, e.g., latency? - Redundant, non-scalable, overhead (expensive!)
- What common service we may need in place?
- An Internet weather-report service
3Proposed Approach
- Fact
- CDNs (e.g., Akamai) perform extensive network and
server measurements - Publish the results through DNS over short time
scales - Can overlay networks recycle measurements
collected by production CDNs? - Significantly reduce the amount of measurements
(a complementary service) - No new infrastructure need to be deployed
- Inherit the robustness of DNS
- Easy integration with existing systems
4CDN-Driven One-Hop Source Routing
5Key Questions
- How does Akamai work?
- DNS translation
- How many web replicas does a client see?
- Impact of different sites (e.g., Yahoo vs. NY
Times)? - DNS redirection dynamics?
- Network or server latency?
- An example application one-hop source routing
- Mapping CDN servers to overlay nodes
- Low-overhead protocols for exploiting CDN
redirections
6DNS Black Magic
www.pcworld.com
www.pcworld.com
a1694.g.akmai.net
CNAME a1694.g.akamai.net
images.pcworld.com
www.pcworld.com
a1694.g.akmai.net
2 ip addresses of Akamai Edge Servers
2 ip addresses of Akamai Edge Servers
www.pcworld.com
images.pcworld.com
fetch image files
http request/response
7Measuring Akamai
- 2-months long measurement
- 140 PlanetLab (PL) nodes
- 50 US and Canada, 35 Europe, 18 Asia, 8 South
America, the rest randomly scattered - Every 20 sec, each PL node queries an appropriate
CNAME for - Yahoo, CNN, Fox News, NY Times, etc.
.
8Initial Results
Berkeley
Purdue
9Server Diversity for Yahoo
Majority of PL nodes see between 10 and 50
Akamai edge-servers
10Multiple Akamai Customers
11Redirection Dynamics
12Key Questions
- How does Akamai work?
- DNS translation
- How many web replicas does a client see?
- Impact of different sites (e.g., Yahoo vs. NY
Times)? - DNS redirection dynamics?
- Network or server latency?
- Potentials for one-hop source routing?
- Mapping CDN servers to overlay nodes
- Low-overhead protocols for exploiting CDN
redirections
13Methodology
10 Best Akamai Edge Servers
14Do CDN redirections correlate to network
latencies? (1)
- Rank r1r2-1
- 16 means perfect correlation
- 0 means poor correlation
15Do CDN redirections correlate to network
latencies? (2)
16Akamai-Driven One-Hop Source Routing
Redirections driven by network conditions
Potential for CDN-to-overlay mapping
Redirection dynamics sufficiently small for
network control
17Methodology
18Akamai-driven source routing (1)
Taiwan-UK
UK-Taiwan
19Akamai-driven source routing (2)
Experiment US (6), Europe (3), S. America (2),
Asia (3)
20Path pruning
- Fact
- Not always is Akamai-driven path better than the
direct one - Practical issues
- How frequently to make a decision whether to use
the direct or the Akamai path? - Should one use
- the first (of the 2 paths) returned by Akamai
(FAS) - the better (of the 2 paths) returned by Akamai
(BTAS)
21Path Pruning Result
22Conclusions
- Reuse measurements performed by CDNs
- Reverse-engineering Akamai
- DNS redirections sufficiently small
- Strong correlation to network conditions
- All clients see a large number of paths
- CDN-driven one-hop source routing
- 25 of Akamai paths outperform direct paths
- 50 of nodes discovered by Akamai outperform
direct paths - Low-overhead pruning algorithms
- Global Internet weather-report service for
little to no cost