A publish-subscribe architecture for the Constrained Application Protocol (CoAP)
draft-ietf-core-coap-pubsub-18
| Document | Type |
Expired Internet-Draft
(core WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jaime Jimenez , Michael Koster , Ari Keränen | ||
| Last updated | 2025-09-01 (Latest revision 2025-02-28) | ||
| Replaces | draft-koster-core-coap-pubsub | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources |
Sample implementation
Working Group Repo Mailing list discussion |
||
| Stream | WG state | Waiting for WG Chair Go-Ahead | |
| Associated WG milestone |
|
||
| Document shepherd | Esko Dijk | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Yes | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | esko.dijk@iotconsultancy.nl |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes a publish-subscribe architecture for the Constrained Application Protocol (CoAP), extending the capabilities of CoAP communications for supporting endpoints with long breaks in connectivity and/or up-time. CoAP clients publish on and subscribe to a topic via a corresponding topic resource at a CoAP server acting as broker.
Authors
Jaime Jimenez
Michael Koster
Ari Keränen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)