This blog is on TCP/IP Networking, you can know here more about Networking, it’s model and History Leading to TCP/IP with description.
Introduction to TCP/IP Networking
So, you’re new networking. Like many of us , your perspective about networks could be that of a user of the network, as against the network engineer who builds networks. For some, your view of networking could be supported how you use the web , from home, using a high-speed Internet connection like digital subscriber line (DSL) or cable TV, as shown in Figure 1-1.
The top a part of the figure shows a typical high-speed cable Internet user. The PC connects to a cable modem using an ethernet cable. The cable modem then connects to a cable TV (CATV) outlet within the wall using a round coaxial cable—the same quite cable wont to connect your TV to the CATV wall outlet. Because cable Internet services provide service continuously, the user can just sit down at the PC and begin sending email, browsing websites, making Internet phone calls, and using other tools and applications.
The lower part of the figure uses two different technologies. First, the tablet computer uses wireless technology that goes by the name wireless local-area network (wireless LAN), or Wi-Fi, rather than using an ethernet cable. during this example, the router uses a different technology, DSL, to communicate with the web . Both home-based networks and networks built to be used by a corporation make use of comparable networking technologies. the information Technology (IT) world refers to a network created by one corporation, or enterprise, for the aim of allowing its employees to communicate, as an enterprise network. The smaller networks at home, when used for business purposes, often go by the name small office/home office (SOHO) networks.
Users of enterprise networks have some idea about the enterprise network at their company or school. People realize that they use a network for several tasks. PC users might realize that their PC connects through an ethernet cable to a matching wall outlet, as shown at the top of Figure 1-2. those self same users might use wireless LANs with their laptop when getting to a gathering within the conference room also . Figure 1-2 shows these two end-user perspectives on an enterprise network.
Some users won’t even have a concept of the network at all. Instead, these users just enjoy the functions of the network—the ability to post messages to social media sites, make phone calls, look for information on the web , listen to music, and download countless apps to their phones—without caring about how it works or how their favorite device connects to the network.
Regardless of how much you already know about how networks work, this book and therefore the related certifications assist you learn how networks do their job. That job is just this: moving data from one device to another. the rest of this chapter, and therefore the rest of this first a part of the book, reveals the basics of how to build both SOHO and enterprise networks so that they will deliver data between two devices.
In the building business, much work happens before you nail the first boards together. the method starts with some planning, an understanding of how to build a house, and a few architectural blueprints of the way to build that specific house. Similarly, the journey toward building any computer network doesn’t begin by installing devices and cables, but instead by watching the architectural plans for those modern networks: the TCP/IP model.
TCP/IP Networking Model
A networking model, sometimes also called either a networking architecture or networking blueprint, refers to a comprehensive set of documents. Individually, each document describes one small function required for a network; collectively, these documents define everything that ought to happen for a computer network to work. Some documents define a protocol, which may be a set of logical rules that devices must follow to communicate. Other documents define some physical requirements for networking. for instance , a document could define the voltage and current levels used on a specific cable when transmitting data.
The TCP/IP protocol suite’s Network Access Layer
You can consider a networking model as you think that of an architectural blueprint for building a house. Sure, you’ll build a house without the blueprint. However, the blueprint can make sure that the house has the proper foundation and structure so that it’ll not fall down, and it’s the right hidden spaces to accommodate the plumbing, electrical, gas, and so on. Also, the various different people that build the house using the blueprint—such as framers, electricians, bricklayers, painters, then on—know that if they follow the blueprint, their a part of the work shouldn’t cause problems for the opposite workers.
Similarly, you’ll build your own network—write your own software, build your own networking cards, then on—to create a network. However, it’s much easier to easily buy and use products that already conform to some well-known networking model or blueprint. Because the networking product vendors build their products with some networking model in mind, their products should work well together.
Also Read:- Introduction of OSI Networking Model
History Leading to TCP/IP
Today, the planet of computer networking uses one networking model: TCP/IP. However, the planet has not always been so simple. Once upon a time, networking protocols didn’t exist, including TCP/IP. Vendors created the primary networking protocols; these protocols supported only that vendor’s computers. for instance , IBM published its Systems network architecture (SNA) networking model in 1974. Other vendors also created their own proprietary networking models. As a result, if your company bought computers from three vendors, network engineers often had to make three different networks supported the networking models created by each company, then somehow connect those networks, making the combined networks much more complex. The left side of Figure 1-3 shows the overall idea of what a company’s enterprise network may need looked like back within the 1980s, before TCP/IP became common in enterprise internetworks.
Although vendor-defined proprietary networking models often worked well, having an open, vendor-neutral networking model would aid competition and reduce complexity. The world organization for Standardization (ISO) took on the task to make such a model, starting as early because the late 1970s, beginning work on what would become referred to as the Open Systems Interconnection (OSI) networking model. ISO had a noble goal for the OSI model: to standardize data networking protocols to allow communication among all computers across the entire planet. ISO worked toward this ambitious and noble goal, with participants from most of the technologically developed nations on Earth participating within the process.
A second, less-formal effort to make an open, vendor-neutral, public networking model sprouted forth from a U.S. Department of Defense (DoD) contract. Researchers at various universities volunteered to assist further develop the protocols surrounding the original DoD work. These efforts resulted during a competing open networking model called TCP/IP.
During the 1990s, companies began adding OSI, TCP/IP, or both to their enterprise networks. However, by the end of the 1990s, TCP/IP had become the common choice, and OSI fell away. the middle a part of Figure 1-3 shows the general idea behind enterprise networks therein decade—still with networks built upon multiple networking models but including TCP/IP. Here within the twenty-first century, TCP/IP dominates. Proprietary networking models still exist, but they need mostly been discarded in favor of TCP/IP. The OSI model, whose development suffered in part due to a slower formal standardization process as compared with TCP/IP, never succeeded within the marketplace. And TCP/IP, the networking model originally created almost entirely by a bunch of volunteers, has become the most prolific network model ever, as shown on the right side of Figure 1-3. In this chapter, you will read about some of the basics of TCP/IP. Although you will learn some interesting facts about TCP/IP, the true goal of this chapter is to help you understand what a networking model or networking architecture really is and how it works. Also in this chapter, you will learn about some of the jargon used with OSI. Will any of you ever work on a computer that is using the full OSI protocols instead of TCP/IP? Probably not. However, you will often use terms relating to OSI.
Questions related to this topic
- Is TCP used in networking?
- Why are the OSI and TCP IP network models important in networking?
- What is TCP IP OSI model?
- What is the difference between the TCP IP network and the OSI network model?
This Blog Article is posted by
Infosavvy, 2nd Floor, Sai Niketan, Chandavalkar Road Opp. Gora Gandhi Hotel, Above Jumbo King, beside Speakwell Institute, Borivali West, Mumbai, Maharashtra 400092
Contact us – www.info-savvy.com
