metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 7641: Observing Resources in the Constrained Application Protocol (CoAP)

Still current, but amended. Parts of this document are changed or extended by RFC 8323. Read both.

In plain English — editorial summary, not part of the RFC

The Constrained Application Protocol (CoAP) is a RESTful application protocol for constrained nodes and networks. The state of a resource on a CoAP server can change over time. This document specifies a simple protocol extension for CoAP that enables CoAP clients to "observe" resources, i.e., to retrieve a representation of a resource and keep this representation updated by the server over a period of time. The protocol follows a best-effort approach for sending new representations to clients and provides eventual consistency between the state observed by each client and the actual resource state at the server.

Document record

Document ID
RFC7641
Published
September 2015
Authors
K. Hartke
Status
PROPOSED STANDARD
Stream
IETF
Area
wit
Pages
30
Also known as
—
Updated by:
RFC 8323

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/7641-observing-resources-in-the-constrained-application-protocol-coap