Protocols
Saved & recent

End-to-end principle

Also called: end-to-end argument

The end-to-end principle asks which functions need knowledge available only at the communicating endpoints. Lower layers can help, but they cannot always establish that the application’s full goal was achieved. Reliability and security checks may therefore still be required at the ends of a complete exchange.

For example, a file-transfer tool can compare a checksum of the saved file with one supplied by the sender. Successful packet delivery alone does not establish that the correct file reached durable storage. This is a design argument about responsibility, not a rule forbidding useful error detection or other assistance inside the network.

Read first
Protocol stack
Related
TCP, TLS, Protocol stack
Further reading
IETF RFC 1958 — Architectural Principles of the Internet
full-file checksum comparison 1 2 3 file data packets writes file original file network receiver buffer saved file ✓ per-packet checks
Illustrative integrity check from the original file to the saved copy. A plain checksum is not sender authentication.

View in the full Protocols collection