FREE & OPEN
THE OPEN PROTOCOL PLAYGROUND

Make every packet make sense.

Explore the conversations that connect our world. One packet at a time.

66 protocolsZero paywalls. Endless curiosity.

DTLS

Security & VPNAdvanced

Secure datagrams while handling handshake loss.

SIMULATION01 / 04
Loading topology…
0.0s / 4.2s
01
STEP 1 OF 4Client → Server / peer

ClientHello

DTLS 1.3 adapts TLS to datagrams without creating a reliable application byte stream.

#TIMESOURCE → DESTINATIONMESSAGE
0.000192.0.2.10198.51.100.20ClientHello
1.400198.51.100.20192.0.2.10HelloRetryRequest cookie
2.800192.0.2.10198.51.100.20ClientHello with cookie
4.200198.51.100.20192.0.2.10Handshake flight

Secure datagrams while handling handshake loss.

Explain ClientHello and distinguish it from Handshake flight.

Prerequisites: UDP

Ready to test your understanding?

Rebuild the exchange. Read the fields. Find the mistakes.

Learn from the sourceRFC 9147Protocol guide

DTLS: protocol guide / panduan protokol

Secure datagrams while handling handshake loss.

Amankan datagram sambil menangani kehilangan handshake.

Communication walkthrough / Alur komunikasi

  1. ClientHello

    DTLS 1.3 adapts TLS to datagrams without creating a reliable application byte stream.

    DTLS 1.3 mengadaptasi TLS ke datagram tanpa membuat aliran byte aplikasi andal.

  2. HelloRetryRequest cookie

    A server may request a cookie to validate the sender before expensive work.

    Server dapat meminta cookie untuk memvalidasi pengirim sebelum pekerjaan mahal.

  3. ClientHello with cookie

    The client repeats its hello with the requested cookie.

    Klien mengulang hello dengan cookie yang diminta.

  4. Handshake flight

    Acknowledgements and retransmissions support handshake reliability; details are condensed.

    Acknowledgement dan retransmisi mendukung keandalan handshake; detail diringkas.

Source and simulation scope

This is a simplified, deterministic teaching scenario. Timing is illustrative. Messages grouped within one event are explicitly condensed. Hexadecimal fixtures, where shown, contain only the indicated protocol ADU, not a full network capture. No PCAP files are supplied.

RFC 9147 ↗