In every ISP's engineering group there invariably lurks a list of those tasks that lie just a little a bit beyond the normal day to day activity of reacting to events as they happen. For many the item "IPv6??!! has been on this "to do" list for some years, if not for the entire lifetime of the ISP itself! This particular task falls into the category of being large enough that there's never normally enough time to put aside to work on it in between all the other day to day tasks, but its not important enough on any day to push the task to the top of the priority stack. So instead it resides on this "to do" list for year after year. This seemingly endless deferral of core engineering for IPv6 appears to be a pretty typical scenario at the moment across the Internet. A look at the IPv6 inter-domain routing table at the moment reveals some 900 unique Autonomous System numbers (AS's), or 900 networks that are publicly routing IPv6, while there are some 27,300 equivalent AS entries in the IPv4 Internet. So there are still a fair number of networks for whom turning on IPv6 remains something to do tomorrow, or possibly the day after.

But is switching on IPv6 support in the network really such a hard task? What does it take to turn on IPv6 in your network?

You might be asking, before you've clicked through, what is Tui?

Tui is an appliance for Internet connected networks to use to connect their IPv6 cloud to other IPv6 clouds over IPv4 best paths.

Tui is also a Teredo and 6to4 relay, to provide efficient tunnelled connectivity to end users of an IPv4-only access network.

Also:

The Tui (Prosthemadera novaeseelandiae) is an endemic passerine bird of New Zealand. It is one of the largest members of the diverse honeyeater family.