All of our internal production sites starting in 2009 have been launched with dual stack IPv4/IPv6 from day one.  We typically serve static assets (images and javascript) from our content delivery network to improve load performance.  Unfortunately, the CDN we use is IPv4 only. The following Ruby on Rails code snippet is from /config/environments/production.rb that [...]

I have been accessing Google via IPv6 for the past few months thanks to the nice people at Hurricane Electric. Every once in a while when using Gmail, I will get a security error warning me that the SSL certificate for mail.google.com does not belong to that site (see below).  This only happens over IPv6. [...]

The launch of Pay4Bugs was unique not only because it is one of the first real products launched from day one with dual stack IPv4/IPv6 access, but also because Pay4Bugs, along with its sister IPv6-enabled OpenID provider, 87id,  is the first site to make possible OpenID sign on using exclusively IPv6 in a production environment.  [...]

Aaron Toponce over at Planet Ubuntu has an excellent article with graphics that really puts the vast size of the IPv6 address space in perspective in relationship to the almost used up IPv4 address space in perspective. I would just add that 64bits of the 128bit IPv6 address space do not necessarily have to be [...]

This post is the second in a series about radical technology choices in Pay4Bugs. In my previous post, I discussed our decision to make several radical technology choices in designing the new Pay4Bugs software testing service. In this article, I will discuss the decision to launch Pay4Bugs with IPv6 enabled from the beginning. What is [...]