Transport Layer Of OSI Model Working Functionalities and Protocols (A Beginner’s Guide) vpskotru, vpsdedicru
Ethical Hacking Training Institute in Pune-India
Extreme Hacking | Sadik Shaikh | Cyber Suraksha Abhiyan
As we talked earlier in the article OSI Model its 7 layers, the transport layer is responsible for the most of the functionalities out of all the OSI layers. So, let’s go further and take a look into what all basic things transport layer does and what all protocols are run at the transport layer.
In the internet world, the data packets are delivered in two fashions:
Let’s see these connection-oriented communications this way:
If you are driving from town A to town B and there is a lot of traffic then in that scenario, you would decide two things:
And, that’s what the functionalities of two type of connections at the transport layer do namely, TCP and UDP. TCP, before delivering a packet, decides the entire path before hand and the data packets are delivered via the same path for the entire connection.
Whereas, UDP just looks around and without a predefined path and delivers the packet. However, the difference between UDP and TCP is:
Let’s understand same order delivery this way.
One day, we decide to make chicken Biriyani. We buy everything, like chicken, spices, rice, oil but we forget salt, insignificant yet very important ingredient.
So, would you be able to prepare Biriyani without the salt? I don’t think so. Because you will have to wait for salt to arrive. And that’s what the transport layer takes care of.
It makes sure that all the packets, chunk by chunk, arrive in order to your computer. Imagine, you just get the footer of the mail without any Body. How would that be like? That would look really bad. Right? In computer networks term, this will also be called as head of line blocking.
Transport layer makes sure of reliability. What would happen if some of the data packets do not arrive due to network congestion? In those situations, the transport layer uses Automatic repeat request (ARQ) schemes to retransmit the lost or corrupted data.
As previously discussed in the data link layer, the rate of data transmission between two nodes must sometimes be managed to prevent a fast sender from transmitting more data than can be supported by the receiving data buffer, causing a buffer overrun. This can also be used to improve efficiency by reducing buffer underrun.
Now a computer has all the data and how should it send all? All at once? Part by part? Then in what proportion? Well, sometimes the transport layer in the case of high congestion, starts with a slow start. That means it sends one packet, then two, then four, then eight and it keeps on increasing data packets until it finds a threshold at which a congestion is experienced.
You might not be aware of Natting but think Natting as this way:
There was a pool of IP addresses and over the time, all the IP addresses were taken by some or others. But computers and network devices kept on growing. So how to address that problem?
In that situation, private IP addresses came into existence which is more like privately naming your computers inside an area and when the data packets go of the area, it will represent the area in terms of a public IP address.
Cyber Suraksha Abhiyan , CEHv9 , CHFI , ECSAv9 , CAST , ENSA , CCNA , CCNA SECURITY , MCITP , RHCE , CHECKPOINT , ASA FIREWALL , VMWARE , CLOUD , ANDROID , IPHONE , NETWORKING HARDWARE , TRAINING INSTITUTE IN PUNE , Certified Ethical Hacking , Center For Advanced Security Training in India , ceh v9 course in Pune-India , ceh certification in pune-India , ceh v9 training in Pune-India , Ethical Hacking Course in Pune-India