Blog entries for "IPv6"

Routing configuration over DHCPv6

Currently the DHCPv6 protocol does not allow the provisioning of any routing-related information to hosts. A new proposal is addressing this shortcoming. The draft draft-ietf-mif-dhcpv6-route-option defines a mechanism for delivering routing information over the DHCPv6 protocol. This article explains core concepts and explains how to use the ISC DHCP software to deliver such information.

DS-Lite architecture: overview and automatic configuration

Dual Stack Lite is an architecture that allows IPv4 services to be provided in an IPv6 network, despite a limited amount of available IPv4 addresses. Work on DS-Lite was conducted within the Softwires working group in the IETF, and began in late 2008. After many revisions it was recently published as RFC6333, with its companion RFC6334 dedicated to automated configuration.

New Opportunities for Criminal Growth - Forecasting Cyber-Crime during the IPv6 Transition

 I had the fortunate opportunity to present the Wednesday Keynote at the Rocky Mountain 2011 IPv6 Summit.  The session was a slightly different angle to the normal "IPv6" presentations.

ISC DHCP and IPv6 - the DHCPv6 story

Numbering Computers in IPv6

Computers and other IPv6-enabled devices need a way to select which IP address they are using, just like in IPv4. IPv6 provides several ways to do this:

An Ending and An Opportunity

A new milestone in the history and evolution of the Internet has passed: On Thursday, February 3, 2011, it was announced that the Internet Assigned Numbers Authority (IANA), steward of the Internet's reserves of unassigned IP addresses, has distributed the final blocks of IPv4 addresses to the Regional Internet Registries (RIRs). The RIRs, based in North America, Europe, Asia, South America, and Africa, will now allocate them, according to rules developed in each region, to service providers and enterprises worldwide. And then all of the IPv4 addresses will be in use.

How to connect to a multi-homed server over TCP.

With the world wide deployment of IPv6 in parallel with IPv4, it has become apparent that a traditional connection loop is no longer good enough.

In fact, this is a large part of the reason why Google is white listing resolvers and Yahoo only wants to return to AAAA records to DNS queries made over IPv6.  The traditional connection loop does not behave well in the presence of some network errors.  It introduces excessive delays when there are good alternate addresses to use.

Implementing IPv6 is no longer optional

The exhaustion of IPv4 space from IANA is coming as soon as February (yes, next month!) and the reserve held by the RIRs will be running dry shortly thereafter. The ability to provide (and use) IPv6 infrastructure is no longer optional; it is a requirement.