Info ...more details to follow. and hopefully a video soon to come as attachment!For your information, below is an outline on the potential impact of deploying IPv6 on cell phones and on any battery-driven device. NAT is energy-depleting while IPv6 could save up to 50% and enhance thereby always-on availability.

If we consider IPv4 as the protocol to interoperate peacefully networks ( the Peace Protocol as stated by a German General in the German IPv6 Summit back in July 2004, due to the coalition networking for the Balkan wars), let me declare from Teemu's work as well as from the efforts and energy savings lessons learned from the Japanese Feel6 and the Building Automation projects that IPv6 is an environmentally friendly protocol and therefore could be safely called The Green Protocol!!

Cellular phones are battery operated devices that utilize sophisticated techniques to maximize standby time. Generally a cellular phone tries to be at "sleep" as much as possible. When a cellular phone is behind a NAT or a stateful firewall and it needs to keep a TCP or UDP connection open, it has to periodically "wake up" to send keep-alive messages to refresh mappings in NAT and/or firewall. This can happen, for example, when an IPv6 transition mechanism that utilizes UDP-tunneling is used or a cellular phone is running an always-on application such as e-mail, IP telephony, or instant-messaging. The lifetime of a mapping in NAT and firewall can be as low as 30 seconds for UDP connections. TCP mapping lifetimes are significantly longer, usually more than 30 minutes. Sending of the keep-alive messages is power consuming. The rate of battery consumption is different with different access technologies, for example, in the 2G GPRS and the 3G WCDMA packet data technologies the power consumption is significantly higher than in Wireless LAN. If a cellular phone in 2G or 3G network has to send keep-alive message every 30 seconds, the standby time will be reduced to less than half when compared to being completely idle. When public IPv4-address or IPv6 connectivity that does not require UDP tunneling is available, sending of the NAT keep-alive messages can be avoided. However, keep-alive messages still have to be sent to refresh mappings in firewalls and therefore mapping lifetimes for UDP connections, especially in IPv6, firewalls should be configured to minutes instead of seconds. It should be noted that firewalls do not have such scarce resource as public IPv4 addresses to conserve as NATs do. If keep-alive messages can be sent only once in every 5-15 minutes and timeouts for UDP mappings are extended to 20-30 minutes, the cellular phone battery consumption in 2G/3G networks will be reasonable.