W3C home > Mailing lists > Public > public-wot-ig@w3.org > February 2016

Re: Device Discovery and Telehash

From: Tibor Pardi <tibor@zovolt.com>
Date: Tue, 9 Feb 2016 13:12:34 +0000
Message-ID: <CAMJB5dtR1iiSovbk7G8gPEb5ChYyysWKuceLN08+piPCvLSU6g@mail.gmail.com>
To: Jaime Jiménez <jaime.jimenez@ericsson.com>, Drasko DRASKOVIC <drasko.draskovic@gmail.com>, Dave Raggett <dsr@w3.org>, public-wot-ig@w3.org
Hi Jaime,

Thanks!

The W3C web-of-things-framework is a very early stage software and we
haven't progressed as much, but your idea about storing such entries sounds
very good! It seems to me a P2P DHT is a perfect medium to store such
entries like data from the CoAP Resource Directory. The peers by definition
store and propagate the entries of the DHT and such topology could solve
many device discovery as well as interoperability issues. The entries of
the CoAP Resource Directory can be just normal, keyed items of the DHT. The
content of the item could be a JWS token and it can be encrypted to make it
available only to certain users (if that is required). I think it is a very
good idea and we should put this on our TODO list.

Regards,
Tibor



On Tue, Feb 9, 2016 at 12:39 PM, Jaime Jiménez <jaime.jimenez@ericsson.com>
wrote:

> Hi Tibor,
>
> this sounds extremely interesting to me.
>
> Have you looked into making it work with standard discovery mechanisms
> like CoAP Resource Directory?
> For example by storing the entries of the RD into a DHT?
>
> Ciao!
> - - Jaime Jimenez
>
> On 08 Feb 2016, at 18:29, Tibor Pardi <tibor@zovolt.com> wrote:
>
> Hi Drasko
>
> We have started to implement a P2P device discovery module in the
> https://github.com/w3c/web-of-things-framework project. Our P2P discovery
> module uses the a Kademlia DHT table, the implementation and concept is
> very similar to Telehash. I investigated Telehash as well, I understand
> IBM's Adept (before it was abandoned) selected Telehash, but there are very
> little Nodejs support for Telehash which I could integrate at the time. Our
> underlying or ECDSA modules are based on Bitcoin crypto as well and use a
> Bitcoin crypto library.
>
> Device discovery is one of the main area which need to be addressed, and
> an open source, decentralised, P2P device discovery mechanism that operates
> without using a proprietary cloud or client/server module is one possible
> way to manage the topic. In fact I believe P2P is the best possible
> solution for device discovery. P2P by definition addresses requirements
> such as scalability and high availability without the need to spend a
> fortune on load balancing and cluster infrastructure.
>
> There is a brief readme to explain our P2P device discovery module at
> https://github.com/w3c/web-of-things-framework/tree/master/examples/p2p_demo
>
> Please note I am updating the P2P module at the DEV branch with optimizing
> the module, providing tests for ECDSA and ECDH and using TCP/IP by default
> instead of UDP (several users reported that their mobile operators blocks
> UDP traffic).
>
> Regards,
> Tibor
>
>
>
> On Mon, Feb 8, 2016 at 3:46 PM, Drasko DRASKOVIC <
> drasko.draskovic@gmail.com> wrote:
>
>> Hi Dave,
>> I was wondering what is the IoT framework approach towards device
>> discovery?
>>
>> Iotivity and AllJoyn approach this problem, but are closed standards.
>> Do we have open technologies that we can use in decentralized manner
>> for WOT Framework?
>>
>> One new interesting p2p protocol is Telehash: http://telehash.org/,
>> specified by Jeremie Miller (XMPP creator - and we all know how much
>> industry loves XMPP for NAT traversals ;)). This protocol is based on
>> Bitcoin Blockchain for encryption (and some king od DNS resolution
>> (https://github.com/telehash/blockname), and I guess it can be used
>> for decentralized device discovery.
>>
>> BR,
>> Drasko
>>
>>
>
>
Received on Tuesday, 9 February 2016 13:13:04 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 10 February 2016 08:15:37 UTC