Skip to main content

Internet architecture

Internet architecture
9.1.7 This page will examine the basic architecture of the Internet.


The Internet enables nearly instantaneous worldwide data communications between anyone, anywhere, at any time.

LANs are networks within limited geographic areas. However, LANs are limited in scale. Although there have been technological advances to improve the speed of communications, such as Metro Optical, Gigabit, and 10-Gigabit Ethernet, distance is still a problem.

Students can focus on the communications between source and destination computers or intermediate computers at the application layer to get an overview of the Internet architecture. Identical instances of an application could be placed on all the computers in a network to ease the delivery of messages. However, this does not scale well. New software would require new applications to be installed on every computer in the network. For new hardware to function properly, the software would need to be modified. Any failure of an intermediate computer or computer application would cause a break in the chain of the messages that are passed.

The Internet uses the principle of network layer interconnection. The goal is to build the functionality of the network in independent modules. This allows a diversity of LAN technologies at Layers 1 and 2 of the OSI model and a diversity of applications at Layers 5, 6, and 7. The OSI model provides a mechanism where the details of the lower and the upper layers are separated. This allows intermediate networking devices to relay traffic without details about the LAN.

This leads to the concept of internetworks, or networks that consist of many networks. A network of networks is called an internetwork, which is indicated with the lowercase i. The network on which the World Wide Web (www) runs is the Internet, which is indicated with a capital I. Internetworks must be scalable with regard to the number of networks and computers attached. They must also be able to handle the transport of data across vast distances. An internetwork must be flexible to account for constant technological innovations. It must be able to adjust to dynamic conditions on the network. And internetworks must be cost-effective. Internetworks must be designed to permit data communications to anyone, anywhere, at any time.

Figure summarizes the connection of one physical network to another through a special purpose computer called a router. These networks are described as directly connected to the router. The router is needed to handle any path decisions required for the two networks to communicate. Many routers are needed to handle large volumes of network traffic.

Figure extends the idea to three physical networks connected by two routers. Routers make complex decisions to allow users on all the networks to communicate with each other. Not all networks are directly connected to one another. The router must have some method to handle this situation.

One option is for a router to keep a list of all computers and all the paths to them. The router would then decide how to forward data packets based on this reference table. Packets would be forwarded based on the IP address of the destination computer. This option would become difficult as more users were added to the network. Scalability is introduced when the router keeps a list of all networks, but leaves the local delivery details to the local physical networks. In this situation, the routers pass messages to other routers. Each router shares information about its connected network.

Figure shows the transparency that users require. However, the physical and logical structures inside the Internet cloud can be extremely complex as shown in Figure . The Internet has grown rapidly to allow more and more users. The fact that the Internet has grown so large, with more than 90,000 core routes and 300,000,000 end users, proves the effectiveness of the Internet architecture.

Two computers located anywhere in the world that follow certain hardware, software, and protocol specifications can communicate reliably. The standardization of ways to move data across networks has made the Internet possible.

This page concludes this lesson. The next lesson will discuss Internet addressing. The first page covers IP addressing.

Comments

Popular posts from this blog

OSI layers / Peer-to-peer communications / TCP/IP model

OSI layers 2.3.4 This page discusses the seven layers of the OSI model. The OSI reference model is a framework that is used to understand how information travels throughout a network. The OSI reference model explains how packets travel through the various layers to another device on a network, even if the sender and destination have different types of network media. In the OSI reference model, there are seven numbered layers, each of which illustrates a particular network function. - Dividing the network into seven layers provides the following advantages: • It breaks network communication into smaller, more manageable parts. • It standardizes network components to allow multiple vendor development and support. • It allows different types of network hardware and software to communicate with each other. • It prevents changes in one layer from affecting other layers. • It divides network communication into smaller parts to make learning it easier to understand. In the foll...

Advantages and disadvantages of link-state routing

Advantages and disadvantages of link-state routing 2.1.5  This page lists the advantages and disadvantages of link-state routing protocols. The following are advantages of link-state routing protocols:  Link-state protocols use cost metrics to choose paths through the network. The cost metric reflects the capacity of the links on those paths. Link-state protocols use triggered updates and LSA floods to immediately report changes in the network topology to all routers in the network. This leads to fast convergence times. Each router has a complete and synchronized picture of the network. Therefore, it is very difficult for routing loops to occur. Routers use the latest information to make the best routing decisions. The link-state database sizes can be minimized with careful network design. This leads to smaller Dijkstra calculations and faster convergence. Every router, at the very least, maps the topology of it...

Ports for services

Ports for services 10.2.2  Services running on hosts must have a port number assigned to them so communication can occur. A remote host attempting to connect to a service expects that service to use specific transport layer protocols and ports. Some ports, which are defined in RFC 1700, are known as the well-known ports. These ports are reserved in both TCP and UDP.  These well-known ports define applications that run above the transport layer protocols. For example, a server that runs FTP will use ports 20 and 21 to forward TCP connections from clients to its FTP application. This allows the server to determine which service a client requests. TCP and UDP use port numbers to determine the correct service to which requests are forwarded. The next page will discuss ports in greater detail.