Home / Blogs

The Christmas Goat and IPv6 (Year 3)

Christmas Goat – A pretty picture of the Christmas goat from the night before it was burnt down (top) and the early morning photo after it was burnt down (below). Image source: www.merjuligavle.seAs Christmas were getting closer, the third time of load balancing the streaming pictures of the famous Christmas goat in the city of Gävle, Sweden, was on the agenda. My goal with this activity is the same as before, to track the use of IPv6 and DNSSEC validation. The results from the last two years are published on CircleID: 2010 and 2011

A somewhat odd and long tradition in Gävle is to burn the poor Christmas goat down. Not in any official way I might add, more often as a result of bad behavior from some youngsters on their way home from a late night on the town. This obscure activity has ironically made the Christmas goat more famous, even on an international scale.

This year the Christmas goat was standing for 10 days before it was burnt down.

So how did we do this? Below is a brief description:

At the time of the premier of the 2012 Christmas Goat the following was set up:

http://www.julbockmedipv6ochdnssec.se/kamera1 (may not be active)

In order to:

• Track native IPv6 with a RR with A and AAAA.
• Track those who can run IPv6 native or tunneled.
• Track validating DNS-resolvers with a domain that has a faulty DNSSEC.

The result was quite surprising. The use of native IPv6 had not increased as much as I expected. Tunneling with 6to4 and Teredo was very low and the DNSSEC validation was almost half.

When I first counted the use of native IPv6 for 2012 I only reached a figure of 0.7%, compared to 0.5% last year. This made me curious, and I had to investigate some more. It turned out that from the total of more than 62,000 unique IP-addresses visiting the page, the 50 top talkers represented more than 50% of the hits. Not any of these 50 top talkers were using native IPv6. If I removed the top talkers, the figure for native IPv6 increased to 1.4%.

The use of IPv6 with native, 6to4 and Teredo was 11%, compared to 52% last year. DNSSEC validation came in at 32%, compared to 72% for 2011.

Is there any explanation to that reduction? Well, I don’t know really. For the previous years I cannot find that many top talkers. Also I can’t see any pattern in home and enterprise users. So my conclusion as of last year, that I only need a few days of data to get quite an accurate reading of the percentage, now seems to be completely wrong. Even the sun… :)

Conclusion:

Another way of looking at it is that if we discard 2011, and just compare native IPv6 in 2010 and 2012, we can see a fourteen times increase. And that makes me happy! I don’t need much to be happy. :)

Unfortunately my logs don’t show me any hints on why DNSSEC, 6to4 and teredo are reduced. For now, I will however not let these things disturb my Christmas holiday. Instead I will await the data from next Christmas and hope that our famous Christmas goat then will stand all the way past Christmas!

Merry Christmas and A Happy New Year to you all!

By Torbjörn Eklöv, Senior Network Architect, DNSSEC/IPv6

Filed Under

Comments

Comment Title:

  Notify me of follow-up comments

We encourage you to post comments and engage in discussions that advance this post through relevant opinion, anecdotes, links and data. If you see a comment that you believe is irrelevant or inappropriate, you can report it using the link at the end of each comment. Views expressed in the comments do not represent those of CircleID. For more information on our comment policy, see Codes of Conduct.

CircleID Newsletter The Weekly Wrap

More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

Related

Topics

IPv4 Markets

Sponsored byIPv4.Global

Brand Protection

Sponsored byCSC

DNS

Sponsored byDNIB.com

Threat Intelligence

Sponsored byWhoisXML API

Domain Names

Sponsored byVerisign

New TLDs

Sponsored byRadix

Cybersecurity

Sponsored byVerisign