UniPro protocol stack: Difference between revisions

Content deleted Content added
VdHamer (talk | contribs)
m L4 features: editorial
VdHamer (talk | contribs)
m L4 connection and flow control: added link for TCP
Line 315:
In UniPro 1.0/1.1 connection setup is assumed to be relatively static (states of both connected CPorts aligned by the rspective UniPro devices). In a later version, this will be be replaced by a conventional (dynamic) connection management protocol.
 
CPorts also contain variables (state) used to track how much buffer space the peer CPort at the other end of the link has. This is used to prevent the situation whereby a CPort sends segments to a CPort which it cannot store, thus leading to a traffic jam that starts at the destination and a rapidly moves towards the data source, congesting the network for other users as well. This mechanism at L4 is known as end-to-end flow control because it involves the endpoints of a connection regulating their mutual traffic. This makes L4 flow control complementary to L2 flow control. The latter is less fine grained (no distinction between connections) and serves to avoid data loss rather than avoid congestion on the network. Internet's equivalent, the [[Transmission_Control_Protocol|TCP]] protocol, has a similar congestion management feature, although it works very differently.
 
===L4 and Messages===