82,891
edits
End-to-end principle: Difference between revisions
no edit summary
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 8: | Line 8: | ||
:''Keep the [[network]] as simple as possible. Put all the complications, intelligence and {{risk|complexity}} at its ''edges''. Let people build whatever structures they like on it — if it is a [[digital commons]],<ref>Unlike real commonses, [[digital commons]] do not suffer from the [[tragedy of the commons]].</ref> there will be unlimited scope for other users to build their own castles in the air, but the most basic, common, layer must be as clear and simple as it can be.'' | :''Keep the [[network]] as simple as possible. Put all the complications, intelligence and {{risk|complexity}} at its ''edges''. Let people build whatever structures they like on it — if it is a [[digital commons]],<ref>Unlike real commonses, [[digital commons]] do not suffer from the [[tragedy of the commons]].</ref> there will be unlimited scope for other users to build their own castles in the air, but the most basic, common, layer must be as clear and simple as it can be.'' | ||
{{author|Lawrence Lessig}} lays out the concept very well in his magnificent {{br|Code: Version 2.0}}.<ref>Page | {{author|Lawrence Lessig}} lays out the concept very well in his magnificent {{br|Code: Version 2.0}}.<ref>Page 44-45 and 112-116, analog freaks.</ref> | ||
{{quote|This minimalism in the Internet’s design was not an accident. It reflects a decision about how best to design a network to perform a wide range over very different functions. Rather than build into this network a complex set of functionality thought to be needed by every single application, this network philosophy pushes complexity to the edge of the network—to the applications that run on the network, rather than the network’s core. The core is kept as simple as possible. Thus if authentication about who is using the network is necessary, that functionality should be performed by an application connected to the network, not by the network itself. Or if content needs to be encrypted, that functionality should be performed by an application connected to the network, not by the network itself. | |||
This design principle was named by network architects Jerome Saltzer, David Clark, and David Reed as the [[end-to-end principle]]. It has been a core principle of the Internet’s architecture, and, in my view, one of the most important reasons that the Internet produced the innovation and growth that it has enjoyed.}} | |||
''Later'' | |||
{{quote|As I’ve already described, the Internet embodied this principle by keeping the functionality of TCP/IP focused quite narrowly—that is, on the single function best-efforts delivery of packets of data. What those packets do, or who they’re meant for, is not a concern of the protocol. Just delivering packets is the end. | {{quote|As I’ve already described, the Internet embodied this principle by keeping the functionality of TCP/IP focused quite narrowly—that is, on the single function best-efforts delivery of packets of data. What those packets do, or who they’re meant for, is not a concern of the protocol. Just delivering packets is the end. | ||