IPV6

 If TI would like to see “An Internet of Things” then it should embrace IPV6 which will allow every device in your home to have a unique, internet routable, IP address. This would allow remote control of all those things from anywhere you have internet connectivity. Presently, remote control is hampered by NAT and requires people to use Dynamic DNS (which you have to pay for) in order to access devices connected via a NAT Router. I was just looking at the TI (CC3000-TiWi-SL) which is a complete WiFi node (no software needed) in a single package. Its purpose is to make simple, low cost, devices that connect to the internet. The trouble with this device is that it only supports IPV4 which has now run out of routable addresses. This device would be infinitely more powerful if it supported IPV6 with the much larger IPV6 address space.

  • Dale,

    We have embraced the IPv6! We are actively working with a standard called 6LoWPAN, which very simply put is a way of transmitting IPv6 data in a low power wireless environment. Have a look at ti.com/6lowpan 6LoWPAN will also be used in the upcoming ZigBee IP standard.

    I will let someone else comment on the choice on IP version for the CC3000 chip.

    -Jonas

  • In reply to Firefighter:

    But 6LoWPAN not WiFi compatible...

  • Hi Dale,

    First, as a matter fo fact you are correct. TI's shares the view that in the long-run there will be a string correlation between a 'connected universe' and IPv6 deployment.

    However, we witness the proliferation of IPv6 as an evolution process. The same we believe will happen with IOT. Without appropriate evolvement in the backhaul there isn't much value for IPv6. Further, IPv6 is more than a protocol it is a protocol suite and entails an ecosystem. Starting from the way to obtain and determine address, routing nodes availability and more. The evolvement of endpoints should go hand in hand with that of the infrastructure. Some of these aspects still didn't reach a clear industry verdict.

    The current install base is massively dominated by the IPv4, and solutions to endpoint accessibility problems should be solved as you mention with alternatives such as registration to a central office or port forwarding configuration in the AP. (depending on topology). While this is not the ultimate picture of IOT, it is still a practical step along this road. If you are truly interested we can explore a number of standard and proprietary means to address this concern elegantly.

    Having said that, as mentioned above, IPv6 is definitely an integral part of the IOT future and we will thus support IPv6 in our next-generation portfolio, along with the proper set of capabilities based on market and actual deployment verdict.

    Avi Baum

  • In reply to Avi Baum:

    This IC will be place in devices with relatively long life. And this devices will be auxiliary to other network components. And if you wont to simplify internal network you will need to replace this devices. Dual stack good for connectivity of end host or network, but not for secondary or auxiliary (relatively to backbone) networks.