IPv6 deployments growing steadily though not exponentially (yet)

The percentage of users of google's websites accessing via IPv6 has reached 8% for the first time last week, essentially doubling up the percentage from only a bit more than a year ago. It was then, a year ago that I had last blogged about predicting future IPv6 adoption trends based on "curve fitting" historical measurements. At that time, the predictions for the end of 2014 indicated 6.2% for the exponential growth model, while the polynomial model predicted 5.6%. The actual measurement was 5.7%.

As illustrated in the graph below with curve fits based on the most recent data, the exponential curve, the top (green) curve is certainly the most ambitious as it was last year. It predicts the percentage of IPv6 users accessing google's sites at 11.4% by the end of this year and over 25% by the end of next. Meanwhile the polynomial curve fits are more conservative predicting 8-9% by the end of this year and 12-15% by the end of next.


While IPv6 adoption growth hasn't "gone exponential" just yet, could the exhaustion of IPv4 space most recently within the ARIN region  (mostly N. America), following RIPE (Europe) and APNIC (Asia) serve as the catalyst to drive IPv6 deployment growth exponentially? Further requirements for IP address space must by necessity be filled by IPv6 address space, unless an IPv4 address exchange can be brokered.

But even if no additional IP space is needed, the population of IPv6 capable Internet users is clearly growing. Are they able to access your website? Where do you stand with IPv6 deployment? You can make your opinions known by completing our annual IPv6 survey.   They survey takes only five minutes to complete and you can register to win a $100 Visa gift card, the winner of which will be selected randomly among participants. Hurry, the survey closes at the end of July.

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