End-to-end arguments in system design

Abstract

This paper presents a design principle that helps guide placement of functions among the modules of a distributed computer system. The principle, called the end-to-end argument, suggests that functions placed at low levels of a system may be redundant or of little value when compared with the cost of providing them at that low level. Examples discussed in the paper include bit error recovery, security using encryption, duplicate message suppression, recovery from system crashes, and delivery acknowledgement. Low level mechanisms to support these functions are justified only as performance enhancements.

The lean core in digital platforms

“…Whereas Videotex networks bet on tight integration and centralized intelligence, the Internet designers bet instead on modularity and distributed intelligence (Saltzer et al, 1984;Isenberg, 1997). The rapid rate of advance of personal computers-the intelligent nodes at Internet's edge-has proven this design to be right, at the same time that it has made it all the more compelling.…”

Open data and distributed knowledge work in open government

“…This principle is implemented in the end-to-end policy, which, above all, makes it clear what openness requires. There are three aspects here (Saltzer et al, 1984;Sandvig, 2003):…”

Building a self-adaptive content distribution network

“…Furthermore, we exclude adaptive behaviour at the network level, an approach that would have been favoured by researchers in active networks. As advocated by [8], it is our design philosophy to push the complex functionalities of a system in its higher layers as much as possible.…”