That's a good point Itojun, I agree. It's the seamless movement to IPv6 over a period of time that is important. The user or client shouldn't have to worry about the background technology. At the moment, I only have the Apache 2.xx at http://ruby.chalmers.com.au listening on the IPv6 port. However, the server 'ruby' has both A and AAAA records. Once I am satisfied with it's operation, well, as far as Apache is concerned, then I'll open the 4bone port to Apache as well.
Once I am happy that all is running well, I'll set up a robust production server (ruby is only for experiments) and run virtual hosts on it as well. Serving both IPv6 and IPv4 users. Over the next few years it will be interesting to see what movement there is away from the 4bone to the 6bone. I'd really like to have the program Shoutcast Server (www.shoutcast.com) able to run on the 6bone, able to listen to IPv6 addreses, but the authors aren't answering me :-) I believe that as applications that are mainstream increase in availability, more people will want to move across, even if it's only initially running dual-stack. > > it depends on how you run your IPv4/v6 servers. for instance, we are > running ftp.iij.ad.jp, one of the most famous anonymous ftp server in > Japan, dual-stacked. this is because we think it robust enough. That's what it's all about. Robustness. And that takes management. > > - "AAAA" record for www.iij.ad.jp points to another one, which NFS- > mounts the data partition from IPv4 one. interesting idea... > we do monitor them closely, and they have impressive uptime. cheers Robert Quantum Radio --------------------------------------------------------------------- The IPv6 Users Mailing List Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
