If people should happen to find themselves forced to use the same equipment 10+ years from now and it's not IP v6 compatible then it will need to sit behind a IP v6 device/infrastructure that Craig_B was mentioning.
The good news is that network equipment for the last few years have already had support for IP v6 built in.
Craig_ B's comments is the right and practical approach. It's sort of like preparing your home for an upcoming storm. Start taking the time now to prepare.
Perhaps do a quick assessment on your infrastructure and see what will need to be replaced. This sort of reminds of the Y2K scare. Not everything needed to be compliant or replaced. I started the Y2K assessment in my infrastructure in mid-1998, put together an assessment and presented to management (along with a plan) so that I could get proper support and funding to address the effected systems in 1999.
In this case, IP v6, it's not as bad as the Y2K thing but it's better to start now.
In addition, I would also speak with your ISP/Circuit provider to learn what their plans are along with their time lines. If your public DNS is hosted by another provider, talk with them too.
Basically start making notes on what IP v6 touches in your infrastructure (internally and public), score it with a severity (ie: N/A, Low, Medium, High, Critical, etc... or use numbers, whatever works for you) and then use it as a road map. It will most likely be a living-dynamic document so don't worry if things change.
HTH ...
