Quote:
hah, tell me about it. thanks. hows the recertification going?
Slow, stalled. My goal has been two fold, get up to date and re-certify in the process. So I have spent the last 4 weeks getting "real world" comfortable with IPv6. It is a big change from the current and will be common place sooner rather than later, we will run out of Internet IP's using the IPv4 standard in about 250 days. So I am pretty comfortable now, have it running at home, and feel comfortable setting it up for a production business.
I kind of expect by this time next year if your presence on the Internet does not support IPv6 you will be left behind. It becomes a self powering cycle, some popular new service, app, site only runs on IPv6, so people start demanding IPv6 from their service providers, more people only get IPv6 so more sites support IPv6.
Many of the big boys have already made the shift, Google, Youtube, Facebook, etc, etc all already have IPv6 access.
The "OMG" moment for me was finding out that MS is ahead of the game for IPv6 deployment compared to Linux. MS has a everything in place, ready to use, easy to use, well documented, while Linux has the tools, its not what I would call "ready for prime time", e.g. DHCPv6 is standard in Win2K8 server, but to get the version that fully supports IPv6 on Linux you have to compile it from source code because the prepackaged "stable/trusted" version doesn't support IPv6, and good luck in finding detailed instructions on configuration or working examples. Oh and the Linux version can't do both at the same time, while the MS server can. Sad.