Seriously? People that use such easy to guess (and therefore pointless) shouldn't even have access to anything that needs protection...

Pfffft. You ever worked for a Director/VP or higher? Try telling them how to set their passwords. I've seen "boss", "super" and other motivational-poster-worthy simple words. And they want everything to auto-login. One of the last major worm outbreaks I encountered originated in the senior executive offices.

Okay, that was a few years ago. Maybe that company has learned a few things since then.

Um, even Win2k had IPv6 downloadable. WinXP just needs it turned on. Vista an 7 have it on by default and will use it for file sharing and terminal services.

Outside of ISP availability and SOHO router support, the only current stumbling blocks with IPv6 are programs that try to store IP addresses and haven't been updated to store IPv6 addresses. Programs that use or store host names and use the OS'es name resolution work fine as-is.

Having IPv6 to the router and IPv4 behind it doesn't make a lot of sense. Layer 2 and client IPv6 really isn't a problem.

But no, IPv4 isn't going away soon. Dual-stack will be a reality for at least a few years, probably 10-20.

Aside from IPv4-only servers, the biggest stumbling block to ditching IPv4 entirely (once IPv6 is ubiquitous) is that there is no PXE boot for IPv6 yet. Will somebody please develop that and start getting it into boot firmware?

Plus wastage due to subnetting (network address, broadcast etc)...
Imagine trying to segment a network of that size, and then trying to keep track of what was in which segment etc... Would be quite a nightmare.

Allow me to point out a couple of IPv6's features for you:

- IPv6 is designed to be hierarchical, so knowing the location of a segment will be easier than IPv4. Each /64 is routed under a matching /48, which is under a /32, etc..

- All subnets should be /64's

- IPv6 does not use broadcast IPs. It has various multicast addresses with the prefix ff00:/8 to address the link-local domain (~=broadcast), site-local domain, etc.

- Don't think of "wastage". By design every subnet should be a /64. The host address is intended to be globally unique, so there are 2^63 available globally-unique host addresses that by design can move to another prefix and still be unique within that prefix. If you don't want to use a globally unique ID, there are also 2^63 non-globally-unique IDs, and for example prefix::1 is one of them. By your thinking the IPv6 waste is colossal, but it's not waste, it's a design feature which allows hierarchical routing and collision-free merging of subnets.

- Routers need not take up a public IPv6 address if you're that desperate for space (which you aren't, I promise). All IPv6 hosts have a link-local address (think 169.254.0.0/16, but always there), and the router can advertise a route on the link-local address

I switched to JaguarPC for an unmanaged Debian VPS after my old provider had my VPS down 5 days, didn't communicate with me well and ultimately never got my VPS and data back. (I kept my own backups, luckily.) JaguarPC had a special running and had been in business 10 years at the time, so I gave them a try. Never a problem. 3 years later they upgraded my resources and lowered my fee, and did it without having to restart my VPS. I once got an email that they were experiencing a DDoS attack that might affect me and pointed me to a website with running updates, but it didn't seem to affect me. Much better service than I had before and have seen with my friends' providers who would have issues, look at the status page and get a false "everything is fine!" message. I'm about to leave them to self-host at home, so I wrote them a thank-you blog singing their praises.

Unfortunately, after you program it you no longer know where it is.

Crap, how would I pay for prostitutes?

On the other hand, I just wrote two checks to family (um, not for services previously mentioned in this post). It seems like there should be a way to wire/ACH funds between individuals.

Then again, there are certain places (besides prostitutes) I would not trust with the information necessary to debit my accounts.

djbdns is a collection of programs. The 512B limit doesn't apply to all of them. The resolver dnscache would be the program of concern in this context, and it can both request and serve requests over 512B on TCP in the default build. I am currently using other resolvers for IPv6 reasons, but I don't expect dnscache to have a problem with DNSSEC on the root servers.

Oh no, not again...

Some clients may erroneously think they have working IPv6, get an AAAA address and timeout trying to use it before falling back to IPv4. This really annoys users. It wouldn't be Google's fault that this happens, but their sites would be perceived as very slow and they'd lose users.

It is not clear to me exactly what they're doing. They might be whitelisting networks and not individual resolvers. If so then your home resolver may work when your ISP signs up with them.

Short answer: No problem. You will have many addresses to use in your LAN, and your packets will not enter the internet to go to a local file server.

Slightly longer explanation: IPv6 routing is quite similar to IPv4 routing. I think you might be misunderstanding what is keeping your current local traffic from bouncing over the WAN link.