Thing-to-Thing Data Hub
draft-hartke-t2trg-data-hub-03
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-03-11
|
|
Replaces |
|
draft-hartke-t2trg-bulletin-board
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| 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)
|
Thing-to-Thing Research Group K. Hartke
Internet-Draft Ericsson
Intended status: Experimental March 11, 2019
Expires: September 12, 2019
Thing-to-Thing Data Hub
draft-hartke-t2trg-data-hub-03
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 September 12, 2019.
Copyright Notice
Copyright (c) 2019 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 September 12, 2019 [Page 1]
Internet-Draft Thing-to-Thing Data Hub March 2019
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Notational Conventions . . . . . . . . . . . . . . . . . 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
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9
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. Similarly, a
Firmware Server [I-D.ietf-suit-architecture] stores 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
servers are not a good fit for these kinds of data, as they're
specialized to their use cases and generally not accepting any other
kinds of data. And creating new, specialized applications for every
type of data is not practical in the long term.
This document defines a simple "data hub" application, a RESTful Web
application with a machine-understandable hypermedia API. A "data
hub" generalizes the concept of a central repository for different
applications and is suitable for constrained environments [RFC7228].
Specifically, it 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 Constrained
Application Protocol (CoAP) [RFC7252].
Hartke Expires September 12, 2019 [Page 2]
Internet-Draft Thing-to-Thing Data Hub March 2019
Features:
o General
The data hub generalizes the concept of a directory or repository
Show full document text