1 / 26

CS640: Introduction to Computer Networks

CS640: Introduction to Computer Networks. Aditya Akella Lecture 15 TCP – II - Connection Set-up and Congestion Control. TCP Packet. Reliable, In-order, Connection oriented, Byte stream abstraction. Source port. Destination port. Sequence number.

jenette-bailey
Télécharger la présentation

CS640: Introduction to Computer Networks

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CS640: Introduction to Computer Networks Aditya Akella Lecture 15 TCP – II - Connection Set-up and Congestion Control

  2. TCP Packet Reliable, In-order, Connection oriented, Byte stream abstraction Source port Destination port Sequence number Flags from MSBto LSB: Acknowledgement URG ACK PSH RST SYN FIN HdrLen Advertised window Flags 0 Checksum Urgent pointer Options (variable) Data

  3. Sequence and Acknowledge Numbers • Sequence number  byte num of first byte in payload • Acknowledgement number • TCP is full duplex • Sequence number of next byte expected in reverse direction

  4. Advertised Window • Used for “flow control” • Different from “congestion control”, which we will see in second half of today’s lecture • Both sender and receiver advertise window • Sender action: lastSent – lastACK <= Receiver’s advertised window

  5. Establishing Connection:Three-Way handshake • Each side notifies other of starting sequence number it will use for sending • Why not simply chose 0? • Must avoid overlap with earlier incarnation • Security issues • Each side acknowledges other’s sequence number • SYN-ACK: Acknowledge sequence number + 1 • Can combine second SYN with first ACK SYN: SeqC ACK: SeqC+1 SYN: SeqS ACK: SeqS+1 Client Server

  6. Tearing Down Connection • Either side can initiate tear down • Send FIN signal • “I’m not going to send any more data” • Other side can continue sending data • Half open connection • Must continue to acknowledge • Acknowledging FIN • Acknowledge last sequence number + 1 Client Server FIN, SeqA ACK, SeqA+1 Data ACK FIN, SeqB ACK, SeqB+1

  7. Client Server TCP State Diagram: Connection Setup CLOSED active OPEN create TCB Snd SYN passive OPEN create TCB LISTEN rcv SYN SYN RCVD SYN SENT snd SYN ACK Rcv SYN, ACK rcv ACK of SYN Snd ACK CLOSE ESTAB Send FIN

  8. Active Close Passive Close State Diagram: Connection Tear-down ESTAB CLOSE rcv FIN send FIN send ACK FIN WAIT-1 CLOSE WAIT rcv FIN CLOSE snd ACK rcv ACK snd FIN rcv FIN+ACK FIN WAIT-2 CLOSING LAST-ACK snd ACK rcv ACK of FIN rcv ACK of FIN TIME WAIT CLOSED rcv FIN Timeout=2msl snd ACK delete TCB

  9. Congestion • Different sources compete for resources inside network • Why is it a problem? • Sources are unaware of current state of resource • Sources are unaware of each other • Manifestations: • Lost packets (buffer overflow at routers) • Long delays (queuing in router buffers) • Can result in effective throughput less than bottleneck link (1.5Mbps for the above topology)  a.k.a. congestion collapse 10 Mbps 1.5 Mbps 100 Mbps

  10. Four senders – multihop paths Timeout/retransmit Q:What happens as rate increases? Causes & Costs of Congestion

  11. Causes & Costs of Congestion • When packet dropped, any upstream transmission capacity used for that packet was wasted!

  12. Congestion “Collapse” • Definition: Unchecked Increase in network load results in decrease of useful work done • Fewer and fewer useful packets carried in network • Many possible causes • Spurious retransmissions of packets still in flight • Classical congestion collapse • Undelivered packets • Packets consume resources and are dropped elsewhere in network

  13. Congestion Control and Avoidance • A mechanism which: • Uses network resources efficiently • Preserves fair network resource allocation • Controls or Avoids congestion

  14. End-end congestion control: No explicit feedback from network Congestion inferred from end-system observed loss, delay Approach taken by TCP Problem: approximate, possibly inaccurate Network-assisted congestion control: Routers provide feedback to end systems Single bit indicating congestion (SNA, DECbit, TCP/IP ECN, ATM) Explicit rate sender should send at Problem: makes routers complicated Approaches Towards Congestion Control • Two broad approaches towards congestion control:

  15. End-End Congestion Control • So far: TCP sender limited by available buffer size at receiver • Receiver flow control • “receive window” or “advertised window” • To accommodate network constraints, sender maintains a “congestion window” • Reflects dynamic state of the network • Max outstanding packets ≤ min {congestion window, advertised window} • When receiver window is very large, congestion window determines how fast sender can send • Speed = CWND/RTT (roughly)

  16. TCP Congestion Control • Very simple mechanisms in network • FIFO scheduling with shared buffer pool • Feedback through packet drops • End-host TCP interprets drops as signs of congestion and slows down  reduces size of congestion window • But then, periodically probes – or increases congestion window • To check whether more bandwidth has become available

  17. Congestion Control Objectives • Simple router behavior • Distributed-ness • Efficiency: Sxi(t) close to system capacity • Fairness: equal (or propotional) allocation • Metric = (Sxi)2/n(Sxi2) • Convergence: control system must be stable

  18. Linear Control • Many different possibilities for reaction to congestion and probing • Examine simple linear controls • Window(t + 1) = a + b Window(t) • Different ai/bi for increase and ad/bd for decrease • Various reaction to signals possible • Increase/decrease additively • Increased/decrease multiplicatively • Which of the four combinations is optimal? • Consider two end hosts vying for network bandwidth

  19. Additive Increase/Decrease • Both X1 and X2 increase/ decrease by the same amount over time • Additive increase improves fairness and additive decrease reduces fairness Fairness Line T1 User 2’s Allocation x2 T0 Efficiency Line User 1’s Allocation x1

  20. Multiplicative Increase/Decrease • Both X1 and X2 increase by the same factor over time • Extension from origin – constant fairness Fairness Line T1 User 2’s Allocation x2 T0 Efficiency Line User 1’s Allocation x1

  21. Convergence to Efficiency Fairness Line xH User 2’s Allocation x2 Efficiency Line User 1’s Allocation x1

  22. Distributed Convergence to Efficiency a>0 & b>1 a=0 b=1 Fairness Line a<0 & b>1 xH a>0 & b<1 User 2’s Allocation x2 a<0 & b<1 Efficiency Line User 1’s Allocation x1

  23. Convergence to Fairness Fairness Line xH User 2’s Allocation x2 xH’ Efficiency Line User 1’s Allocation x1

  24. Convergence to Efficiency & Fairness • Intersection of valid regions • For decrease: a=0 & b < 1 Fairness Line xH User 2’s Allocation x2 xH’ Efficiency Line User 1’s Allocation x1

  25. What is the Right Choice? • Constraints limit us to AIMD • Can have multiplicative term in increase(MAIMD) • AIMD moves towards optimal point Fairness Line x1 x0 User 2’s Allocation x2 x2 Efficiency Line User 1’s Allocation x1

  26. Summary • Significance of fields in TCP packet • TCP is full duplex • Data can go in either direction • TCP connection set-up – three-way hand-shake • Also, teardown • Costs of congestion • Delay, loss, useless work… • Cure: congestion control • TCP uses AIMD congestion control

More Related