A few Questions about computer networks
Hello,
I have a few questions about computer networks.
Can you please help me to answer them?
Thank you.
1) What is the difference between an Ethernet header, Ethernet packet, Ethernet frame and Ethernet protocol?
2) Why is horizontal communication possible at all? There is no horizontal connection between the end devices (based on the ISO / OSI model)
3) What are examples of horizontal and vertical communication(based on the ISO / OSI model)?
4) When is communication horizontal and when is communication vertical(based on the ISO / OSI model)?
5) Why does the number of layer-specific user data increase in each additional layer, starting from the application layer in the direction of the physical layer?
6) What is the difference between the OSI model, TCP-IP model and the middleware model (https://de.wikipedia.org/wiki/Middleware)?
Why are there 3 different models for the same?
When to use which model?
I have a few questions about computer networks.
Can you please help me to answer them?
Thank you.
1) What is the difference between an Ethernet header, Ethernet packet, Ethernet frame and Ethernet protocol?
2) Why is horizontal communication possible at all? There is no horizontal connection between the end devices (based on the ISO / OSI model)
3) What are examples of horizontal and vertical communication(based on the ISO / OSI model)?
4) When is communication horizontal and when is communication vertical(based on the ISO / OSI model)?
5) Why does the number of layer-specific user data increase in each additional layer, starting from the application layer in the direction of the physical layer?
6) What is the difference between the OSI model, TCP-IP model and the middleware model (https://de.wikipedia.org/wiki/Middleware)?
Why are there 3 different models for the same?
When to use which model?
The OSI model is the theoretical standard from which all others are supposed to flow.
In fact no networking stacks actually use it, or come anywhere near to implementing it. It demonstrates the difference between what capital-C capital-S Computer Science envisions, and what is practical out in the field. One might even say it is a relic, as it has implicit assumptions which are no longer valid -- e.g., that the hardware level is dumb. This is no longer the case when interface chips implementing the TCP and UDP protocols are readily available.
It's illustrative, but in practical networks layers overlap and are combined, and there is no clear division.
It's what happens when a standards committee is formed of people who have lots of theory and no practical experience.
"The OSI model is still used as a reference for teaching and documentation;[16] however, the OSI protocols originally conceived for the model did not gain popularity." -- Wikipedia
In fact no networking stacks actually use it, or come anywhere near to implementing it. It demonstrates the difference between what capital-C capital-S Computer Science envisions, and what is practical out in the field. One might even say it is a relic, as it has implicit assumptions which are no longer valid -- e.g., that the hardware level is dumb. This is no longer the case when interface chips implementing the TCP and UDP protocols are readily available.
It's illustrative, but in practical networks layers overlap and are combined, and there is no clear division.
It's what happens when a standards committee is formed of people who have lots of theory and no practical experience.
"The OSI model is still used as a reference for teaching and documentation;[16] however, the OSI protocols originally conceived for the model did not gain popularity." -- Wikipedia
ASKER
I am still interested in having my questions answered.
Thank you very much.
Thank you very much.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
An Ethernet packet is the entire "block" of a single transmission. The start of it is the Ethernet header. The actual data follows.
Ethernet protocol is the set of standards about how Ethernet "works".
5) Why does the number of layer-specific user data increase in each additional layer, starting from the application layer in the direction of the physical layer?
That's just a standard about how we talk about these layers.