6LOWPAN is a very good choice for this, but it is part of the TCP/IP suite of standards. The advantage to it is that it can easily be mapped into a full IPv6 network, so it can be gatewayed into the wider Internet. That only fills out the bottom layers of the protocol stack, though. Application - level protocols will be necessary for real integration of these devices at the network level.
I agree Bert, this doesn't seem to me like a useful action...and without puting any money in nothing will happen anyways so maybe we should not worry too much...what will happen will be driven by business sense and market needs
This also makes my eyes roll to the back of my head. My knee jerk reaction being, thank goodness that in the US, at least, innovation happens without "help" from politically motivated politicians.
I'll acknowledge that sometimes an external force providing "focus" is helpful, however the outcome of such "focus" is usually not very productive. Even if results are achieved.
The IoT (so-called), which already exists in truth, will continue to develop. Not because a politician spurs it along, but because it provides solutions to real needs. The White House does not need to concern itself that the electric light switches in my house are not all networked together. I'm sure it's possible to coerce me into building such a network, and then I can show it to grandma.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.