Teemu Koponen

Architecting for Innovation

By: 
Teemu Koponen, Scott Shenker, Hari Balakrishnan, Nick Feamster, Igor Ganichev, Ali Ghodsi, P. Brighten Godfrey, Nick McKeown, Guru Parulkar, Barath Raghavan, Jennifer Rexford, Somaya Arianfar, and Dmitriy Kuptsov
Appears in: 
CCR July 2011

We argue that the biggest problem with the current Internet architecture is not a particular functional deficiency, but its inability to accommodate innovation. To address this problem we propose a minimal architectural “framework” in which comprehensive architectures can reside. The proposed Framework for Internet Innovation (FII) — which is derived from the simple observation that network interfaces should be extensible and abstract — allows for a diversity of architectures to coexist, communicate, and evolve.

Dynamic route recomputation considered harmful

By: 
Matthew Caesar, Martin Casado, Teemu Koponen, Jennifer Rexford, and Scott Shenker
Appears in: 
CCR April 2010

This paper advocates a different approach to reduce routing convergence—side-stepping the problem by avoiding it in the first place! Rather than recomputing paths after temporary topology changes, we argue for a separation of timescale between offline computation of multiple diverse paths and online spreading of load over these paths. We believe decoupling failure recovery from path computation leads to networks that are inherently more efficient, more scalable, and easier to manage.

Accountable Internet Protocol (AIP)

By: 
David G. Andersen, Hari Balakrishnan, Nick Feamster, Teemu Koponen, Daekyeong Moon, and Scott Shenker
Appears in: 
CCR October 2008

This paper presents AIP (Accountable Internet Protocol), a networkarchitecture that provides accountability as a first-order property.AIP uses a hierarchy of self-certifying addresses, in which eachcomponent is derived from the public key of the correspondingentity. We discuss how AIP enables simple solutions to sourcespoofing, denial-of-service, route hijacking, and route forgery. Wealso discuss how AIP’s design meets the challenges of scaling, keymanagement, and traffic engineering.

NOX: Towards an Operating System for Networks

By: 
Natasha Gude, Teemu Koponen, Justin Pettit, Ben Pfaff, Martín Casado, Nick McKeown, and Scott Shenker
Appears in: 
CCR July 2008

As anyone who has operated a large network can attest, enterprise networks are difficult to manage. That they have remained so despite significant commercial and academic efforts suggests the need for a different network management paradigm. Here we turn to operating systems as an instructive example in taming management complexity...

A Data-Oriented (and Beyond) Network Architecture

By: 
Teemu Koponen, Mohit Chawla, Byung-Gon Chun, Andrey Ermolinskiy, Kye Hyun Kim, Scott Shenker, and Ion Stoica
Appears in: 
CCR October 2007

The Internet has evolved greatly from its original incarnation. For instance, the vast majority of current Internet usage is data retrieval and service access, whereas the architecture was designed around host-to-host applications such as telnet and ftp. Moreover, the original Internet was a purely transparent carrier of packets, but now the various network stakeholders use middleboxes to improve security and accelerate applications.

Syndicate content