Observing Resources in the Constrained Application Protocol
RFC 7641, “Observing Resources in the Constrained Application Protocol”, is a Proposed Standard document published in September 2015 by K. Hartke. It has since been updated by RFC 8323. The canonical text is published by the RFC Editor.
Abstract
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 7641 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7640 Traffic Management Benchmarking
- RFC 7642 System for Cross-domain Identity Management: Definitions, Overview, Concepts, and Requirements
- RFC 7639 The ALPN HTTP Header Field
- RFC 7643 System for Cross-domain Identity Management: Core Schema
- RFC 7638 JSON Web Key Thumbprint
- RFC 7644 System for Cross-domain Identity Management: Protocol
- RFC 7637 NVGRE: Network Virtualization Using Generic Routing Encapsulation
- RFC 7645 The Keying and Authentication for Routing Protocol IS-IS Security Analysis