Code Components extracted from this document must
Please review these documentsĬarefully, as they describe your rights and restrictions with respect This document is subject to BCP 78 and the IETF Trust's Legal
RFC 7641 Observing Resources in CoAP September 2015Ĭopyright (c) 2015 IETF Trust and the persons identified as the
Qbserve extension how to#
Information about the current status of this document, any errata,Īnd how to provide feedback on it may be obtained at Internet Standards is available in Section 2 of RFC 5741. Internet Engineering Steering Group (IESG). Received public review and has been approved for publication by the It represents the consensus of the IETF community. This document is a product of the Internet Engineering Task Force This is an Internet Standards Track document. The state observed by each client and the actual resource state at Representations to clients and provides eventual consistency between The protocol follows a best-effort approach for sending new "observe" resources, i.e., to retrieve a representation of a resourceĪnd keep this representation updated by the server over a period of Simple protocol extension for CoAP that enables CoAP clients to Protocol for constrained nodes and networks. The Constrained Application Protocol (CoAP) is a RESTful application Observing Resources in the Constrained Application Protocol (CoAP) Request for Comments: 7641 Universitaet Bremen TZI Updated by: 8323 Internet Engineering Task Force (IETF) K. RFC 7641: Observing Resources in the Constrained Application Protocol (CoAP)
0 kommentar(er)
