• Documents
  • Authors
  • Tables
  • Log in
  • Sign up
  • MetaCart
  • DMCA
  • Donate

CiteSeerX logo

Advanced Search Include Citations
Advanced Search Include Citations | Disambiguate

DMCA

End-To-End Arguments In System Design (1984)

Cached

  • Download as a PDF

Download Links

  • [www.cc.gatech.edu]
  • [www.cs.wisc.edu]
  • [www.cs.princeton.edu]
  • [www.caip.rutgers.edu]
  • [www.cse.nd.edu]
  • [www.cs.cmu.edu]
  • [www.cs.binghamton.edu]
  • [www.soe.ucsc.edu]
  • [www.eecs.berkeley.edu]
  • [www.cs.princeton.edu:80]
  • [www.cs.wisc.edu]
  • [www.nd.edu]
  • [www.cs.berkeley.edu]
  • [www.cct.lsu.edu]
  • [www.cs.wisc.edu]
  • [people.cs.vt.edu]
  • [www.cs.berkeley.edu]
  • [pages.cs.wisc.edu]
  • [www.eecs.berkeley.edu]
  • [pages.cs.wisc.edu]
  • [www.cs.illinois.edu]
  • [www3.nd.edu]
  • [www.cs.cmu.edu]
  • [research.cs.wisc.edu]
  • [web.eecs.umich.edu]
  • [www.cs.cornell.edu]
  • [www.cs.uiuc.edu]
  • [www.cs.cmu.edu]
  • [cs.nyu.edu]
  • [dforeman.cs.binghamton.edu]
  • [www.cs.cmu.edu]
  • [pages.cs.wisc.edu]
  • [www.cs.princeton.edu]
  • [people.cs.vt.edu]
  • [web.engr.illinois.edu]
  • [pages.cs.wisc.edu]
  • [www.cs.berkeley.edu]
  • [www.cs.princeton.edu]
  • [web.eecs.umich.edu]
  • [pbg.cs.illinois.edu]
  • [www.cs.siue.edu]
  • [people.cs.vt.edu]
  • [www.cs.princeton.edu]
  • [pages.cs.wisc.edu]
  • [pages.cs.wisc.edu]
  • [www.cs.illinois.edu]
  • [www.cs.cmu.edu]
  • [dforeman.cs.binghamton.edu]
  • [www.cs.cmu.edu]
  • [www.cs.cmu.edu]
  • [www.cs.cmu.edu]
  • [www.cmlab.csie.ntu.edu.tw]
  • [courses.cs.vt.edu]
  • [pages.cs.wisc.edu]

  • Other Repositories/Bibliography

  • DBLP
  • Save to List
  • Add to Collection
  • Correct Errors
  • Monitor Changes
by Jerome H. Saltzer , David P. Reed , David D. Clark
Citations:1021 - 9 self
  • Summary
  • Citations
  • Active Bibliography
  • Co-citation
  • Clustered Documents
  • Version History

BibTeX

@MISC{Saltzer84end-to-endarguments,
    author = {Jerome H. Saltzer and David P. Reed and David D. Clark},
    title = {End-To-End Arguments In System Design},
    year = {1984}
}

Share

Facebook Twitter Reddit Bibsonomy

OpenURL

 

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. Introduction

Keyphrases

end-to-end argument    system design    low level    little value    duplicate message suppression    system crash    bit error recovery    performance enhancement    low level mechanism    computer system    design principle    delivery acknowledgement   

Powered by: Apache Solr
  • About CiteSeerX
  • Submit and Index Documents
  • Privacy Policy
  • Help
  • Data
  • Source
  • Contact Us

Developed at and hosted by The College of Information Sciences and Technology

© 2007-2019 The Pennsylvania State University