1 / 10

End to end arguments in system design (1981)

CS244 Lecture 3 Architecture and Principles. End to end arguments in system design (1981). Sachin Katti & Keith Winstein. Conclusion (Internet Design Principles). “ Datagram ” good for most important goals, but poor for the rest of the goals.

jillrbrown
Download Presentation

End to end arguments in system design (1981)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CS244 Lecture 3 Architecture and Principles • End to end arguments in system design (1981) Sachin Katti & Keith Winstein

  2. Conclusion (Internet Design Principles) • “Datagram” good for most important goals, but poor for the rest of the goals. • Processing packets in isolation, resource management, accountability all hard. • Anticipates flows and “soft-state”for the future.

  3. End-to-End Arguments in System Design[Saltzer, Reed, Clark 1981] End-to-end in a nutshell “The function in question can completely and correctly be implemented only with the knowledge and help of the application standing at the end points of the communication system. Therefore, providing that questioned function as a feature of the communication system itself is not possible. (Sometimes an incomplete version of the function provided by the communication system may be useful as a performance enhancement.)”

  4. Some consequences • In layered design, the E2E principle provides guidance on where functions belong. • “Dumb, minimal” network and “intelligent” end-points. Many argue that: E2E principle allowed the Internet to grow rapidly because innovation took place at the edge, in applications and services. Ex. WWW, Skype, BitTorrent, Bitcoin

  5. Case studies • Error handling in file transfer • Encryption and authentication • The partition between TCP, IP, and the link layer of error handling, flow control and congestion control. • Fairness in resource allocation

  6. What you said “Performance matters, and we should strive to make the network provide the desired behaviors most of the time, and make the failures rare in which case the (maybe) costly recovery at the higher level can kick in” - Peiqian Li

  7. What you said “The application function is necessary to ensure encryption between the application endpoints, while the network implementation serves the role of preventing leaking of information that the network operator does not wish to be exposed. I felt this area of non-overlapping functionality could have been explored further in regards to other types of functions.” - Jayden Navarro

  8. On the other hand… E2E principle appears to have become diluted: NATs, firewalls, VPN tunnel endpoints, … • Perhaps not surprising: E2E principle grew in an era of trust among users. Now network must protect itself. The network is no longer “dumb, minimal” • Now over 7,000 RFCs. • Router OS’s based on 100M lines of source code. Q: Is this a problem?

  9. What belongs in, what out? Questions: • Does routing belong in the “dumb, minimal” network? • How about multicast, mobility, QoS…? • Are NATs necessary, good, or evil? • Is the E2E principle constraining innovation of the infrastructure?

  10. Additional references [rfc3724] “The Rise of the Middle and the Future of End-to-End: Reflections on the Evolution of the Internet Architecture”- Kempf et al. [Blumenthal] “Rethinking the design of the Internet: The end-to-end arguments vs. the brave new world”, ACM Transactions on Internet Technology, Vol. 1, No. 1, August 2001, pp 70-109.

More Related