The only possible solution for integrating native IP into the ZigBee stack would be the 6LoWPAN standards, as it allows IPv6 to be used in very small frame sizes such as the < 100 bytes left over after IEEE 802.15.4. By using 6LoWPAN it is quite easy for ZigBee to add this to their specifications - in practice all that is needed is to replace the ZigBee networking layer with 6LoWPAN and UDP. Already there has been a proposal to the IETF for how to use the ZigBee Application Layer and Profiles over UDP/IP.
I just made a post about the ZigBee IP transition that might give some insight to how I think it will happen (http://zachshelby.org).
Following the commercial success (and technical disappointment) of the original Wildfire -- which featured a miserly 528MHz CPU and QVGA display -- HTC has returned with the Wildfire S.
The most commented posts on Engadget over the past 24 hours.
Now that we've thrown 'em off the trail, use the form below to get in touch with the people at Engadget. Please fill in all of the required fields because they're required.
The only possible solution for integrating native IP into the ZigBee stack would be the 6LoWPAN standards, as it allows IPv6 to be used in very small frame sizes such as the < 100 bytes left over after IEEE 802.15.4. By using 6LoWPAN it is quite easy for ZigBee to add this to their specifications - in practice all that is needed is to replace the ZigBee networking layer with 6LoWPAN and UDP. Already there has been a proposal to the IETF for how to use the ZigBee Application Layer and Profiles over UDP/IP.
I just made a post about the ZigBee IP transition that might give some insight to how I think it will happen (http://zachshelby.org).