Skip to main content

Proxy Operations for CoAP Group Communication

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Marco Tiloca , Esko Dijk
Last updated 2023-08-31
Replaced by draft-ietf-core-groupcomm-proxy
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-core-groupcomm-proxy
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


This document specifies the operations performed by a proxy, when using the Constrained Application Protocol (CoAP) in group communication scenarios. Such a proxy processes a single request sent by a client over unicast, and distributes the request over IP multicast to a group of servers. Then, the proxy collects the individual responses from those servers and relays those responses back to the client, in a way that allows the client to distinguish the responses and their origin servers through embedded addressing information. This document updates RFC7252 with respect to caching of response messages at proxies.


Marco Tiloca
Esko Dijk

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)