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

 
Document
Type Active Internet-Draft (individual in rai area)
Last updated 2015-04-15
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html
Stream
WG state (None)
Consensus Unknown
Document shepherd Carlos Bernardos
Shepherd write-up Show (last changed 2015-02-04)
IESG
IESG state In Last Call (ends 2015-05-13)
Telechat date
Responsible AD Ben Campbell
Send notices to jmlvega@ugr.es, jaime.jimenez@ericsson.com, gonzalo.camarillo@ericsson.com, cjbc@it.uc3m.es, Jouni.Maenpaa@ericsson.com
IANA
IANA review state IANA - Review Needed
IANA action state None

Email authors IPR 1 References Referenced by Nits Search lists

P2PSIP                                                        J. Jimenez
Internet-Draft                                                  Ericsson
Intended status: Standards Track                           J. Lopez-Vega
Expires: October 17, 2015                          University of Granada
                                                              J. Maenpaa
                                                            G. Camarillo
                                                                Ericsson
                                                          April 15, 2015

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

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 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 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 October 17, 2015.

Jimenez, et al.         Expires October 17, 2015                [Page 1]
Internet-Draft           A CoAP Usage for RELOAD              April 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   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 . . . . . . . . . . . . . . . . . . . . . . .  12
   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 . . . . . . . . . . . . . . . . . . . . .  16
     11.1.  CoAP-REGISTRATION Kind-ID  . . . . . . . . . . . . . . .  16
     11.2.  CoAP-CACHING Kind-ID . . . . . . . . . . . . . . . . . .  17
     11.3.  Access Control Policies  . . . . . . . . . . . . . . . .  17
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  17
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  17
     12.2.  Informative References . . . . . . . . . . . . . . . . .  18
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  18

1.  Introduction

   This usage is intended for interconnected devices over a wide-area
   geographical coverage.  For example in cases multiple Wireless Sensor
   Networks (WSN) that need to be federated over some wider-area
Show full document text