Well, you're right in how SLAAC assigns addresses, in that a node has the same suffix no matter where it goes. But traffic doesn't get automatically forwarded as you roam between IPv6 networks. (That requires another standard, Mobile IP or Mobile IPv6, to make that happen.)

If you read the 25-page summary looking for hard details on what would happen were an asteroid impact to be inevitable, you might be disappointed. In that case, I would recommend Ben H. Winters' The Last Policeman trilogy. It covers the work of a detective in the months prior to a meteor impact that's presumed to be civilization-ending.

Almost entirely. The client connectivity features (like Export to Excel and Connect to Outlook buttons) still don't work in anything but IE. Everything else seems to be vastly improved, though. Maybe in SP2016...

But what does that say about us? The majority of you (myself included) will be on here until the last day, long after it's Geocitied or MySpaced itself.

Accurate, though most implementations of LSNAT will probably use the now-reserved address space of 100.64/10 rather than one of the well-known private ranges.

(Yes, in the face of IPv4 exhaustion, The Powers That Be burned an entire /10. There must be some IPv6 engineers on that committee.)

I have a Mac, so I created a bunch of writable sparsebundle disk images ranging in size from 10 MB (single-PDF tax returns) to 1 GB (car documentation). I save them all directly to iCloud Drive. When I mount the disk image and make changes, only the changed bands are uploaded, avoiding a bottleneck or incomplete sync situation.

Time Machine keeps versioned backups of the iCloud Drive files on my offline backup disk (as of OS X 10.10.2). Periodically, I copy the disk images into OneDrive and Dropbox for redundancy.

Each disk image has a different password, all of which are secure (long strings of random characters) and managed well (saved on my Mac, as well as printed out and safely hidden in case of total disaster). My cloud accounts all have secure passwords, two-factor authentication, and all my computers have encrypted drives so I'm not out of luck if my computer gets lost or stolen.

For disk images that I know will never be modified again (e.g., Taxes 2003), I convert the disk images to a read-only format to save space in my clouds. I haven't paid a dime for cloud space, ever.

It sounds overkill when I type out the procedure, but because I've used only features built into the operating system, I can scan and archive a document in under a minute. On the other hand, this is complete vendor lock-in, so if I switch my primary computers from OS X down the road, I would have to throw out this entire solution and start a useless Ask Slashdot thread like this.

Hope this helps out any Apple nerds.

Truth be told, I like the look of the beta site. I could read that day in and day out. The comments section has a few nice improvements, but I wish they'd just port the classic comments over and give it the "beta" color scheme. (Also, UTF-8 support, if they haven't coded that already.) This beta is hardly a Windows Vista. At its current state, it's more like Windows Vista SP2 -- usable, but still not everything you'd hoped. Well, excellent karma, it was nice knowing you.

What equipment with 100 MB drives is still in production? Not berating you, just genuinely curious.

To be fair, the iPad has had those same multi-finger gestures for quite some time. For some reason, though, the iPhone never got that feature.

I don't know where you live, but I spoke with a surprisingly-knowledgeable Comcast representative some time ago about the future of IPv6 on their network. They are rolling it out market by market, but unfortunately for me, the northeast and mid-Atlantic states will be one of the last regions to have it activated. Something something legacy equipment up there. She couldn't provide a time frame, though it will definitely be addresses. (Whenever that may be.)

If you do have it enabled, though, your router will get a single IPv6 address. If it's capable of DHCPv6-PD and you left that enabled, you'll wake up one morning to see that IPv6 has magically come to your house.

I know Charter Communications is selling only DOCSIS 3.0 modems now, but that seems to be solely for the speed benefits. However, relevant to the article, there was an extension to the old standard called "DOCSIS 2.0 + IPv6" which does exactly what you think it does. I'm not sure how popular that was, but it does exist.

Well, except for the few remaining white MacBooks. But I do see your point. Apple products aren't typically just a couple plastic housings molded, glued, screwed, or snapped together. They're glass, metal, or whatever else Jony Ive's been playing with lately. When you pick one up, it feels solid, just the right weight... and hopefully, like it's worth the price tag.

And IPv6. Granted, I hate the fact of registering hardware before it will accomplish its intended goals, but if Hardware Manufacturer A fires out 50 million mice without an IPv6 stack, they're just asking for trouble.

Although, if this mouse does support IPv6, I still won't buy one. I'll just laud it for its one non-saving grace.

I don't operate a datacenter, but for virtualized servers in an office, I always enable the NTP server functionality in the hypervisor, have it sync to a stratum-1 time source, then advertise that address via DHCP and DHCPv6 for my guests and workstations (and visiting cell phones) to use. Being the definitive time source, I also tell the hypervisor to automatically set the clock on the guests, then give a virtualized AD domain controller (if any) the PDC FSMO role to set the Windows domain time. I have sites with two or three hypervisors running NTP, and it seems to work well. Not sure if it will scale to your environment, OP, but it may be worth mulling over.

Just using the public IPv6 prefix given out by your router would be easier than setting up your router to hand out unique local addresses, or using link-local addressing and hoping that all of your devices are on the same physical link. Plus, it would make remote management easier, assuming your theoretical iPhone app doesn't communicate with some kind of master gateway device. An argument can easily be made for both sides in this case.