This document describes the design philosophies for the Internet protocol suite, TCP/IP, first proposed 15 years ago by DARPA. It shows us the design goals of the Internet with their importance and how these goals led to the evolution of the Internet. The author motivated the creation of the Internet architecture and how protocol designs were selected and the reasoning behind the design decisions. He discussed the goals of the Internet in detail. Say no to plagiarism. Get a tailor-made essay on "Why Violent Video Games Shouldn't Be Banned"? Get an original essay The main goal for them was to develop an effective technique for multiplexing existing interconnected networks. The first networks to be connected used packet switching, packet switching was adopted as a fundamental component of the Internet architecture. A packet-switched communication in which a number of networks are connected using gateways that implement the store-and-forward algorithm. This objective clearly says "what" should be achieved, i.e. "effective communication", but does not offer a clear picture of the characteristics of an effective system. Therefore, the second level objectives were presented in order of priority: Internet communication must continue despite the loss of networks or gateways. The Internet must support multiple types of communication services. The Internet's architecture must accommodate a variety of networks. The architecture of the Internet must allow distributed management of its resources. The architecture of the Internet must be cost-effective. The architecture of the Internet must allow the host to connect with a low level of effort. The resources used in the Internet architecture must be responsible. The above objectives have been listed in order of importance and if the order were changed a completely different network architecture would result. This is the point I liked about this article. It was interesting to know that if the goals or their order had been different, the Internet would have been designed very differently. The author provides a detailed description of the first three objectives. The first of these is "Surviving in the face of failure", which means that the Internet should continue to provide communication services, even if networks and gateways fail, i.e. communication between two entities should never be lost. In case of failure, to synchronize communication without breaking the connection we must have a way to store the state information stored somewhere in the lower layers such as intermediate nodes and replicate it to avoid data loss. But the designers used a much simpler solution called "fate sharing". Destiny sharing suggests collecting all the information and storing it at the network endpoints at the entity using the network service. The second objective was “Manage multiple types of communication services.” The services here are speed, latency, reliability, etc. For example, a remote access requires a small delay but less bandwidth while file transfer was no longer concerned with the delay but with the throughput. Basically, both used two-way reliable data delivery service (virtual circuit), which was the first service provided over the Internet. The author also said that there are few types of services that do not directly adapt to the Internet such as XNET (Cross-Internet debugger) and VOIP. That's when they realized that more than just TCP was needed. XNET didn't seem to be".