What is a TCP connection termination?
TCP is an example of a connection-oriented protocol in computer networks. In another tutorial for the TCP three-way handshake, we have shown the connection setup procedure. In this tutorial, we are describing the connection termination procedure in detail with examples.
The first thing comes to mind why there is a procedure for connection termination? A communicating entity can just stop sending data and inform the other side about the connection termination? Yes this is possible, but TCP is a reliable protocol (reliable means no message loss at any stage), so requires a protocol procedure to terminate the connection with no message loss.
A TCP connection is a pair of unidirectional streams, one stream in each direction. E.g if hosts A and B have a TCP connection in between, one stream is from A to B and the other stream is from B to A. Each side of the stream should be closed gracefully. Let’s try to understand the need for a connection termination procedure in layman’s terms.
How does a connection terminate? With example –
TCP connection termination
Suppose two-person talking to each other over the phone. The voice flowing in each direction. Now before ending the call, each person makes sure that all spoken words are conveyed to another person. A final bye statement is used. In TCP it is similar, a sender says to the receiver that, I have no more data to send and request to close the stream.
- At the protocol level, this is conveyed in the TCP FIN packet.
- Upon receiving a close request from the TCP user. TCP layer stops sending new packets and waits for the pending TCP acks. Once all pending packets are transmitted successfully, the sender sends the TCP FIN to the receiver.
- Now the other ends do the same.
In the following sections, we will see, how a protocol flow achieves TCP connection termination.
There are two packets TCP FIN and TCP FIN ACK are used for connection termination. Here we will discuss each packet in detail.
TCP FIN and TCP Fin Ack packets:
The sender sends TCP FIN to the receiver for an outgoing stream. The packet has a FIN flag set as another type of TCP message. The packet has a sequence number, the receiver sends the FIN Ack with one more sequence number received in the FIN. Now the connection is closed in one direction. At this stage, the application is informed about the close of the connection.
For another direction, a new fin is sent with a sequence number. The receiving side sends the fin ack and the connection is closed in both directions.
TCP Connection reset (RST, RST Ack)
Above we have discussed the graceful TCP connection termination. But there are situations in which the connection needs to be close or reset immediately. This may be because of system errors or protocol errors.
For example, a TCP end receives a packet for which there is no connection. The receiving side will send a TCP RST to the remote, to close the connection and again setup if requires. The other ends send the TCP RST Ack. In contrast to the FIN, RST and RST Ack closes the connection in both directions immediately. The TCP user application is also informed about the reset so that the application is aware that there can be packet loss and will take action accordingly.
TCP connection termination or reset indication to the TCP user:
Till now we have discussed all protocol messages, but nothing completes without discussing the events handling in the user application. Whenever there is connection termination or reset, the application gets an indication for the event. But How? We will discuss the exact code for the C program for TCP sockets. Here will be just mentioning a way to detect the event.
In socket programming, the server blocks on
recv() system call to read the TCP message from the client. Upon a message from the client,
recv( ) return the number of bytes read. If it returns the zero, means the connection is terminated by the peer with a FIN and FIN Ack. For connection terminated by RST and RST-Ack,
recv system call, return -1, and the
errno is set to 104. In both cases, the connection is closed, but the application gets the reason and can take action accordingly.