Jan.19 th, 2007Seminar In Networks End-To-End Arguments in System Design Ayodele Onibokun Seminar In Networks Jan. 19 th, 2007
Seminar In Networks Introduction End-To-End Argument (E2E) Sets of design principles Helps in proper placement of functions Placing functions at higher levels in a layered design More closer to the application (especially in communication networks)
Jan.19 th, 2007Seminar In Networks Motivation? Observations: No new solutions Existing trends and comment on further implications Then AND Now Current Internet Scenario New and different application requirements
Jan.19 th, 2007Seminar In Networks Which functions belong at which Layer? reliability, routing, encryption, compression, data conversion? - The End-to-End Argument
Jan.19 th, 2007Seminar In Networks Illustrated Examples Careful File-Transfer (CFT) Possible threats to CFT (independent of network communications) Storage disk error / hardware fault Buffer errors in FTP client Soft error Bit change (in packet transmission) The Argument: FTP Client should have built-in reliability 1.Operating System Error 2.Software Engineering Errors
Jan.19 th, 2007Seminar In Networks Illustrated Examples (Cont’d) Delivery Guarantees Acceptability & responsibility of message received The Argument: E2E ACK may still be a requirement Secure transmission of data e.g. Skype, WEP, WPA Router IPSEC, PGP Other Examples
Jan.19 th, 2007Seminar In Networks Critiques Advantages: Ensures proper guidance in system design Ensures proper placement of functions Some of the arguments are convincing Disadvantages: Different application requirements Exponential growth of the Internet Does not take into account technological advances
Jan.19 th, 2007Seminar In Networks Bottom-Line Predicting future design concerns Predicting technology progresses
Jan.19 th, 2007Seminar In Networks Discussion Comments