A Constrained Application Protocol (CoAP) Usage for REsource LOcation And Discovery (RELOAD)
RFC 7650
| Document | Type |
RFC - Proposed Standard
(September 2015; No errata)
Was draft-jimenez-p2psip-coap-reload (individual in rai area)
|
|
|---|---|---|---|
| Authors | Jaime Jimenez , Jose Lopez-Vega , Jouni Maenpaa , Gonzalo Camarillo | ||
| Last updated | 2015-10-14 | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | (None) | |
| Document shepherd | Carlos Bernardos | ||
| Shepherd write-up | Show (last changed 2015-02-04) | ||
| IESG | IESG state | RFC 7650 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Ben Campbell | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) J. Jimenez
Request for Comments: 7650 Ericsson
Category: Standards Track J. Lopez-Vega
ISSN: 2070-1721 University of Granada
J. Maenpaa
G. Camarillo
Ericsson
September 2015
A Constrained Application Protocol (CoAP) Usage
for REsource LOcation And Discovery (RELOAD)
Abstract
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7650.
Jimenez, et al. Standards Track [Page 1]
RFC 7650 A CoAP Usage for RELOAD September 2015
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Architecture . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Registering CoAP URIs . . . . . . . . . . . . . . . . . . . . 7
5. Lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
6. Forming a Direct Connection and Reading Data . . . . . . . . 9
7. Caching Mechanisms . . . . . . . . . . . . . . . . . . . . . 11
7.1. ProxyCache . . . . . . . . . . . . . . . . . . . . . . . 11
7.2. SensorCache . . . . . . . . . . . . . . . . . . . . . . . 13
8. CoAP Usage Kinds Definition . . . . . . . . . . . . . . . . . 14
8.1. CoAP-REGISTRATION Kind . . . . . . . . . . . . . . . . . 14
8.2. CoAP-CACHING Kind . . . . . . . . . . . . . . . . . . . . 15
9. Access Control Rules . . . . . . . . . . . . . . . . . . . . 15
10. Security Considerations . . . . . . . . . . . . . . . . . . . 16
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
11.1. CoAP-REGISTRATION Kind-ID . . . . . . . . . . . . . . . 17
11.2. CoAP-CACHING Kind-ID . . . . . . . . . . . . . . . . . . 17
11.3. Access Control Policies . . . . . . . . . . . . . . . . 17
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
12.1. Normative References . . . . . . . . . . . . . . . . . . 18
12.2. Informative References . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
Jimenez, et al. Standards Track [Page 2]
RFC 7650 A CoAP Usage for RELOAD September 2015
1. Introduction
The Constrained Application Protocol (CoAP) Usage for REsource
LOcation And Discovery (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.
Show full document text