This is an archived page from a previous event. Click here to go to the latest event.

How IPv6 Will Kill Telecom - And What We Need To Do About It

Dan York, Director of Conversations, Voxeo

Date: Wednesday, June 29

Time: 2:30 - 2:45 PM

Location: Salon E

Category: Technology & Engineering

How badly will IPv6 screw up telecommunications?  Where are the areas of telecom that will see the greatest impact? And what can be done to fix it?

With the recent buzz around World IPv6 Day and the exhaustion of top-level IPv4 address allocations, organizations are starting to seriously look at exactly what is involved with migrating to IPv6... and asking questions about what this means for all their VoIP and  Unified Communications systems. Given that the reality is that a "IPv6-only" world is a  distant future, questions are particularly being asked around how those telecommunications systems will work during the transition period from IPv4 to IPv6.

In this session, Voxeo's Dan York will explore where IPv6 and telecom play nice together and where there are serious minefields that may restrict telecom from working over IPv6, including:

  • how the Session Initiation Protocol (SIP) has serious transition issues
  • how embedded devices such as handsets face numerous obstacles
  • the top 5 challenges facing VoIP and UC application developers
  • what role DNS plays in the transition and the issues that lie therein
  • the added complexities of debugging - and of the larger ecosystem of applications 
Beyond simply listing the problems, York will outline potential solutions, relay work  being done with industry groups such as the SIP Forum and provide pointers to resources and ways that people can get involved with helping find more solutions to enable telecom to move smoothly into the world of IPv6.

Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /home/ecommec/public_html/cgi-bin/mt/php/extlib/adodb5/drivers/ on line 443
blog comments powered by Disqus