Slashdot Mirror

The object of the exercise is to discover the endpoints where failover does not properly occur and get them fixed.

If you'd prefer to avoid a nasty surprise on the day, there are ways to test in advance.

Didn't read past the first page, I guess:

"With the exception of some products by D-Link and Apple's AirPort Express and AirPort Extreme, none of today's CPE can operate using IPv6 well enough for a field test trial, Bulk says."

Also, even the high points of Apple and D-Link have gaps in their best models and many models that are still very broken. IIRC, only one of the D-Link (the newest one) includes a stateful firewall and older models probably won't ever because of memory limitations.

http://www.getipv6.info/index.php/Broadband_CPE

I was gonna explain all this here, but instead, I'll just drop this link. Suffice to say that there are a lot of contributors to "IPv6 brokenness" and older Mac OS X [especially pre-10.6.5] behaviors are only one of several ways that Internet users will have problems on World IPv6 Day.

And what makes you think ISPs won't charge per IP address on IPv6?

Well, by the current standards residential assignments in IPv6 will generally be allocated a subnet size of /48, /56, or /64 (out of 128) - see here for ARIN address plan. Given the fact that a subnet of one of those sizes will be required for even basic connectivity, the chances are that you will have a lot of v6 IPs included in the basic cost of your connection.

I have IPv6 at home and have a /48 allocation.

Yes, you can have the very same server answer IPv6 queries as well as IPv4, you just need to add IPv6 interface to the server and make sure the particular server software knows how to bind to IPv6 address.

The particular ISOC survey document which started this thread has a fairly long list of resources at the end of it which might be helpful, but here's a few to get you started: http://www.6diss.org/, http://www.getipv6.info/ and http://www.ipv6tf.org/

The unintended consequence of this is that every user on a system is going to get a fixed ipv6 ip and ipv4 traffic would be gradually phased out. Why bother with the administrative burden of issuing an IP address via dhcp and tracking it, when, you could have an ipv6 theoretically assigned to a customer for the life of a device.

You _ARE_ kidding, right?

Maybe you should check out some information about ipv6 before you make more of a fool of yourself.

There is quite a bit of confusion, and it appears that people like you are the ones that are spreading it. How about just a little ipv6 delivery model to end customers?

.info? Seriously? ARIN couldn't afford a domain that didn't scream "Beware of the Leopard"?

The basic solution to this problem is to deploy IPv6 as soon as you can, figure out what problems remain to be solved before you can use IPv6 100% and then put pressure on your ISPs, vendors, etc. to solve these problems. That's how the Internet grew like topsy in the first place, and its not too late to get this going. Two to three years is enough time.

ARIN has published a web site which collects information about how to move to IPv6 here: http://www.getipv6.info/
It's oriented towards the things that ISPs and other service providers (hosting centers, large IT depts) need to do to get IPv6 working in production.

Soon, the stock market analysts will be asking the big ISPs and telecom companies what actions they are taking to avoid going bankrupt in two years when the crunch hits. Any company that can't get new IPv4 addresses will have to stop growing their IPv4 networks. If they have an IPv6 network to take up the slack, no problem. If not, then customers will flock to the providers that have IPv6 ready to roll.

There was a network operator meeting at NANOG recently where they showed that it is almost possible to provide full Internet access, both IPv4 and IPV6, using an IPv6 connection. Yes, I know, "almost" means there were problems, but they were not massive problems. They were the kind of things that people were working on fixing with IPv4 networks back in the early 90's. And they did that because they went ahead and built IPv4 networks and tried to make them work for everything imaginable. When things broke, they fixed the bugs and moved on, eventually becoming the global Internet that we know today.

There is a way to avoid going bust when the address crunch hits in two-to-three years and that is: Get yourself IPv6 Ready!