Thing-to-Thing Data Hub
draft-hartke-t2trg-data-hub-06
Thing-to-Thing Research Group K. Hartke
Internet-Draft Ericsson
Intended status: Experimental May 9, 2020
Expires: November 10, 2020
Thing-to-Thing Data Hub
draft-hartke-t2trg-data-hub-06
Abstract
A "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 November 10, 2020.
Copyright Notice
Copyright (c) 2020 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 November 10, 2020 [Page 1]
Internet-Draft Thing-to-Thing Data Hub May 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Notational Conventions . . . . . . . . . . . . . . . . . 4
2. Data Hubs . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Data Items . . . . . . . . . . . . . . . . . . . . . . . 4
2.1.1. Data Item Representation . . . . . . . . . . . . . . 4
2.2. Data Collections . . . . . . . . . . . . . . . . . . . . 4
2.2.1. Data Collection Representation . . . . . . . . . . . 5
2.2.2. Filter Query Representation . . . . . . . . . . . . . 5
2.3. Data Hub Discovery . . . . . . . . . . . . . . . . . . . 5
2.4. Interactions . . . . . . . . . . . . . . . . . . . . . . 6
2.4.1. Getting All Data Items . . . . . . . . . . . . . . . 6
2.4.2. Getting Data Items by Metadata . . . . . . . . . . . 6
2.4.3. Creating a Data Item . . . . . . . . . . . . . . . . 6
2.4.4. Reading a Data Item . . . . . . . . . . . . . . . . . 7
2.4.5. Observing a Data Item . . . . . . . . . . . . . . . . 7
2.4.6. Updating a Data Item . . . . . . . . . . . . . . . . 7
2.4.7. Deleting a Data Item . . . . . . . . . . . . . . . . 7
3. Security Considerations . . . . . . . . . . . . . . . . . . . 7
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.1. Normative References . . . . . . . . . . . . . . . . . . 8
5.2. Informative References . . . . . . . . . . . . . . . . . 9
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
In Thing-to-Thing communication, there is often a need to share data
items of common interest through a central location. For example,
the Resource Directory [I-D.ietf-core-resource-directory] aggregates
descriptions of Web resources held on constrained nodes, which
enables other nodes to easily discover these resources; a Thing
Directory [W3C.CR-wot-architecture-20190516] stores metadata of IoT
devices, allowing clients to discover interaction affordances and
supported protocol bindings of Things; a Firmware Server
[I-D.ietf-suit-architecture] stores firmware images and manifests,
making this data available to deployed devices, commissioning tools,
and other services.
As more and more Thing-to-Thing applications are implemented, it
becomes increasingly important being able to not only share resource
descriptions and firmware updates but also many other kinds of data,
such as default configurations for new devices, service locations, or
certificate revocation lists. Resource directories and firmware
Show full document text