blog topics: BGP · IPv6 · more · my publications · my business: inet⁶ consult · contact: Twitter · LinkedIn · email · 🇺🇸 🇳🇱

These are all posts about IPv6. Archive for 2011.

2010 IPv4 Address Use Report

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.

Read the article - posted 2011-01-01

2010 IPv6 Address Use Report

In 2010, twice as many IPv6 address blocks were given out as in 2009, adding up to 5.5 times as much address space.

Read the article - posted 2011-01-01

→ River of IPv4 addresses officially runs dry

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.

Read the article - posted 2011-02-03

→ No more addresses: Asia-Pacific region IPv4 well runs dry

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.

Read the article - posted 2011-04-15

→ RFC 6146: Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers

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.

Read the article - posted 2011-04-27

→ RFC 6147: DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers

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.

Read the article - posted 2011-04-27

→ RFC 6384: An FTP Application Layer Gateway (ALG) for IPv6-to-IPv4 Translation

The File Transfer Protocol (FTP) has a very long history, and despite the fact that today other options exist to perform file transfers, FTP is still in common use. As such, in situations where some client computers only have IPv6 connectivity while many servers are still IPv4-only and IPv6-to-IPv4 translators are used to bridge that gap, it is important that FTP is made to work through these translators to the best possible extent.

Read the article - posted 2011-11-05

Search for:

Archives: 2003, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2018, 2019, 2020, 2021