Flow Control.ppt

Flow Control TCP Flow Control receiver: explicitly informs sender of (dynamically changing) amount of free buffer space RcvWindow field in TCP segment sender: keeps the amount of transmitted, unACKed data less than most recently received RcvWindow TCP: setting timeouts TCP Round Trip Time and Timeout Q: how to set TCP timeout value? longer than RTT note: RTT will vary too short: premature timeout unnecessary retransmissions too long: slow reaction to segment loss Q: how to estimate RTT? SampleRTT: measured time from segment transmission until ACK receipt ignore retransmissions, cumulatively ACKed segments SampleRTT will vary, want estimated RTT “smoother” use several recent measurements, not just current SampleRTT TCP Round Trip Time and Timeout Setting the timeout EstimtedRTT plus “safety margin” large variation in EstimatedRTT - larger safety margin Fast retransmit Congestion Control Principles of Congestion Control Congestion: informally: “too many sources sending too much data too fast for network to handle” manifestations: lost packets (buffer overflow at routers) long delays (queuing in router buffers) a highly important problem! Causes/costs of congestion: scenario 1 two senders, two receivers one router, infinite buffers no retransmission Causes/costs of congestion: scenario 1 Throughput increases with load Maximum total load C (Each session C/2) Large delays when congested The load is stochastic Causes/costs of congestion: scenario 2 one router, finite buffers sender retransmission of lost packet Causes/costs of congestion: scenario 2 always: (goodput) Like to maximize goodput! “perfect” retransmission: retransmit only when loss: Actual retransmission of delayed (not lost) packet makes larger (than perfect case) for same Causes/costs of congestion: scenario 2 Causes/costs of congestion: scenario 3 four senders multihop paths timeout/retransmit Causes/costs of congestion: scenario 3 Approaches towards congestion con