Hi, I'm Iljitsch van Beijnum. These are all posts about IPv6.
Your current connection to the web server is over IPv4, using address 18.119.105.155. Checking your IPv6 address (this requires javascript)...
This document describes stateful NAT64 translation, which allows IPv6-only clients to contact IPv4 servers using unicast UDP, TCP, or ICMP. One or more public IPv4 addresses assigned to a NAT64 translator are shared among several IPv6-only clients. When stateful NAT64 is used in conjunction with DNS64, no changes are usually required in the IPv6 client or the IPv4 server.
Permalink - posted 2011-04-27
DNS64 is a mechanism for synthesizing AAAA records from A records. DNS64 is used with an IPv6/IPv4 translator to enable client-server communication between an IPv6-only client and an IPv4-only server, without requiring any changes to either the IPv6 or the IPv4 node, for the class of applications that work through NATs. This document specifies DNS64, and provides suggestions on how it should be deployed in conjunction with IPv6/IPv4 translators.
Permalink - posted 2011-04-27
APNIC is down to its last 17 million IPv4 addresses, so from now on ISPs in Asia, Australia, and the Pacific will only qualify for one final block of 1,024 addresses each.
Permalink - posted 2011-04-15
It's official: the IPv4 well has run dry. The final five /8 blocks of IPv4 were handed with much pomp and circumstance at an event this morning, which means it's time to get serious about moving everyone to IPv6.
Permalink - posted 2011-02-03
As of January 1, 2011, the number of unused IPv4 addresses is 495.66 million. Exactly a year earlier, the number of available addresses was 721.06 million. So we collectively used up 225.4 million addresses in 2010.
Permalink - posted 2011-01-01
In 2010, twice as many IPv6 address blocks were given out as in 2009, adding up to 5.5 times as much address space.
Permalink - posted 2011-01-01