Key Architectural Principles
An early architectural document, RFC 1122, emphasizes architectural principles over layering.
- End-to-end principle: This principle has evolved over time. Its original expression put the maintenance of state and overall intelligence at the edges, and assumed the Internet that connected the edges retained no state and concentrated on speed and simplicity. Real-world needs for firewalls, network address translators, web content caches and the like have forced changes in this principle.
- Robustness Principle: "In general, an implementation must be conservative in its sending behavior, and liberal in its receiving behavior. That is, it must be careful to send well-formed datagrams, but must accept any datagram that it can interpret (e.g., not object to technical errors where the meaning is still clear)." "The second part of the principle is almost as important: software on other hosts may contain deficiencies that make it unwise to exploit legal but obscure protocol features."
Read more about this topic: Internet Protocol Suite
Famous quotes containing the words key and/or principles:
“It so happened that, a few weeks later, “Old Ernie” [Ernest Hemingway] himself was using my room in New York as a hide-out from literary columnists and reporters during one of his rare stopover visits between Africa and Key West. On such all-too-rare occasions he lends an air of virility to my dainty apartment which I miss sorely after he has gone and all the furniture has been repaired.”
—Robert Benchley (1889–1945)
“I suppose that one of the psychological principles of advertising is to so hammer the name of your product into the mind of the timid buyer that when he is confronted with a brusk demand for an order he can’t think of anything else to say, whether he wants it or not.”
—Robert Benchley (1889–1945)