Hi Brian,
Thank you for your thoughtful insights. I like the idea of the cyclical blockchain.
Anyway, "DNS++" is just a pseudonym I came up with. Its just an extended DNS that provides full
path/address to a specific device.
In terms of the blockchain, we just need two chains / device.
1) For the DNS++ Entry (Which should be updated only if it is different from the previous one)
2) The ACL for the device.
I don't expect the chain to grow exponentially and if it does we will have the cyclical blockchain by then to
trim the tail :).
In terms of the blockchain incentive & proof of work, ... good questions :). TBD.
------------------------------
Santhosh Sathiyaseelan
Verizon Communications
------------------------------
Original Message:
Sent: 09-18-2017 13:02
From: Brian LaVallee
Subject: Catalyst Submission for IOT Home Gateway
Hi Santhosh,
Thought I would move the discussion to your thread on the topic.
Thank you for your response Brian.
There are some gaps between my thinking & your understanding of it :).
My apologies for not articulating it clearly.
1) The device manufacturer does not provide the HUB, The router manufacturer/ISP does that.
The hub is somewhat similar to Samsung SmartThings/ Wink etc but the key difference is that it's
not connected to a central proprietary server. Instead they update the "DNS++" and provide protocol
traslations from IP to Zigbee,ZWave etc. as applicable. Its primary function is to act as a conduit to
the IoT device from the outside world.
2) The blockchain is not on the device, but on the global network as blockchain's should be.
It is where the DNS++ "resides". It is also used for the device ACL's.
Your coffeemaker & washing machine will work as is :)
To start, I am not familiar with "DNS++", unless you are referring to the C++ devel for BIND. Google does not like searching for special characters. Can you give more information about "DNS++"?
I did understand your original concept, but 'maybe' not all of the specific details. I mentioned a lot of different approaches, yours fits into the decentralized, indirect "conduit", and announce 'update the "DNS++"' categories. Just using a router provided by the ISP. While it will work for SOHO routers, Enterprise equipment 'may' be a problem. Just look at the lack of UPnP in Enterprise devices.
What concerns me is the blockchain. Any device that needs to read information from the blockchain, requires the WHOLE blockchain. Without the ability to hash ALL of the previous blocks, you can not verify the current blocks integrity. Unless you're not concerned with security and query a central hub.
I've actually been mulling over this problem for a couple of years, need something like a cyclical blockchain that doesn't grow.
You mention the blockchain is on the global network. So where do the computing resources to fold the blockchain come from, to process the transactions, to mine the next block? The IoT/IoE device manufactures, the router, or my coffee maker? What's the incentive to participate? What if all of the pools are abandoned?
------------------------------
Brian LaVallee
INVITE Communications Co. Ltd
Original Message:
Sent: 09-12-2017 11:19
From: Santhosh Sathiyaseelan
Subject: Catalyst Submission for IOT Home Gateway
My submission to the forum was an offshoot of a platform we built to access Verizon owned CPE from our operations center and wondered if we could use the same approach to access IoT devices within the customer premises.
------------------------------
Santhosh Sathiyaseelan
Verizon Communications
------------------------------