UniPro protocol stack: Difference between revisions

Content deleted Content added
ALasry (talk | contribs)
L4 connections: upgrade to v1.4
ALasry (talk | contribs)
m L4 flow control: re-wording
Line 336:
 
===L4 flow control===
CPorts also contain variables (state) variables that can be used to track how much buffer space the peer or connected CPort has. This is used to prevent the situation whereby a CPort sends segments to a CPort which has insufficient buffer space to hold the data, thus leading to stalled data traffic. Unless resolved fast, this traffic jam at the destination quickly grows into a network-wide gridlock. This is highly undesirable as it can greatly affect network performance for all users or, worse, can lead to deadlock situations. The described L4 mechanism is known as end-to-end flow control (E2E FC) because it involves the endpoints of a connection.
 
===L4 flow control versus L2 flow control===