← Back to the chapter

Technical detail · CoAP Exchange Reliability Contracts

Pending responses, NSTART and reachability

In CoAP, a delayed operation can receive an empty acknowledgement first and return its result later in a separate message.

A Message ID identifies a message for duplicate handling and connects an acknowledgement to that message. A Token is the request-response matching value; it connects the later result to the original request in that peer’s context. Reusing the Token does not turn the later result into the original message.

NSTART limits outstanding interactions with a peer and defaults to 1. A request counts as outstanding while neither its response nor its acknowledgement has arrived. An empty acknowledgement ends that outstanding interaction for NSTART, while its separate response remains pending. A CoAP ping sends an empty confirmable message (CON), which requests acknowledgement, and expects Reset (RST), which reports missing message context; it checks peer reachability, not physical state.

← Back to the chapter