Because TCP/IP is so central to working with the Internet and with intranets, you should understand it in detail. We’ll start with some background on TCP/IP and who it come about and when move on to the descriptions of the technical goals defined by the original designers. Then you’ll get a look at how TCP?IP compares to a theoretical mode, the Open system Interconnect (OSI) model.
A Brief History of TCP/IP
The first Request for Comments (RFC) was published in April 1969, laying the groundwork for today’s Internet, the protocol of which are specified in the numerous RGCs monitored, ratified, and archived by the Internet Engineering Task Force (IETF). TCP/IP was first proposed in 1973 and was split into separate protocols, TCP and IP, in 1978. In 1983, TCP/IP because the official transport mechanism for all connections to ARP Anet, a forerunner of the Internet, replacing the earlier Network Control Protocol (NCP). APR anet was developed by the Department of Defense’s (DoD’s) Advanced Research Project Agency (ARPA), formed in 1957 in response to the Soviet Union’s launch of Sputunik and later renamed the Defense Advanced Research Projects Agency (DARPA), which was split into ARP Ant and MILNET in 1983 and disbanded in 1990.
Much of the original work on TCP/IP was done at the University of California. Berkeley, where computer scientists were also working on the Berkeley version of UNIX (which eventually grew into the Berkeley Software Distribution (BSD) series of UNIX releases.) TCP/IP was added to the BSD releases, which in turn was made available to universities and other institutions for the cost of a distribution tape. Thus TCP/IP began to spread in the academic world, laying the foundation for today’s explosive growth of the Internet and of intranets as well.
During this time. The TCP/IP family continued to evolve and add new members. One of the most important aspects of this growth was the continuing development of the certification and testing program carried out by the U.S. government to ensure that the published standards, which were free, were met. Publication ensured that the developers did not change anything or add any features specific to their own needs. This open approach has continued to the present day; use of the TCP/IP family of protocols virtually guarantees a trouble-free connection between many hardware and software platforms.
The Internet, an internet, an internet, and an extranet
The title of this sidebar may be a bit confusing and look a bit informal with the odd capitalization, but it’s for a very good reason. While internet is a truncated version of internetwork, a lot of play has come from the root of these words. Let’s examine the word internetwork first, just to make sure we understand where all the variants come from. As you know, a network is a conglomeration of devices tied together with a common technology. Well, once you establish two or more of these networks, work can be started on bringing them together. The interconnection and intercommunication between these autonomous networks is known as an internetwork or just internet. We know we have an internet when we use routers or other layer 3 devices to interconnect the networks. What kind of fun can we have with these words?
First of all, just by capitalizing the word internet to form Internet, we get the proper name of the global commercial internetwork that is tied together by TCP/IP (actually, all of these entities are) and that has a scope of the planet we call home. If those Mars rovers have IP addresses, the scope suddenly gets a bit grander. That’s the flexibility of TCP/IP for you. What if we analyze the meaning of inter? An internet is connectivity and communication across network boundaries. Does that mean, then, that an internet is connectivity and communication within a network? Gotcha. An intranet is more an opposite of the Internet, in terms of scope. If the Internet spans many administrative boundaries, encompassing many disparate networks, then and intranet, while often an internet (how’s that for a catch?), encompasses only networks under a single administrative domain, a large corporation’s internal internetwork. Did you catch that? An intranet can be an internet, but not the Internet. Fun, huh?
Well, the, that just leaves extranet. Think of an extranet as an intranet becoming a very controlled internet. That is, if an intranet is mode up of all networks under a single administrative control, then an extranet is the expansion of that to include one, two, or just a few a additional outside networks. Said differently, an extranet is an intranet interconnected and intercommunicating with networks that are under separate administrative control. This isn’t nearly as unruly as the Internet, because this interconnectivity arose from some sort of partnership or affiliation between the parties. Let’s say, for instance, that a manufacturing company wants to have vendor monitor its inventory so that whenever materials that the vendor supplies reach a minimum threshold, an order can be generated automatically, without personnel from the manufacturing company getting involved. That would require some sort of limited vendor access to internal manufacturing company resources’. While the manufacturing company resources. While the manufacturing company wants the vendor to have access to all that they need to help automate the supply process, they don’t want the vendor accessing sensitive financial, personnel, or possibly engineering information. By tweaking the firewalls just so, the vendor’s trusted network assets can be allowed access to the manufacturing company’s inventory control system but nothing else. That’s an extranet. While there’s a bit=g difference between them all, they are all very similar. They are all generally TCP/IP internetworks.