160 likes | 288 Views
P2P-TV Workshop Torino, Jan 2011. Application-Layer Traffic Optimization How did we get here? Where are we going?. Weekend Planning. Portofino. Sanremo. Rimini. Sorrento. Taormina. 1960s. Network Applications – Client-to-server File transfer, remote shell, web browsing. Client. Server.
E N D
P2P-TV WorkshopTorino, Jan 2011 Application-Layer Traffic Optimization How did we get here? Where are we going? Enrico Marocco enrico.marocco@telecomitalia.it
Weekend Planning Portofino Sanremo Rimini Sorrento Taormina
1960s Network Applications – Client-to-serverFile transfer, remote shell, web browsing Client Server Client Client Resource
1970s Network Applications – Client-to-server-to-serverDNS, email, usenet, messaging Client Client Server Server Server Client Client Server Resource Resource Resource
1990s Network Applications – Peer-to-peerFile sharing, realtime communications Resource Resource Client Client Client Server Server Client Server Client Resource Client Resource
Network Applications Evolution Peer-to-peer BitTorrent ed2k Spotify PPLive . . . Skype usenet Napster VoIP DNS streaming CDN email file transfer web browsing remote shell Client/Server 1960 1970 1980 1990 2000 2010
ALTO Peer-to-peer BitTorrent ed2k Spotify PPLive Skype Transaction Target: A replicated resource VoIP Napster CDN streaming Optimization goal: Find the best resource instance(s) usenet DNS email web browsing file transfer remote shell Transaction Target: A host on the Internet Client/Server Optimization goal: Find the best route from client to server
IETF ALTO Working GroupGenesis • “Can ISPs and P2P systems co-operate for improved performance?” V. Aggarwal, A. Feldmann, C. Scheideler (July 2007) • “Comcast Throttles BitTorrent Traffic. Seeding Impossible,” TorrentFreak (August 2007) • “Verizon reports P4P can slash P2P's impact on ISPs,” Newsfactor.com (March 2008) • IETF P2P Infrastructure Workshop (March 2008, Boston, MA, USA) • Application-Layer Traffic Optimization BoF (July 2008, 72nd IETF Meeting, Dublin, Ireland) • IETF Application-Layer Traffic Optimization Working Group formed (October 2008)
IETF ALTO Working GroupGoal “[..] design and specify an Application-Layer Traffic Optimization (ALTO) service that will provide applications with information to perform better-than-random initial peer selection”
ALTO InformationNetwork and Cost Maps http://xkcd.org/195
Status of the IETF ALTO Working Group • Problem statement: done • Requirements: ~90% • Protocol specification: ~70% • Discovery mechanism: ~50% • Deployment considerations: ~40% • CDN use case: ~20% • Interoperability event for pre-standard implementations planned for July
Experiences • Several independent implementations • >= 4 vendors, research labs, universities • Integration in real applications • P4P trial • Comcast, Verizon, Telefonica, AT&T • China Telecom / Xunlei trial
(Possibly) Waiting for ALTORIPE ATLAS Initiative http://atlas.ripe.net/
A Few Pointers • Application-Layer Traffic Optimization (ALTO) Problem Statement, RFC 5693 • A Survey on Research onthe Application-Layer Traffic Optimization (ALTO) Problem, RFC 6029 • Comcast's ISP Experiences in a Proactive Network Provider Participation for P2P (P4P) Technical Trial, RFC 5632 • ALTO and DECADE service trial within China Telecom, http://tools.ietf.org/html/draft-lee-alto-chinatelecom-trial • IETF ALTO Working Group, http://datatracker.ietf.org/wg/alto/charter/ • RIPE ATLAS Initiative, http://atlas.ripe.net/