osi model presentation layer. OSI network model. Description of the levels of the network model

Just because a protocol is an agreement adopted by two interacting entities, in this case two computers operating on a network, does not mean that it is necessarily standard. But in practice, when implementing networks, they usually use standard protocols. These can be branded, national or international standards.

In the early 80s, a number of international standardization organizations - ISO, ITU-T and some others - developed a model that played a significant role in the development of networks. This model is called the ISO/OSI model.

Open Systems Interoperability Model (Open System Interconnection, OSI) defines different levels of interaction between systems in packet switching networks, gives them standard names and specifies what functions each layer should perform.

The OSI model was developed based on extensive experience gained from creating computer networks, mainly global ones, in the 70s. A full description of this model takes up more than 1000 pages of text.

In the OSI model (Fig. 11.6), communication means are divided into seven levels: application, representative, session, transport, network, channel and physical. Each layer deals with a specific aspect of network device interaction.

Rice. 11.6.

The OSI model describes only the system communications implemented by the operating system, system utilities and hardware. The model does not include means for end-user application interaction. Applications implement their own communication protocols by accessing system tools. Therefore, it is necessary to distinguish between the level of interaction between applications and application layer.

It should also be kept in mind that the application can take over the functions of some of the upper layers of the OSI model. For example, some DBMSs have built-in tools remote access to files. In this case, the application does not use the system file service when accessing remote resources; it bypasses the upper layers of the OSI model and accesses directly the system facilities responsible for transportation messages over the network, which are located at the lower levels of the OSI model.

So, let's say an application makes a request to an application layer, such as a file service. Based on this request, the application level software generates a message in a standard format. A typical message consists of a header and a data field. The header contains service information that must be passed through the network to the application layer of the destination machine to tell it what work needs to be done. In our case, the header obviously must contain information about the location of the file and the type of operation that needs to be performed. The message data field can be empty or contain some data, such as data that needs to be written to a remote . But in order to deliver this information to its destination, there are still many tasks to be solved, the responsibility for which lies with lower levels.

After generating the message application layer sends it down the stack representative level. Protocol representative level based on information received from the application level header, performs the required actions and adds its own service information to the message - header representative level, which contains instructions for the protocol representative level destination machine. The resulting message is passed down session level, which in turn adds its header, etc. (Some protocols place service information not only at the beginning of the message in the form of a header, but also at the end, in the form of a so-called “trailer”.) Finally, the message reaches the bottom, physical level , which, in fact, transmits it via communication lines to the recipient machine. At this point, the message is “overgrown” with headers of all levels (

Model Open Systems Interconnection (OSI) is the skeleton, foundation and base of all network entities. The model defines network protocols, distributing them into 7 logical layers. It is important to note that in any process, network transmission control moves from layer to layer, sequentially connecting protocols at each layer.

Video: OSI model in 7 minutes

The lower layers are responsible for physical transmission parameters, such as electrical signals. Yes - yes, signals in wires are transmitted using representation into currents :) Currents are represented as a sequence of ones and zeros (1s and 0s), then the data is decoded and routed over the network. Higher levels cover queries related to data presentation. Relatively speaking, higher layers are responsible for network data from the user's point of view.

The OSI model was originally coined as standard approach, an architecture or pattern that would describe the network interaction of any network application. Let's take a closer look, shall we?

#01: Physical level

On the first level OSI models physical signals (currents, light, radio) are transmitted from source to recipient. At this level we operate with cables, contacts in connectors, coding of ones and zeros, modulation, and so on.

Among the technologies that live at the first level, we can highlight the most basic standard - Ethernet. It is now in every home.

Note that not only electric currents. Radio frequencies, light or infrared waves are also used everywhere in modern networks.

Network devices that belong to the first level are hubs and repeaters - that is, “stupid” pieces of hardware that can simply work with a physical signal without delving into its logic (without decoding).

#02: Data Link level

Imagine, we received a physical signal from the first level - physical. This is a set of voltages of different amplitudes, waves or radio frequencies. Upon receipt, the second level checks and corrects transmission errors. At the second level, we operate with the concept of “frame”, or as they also say “frame”. Here the first identifiers appear - MAC addresses. They consist of 48 bits and look something like this: 00:16:52:00:1f:03.

The link layer is complex. Therefore, it is conventionally divided into two sublevels: logical channel control (LLC, Logical Link Control) and media access control (MAC, Media Access Control).

Devices such as switches and bridges live at this level. By the way! The Ethernet standard is also here. It is comfortably located at the first and second (1 and 2) levels of the OSI model.

