RFC 7650: A Constrained Application Protocol (CoAP) Usage for REsource LOcation And Discovery (RELOAD)
In plain English — editorial summary, not part of the RFC
This document defines a Constrained Application Protocol (CoAP) Usage for REsource LOcation And Discovery (RELOAD). The CoAP Usage provides the functionality to federate Wireless Sensor Networks (WSNs) in a peer-to-peer fashion. The CoAP Usage for RELOAD allows CoAP nodes to store resources in a RELOAD peer-to-peer overlay, provides a lookup service, and enables the use of RELOAD overlay as a cache for sensor data. This functionality is implemented in the RELOAD overlay itself, without the use of centralized servers. The RELOAD AppAttach method is used to establish a direct connection between nodes through which CoAP messages are exchanged.
Document record
- Document ID
- RFC7650
- Published
- September 2015
- Authors
- J. Jimenez; J. Lopez-Vega; J. Maenpaa; G. Camarillo
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7904A SIP Usage for REsource LOcation And Discovery (RELOAD)Current
October 2016
- RFC 7959Block-Wise Transfers in the Constrained Application Protocol (CoAP)Updated
August 2016
- RFC 8075Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP)Current
February 2017
- RFC 8132PATCH and FETCH Methods for the Constrained Application Protocol (CoAP)Current
April 2017
- RFC 8152CBOR Object Signing and Encryption (COSE)Obsoleted
July 2017
- RFC 8323CoAP (Constrained Application Protocol) over TCP, TLS, and WebSocketsUpdated
February 2018
- RFC 8352Energy-Efficient Features of Internet of Things ProtocolsCurrent
April 2018
- RFC 8387Practical Considerations and Implementation Experiences in Securing Smart Object NetworksCurrent
May 2018
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?