{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

CS536-2009-01-20-end2end

CS536-2009-01-20-end2end - CS536 End to End Argument J...

Info iconThis preview shows pages 1–4. Sign up to view the full content.

View Full Document Right Arrow Icon
CS536: End to End Argument J. Saltzer, D. Reed, and D. Clark, End-to-end Arguments in System Design. ACM Transactions on Computer Systems (TOCS) , Vol. 2, No. 4, pp. 195-206, 1984. Introduction 1-1
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Introduction 1-2 The End-to-End Argument Correctness and completeness are often (usually?) only able to be certified at the highest layer. Ex: Suppose I ask you to read a research paper. Which are sufficient? [Link Layer] Do nothing. Of course you’ll read the paper, as you do everything the professor asks. [Network Layer] Check to make sure someone standing near you heard the request. [Transport Layer] Confirmation you heard my request. [Presentation Layer] Showing me a copy of the paper. [Session Layer] Telling me you’ve read the paper. [Application Layer] Quizzing or testing you on the material covered in the paper.
Background image of page 2
Sufficiency (restated) Only a complete check of end-to-end requirements is sufficient. Failures may occur at any place Temporary hearing problem Short-term memory loss Printing wrong paper Lazyness in actually reading the paper Reading comprehension Must verify objective is complete!
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Image of page 4
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}