CoAP: Non-traditional response forms

Document Type Expired Internet-Draft (individual)
Author Carsten Bormann 
Last updated 2018-05-16 (latest revision 2017-11-12)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


In CoAP as defined by RFC 7252, responses are always unicast back to a client that posed a request. The present memo describes two forms of responses that go beyond that model. These descriptions are not intended as advocacy for adopting these approaches immediately, they are provided to point out potential avenues for development that would have to be carefully evaluated.


Carsten Bormann (

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