#03: Network layer

Let's go up! The network layer introduces the term “routing” and, accordingly, the IP address. By the way, to convert IP addresses to MAC addresses and back, it is used ARP protocol.

It is at this level that traffic routing occurs as such. If we want to go to the site website, then we send, receive a response in the form of an IP address and substitute it into the packet. Yes - yes, if at the second level we use the term frame/frame, as we said earlier, then here we use a package.

Of the devices, His Majesty the Router lives here :)

The process when data is transferred from upper layers to lower ones is called encapsulation data, and when on the contrary, upward, from the first, physical to the seventh, then this process is called decapsulation data

#04: Transport layer

The transport layer, as the name suggests, provides data transmission over the network. There are two main rock stars here - TCP and UDP. The difference is that different transport is used for different categories of traffic. The principle is this:

• Traffic is sensitive to losses- no problem, TCP (Transmission Control Protocol)! It provides control over data transfer;
• We'll lose a little - no big deal- in fact, now that you are reading this article, a couple of packages might have been lost. But this is not felt for you as a user. UDP (User Datagram Protocol) is good for you. What if it was telephony? The loss of packets there is critical, since the voice in real time will simply begin to “croak”;

#05: Session layer

Ask any network engineer to explain the session layer to you. It will be difficult for him to do this, infa 100%. The fact is that in everyday work, a network engineer interacts with the first four layers - physical, channel, network and transport. The rest, or the so-called “upper” levels, relate more to the work of software developers :) But we’ll try!

The session layer is responsible for managing connections, or simply put, sessions. He tears them apart. Remember the meme about “ THERE WAS NOT A SINGLE BREAK"? We remember. So, this is the fifth level tried :)

#06 Presentation layer

At the sixth level, conversion of message formats, such as encoding or compression, occurs. JPEG and GIF, for example, live here. The level is also responsible for transmitting the stream to the fourth (transport layer).

#07 Application level

On the seventh floor, at the very tip of the iceberg, lives the application layer! There are network services here that allow us, as end users, to surf the Internet. Look, what protocol do you use to open our knowledge base? That's right, HTTPS. This guy is from the seventh floor. Simple HTTP, FTP and SMTP also live here.

Was this article useful to you?

Please tell me why?

