1 / 22

T CP Connection Management

T CP Connection Management. Created by M Bateman, A Ruddle & C Allison As part of the TCP View project. C onnections. Both sender an receiver must be ready before start of data transfer Sender and receiver need to agree on parameters Receive buffer size, initial sliding window variables

tave
Download Presentation

T CP Connection Management

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. TCP Connection Management Created by M Bateman, A Ruddle & C Allison As part of the TCP View project

  2. Connections • Both sender an receiver must be ready before start of data transfer • Sender and receiver need to agree on parameters • Receive buffer size, initial sliding window variables • Sender and receiver must agree when transfer is over • Both sides must discard state • This is signalling • Setup/teardown state at the endpoints • Compare to ‘dialing’ in the telephone network

  3. Connection Management • Setup • 3-way handshake • Transfer • Sliding window, data and ACKs in both directions • Teardown • 4-way handshake • Client-server model • Initiator (client) server • Listener (server) responds, provides service

  4. Connection Creation

  5. Connection Creation

  6. Connection Creation

  7. Connection Creation

  8. Data Transfer • Connection is bi-directional • ACKs can carry data

  9. Connection Teardown

  10. Connection Teardown

  11. Connection Teardown

  12. Connection Teardown

  13. Connection Teardown

  14. The TIME_WAIT State • We wait 2 * maximum segment lifetime (60 seconds) before completing the close • Why? • ACK might have been lost so FIN would be resent • Could interfere with subsequent connections

  15. ‘Two-Army’ Problem • Can we use messages and retries to synchronise two machines so they are guaranteed to do some operation at the same time?

  16. Two-Army Problem

  17. Two-Army Problem

  18. Two-Army Problem

  19. Two-Army Problem

  20. Two-Army Problem

More Related