Electrical Engineering
      and Computer Sciences

Electrical Engineering and Computer Sciences

COLLEGE OF ENGINEERING

UC Berkeley

Enabling Innovation Below the Communication API

Ganesh Ananthanarayanan, Kurtis Heimerl, Matei Zaharia, Michael Demmer, Teemu Koponen, Arsalan Tavakoli, Scott Shenker and Ion Stoica

EECS Department
University of California, Berkeley
Technical Report No. UCB/EECS-2009-141
October 19, 2009

http://www.eecs.berkeley.edu/Pubs/TechRpts/2009/EECS-2009-141.pdf

Innovation in the network is notoriously difficult due to the need to support legacy applications. We argue that this difficulty stems from the API used to access the network. The ubiquitous Sockets API lets applications choose from a number of communication mechanisms, but binds them tightly to their chosen mechanism (e.g. specifying a destination using IPv4). Applications must therefore be modified in order to benefit from new network technologies. To address this problem, we propose a new communication API called NetAPI that lets applications specify their communication intents without binding to particular network mechanisms, enabling evolution below the API. We have built a NetAPI prototype for the iPhone, and use it to show that we can add disconnection tolerance, content shaping and power saving policies under NetAPI without application modifications.


BibTeX citation:

@techreport{Ananthanarayanan:EECS-2009-141,
    Author = {Ananthanarayanan, Ganesh and Heimerl, Kurtis and Zaharia, Matei and Demmer, Michael and Koponen, Teemu and Tavakoli, Arsalan and Shenker, Scott and Stoica, Ion},
    Title = {Enabling Innovation Below the Communication API},
    Institution = {EECS Department, University of California, Berkeley},
    Year = {2009},
    Month = {Oct},
    URL = {http://www.eecs.berkeley.edu/Pubs/TechRpts/2009/EECS-2009-141.html},
    Number = {UCB/EECS-2009-141},
    Abstract = {Innovation in the network is notoriously difficult due to the need to support legacy applications. We argue that this difficulty stems from the API used to access the network. The ubiquitous Sockets API lets applications choose from a number of communication mechanisms, but binds them tightly to their chosen mechanism (e.g. specifying a destination using IPv4). Applications must therefore be modified in order to benefit from new network technologies. To address this problem, we propose a new communication API called NetAPI that lets applications specify their communication intents without binding to particular network mechanisms, enabling evolution below the API. We have built a NetAPI prototype for the iPhone, and use it to show that we can add disconnection tolerance, content shaping and power saving policies under NetAPI without application modifications.}
}

EndNote citation:

%0 Report
%A Ananthanarayanan, Ganesh
%A Heimerl, Kurtis
%A Zaharia, Matei
%A Demmer, Michael
%A Koponen, Teemu
%A Tavakoli, Arsalan
%A Shenker, Scott
%A Stoica, Ion
%T Enabling Innovation Below the Communication API
%I EECS Department, University of California, Berkeley
%D 2009
%8 October 19
%@ UCB/EECS-2009-141
%U http://www.eecs.berkeley.edu/Pubs/TechRpts/2009/EECS-2009-141.html
%F Ananthanarayanan:EECS-2009-141