TCP handshake process is a separate topic, so we are not covering that in this article. In HTTPS, a TLS handshake will happen after the completion of a successful TCP handshake. Whereas in TLS 1.3 it’s been reduced to 200ms. According to IETF (Internet Engineering Task Force), TLS 1.2 average time to complete the handshake process is 300ms. This shortened handshake process lets the exchange of application data to began in the way faster than older versions of TLS protocols. Reduced round trip to complete the handshake process: Another big factor seen in this revision is a reduction in the time of the handshake process by reducing the back and forth messages between the Client and the Server.In TLS 1.3 everything after the server hello packet is encrypted. Security: As we said earlier, in this revision most of the messages were encrypted including the server certificate unlike in TLS 1.2.There are two main factors that made this version superior:

We should require programs like OpenSSL or Wireshark to decode TLS 1.3 protocol handshake process. We can’t use tcpdump to see the message exchange. In TLS 1.3 everything after the server hello packet is encrypted including certificate exchange. So tcpdump is not enough to examine the TLS 1.3 protocol handshake. Because most of the handshake process is encrypted in this revision. Decoding TLS 1.3 protocol handshake is not as simple as decoding TLS 1.2. It’s worth understanding the new TLS 1.3 protocol as TLS has seen a significant change in version 1.3 compared to its predecessors. But, many people don’t know much about it. TLS 1.3 the most latest version of TLS protocol is now two years old.

Wireshark certificate details