BT survey indicates movement on IPv6 deployments

We recently invited network engineers to participate in an online industry survey to characterize opinions and attitudes about IPv6 deployment in their networks. We’ve conducted this survey for five years running now, and we’ve observed a steady climb in the proportion of survey participants who have deployed or were actively deploying IPv6. This year’s survey didn’t disappoint, as we saw continued IPv6 deployment progress with over half of survey participants indicating they had deployed or were in the process of deploying IPv6. This tally represented a fifteen percent higher proportion that in last year’s survey.

Deploying IPv6 is necessary for organizations to continue to communicate with all users on the “total Internet,” which is slowly evolving from a homogeneous IPv4 Internet to a mixed protocol IPv4-IPv6 Internet. Evidence of such an evolution is visible from various industry measurements, such as the proportion of Google users accessing their sites via IPv6 and vyncke.org’s measurements of IPv6 use globally and by country for web and email servers and DNS.

In the face of evaporating of IPv4 address space availability, growth of the Internet is accelerating due to new Internet users, new and multiple mobile devices for Internet users, and non-user devices or “things” spurring the emergence of the Internet of Things (IoT). Internet accessibility for these users and things will by necessity require IPv6.

Unfortunately IPv4 and IPv6 are not interoperable, so organizations desiring to communicate with these users and things, members of today’s growing total Internet, must support both IPv4 and IPv6. In fact, three of four survey respondents agreed that continued global Internet presence was a key benefit to deploying IPv6. And most survey respondents deploying IPv6 use a dual stack approach to enable Internet reachability via either protocol for their web, email and other Internet-reachable application servers.

Survey results also yielded some interesting shifts in attitudes about IPv6. As the reality of IPv4 address space exhaustion materializes, organizations are becoming more accepting of the need for IPv6 and are increasingly bullish about IPv6’s benefits and value.  For example, survey respondents from organizations that have or are deploying IPv6 recognized as top benefits offering a competitive advantage, supporting IoT initiatives, spurring innovative applications, and enabling a continued global Internet presence.

This year’s survey once again signified that the inability to demonstrate a strong business case was the leading obstacle to IPv6 deployment, followed by the complexity of infrastructure upgrades, conversion of applications or middleware, and staff training. These concerns represent a shift away from networking focused issues from past surveys to those of practical implementation and support, another indicator of attitude shift favoring deployment.

BT’s IPv6 survey findings and public IPv6 measurements corroborate increasing IPv6 deployment worldwide. We’d recommend that organizations that rely on Internet communications for ubiquitous Internet access to resources, collaboration, or commerce start planning for IPv6 deployment if they haven’t done so already. And BT can help along the way, with Advise services to assist with IPv6 deployment planning, execution and management and IP address management (IPAM) solutions from Diamond IP to enable IPv4-IPv6 address planning, discovery and management.  We invite you to review our full survey results and analysis in our survey report.

Comments

Post a Comment

Popular posts from this blog

Handy AAAA filter in BIND 9.8

The ISC introduced a pair of new configuration file options in BIND 9.8 to enable administrators to easily filter who may receive AAAA record type responses even if valid responses exist. For example, clients on subnets that do not have IPv6 network access can be excluded from receiving affirmative answers for AAAA queries. This feature provides simpler administration than the alternative mechanism using views. The first option, filter-aaaa-on-v4,defines whether the server will return AAAA records to certain clients. Such clients are defined by the address match list parameter of the second option, filter-aaaa. Note that BIND must be compiled with the --enable-filter-aaaa option on the configure command line to enable AAAA filtering. The syntax of these options is as follows: filter-aaaa-on-v4 (yes | no | break-dnssec) ; filter-aaaa {addr_match_list;} ; The filter-aaaa option identifies the address match list for which the filter-aaaa-on-v4 option is to be applied as described ...
Read more

Inglorious DDI

We all know how critical DHCP/DNS/IPAM (DDI) services are. Your network cannot function without them. But like most foundational elements of anything, they are certainly not glamorous...like good luck finding a home designer who specializes in home foundations. I would not be shocked should HGTV pass on my brilliant concept for a foundation building show. I suppose most people would find a show detailing footing depths and concrete pouring techniques rather boring.  Nevertheless, there are countless shows for redesigning and remodeling homes. On most episodes the foundation is out of sight, out of mind. If it's stable, no one wants to pay it attention, they just expect it to keep doing its job, supporting the structure. Once in a while a foundational issue is brought up that unexpectedly threatens to raise the budget to heighten the drama. All work stops until the issue is addressed. And you'll notice that the owner never denies paying the extra amount to fix the issue. ...
Read more

BIND 9.8.0 Adds DNS64 Support - Part 2 - How is it configured?

BIND 9.8.0 introduced a new dns64 option statement that can be configured within the server named.conf options block or within a view options block. Recall from a prior post that DNS64 configures a recursive DNS server to issue A record queries on behalf of a client requesting AAAA records, then appends the returned IPv4 address to a defined IPv6 prefix. This manufactured IPv6 address enables the querying host to connect to a NAT64 gateway which will terminate the IPv6 connection from the client and map it to an outbound IPv4 connection to the appended IPv4 address, completing the connection! Whew! BIND offers a number of useful parameters within the dns64 statement to control this process. The statement syntax is: dns64 IPv6_prefix { [clients {address_match_list };] [mapped {address_match_list };] [exclude {address_match_list };] [suffix IPv6_addr;] [recursive-only (yes|no);] [break-dnssec (yes|no);] }; The IPv6_prefix parameter is the prefix to which returned...
Read more