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.

CoAP

IoT & mediaIntermediate

Retrieve a constrained sensor resource with a confirmable request.

SIMULATION01 / 03
Loading topology…
0.0s / 2.8s
01
STEP 1 OF 3Client → Server / peer

CON GET /temperature

A confirmable request uses Message ID for duplicate detection and Token for request matching.

#TIMESOURCE → DESTINATIONMESSAGE
0.000192.0.2.10198.51.100.20CON GET /temperature
1.400198.51.100.20192.0.2.10ACK 2.05 Content
2.800192.0.2.10198.51.100.20Next CON GET

Retrieve a constrained sensor resource with a confirmable request.

Explain CON GET /temperature and distinguish it from Next CON GET.

Prerequisites: UDP

Ready to test your understanding?

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

Learn from the sourceRFC 7252Protocol guide

CoAP: protocol guide / panduan protokol

Retrieve a constrained sensor resource with a confirmable request.

Ambil resource sensor terbatas melalui request confirmable.

Communication walkthrough / Alur komunikasi

  1. CON GET /temperature

    A confirmable request uses Message ID for duplicate detection and Token for request matching.

    Request confirmable memakai Message ID untuk deteksi duplikat dan Token untuk pencocokan.

  2. ACK 2.05 Content

    A piggybacked response acknowledges the request and returns content.

    Respons piggyback mengakui request sekaligus mengirim isi.

  3. Next CON GET

    A new request uses a new Message ID; CoAP normally uses UDP port 5683.

    Request baru memakai Message ID baru; CoAP umumnya memakai port UDP 5683.

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 7252 ↗