IP Convergence: Beyond VoIP, Beyond Cost Savings

Imagine starting your car and seeing that message on your dash.

If this happens, it's not outside of the realm of possibility.  BMW labs is experimenting with the use of IP sub-systems for internal communications, which is a pretty interesting idea!  One of the draw backs of using standard protocols and components is the availability of knowledge around said commonly available technology, but IP can be secured pretty well, so if it's done properly hacking shouldn't be a big concern. 

The author didn't mention the possibility for 3rd party after market add-ons, but one would think they'd be possible if the car has IP packets flowing through it's veins, but then that would reopen the possibility of security threats too, so it might be in BMW's best interest to try and prevent any sort of external tampering with the system.

I think the author of the article is a little confused about IPv6, though.  He says:

Costs drop because fewer specialized components are needed, and the new
version of IPv6 is even better than the more than fine performance from
IPv4.

I would love to know how the new version of IP is even better than the performance of IPv4, especially given that it doesn't perform as well as IPv4, which I noted in a previous post.  In some discussions with members of the IT community from various government agencies, they are leery of deploying IPv6 for security reasons (not because of known issues but more because of the unknown issues that have yet to be discovered because IPv6 is not widely adopted yet).  As a result of these factors as well as overall adoption rate, IPv6 support might actually cost a bit more than IPv4 for several more years.

Despite the erroneous implication of improved performance, if this just a proof of concept and 3rd party after-market add-ons are not a priority, why not design it around IPv6?  IPv6 might even help insure that the system stays a somewhat closed
one...or it might be the killer app that drives further development and
investment in IPv6.  Furthermore, you could do crazy stuff like putting an RFID tag on every nut and bolt in the car, build an RFID-to-IPv6 proxy server, ping every last component on the car, and triangulate their position to make sure they're all where they are supposed to be.  Then when your mechanic ends up with those extra parts and throws them to the side like he did before, you can run the diagnostic before leaving the shop and call him on it.

Better make sure there's an on-board DNS system too, just so we don't have to see the following error message 'Communication Failed with device 2001:450:1999:900:0:670:1708:1920'.  :-)

posted by Dave Siegel