Another UC Planning Issue Needing Some Attention

When I bring up IPv6 as another issue that Enterprises need to deal with as they consider/plan/ implement UC, most Enterprises will likely say, “What is IPv6?” Well, IPv6, the new internet addressing scheme replacing the legacy Internet addressing scheme (IPv4) will becoming increasingly important as it is expected that IPv6 addresses will be exhausted sometime in 2011 – and if Wireless 4G networks take-off, likely sooner. So what does this mean, you ask? Doesn’t my private Network Address Translation (NAT) capability protect me by mapping public and private IP addresses? And the answer is yes, but. Service Providers are migrating/transforming their core networks to IPv6 and many (at least those doing business through the Federal General Services Administration’s Networx procurement contract) have been operating in dual-IPv4/IPv6 mode for a while. Enterprises have not been concerned but they will need to become, at least IPv6 aware. 

When we run out of IPv4 addresses, all new network elements, including the explosion of data-capable 3G/4G mobile devices, will require IPv6 addressing. Address translation capabilities will be required and, while likely wire-speed capable, any translation can effect network latency and, thereby potentially impact a user’s quality of experience (QoE). Also, some products/solutions/applications may use IPv6 techniques internally and may require upgrades/changes to support IPv6.

So, Enterprises need to fold the IPv6 transition into all network planning – certainly including the real-time aspects of UC (e.g., voice and video). Plans must at least ensure that any new procurements for new solutions, growth or just replacements are IPv6 capable. That certainly includes network components that deal with addressing/gateway/routing functionality – just about every component in a UC network – including smart devices, such as PCs or mobile/smart phones that may directly manage their own or other device/application’s address translations for capabilities like presence or IM. In addition, investigation is needed to determine whether existing/legacy solutions have any inherent IPv4 limitations or characteristics that will need updating in order to work in an IPv6 environment. While one might think that the end of IPv4 addresses is over a year away, it is certainly not too late to begin to ensure that your network, UC and applications are going to continue providing good QoE to your users. And new procurements and planning for same must also be IPv6 compliant.