1 / 29

Transmission Control Protocol (TCP)

Transmission Control Protocol (TCP). reliable, in-order byte steam: no “message boundaries” send & receive buffers buffer incoming & outgoing data flow controlled: sender will not overwhelm receiver congestion controlled: sender will not overwhelm network. point-to-point (unicast):

dspell
Download Presentation

Transmission Control Protocol (TCP)

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. Transmission Control Protocol (TCP)

  2. reliable, in-order byte steam: no “message boundaries” send & receive buffers buffer incoming & outgoing data flow controlled: sender will not overwhelm receiver congestion controlled: sender will not overwhelm network point-to-point (unicast): one sender, one receiver connection-oriented: handshaking (exchange of control msgs) init’s sender, receiver state before data exchange State resides only at the END systems – Not a virtual circuit! full duplex data: bi-directional data flow in same connection (A->B & B->A in the same connection) MSS: maximum segment size TCP: Overview RFCs: 793, 1122, 1323, 2018, 2581

  3. 32 bits source port # dest port # sequence number acknowledgement number head len not used Receive window U A P R S F checksum Urg data pnter Options (variable length) application data (variable length) TCP segment structure URG: urgent data (generally not used) counting by bytes of data (not segments!) ACK: ACK # valid PSH: push data now (generally not used) # bytes rcvr willing to accept RST, SYN, FIN: connection estab (setup, teardown commands) Internet checksum (as in UDP)

  4. TCP socket identified by 4-tuple: source IP address source port number dest IP address dest port number receiving host uses all four values to direct segment to appropriate socket TCP Connection-oriented demux

  5. P P P1 P P SP: 5775 SP: 80 SP: 80 DP: 9157 DP: 80 DP: 5775 TCP Demultiplexing Example SP: 9157 client IP: A Client IP:B server IP: C DP: 80

  6. A TCP Transaction consists of 3 Phases Connection Establishment Handshaking between client and server Reliable, In-Order Data Exchange Recover any lost data through retransmissions and ACKs Connection Termination Closing the connection time time Typical TCP Transaction Server Client Connection Establishment Reliable, In-Order Data Exchange Connection Termination

  7. TCP sender, receiver establish “connection” before exchanging data segments initialize TCP variables: seq. #s buffers, flow control info (e.g. RcvWindow) client: connection initiator Socket clientSocket = new Socket("hostname", port#); server: contacted by client Socket connectionSocket = welcomeSocket.accept(); TCP Connection Establishment

  8. Three way handshake: Step 1:client host sends TCP SYN segment to server specifies a random initial seq # no data Step 2:server host receives SYN, replies with SYNACK segment server allocates buffers specifies server initial seq. # Step 3: client receives SYNACK, replies with ACK segment, which may contain data time time Connection Establishment (cont) Host B Host A Connection request SYN, Seq=42 host ACKs and selects its own initial seq # SYN+ACK, Seq=79, ACK=43 host ACKs ACK, Seq=43, ACK=80 Three-way handshake

  9. Seq. #’s: byte stream “number” of first byte in segment’s data ACKs: seq # of next byte expected from other side cumulative ACK time time Connection Establishment (cont) Host B Host A Connection request SYN, Seq=42 host ACKs and selects its own initial seq # SYN+ACK, Seq=79, ACK=43 host ACKs ACK, Seq=43, ACK=80 Three-way handshake

  10. TCP Starting Sequence Number Selection • Why a random starting sequence #? Why not simply choose 0? • To protect against two incarnations of the same connection reusing the same sequence numbers too soon • That is, while there is still a chance that a segment from an earlier incarnation of a connection will interfere with a later incarnation of the connection • How? • Client machine seq #0, initiates connection to server with seq #0. • Client sends one byte and client machine crashes • Client reboots and initiates connection again • Server thinks new incarnation is the same as old connection

  11. Closing a connection: client closes socket:clientSocket.close(); Step 1:client end system sends TCP FIN control segment to server Step 2:server receives FIN, replies with ACK. Server might send some buffered but not sent data before closing the connection. Server then sends FIN and moves to Closing state. TCP Connection Termination client server close FIN ACK Data write DATA ACK FIN close timed wait ACK closed

  12. Step 3:client receives FIN, replies with ACK. Enters “timed wait” - will respond with ACK to received FINs Step 4:server, receives ACK. Connection closed. Why wait before closing the connection? If the connection were allowed to move to CLOSED state, then another pair of application processes might come along and open the same connection (use the same port #s) and a delayed FIN from an earlier incarnation would terminate the connection. client server closing FIN ACK closing FIN ACK timed wait closed closed TCP Connection Termination

  13. CLOSED Active open /SYN Passive open Close Close LISTEN SYN/SYN + ACK Send/ SYN SYN/SYN + ACK SYN_RCVD SYN_SENT ACK SYN + ACK/ACK Close /FIN ESTABLISHED Close /FIN FIN/ACK FIN_WAIT_1 CLOSE_WAIT FIN/ACK ACK Close /FIN ACK + FIN/ACK FIN_WAIT_2 CLOSING LAST_ACK Timeout after two ACK ACK segment lifetimes FIN/ACK TIME_WAIT CLOSED TCP State-Transition Diagram

  14. Typical TCP Client/Server Transitions TCP server lifecycle TCP client lifecycle

  15. TCP UDP IP LL PL TCP UDP IP LL PL TCP UDP IP LL PL Socket Layer Socket Layer Socket Layer How to program using the TCP? • Socket Layer: • Programmer’s API to the protocol stack • Typical network app has two pieces: client and server • Server: Passive entity.Provides service to clients • e.g., Web server responds with the requested Web page • Client: initiates contact with server (“speaks first”) • typically requests service from server, e.g., Web Browser

  16. Socket Creation • mySock = socket(family, type, protocol); • UDP/TCP/IP-specific sockets • Socket reference • File (socket) descriptor in UNIX • Socket handle in WinSock

  17. Client Create a TCP socket Establish connection Communicate Close the connection Server Create a TCP socket Assign a port to socket Set socket to listen Repeatedly: Accept new connection Communicate Close the connection TCP Client/Server Interaction Server starts by getting ready to receive client connections…

  18. Client Create a TCP socket Establish connection Communicate Close the connection Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection TCP Client/Server Interaction /* Create socket for incoming connections */ if ((servSock = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP)) < 0) DieWithError("socket() failed");

  19. Client Create a TCP socket Establish connection Communicate Close the connection Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection TCP Client/Server Interaction echoServAddr.sin_family = AF_INET; /* Internet address family */ echoServAddr.sin_addr.s_addr = htonl(INADDR_ANY);/* Any incoming interface */ echoServAddr.sin_port = htons(echoServPort); /* Local port */ if (bind(servSock, (struct sockaddr *) &echoServAddr, sizeof(echoServAddr)) < 0) DieWithError("bind() failed");

  20. Client Create a TCP socket Establish connection Communicate Close the connection Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection TCP Client/Server Interaction /* Mark the socket so it will listen for incoming connections */ if (listen(servSock, MAXPENDING) < 0) DieWithError("listen() failed");

  21. Client Create a TCP socket Establish connection Communicate Close the connection Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection TCP Client/Server Interaction for (;;) /* Run forever */ { clntLen = sizeof(echoClntAddr); if ((clntSock=accept(servSock,(struct sockaddr *)&echoClntAddr,&clntLen)) < 0) DieWithError("accept() failed");

  22. Client Create a TCP socket Establish connection Communicate Close the connection Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection TCP Client/Server Interaction Server is now blocked waiting for connection from a client

  23. Client Create a TCP socket Establish connection Communicate Close the connection Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection TCP Client/Server Interaction Later, a client decides to talk to the server…

  24. Client Create a TCP socket Establish connection Communicate Close the connection Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection TCP Client/Server Interaction /* Create a reliable, stream socket using TCP */ if ((sock = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP)) < 0) DieWithError("socket() failed");

  25. Client Create a TCP socket Establish connection Communicate Close the connection Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection TCP Client/Server Interaction echoServAddr.sin_family = AF_INET; /* Internet address family */ echoServAddr.sin_addr.s_addr = inet_addr(servIP); /* Server IP address */ echoServAddr.sin_port = htons(echoServPort); /* Server port */ if (connect(sock, (struct sockaddr *) &echoServAddr, sizeof(echoServAddr)) < 0) DieWithError("connect() failed");

  26. Client Create a TCP socket Establish connection Communicate Close the connection Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection TCP Client/Server Interaction echoStringLen = strlen(echoString); /* Determine input length */ /* Send the string to the server */ if (send(sock, echoString, echoStringLen, 0) != echoStringLen) DieWithError("send() sent a different number of bytes than expected");

  27. Client Create a TCP socket Establish connection Communicate Close the connection Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection TCP Client/Server Interaction /* Receive message from client */ if ((recvMsgSize = recv(clntSocket, echoBuffer, RCVBUFSIZE, 0)) < 0) DieWithError("recv() failed");

  28. Client Create a TCP socket Establish connection Communicate Close the connection Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection TCP Client/Server Interaction close(sock); close(clntSocket)

  29. Client send(“Hello Bob”) recv() -> “Hi Jane” Server recv() -> “Hello ” recv() -> “Bob” send(“Hi ”) send(“Jane”) TCP Tidbits • Client knows server address and port • No correlation between send() and recv()

More Related