We are sorry that the article was not useful for you: (Please, if it is not difficult, indicate why? We will be very grateful for a detailed answer. Thank you for helping us become better!

In network science, as in any other field of knowledge, there are two fundamental approaches to learning: movement from the general to the specific and vice versa. Well, it’s not that in life people use these approaches in their pure form, but still, at the initial stages, each student chooses for himself one of the above-mentioned directions. For higher education (at least the (post)Soviet model) the first method is more typical, for self-education most often the second: a person was working on the network, solving small single-user administrative tasks from time to time, and suddenly he wanted to figure out how, Actually, how does all this crap work?

But the purpose of this article is not philosophical discussions about teaching methodology. I would like to introduce to the attention of novice networkers that general and most importantly, from which, like from a stove, you can dance to the most sophisticated private shops. By understanding the seven-layer OSI model and learning to “recognize” its layers in the technologies you already know, you can easily move forward in any direction of the networking industry you choose. The OSI model is the framework on which any new knowledge about networks will be hung.

This model is mentioned in one way or another in almost any modern literature on networks, as well as in many specifications of specific protocols and technologies. Not feeling the need to reinvent the wheel, I decided to publish excerpts from the work of N. Olifer, V. Olifer (Center Information technologies) entitled “The role of communication protocols and the functional purpose of the main types of equipment in corporate networks,” which I consider the best and most comprehensive publication on this topic.

chief editor

model

Just because a protocol is an agreement between two interacting entities, in this case two computers working on a network, does not mean that it is necessarily a standard. But in practice, when implementing networks, they tend to use standard protocols. These may be proprietary, national or international standards.

The International Standards Organization (ISO) has developed a model that clearly defines the different levels of interaction between systems, gives them standard names, and specifies what work each level should do. This model is called the Open System Interconnection (OSI) model or ISO/OSI model.

In the OSI model, communication is divided into seven layers or layers (Figure 1.1). Each level deals with one specific aspect of interaction. Thus, the interaction problem is decomposed into 7 particular problems, each of which can be solved independently of the others. Each layer maintains interfaces with the layers above and below.

Rice. 1.1. ISO/OSI Open Systems Interconnection Model

The OSI model describes only system communications, not end-user applications. Applications implement their own communication protocols by accessing system facilities. It should be borne in mind that the application can take over the functions of some of the upper layers of the OSI model, in which case, if necessary, internetworking it accesses directly the system tools that perform the functions of the remaining lower layers of the OSI model.

An end-user application can use system interaction tools not only to organize a dialogue with another application running on another machine, but also simply to receive the services of a particular network service, for example, accessing remote files, receiving mail, or printing on a shared printer.

So, let's say an application makes a request to an application layer, such as a file service. Based on this request, the application level software generates a standard format message, which contains service information (header) and, possibly, transmitted data. This message is then forwarded to the representative level. The presentation layer adds its header to the message and passes the result down to the session layer, which in turn adds its header, and so on. Some protocol implementations provide that the message contains not only a header, but also a trailer. Finally, the message reaches the lowest, physical layer, which actually transmits it along the communication lines.

When a message arrives on another machine over the network, it moves up sequentially from level to level. Each level analyzes, processes and deletes the header of its level, performs functions corresponding to this level and passes the message to the higher level.

In addition to the term message, there are other names used by network specialists to designate a unit of data exchange. ISO standards for protocols of any level use the term “protocol data unit” - Protocol Data Unit (PDU). In addition, the names frame, packet, and datagram are often used.

ISO/OSI Model Layer Functions

Physical Layer: This layer deals with the transmission of bits over physical channels such as coaxial cable, twisted pair cable, or fiber optic cable. This level is related to the characteristics of physical data transmission media, such as bandwidth, noise immunity, characteristic impedance and others. At the same level, the characteristics of electrical signals are determined, such as requirements for pulse edges, voltage or current levels of the transmitted signal, type of coding, signal transmission speed. In addition, the types of connectors and the purpose of each contact are standardized here.

Physical layer functions are implemented in all devices connected to the network. On the computer side, the physical layer functions are performed by the network adapter or serial port.

An example of a physical layer protocol is the 10Base-T Ethernet technology specification, which defines the cable used as a Category 3 unshielded twisted pair with a characteristic impedance of 100 Ohms, an RJ-45 connector, maximum length physical segment of 100 meters, Manchester code for representing data on the cable, and other characteristics of the environment and electrical signals.

Data Link Layer: The physical layer simply transfers bits. This does not take into account that in some networks in which communication lines are used (shared) alternately by several pairs of interacting computers, the physical transmission medium may be occupied. Therefore, one of the tasks of the link layer is to check the availability of the transmission medium. Another task of the link layer is to implement error detection and correction mechanisms. To do this, at the data link layer, bits are grouped into sets called frames. The link layer ensures that each frame is transmitted correctly by placing a special sequence of bits at the beginning and end of each frame to mark it, and also calculates a checksum by summing all the bytes of the frame in a certain way and adding the checksum to the frame. When the frame arrives, the receiver again calculates the checksum of the received data and compares the result with the checksum from the frame. If they match, the frame is considered correct and accepted. If the checksums do not match, an error is recorded.

In link layer protocols used in local networks, a certain structure of connections between computers and methods of addressing them are laid down. Although the data link layer provides frame delivery between any two nodes on a local network, it does this only in a network with a very specific connection topology, precisely the topology for which it was designed. Typical topologies supported by LAN link layer protocols include shared bus, ring, and star. Examples of link layer protocols are Ethernet, Token Ring, FDDI, 100VG-AnyLAN.

In local area networks, link layer protocols are used by computers, bridges, switches, and routers. In computers, link layer functions are implemented through the joint efforts of network adapters and their drivers.

In global networks, which rarely have a regular topology, the data link layer ensures the exchange of messages between two neighboring computers connected by an individual communication line. Examples of point-to-point protocols (as such protocols are often called) are the widely used PPP and LAP-B protocols.

Network level. This level serves to form a unified transport system that unites several networks with different principles for transmitting information between end nodes. Let's look at the functions of the network layer using local networks as an example. The local network link layer protocol ensures the delivery of data between any nodes only in a network with the appropriate typical topology. This is a very strict limitation that does not allow building networks with a developed structure, for example, networks that combine several enterprise networks into a single network, or highly reliable networks in which there are redundant connections between nodes. In order, on the one hand, to maintain the simplicity of data transfer procedures for standard topologies, and on the other hand, to allow the use of arbitrary topologies, an additional network layer is used. At this level the concept of "network" is introduced. In this case, a network is understood as a collection of computers connected to each other in accordance with one of the standard typical topologies and using one of the link layer protocols defined for this topology to transmit data.

Thus, within the network, data delivery is regulated by the data link layer, but data delivery between networks is handled by the network layer.

Network layer messages are usually called packages. When organizing packet delivery at the network level, the concept is used "network number". In this case, the recipient's address consists of the network number and the computer number on this network.

Networks are connected to each other by special devices called routers. Router is a device that collects information about the topology of internetwork connections and, based on it, forwards network layer packets to the destination network. In order to transmit a message from a sender located on one network to a recipient located on another network, you need to make a number of transit transfers (hops) between networks, each time choosing the appropriate route. Thus, a route is a sequence of routers through which a packet passes.

The problem of choosing the best path is called routing and its solution is the main task of the network level. This problem is complicated by the fact that the shortest path is not always the best. Often the criterion for choosing a route is the time of data transmission along this route; it depends on the capacity of communication channels and traffic intensity, which can change over time. Some routing algorithms try to adapt to changes in load, while others make decisions based on long-term averages. The route can be selected based on other criteria, for example, transmission reliability.

At the network level, two types of protocols are defined. The first type refers to the definition of rules for transmitting end node data packets from the node to the router and between routers. These are the protocols that are usually meant when people talk about network layer protocols. The network layer also includes another type of protocol called routing information exchange protocols. Using these protocols, routers collect information about the topology of internetwork connections. Network layer protocols are implemented by operating system software modules, as well as router software and hardware.

Examples of network layer protocols are the TCP/IP stack IP Internetwork Protocol and the Novell IPX stack Internetwork Protocol.

Transport Layer: On the way from the sender to the recipient, packets may be corrupted or lost. While some applications have their own error handling, there are others that prefer to deal with a reliable connection right away. The job of the transport layer is to ensure that applications or the upper layers of the stack - application and session - transfer data with the degree of reliability that they require. The OSI model defines five classes of service provided by the transport layer. These types of services are distinguished by the quality of the services provided: urgency, the ability to restore interrupted communications, the availability of means for multiplexing multiple connections between different application protocols through a common transport protocol, and most importantly, the ability to detect and correct transmission errors, such as distortion, loss and duplication of packets.

The choice of transport layer service class is determined, on the one hand, by the extent to which the problem of ensuring reliability is solved by the applications and protocols of higher levels than the transport one, and on the other hand, this choice depends on how reliable the entire data transportation system is online. So, for example, if the quality of communication channels is very high, and the likelihood of errors not detected by lower-level protocols is small, then it is reasonable to use one of the lightweight transport layer services that are not burdened with numerous checks, handshaking, and other techniques for increasing reliability. If vehicles are initially very unreliable, then it is advisable to turn to the most developed transport level service, which works using maximum means for detecting and eliminating errors - by first establishing a logical connection, monitoring message delivery using checksums and cyclic numbering of packets, setting delivery timeouts, etc.

As a rule, all protocols, starting from the transport layer and above, are implemented software end nodes of the network - components of their network operating systems. Examples of transport protocols include the TCP and UDP protocols of the TCP/IP stack and the SPX protocol of the Novell stack.

Session Layer: The session layer provides conversation management to record which party is currently active and also provides synchronization facilities. The latter allow you to insert checkpoints into long transfers so that in case of failure you can go back to the last checkpoint, instead of starting all over again. In practice, few applications use the session layer, and it is rarely implemented.

Presentation Layer: This layer provides assurance that information conveyed by the application layer will be understood by the application layer in another system. If necessary, the presentation layer converts data formats into some common presentation format, and at the reception, accordingly, performs the reverse conversion. In this way, application layers can overcome, for example, syntactic differences in data representation. At this level, encryption and decryption of data can be performed, thanks to which the secrecy of data exchange is ensured for all application services at once. An example of a protocol that operates at the presentation layer is the Secure Socket Layer (SSL) protocol, which provides secure messaging for the application layer protocols of the TCP/IP stack.

Application layer. The application layer is really just a set of various protocols with which network users access shared resources such as files, printers or hypertext Web pages, and also organize their collaboration, for example, using the protocol Email. The unit of data that the application layer operates on is usually called message .

There is a very wide variety of application layer protocols. Let us give as examples at least a few of the most common implementations of file services: NCP in the Novell NetWare operating system, SMB in Microsoft Windows NT, NFS, FTP and TFTP included in the TCP/IP stack.

The OSI model, although very important, is only one of many communication models. These models and their associated protocol stacks may differ in the number of layers, their functions, message formats, services provided at the upper layers, and other parameters.

Characteristics of popular communication protocol stacks

So, the interaction of computers in networks occurs in accordance with certain rules for exchanging messages and their formats, that is, in accordance with certain protocols. A hierarchically organized set of protocols, solving the problem interaction of network nodes is called a communication protocol stack.

There are many protocol stacks that are widely used in networks. These are stacks that are international and national standards, and proprietary stacks that have become widespread due to the prevalence of equipment from a particular company. Examples of popular protocol stacks include Novell's IPX/SPX stack, the TCP/IP stack used in Internet networks and in many operating-based networks UNIX systems, OSI stack of the International Organization for Standardization, DECnet stack of Digital Equipment Corporation and some others.

The use of a particular communication protocol stack in a network largely determines the face of the network and its characteristics. Smaller networks may use only one stack. In large corporate networks connecting various networks, as a rule, several stacks are used in parallel.

Communication equipment implements lower-layer protocols that are more standardized than higher-layer protocols, and this is a prerequisite for successful collaboration equipment from various manufacturers. The list of protocols supported by a particular communication device is one of the most important characteristics of this device.

Computers implement communication protocols in the form of corresponding software elements of a network operating system, for example, link-level protocols are usually implemented in the form of network adapter drivers, and upper-level protocols are implemented in the form of server and client components of network services.

The ability to work well in a particular operating system environment is an important characteristic of communications equipment. You can often read in advertisements for a network adapter or hub that it was designed specifically to work on a NetWare or UNIX network. This means that the hardware developers have optimized its characteristics for the protocols used in that network operating system, or for a given version of their implementation if these protocols are used in different operating systems. Due to the peculiarities of the implementation of protocols in various operating systems, one of the characteristics of communication equipment is its certification for the ability to work in the environment of a given operating system.

At the lower levels - physical and data link - almost all stacks use the same protocols. These are well-standardized protocols: Ethernet, Token Ring, FDDI and some others, which allow the same equipment to be used in all networks.

The network and higher layer protocols of existing standard stacks are highly variable and generally do not conform to the layering recommended by the ISO model. In particular, in these stacks, session and presentation layer functions are most often combined with the application layer. This discrepancy is due to the fact that the ISO model appeared as a result of a generalization of already existing and actually used stacks, and not vice versa.

OSI stack

A distinction must be made between the OSI protocol stack and the OSI model. While the OSI model conceptually defines the procedure for interaction of open systems, decomposing the task into 7 layers, standardizes the purpose of each layer and introduces standard names for the layers, the OSI stack is a set of very specific protocol specifications that form a consistent protocol stack. This protocol stack is supported by the US government in its GOSIP program. All computer networks Government installations after 1990 must either directly support the OSI stack or provide a means to migrate to that stack in the future. However, the OSI stack is more popular in Europe than in the US, as Europe has fewer legacy networks installed that use their own protocols. There is also a big need for a common stack in Europe, as there are so many different countries.

This is an international, manufacturer-independent standard. It can enable collaboration between corporations, partners and suppliers. This interaction is complicated by addressing, naming, and data security issues. All these problems are partially solved in the OSI stack. OSI protocols require a lot of computing power central processor, making them more suitable for powerful machines rather than networks personal computers. Most organizations are just planning the transition to the OSI stack. Among those working in this direction are the US Navy Department and the NFSNET network. One of the largest manufacturers supporting OSI is AT&T. Its Stargroup network is entirely based on the OSI stack.

For obvious reasons, the OSI stack, unlike other standard stacks, fully complies with the OSI interconnection model; it includes specifications for all seven layers of the open systems interconnection model (Figure 1.3).

Rice. 1.3. OSI stack

On The OSI stack supports Ethernet, Token Ring, FDDI protocols, as well as LLC, X.25 and ISDN protocols. These protocols will be discussed in detail in other sections of the manual.

Services network, transport and session levels are also available in the OSI stack, but they are not very common. The network layer implements both connectionless and connection-based protocols. The OSI stack transport protocol, consistent with the functions defined for it in the OSI model, hides the differences between connection-oriented and connectionless network services so that users receive the desired quality of service regardless of the underlying network layer. To provide this, the transport layer requires the user to specify the desired quality of service. 5 classes of transport service have been defined, from the lowest class 0 to the highest class 4, which differ in the degree of error tolerance and requirements for data recovery after errors.

Services application level include file transfer, terminal emulation, directory services, and mail. Of these, the most promising are directory service (X.500 standard), electronic mail (X.400), virtual terminal protocol (VT), file transfer, access and management (FTAM) protocol, forwarding and job management protocol (JTM). Recently, ISO has concentrated its efforts on top-level services.

The X.400 Recommendations define the following minimum required set of services to be provided to users: access control, maintenance of unique system message identifiers, message delivery or non-delivery notification with reason, message content type indication, message content conversion indication, transmission and delivery timestamps, selecting a delivery category (urgent, non-urgent, normal), multicast delivery, delayed delivery (up to a specific point in time), transforming content to interface with incompatible mail systems such as telex and fax services, querying whether a specific message was delivered, mailing lists, which may have a nested structure, means of protecting messages from unauthorized access, based on an asymmetric public key cryptosystem.

The purpose of the recommendations X.500 is the development of global standards help desk. The process of delivering a message requires knowledge of the recipient's address, which is a problem in large networks, so it is necessary to have a help desk that helps obtain the addresses of senders and recipients. In general, an X.500 service is a distributed database of names and addresses. All users are potentially allowed to log into this database using a specific set of attributes.

The following operations are defined on the names and addresses database:

• reading - getting an address by a known name,
• request - obtaining a name based on known address attributes,
• modification involving deleting and adding records in a database.

The main challenges to implementing the X.500 recommendations stem from the scale of this project, which purports to be a worldwide reference service. Therefore, software implementing X.500 recommendations is very cumbersome and places high demands on hardware performance.

Protocol VT solves the problem of incompatibility between different terminal emulation protocols. Currently, a user of a personal computer compatible with an IBM PC needs to purchase three various programs for terminal emulation various types and using different protocols. If every host computer had ISO terminal emulation protocol software, then the user would only need one program that supported the VT protocol. In its standard, ISO has accumulated widely used terminal emulation functions.

File transfer is the most common computer service. Access to files, both local and remote, is needed by all applications - text editors, email, databases or remote launch programs. ISO provides such a service in the protocol FTAM. Along with the X.400 standard, it is the most popular OSI stack standard. FTAM provides facilities for localizing and accessing file content and includes a set of directives for inserting, replacing, extending, and clearing file content. FTAM also provides facilities for manipulating the file as a whole, including creating, deleting, reading, opening, closing the file, and selecting its attributes.

Forwarding and Work Control Protocol JTM Allows users to forward work that needs to be completed on the host computer. The job control language that enables job submission tells the host computer what actions should be performed on what programs and files. The JTM protocol supports traditional batch processing, transaction processing, remote job entry, and distributed database access.

TCP/IP stack

The TCP/IP stack, also called the DoD stack and the Internet stack, is one of the most popular and promising communication protocol stacks. If it is currently distributed mainly in networks with UNIX OS, then its implementation in latest versions network operating systems for personal computers (Windows NT, NetWare) is a good prerequisite for the rapid growth in the number of installations of the TCP/IP stack.

The stack was developed at the initiative of the US Department of Defense (DoD) more than 20 years ago to connect the experimental ARPAnet network with other satellite networks as a set of common protocols for heterogeneous computing environments. The ARPA network supported developers and researchers in military fields. In the ARPA network, communication between two computers was carried out using the Internet Protocol (IP), which to this day is one of the main ones in the TCP / IP stack and appears in the name of the stack.

Berkeley University made a major contribution to the development of the TCP/IP stack by implementing stack protocols in its version of the UNIX OS. The widespread adoption of the UNIX operating system also led to the widespread adoption of IP and other stack protocols. Worldwide works on the same stack information network Internet, whose division, the Internet Engineering Task Force (IETF), is a major contributor to the improvement of stack standards published in the form of RFC specifications.

Since the TCP/IP stack was developed before the advent of the ISO/OSI open systems interconnection model, although it also has a multi-level structure, the correspondence of the TCP/IP stack levels to the levels of the OSI model is rather conditional.

The structure of the TCP/IP protocols is shown in Figure 1.4. TCP/IP protocols are divided into 4 layers.

Rice. 1.4. TCP/IP stack

The lowest one ( level IV ) - level between network interfaces- corresponds to the physical and data link layers of the OSI model. This level in the TCP/IP protocols is not regulated, but supports all popular standards of the physical and data link layer: for local channels these are Ethernet, Token Ring, FDDI, for global channels - their own protocols for operating on analog dial-up and leased lines SLIP/PPP, which establish point-to-point connections via serial links global networks, and WAN protocols X.25 and ISDN. A special specification has also been developed that defines the use of ATM technology as a data link layer transport.

Next level ( level III ) is the internetworking layer that deals with the transmission of datagrams using various local networks, X.25 area networks, ad hoc lines, etc. The stack uses the protocol IP, which was originally designed as a protocol for transmitting packets in composite networks consisting of a large number of local networks connected by both local and global connections. Therefore, the IP protocol works well in networks with complex topologies, rationally using the presence of subsystems in them and economically spending throughput low-speed communication lines. The IP protocol is a datagram protocol.

The level of internetworking also includes all protocols related to the compilation and modification of routing tables, such as protocols for collecting routing information R.I.P.(Routing Internet Protocol) and OSPF(Open Shortest Path First), as well as the Internet Control Message Protocol ICMP(Internet Control Message Protocol). The latter protocol is designed to exchange error information between the router and the gateway, the source system and the destination system, that is, to organize feedback. Using special ICMP packets, it is reported that it is impossible to deliver a packet, that the lifetime or duration of assembling a packet from fragments has been exceeded, anomalous parameter values, a change in the forwarding route and type of service, the state of the system, etc.

Next level ( level II) is called basic. The transmission control protocol operates at this level TCP(Transmission Control Protocol) and User Datagram Protocol UDP(User Datagram Protocol). The TCP protocol provides a stable virtual connection between remote application processes. The UDP protocol ensures the transmission of application packets using the datagram method, that is, without establishing a virtual connection, and therefore requires less overhead than TCP.

Top level ( level I) is called applied. Over many years of use in the networks of various countries and organizations, the TCP/IP stack has accumulated a large number of protocols and application level services. These include such widely used protocols as FTP file copy protocol, telnet terminal emulation protocol, mail SMTP protocol, used in Internet e-mail and its Russian branch RELCOM, hypertext services for accessing remote information, such as WWW and many others. Let's take a closer look at some of them that are most closely related to the topics of this course.

Protocol SNMP(Simple Network Management Protocol) is used to organize network management. The management problem is divided here into two problems. The first task is related to the transfer of information. Control information transfer protocols determine the procedure for interaction between the server and the client program running on the administrator’s host. They define the message formats that are exchanged between clients and servers, as well as the formats for names and addresses. The second challenge is related to controlled data. The standards regulate what data should be stored and accumulated in gateways, the names of this data, and the syntax of these names. The SNMP standard defines a specification information base network management data. This specification, known as the Management Information Base (MIB), defines the data elements that a host or gateway must store and the permissible operations on them.

File Transfer Protocol FTP(File Transfer Protocol) implements remote file access. In order to ensure reliable transfer, FTP uses the connection-oriented protocol - TCP - as its transport. In addition to file transfer protocol, FTP offers other services. This gives the user the opportunity interactive work with a remote machine, for example, it can print the contents of its directories; FTP allows the user to specify the type and format of the data to be stored. Finally, FTP authenticates users. Before accessing the file, protocol requires users to provide their username and password.

In the TCP/IP stack, FTP offers the most comprehensive set of file services, but is also the most complex to program. Applications that do not require all the capabilities of FTP can use another, more cost-effective protocol - the Simple File Transfer Protocol TFTP(Trivial File Transfer Protocol). This protocol only implements file transfer, and the transport used is a simpler than TCP, connectionless protocol - UDP.

Protocol telnet provides the transfer of a stream of bytes between processes, as well as between a process and a terminal. Most often, this protocol is used to emulate a remote computer terminal.

IPX/SPX stack

This stack is the original Novell protocol stack, which it developed for its NetWare network operating system back in the early 80s. The Internetwork Packet Exchange (IPX) and Sequenced Packet Exchange (SPX) protocols, which give the stack its name, are direct adaptations of Xerox's XNS protocols, which are much less common than IPX/SPX. In terms of installations, IPX/SPX protocols are the leaders, and this is due to the fact that the NetWare OS itself occupies a leading position with a share of installations worldwide of approximately 65%.

The Novell protocol family and their correspondence to the ISO/OSI model are presented in Figure 1.5.

Rice. 1.5. IPX/SPX stack

On physical and data link levels Novell networks use all popular protocols of these levels (Ethernet, Token Ring, FDDI and others).

On network level the protocol works in the Novell stack IPX, as well as routing information exchange protocols R.I.P. And NLSP(analogous to the OSPF protocol of the TCP/IP stack). IPX is a protocol that deals with addressing and routing packets on Novell networks. IPX routing decisions are based on the address fields in its packet header as well as information from routing information exchange protocols. For example, IPX uses information provided by either RIP or NLSP (NetWare Link State Protocol) to forward packets to the destination computer or the next router. The IPX protocol supports only the datagram method of message exchange, due to which it economically consumes computing resources. So, the IPX protocol provides three functions: setting an address, establishing a route, and sending datagrams.

The transport layer of the OSI model in the Novell stack corresponds to the SPX protocol, which carries out connection-oriented message transfer.

On the top application, presentation and session levels NCP and SAP protocols work. Protocol NCP(NetWare Core Protocol) is a protocol for interaction between the NetWare server and the workstation shell. This application layer protocol implements the client-server architecture at the upper layers of the OSI model. Using the functions of this protocol, the workstation connects to the server, maps the server directories to local drive letters, browses the server file system, copies deleted files, changes their attributes, etc., and also performs division network printer between workstations.

Servers and routers use SAP to advertise their services and network addresses. The SAP protocol allows network devices to constantly update information about what services are currently available on the network. At startup, servers use SAP to notify the rest of the network about their services. When a server shuts down, it uses SAP to notify the network that its services have ceased.

On Novell networks, NetWare 3.x servers send out SAP broadcast packets every minute. SAP packets significantly clog the network, so one of the main tasks of routers that access global communications is to filter traffic from SAP packets and RIP packets.

The features of the IPX/SPX stack are determined by the features of the NetWare OS, namely its orientation earlier versions(up to 4.0) to work in small local networks consisting of personal computers with modest resources. Therefore, Novell needed protocols that required a minimum number of random access memory(limited in IBM-compatible computers running MS-DOS to 640 KB) and which would run quickly on processors of low processing power. As a result, the IPX/SPX stack protocols until recently worked well in local networks and not so well in large corporate networks, since they overloaded slow global links with broadcast packets that are intensively used by several protocols in this stack (for example, to establish communications between clients and servers).

This circumstance, as well as the fact that the IPX/SPX stack is the property of Novell and requires a license to implement it, has for a long time limited its distribution only to NetWare networks. However, by the time NetWare 4.0 was released, Novell had made and continues to make major changes to its protocols aimed at adapting them to work in corporate networks. Now the IPX/SPX stack is implemented not only in NetWare, but also in several other popular network operating systems - SCO UNIX, Sun Solaris, Microsoft Windows NT.

NetBIOS/SMB stack

Microsoft and IBM worked together on networking tools for personal computers, so the NetBIOS/SMB protocol stack is their joint brainchild. NetBIOS was introduced in 1984 as a network extension of the standard IBM PC Basic Input/Output System (BIOS) features for network program PC Network from IBM, which at the application level (Fig. 1.6) used the SMB (Server Message Block) protocol to implement network services.

Rice. 1.6. NetBIOS/SMB stack

Protocol NetBIOS works at three levels of the open systems interaction model: network, transport and session. NetBIOS can provide a higher level of service than the IPX and SPX protocols, but does not have routing capabilities. Thus, NetBIOS is not a network protocol in the strict sense of the word. NetBIOS contains many useful networking functions that can be attributed to the network, transport and session layers, but it cannot be used to route packets, since the NetBIOS frame exchange protocol does not introduce such a concept as a network. This limits the use of the NetBIOS protocol to local networks that are not subnetted. NetBIOS supports both datagram and connection-based communications.

Protocol SMB, corresponding to the application and representative levels of the OSI model, regulates the interaction of the workstation with the server. SMB functions include the following operations:

• Session management. Creation and breaking of a logical channel between the workstation and the network resources of the file server.
• File access. A workstation can contact the file server with requests to create and delete directories, create, open and close files, read and write to files, rename and delete files, search for files, get and set file attributes, and lock records.
• Printing service. The workstation can queue files for printing on the server and obtain information about the print queue.
• Messaging service. SMB supports simple messaging with the following functions: send a simple message; send a broadcast message; send start of message block; send message block text; send end of message block; forward username; cancel the shipment; get the machine name.

Because of the large number of applications that use the API functions provided by NetBIOS, many network operating systems implement these functions as an interface to their transport protocols. NetWare has a program that emulates NetBIOS functions based on the IPX protocol, and there are software emulators for NetBIOS for Windows NT and the TCP/IP stack.

Why do we need this valuable knowledge? (editorial)

A colleague once asked me a tricky question. Well, he says, you know what the OSI model is... And why do you need it, what is the practical benefit of this knowledge: unless you show off in front of dummies? It’s not true, the benefits of this knowledge are a systematic approach to solving many practical problems. For example:

• troubleshooting (