Thing-to-Thing Data Hub
draft-hartke-t2trg-data-hub-02

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02

Thing-to-Thing Research Group                                  K. Hartke
Internet-Draft                                                  Ericsson
Intended status: Experimental                           October 22, 2018
Expires: April 25, 2019

                        Thing-to-Thing Data Hub
                     draft-hartke-t2trg-data-hub-02

Abstract

   The Thing-to-Thing Data Hub is a RESTful, hypermedia-driven Web
   application that can be used in Thing-to-Thing communications to
   share data items such as thing descriptions, configurations, resource
   descriptions, or firmware updates at a central location.

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 https://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 April 25, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (https://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.

Hartke                   Expires April 25, 2019                 [Page 1]
Internet-Draft           Thing-to-Thing Data Hub            October 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Notation . . . . . . . . . . . . . . . . . .   3
   2.  Data Model  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Interaction Model . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Appendix A.  Related Work . . . . . . . . . . . . . . . . . . . .   8
     A.1.  CoAP Publish-Subscribe  . . . . . . . . . . . . . . . . .   8
     A.2.  CoRE Resource Directory . . . . . . . . . . . . . . . . .   9
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  11
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   In Thing-to-Thing communication, there is often a need to share data
   items of common interest at a central location.  For example, the
   CoRE Resource Directory [I-D.ietf-core-resource-directory] aggregates
   descriptions of resources held on other servers, which enables Things
   to easily discover these resources.  Similarly, a W3C Web-of-Things
   Thing Description Repository [WOT] stores semantic metadata of Things
   as well as functional descriptions of their interfaces, making this
   data available to Web dashboards, commissioning tools and other
   things.

   As more and more Thing-to-Thing applications are implemented, it
   becomes increasingly important to be able to share not only resource
   and Thing descriptions but also many other kinds of data, such as
   default configurations for new devices, service locations, firmware
   updates, or certificate revocation lists.  The existing resource
   directories and Thing description repositories are not a good fit for
   these kinds of data, as they're specialized to their use cases and
   don't accept any other kinds of data.  Creating a new, specialized
   application for each use case is not practical in the long term.

   This document defines a simple "data hub" application, a RESTful Web
   application with a hypermedia API that is suitable for constrained
   environments and that generalizes the concept of a central repository
   to sharing any kinds of data.  A data hub enables clients to share
   data items in any format and provides means for creating, reading,
   observing, updating, deleting, and finding data items at a data hub
   server.

   Data hubs are intended to be used primarily with CoAP [RFC7252].

Hartke                   Expires April 25, 2019                 [Page 2]