Why do you need to know about the OSI networking model?

Question

Computer networks

I am studying computer networks, now I am specifically reading the famous book by Tanenbaum. So, in any course or book, the OSI model is always studied, and a rather large part of it is given to it. Usually it is considered "reference", but at the same time they write that it is not widely used now. Tanenbaum also writes that this model is relevant, but I just can’t understand what is its relevance? Why is everyone writing about it in textbooks if, as they say, it is not used anywhere? Why should a student know about it at all, where this model can be useful to him?
Perhaps experienced developers will find the question gruppy, but I'm specifically interested in knowing what in life it can come in handy?
Thank you!

Answer 1

The OSI model is not a specific "part" that may or may not be used. This is the fundamental principle of how you need to think about any stack of any protocols, from what angle to look at it )) This is why it is called the open model of intersystem exchange, (and not the protocol stack construction pattern), which gives the most general picture of what protocols have there can be characteristic roles in the stack, and offers a principle of how this can be structured to understand their interaction with each other. And it doesn't need to be memorized, you just need to understand it, the principle itself, and then use this understanding to understand other, already specific things.

Answer 2

No one knows what will come in handy, there's nothing you can do about it.
The model is not used anywhere, but it allows you to understand exactly how the network works from the hardware to the software, to understand that the network is not just "plugged in the cord and works."
I would say that this is the basis for understanding the operation of the network, which will definitely be useful to system administrators, it will also be useful to programmers who write applications that use the network.

Answer 3

This is basic knowledge. Just need to know. If you do not plan to work with networks, then at least at the level than l2 the switch differs from l3.
P.S.
I knew a developer who looked up the last entry in a table by finding the maximum value of the entry's id using the max aggregate function. He did not need sql at one time, apparently.

Answer 4

Why are schools still cramming the multiplication table, teaching division in a column, operations with natural fractions? After all, everyone has a calculator on their phone, right?
The ISO/OSI model is the "multiplication table" of an IT specialist. She just needs to know.

Answer 5

There are a large number of networks and technologies for their organization in addition to TCP / IP. A competent network engineer must understand at what point they begin to differ. What is the difference between v4 and v6, how does ISDN work, where does SDH end and what role does DWDM play, where should VSAT be used and where is SCPC, how to understand SS7 and at what level to enable SIGTRAN for it on a certain section of the network...

Answer 6

Not useful anywhere (practically), this is a basic abstraction to simplify the detailed study of various open systems, such as ip, WiFi, ethernet.

Answer 7

- If you suddenly want to develop your own protocol at a level below the application.
- If you decide to write a packet sniffer
- If you want to use any protocol other than TCP or UDP in your application, such as ICMP.
More precisely, not knowledge of the OSI model itself is useful, but knowledge of the TCP / IP model is a simplified OSI model that is actually used. But the principles of frame transfer from one level to another are exactly the same, it's just that some OSI levels are missing in the TCP / IP model, or rather, they are combined with neighboring levels.

Answer 8

useful when proxying through VPN and vice versa

Answer 9

If you have firmly decided that you will work with computer networks, and at the same time your interaction with networks is limited to:
Then you DO NOT NEED this fucking OSI model . But here the listed points will have to be mastered so that they bounce off the teeth.
If you are designing networks, configuring VLANs and managed switches, then you will have to master this too ...

Answer 10

Why do you need to know about the OSI networking model?

To answer this and many other useless interview questions.

So, in any course or book, the OSI model is always studied, and a rather large part of it is given to it. Usually it is considered "reference", but at the same time they write that it is not widely used now.

While the technobureaucrats were procrastinating this model, the objective reality rushed far ahead. And when the model came out, it was already irrelevant. Stillborn.
The vast majority now drives the ip / tcp stack.

Tanenbaum also writes that this model is relevant, but I just can’t understand what is its relevance?

Suddenly happen with the IS-IS protocol to work.

Perhaps experienced developers will find the question gruppy, but I'm specifically interested in knowing what in life it can come in handy?

Just like with the Pythagorean theorem in everyday life.

Answer 11

All to know on OSI
Read, understand and forget.
You rarely have to remember.

Answer 12

the OSI model is an interoperability standard example different people create network equipment that never intersects so that their equipment is compatible with each other and come up with standards these standards are developed at the IEEE radioelectronics
and RFC standards a document in a series of numbered Internet white papers containing technical specifications and standards that are widely used