ABSTRACT
Over the past decade a variety of network architectures have been proposed to address IP's limitations in terms of flexible forwarding, security, and data distribution. Meanwhile, fueled by the explosive growth of video traffic and HTTP infrastructure (e.g., CDNs, web caches), HTTP has became the de-facto protocol for deploying new services and applications. Given these developments, we argue that these architectures should be evaluated not only with respect to IP, but also with respect to HTTP, and that HTTP could be a fertile ground (more so than IP) for deploying the newly proposed functionalities. In this paper, we take a step in this direction, and find that HTTP already provides many of the desired properties for new Internet architectures. HTTP is a content centric protocol, provides middlebox support in the form of reverse and forward proxies, and leverages DNS to decouple names from addresses. We then investigate HTTP's limitations, and propose an extension, called S-GET that provides support for low-latency applications, such as VoIP and chat.
- Akamai DDoS Mitigation. http://www.dlt.com/akamai-ddos.Google Scholar
- DNS-O-Matic. http://dnsomatic.com/.Google Scholar
- Squid Web Cache. http://www.squid-cache.org/.Google Scholar
- Cisco Visual Networking Index: Forecast and Methodology, 2009--2014, 2010. http://tinyurl.com/3p7v28.Google Scholar
- Adobe. HTTP Dynamic Streaming. http://www.adobe.com/products/httpdynamicstreaming/.Google Scholar
- Alex Russell. Comet: Low Latency Data For Browsers. http://alex.dojotoolkit.org/wp-content/LowLatencyData.pdf.Google Scholar
- A. Alinone. Concrete Comet Examples. Comet Daily (cometdaily.com). http://cometdaily.com/2009/10/23/concrete-comet-examples/.Google Scholar
- D. G. Andersen, H. Balakrishnan, N. Feamster, T. Koponen, D. Moon, and S. Shenker. Accountable internet protocol (aip). In ACM SIGCOMM, 2008. Google ScholarDigital Library
- K. Argyraki and D. R. Cheriton. Active Internet Traffic Filtering: Real-time Response to Denialof-Service Attacks. In USENIX, 2005. Google ScholarDigital Library
- H. Balakrishnan, K. Lakshminarayanan, et al. A layered naming architecture for the internet. In ACM SIGCOMM, 2004. Google ScholarDigital Library
- H. Ballani, Y. Chawathe, S. Ratnasamy, T. Roscoe, and S. Shenker. Off by Default! In ACM HotNets, 2005.Google Scholar
- R. J. Bayardo and J. Sorensen. Merkle tree authentication of HTTP responses. In WWW '05. ACM, 2005. Google ScholarDigital Library
- D. R. Cheriton and M. Gritter. Triad: A scalable deployable nat-based internet architecture. In Stanford Computer Science Technical Report, 2000.Google Scholar
- M. Demmer, K. Fall, T. Koponen, and S. Shenker. Towards a modern communications api. In HotNets-VI, 2007.Google Scholar
- K. Fall. A Delay-Tolerant Network Architecture for Challenged Internets. In ACM SIGCOMM, 2003. Google ScholarDigital Library
- R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, and T. Berners-Lee. HTTP/1.1. RFC 2616 (Draft Standard), June 1999.Google Scholar
- B. Ford and J. Iyengar. Breaking Up the Transport Logjam. In HotNets, 2008.Google Scholar
- C. Gaspard, S. Goldberg, W. Itani, E. Bertino, and C. Nita-Rotaru. SINE: Cache-Friendly Integrity for the Web. Workshop on NPSec, 2009.Google Scholar
- P. B. Godfrey, I. Ganichev, et al. Pathlet routing. In ACM SIGCOMM, 2009. Google ScholarDigital Library
- S. Guha and P. Francis. An End-Middle-End Approach to Connection Establishment. In ACM SIGCOMM, 2007. Google ScholarDigital Library
- M. Handley and A. Greenhalgh. Steps towards a dos-resistant internet architecture. In FDNA '04, 2004. Google ScholarDigital Library
- Internet Draft. RFC1633 - Int. Services in the Internet Architecture, 1994.Google Scholar
- Internet Draft. RFC1992 - The Nimrod Routing Architecture, 1996.Google Scholar
- Internet Draft. RFC2475 - An Architecture for Differentiated Services, 1998.Google Scholar
- Internet Draft. RFC3344 - IP Mobility Support for IPv4, 2002.Google Scholar
- J. Ioannidis and S. M. Bellovin. Implementing Pushback: Router-Based Defense Against DDoS Attacks. In NDDS, 2002.Google Scholar
- V. Jacobson, D. K. Smetters, J. D. Thornton, M. F. Plass, N. H. Briggs, and R. L. Braynard. Networking Named Content. In CoNEXT, 2009. Google ScholarDigital Library
- T. Koponen, M. Chawla, B.-G. Chun, et al. A data-oriented (and beyond) network architecture. In ACM SIGCOMM, 2007. Google ScholarDigital Library
- C. Labovitz, S. Iekel-Johnson, D. McPherson, J. Oberheide, and F. Jahanian. Internet Inter-domain Traffic. In ACM SIGCOMM, 2010. Google ScholarDigital Library
- Microsoft. Smooth Streaming. http://www.iis.net/expand/SmoothStreaming.Google Scholar
- R. Moskowitz, P. Nikander, P. Jokela, and T. Henderson. Host identity protocol, draft-moskowitz-hip-08. In IETF draft, 2003.Google Scholar
- Nate Anderson. P2P traffic drops as streaming video grows in popularity. http://arstechnica.com/old/content/2008/09/p2p-traffic-drops-as-streaming-video-grows-in-popularity.ars.Google Scholar
- A. M. Odlyzko. Internet traffic growth: sources and implications. volume 5247, pages 1--15. SPIE, 2003.Google Scholar
- L. Popa, N. Egi, S. Ratnasamy, and I. Stoica. Building Extensible Networks with Rule-Based Forwarding. In USENIX OSDI, 2010. Google ScholarDigital Library
- L. Popa, A. Ghodsi, and I. Stoica. HTTP as the NarrowWaist of the Future Internet. UCB Technical Report, 2010. http://www.eecs.berkeley.edu/%7Epopa/httpTechReport.pdf.Google Scholar
- J. Rosenberg. UDP and TCP as the New Waist of the Internet Hourglass. IETF Draft 08. http://tools.ietf.org/id/draft-rosenberg-internet-waist-hourglass-00.txt.Google Scholar
- S. Deering. Multicast Routing in a Datagram Internetwork, 1991. PhD thesis. Google ScholarDigital Library
- E. Schonfeld. Cisco: By 2013 Video Will Be 90 Percent Of All Consumer IP Traffic And 64 Percent of Mobile, 2009. http://tinyurl.com/nw8jxg.Google Scholar
- H. Schulze and K. Mochalski. Ipoque internet study 2008/2009. www.ipoque.com/resources/internet-studies/internet-study-2008_2009.Google Scholar
- A. Seehra, J. Nous, M. Walfish, D. Mazieres, A. Nicolosi, and S. Shenker. A Policy Framework for the Future Internet. In ACM Hotnets, 2009.Google Scholar
- D. K. Smetters and V. Jacobson. Securing network content. In PARC TR, 2009.Google Scholar
- I. Stoica, D. Adkins, S. Zhuang, S. Shenker, and S. Surana. Internet Indirection Infrastructure. In ACM SIGCOMM, 2002. Google ScholarDigital Library
- A.-J. Su, D. R. Choffnes, A. Kuzmanovic, and F. E. Bustamante. Drafting behind Akamai (travelocity-based detouring). ACM SIGCOMM, 2006. Google ScholarDigital Library
- D. L. Tennenhouse, J. M. Smith, W. D. Sincoskie, D. J. Wetherall, and G. J. Minden. A Survey of Active Network Research. IEEE Comm., 1997. Google ScholarDigital Library
- P. Vixie and et al. Dynamic Updates in the Domain Name System. RFC 2136, 1997. Updated by RFCs 3007, 4035, 4033, 4034.Google Scholar
- M. Walfish, H. Balakrishnan, and S. Shenker. Untangling the web from DNS. In NSDI'04, pages 17--17, Berkeley, CA, USA, 2004. Google ScholarDigital Library
- M. Walfish, J. Stribling, M. Krohn, H. Balakrishnan, R. Morris, and S. Shenker. Middleboxes no longer considered harmful. In OSDI, 2004. Google ScholarDigital Library
- W. Xu and J. Rexford. MIRO: Multi-path Interdomain ROuting. In ACM SIGCOMM, 2006. Google ScholarDigital Library
- X. Yang, D. J. Wetherall, and T. Anderson. A DoS-limiting Network Architecture. In ACM SIGCOMM, 2005. Google ScholarDigital Library
Recommendations
Future Internet Protocols
The Internet is based on a layered set of protocols — the most basic of which is TCP/IP — and the servers and routers that support them. This special issue addresses challenges to the Internet's basic protocols as our collective Internet usage increases ...
HTTP over UDP: an experimental investigation of QUIC
SAC '15: Proceedings of the 30th Annual ACM Symposium on Applied ComputingThis paper investigates "Quick UDP Internet Connections" (QUIC), which was proposed by Google in 2012 as a reliable protocol on top of UDP in order to reduce Web Page retrieval time. We first check, through experiments, if QUIC can be safely deployed in ...
Comments