rdlink: Robust distributed links to constrained devices

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2019-03-24
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized 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)
T2TRG                                                         C. Amsuess
Internet-Draft                                            March 25, 2019
Intended status: Experimental
Expires: September 26, 2019

        rdlink: Robust distributed links to constrained devices


   Thing to thing communication in Constrained RESTful Environments
   (CoRE) relies on URIs to link to servers.  Next to hierarchical
   configuration and short-lived IP addresses, this document introduces
   a naming scheme for devices based on cryptographic identifiers.  A
   special purpose domain is reserved for expressing those identifiers,
   and mechanisms for constrained devices to announce their names and to
   look them up are described.

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 26, 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

Amsuess                Expires September 26, 2019               [Page 1]
Internet-Drardlink: Robust distributed links to constrained   March 2019

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

1.  Introduction

   Communication between constrained devices using the CoAP protocol
   largely happens in either of two scenarios at the moment: local
   networks with static IP addresses, and communication mediated by
   dedicated servers.

   Direct communication between constrained devices across the Internet
   is currently an exceptional setup, and usually involves static
   configuration or bespoke mechanisms.

   Direct communication with a CoAP severs is often guided by web links
   which point to the URI that both names the server (and a resource on
   it), and indicates how that server can be reached.  Such links often
   indicate registered name which is typically looked up in the DNS
   hierarchy and thus relies on the operator to own and administer a
   domain, If they don't, they indicate an IP address; such links are of
   limited use for stable identifiers, e.g. due to mobile endpoints.

   This document introduces a special purpose domain (rdlink.arpa) along
   the mechanisms with which it is used (employing a Distributed Hash
   Table (DHT)).

   Constrained devices can announce and look up addresses without direct
   interaction with the DHT by interacting with a distributed resource
   directory ([I-D.ietf-core-resource-directory]).

   Resolvable names are provided for compatibility with applications
   that are unaware of these provisions.

2.  Terminology

2.1.  Participants

   This document uses several roles of devices:

   named server  A CoAP server owns a name in the special purpose

   name user  A CoAP client that needs to resolve a name in the special
      purpose domain.

   registration helper  A server that assists constrained named servers
      in announcing their names.

Amsuess                Expires September 26, 2019               [Page 2]
Internet-Drardlink: Robust distributed links to constrained   March 2019

   lookup helper  A serve rthat assists constrained name users in
      finding the named server.

   DHT participant  Any device that is a node in the DHT overlay

   Often, named servers act as name users towards other servers.  The
   roles of registration helper, lookup helper and DHT participant are
   expected to be implemented together in typical use cases.

   Note that a named server can act as a CoAP client towards a name user
   that has ongoing communication with it without being a name user on
   its own by just addressing the client on its own.

3.  Auxiliary Mechanisms

   This section describes mechanisms that are expected to be specified
   in different documents, which will then only be referenced.
Show full document text