A Constrained Application Protocol (CoAP) Usage for REsource LOcation And Discovery (RELOAD)
draft-jimenez-p2psip-coap-reload-05

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-01-02
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
P2PSIP                                                        J. Jimenez
Internet-Draft                                                  Ericsson
Intended status: Standards Track                           J. Lopez-Vega
Expires: July 6, 2015                              University of Granada
                                                              J. Maenpaa
                                                            G. Camarillo
                                                                Ericsson
                                                         January 2, 2015

 A Constrained Application Protocol (CoAP) Usage for REsource LOcation
                         And Discovery (RELOAD)
                  draft-jimenez-p2psip-coap-reload-05

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 (WSN)
   in a peer-to-peer fashion.  The CoAP Usage also provides a rendezvous
   service for CoAP Nodes and caching of sensor information.  The RELOAD
   AppAttach method is used to establish a direct connection between
   nodes through which CoAP messages are exchanged.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 6, 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

Jimenez, et al.           Expires July 6, 2015                  [Page 1]
Internet-Draft           A CoAP Usage for RELOAD            January 2015

   (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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Architecture  . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Registering CoAP URIs . . . . . . . . . . . . . . . . . . . .   5
   5.  Rendezvous  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Forming a direct connection and reading data  . . . . . . . .   7
   7.  Caching Mechanisms  . . . . . . . . . . . . . . . . . . . . .   9
     7.1.  ProxyCache  . . . . . . . . . . . . . . . . . . . . . . .   9
     7.2.  SensorCache . . . . . . . . . . . . . . . . . . . . . . .  10
   8.  CoAP Usage Kinds Definition . . . . . . . . . . . . . . . . .  12
     8.1.  CoAP-REGISTRATION Kind  . . . . . . . . . . . . . . . . .  12
     8.2.  CoAP-CACHING Kind . . . . . . . . . . . . . . . . . . . .  12
   9.  Access Control Rules  . . . . . . . . . . . . . . . . . . . .  13
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  13
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
     11.1.  RELOAD Sensor Type Registry  . . . . . . . . . . . . . .  14
     11.2.  CoAP-REGISTRATION Kind-ID  . . . . . . . . . . . . . . .  14
     11.3.  CoAP-CACHING Kind-ID . . . . . . . . . . . . . . . . . .  14
     11.4.  Access Control Policies  . . . . . . . . . . . . . . . .  15
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  15
     12.2.  Informative References . . . . . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   The Constrained Application Protocol (CoAP) is a specialized web
   transfer protocol [I-D.ietf-core-coap].  It realizes the
   Representational State Transfer (REST) architecture for the most
   constrained nodes, such as sensors and actuators.  CoAP can be used
   not only between nodes on the same constrained network but also
   between constrained nodes and nodes on the Internet.  The latter is
   possible since CoAP can be translated to Hypertext Transfer Protocol
Show full document text