REST/CoAP request-response model incompatible with IoT sleepy devices

7/10 High

REST-based IoT protocols (CoAP, Thread) require both client and server online simultaneously, incompatible with sleepy IoT devices. Resource discovery via DNS/multicast adds overhead.

CoAPRESTThreadMatter
Category
architecture
Workaround
partial
Stage
build
Freshness
persistent
Scope
framework
Upstream
open
Recurring
Yes
Buyer Type
team

Sources

Collection History

Query: “What are the most common pain points with TCP/IP for developers in 2025?”4/9/2026

Many IoT applications implement a resource-oriented request-response communication model... It usually requires resource discovery, such as DNS or Core-RD which in turn uses broadcast. It requires that the client (requester) and the server (resource) is online at the same time.

Created: 4/9/2026Updated: 4/9/2026