impeachment yes, assassination no

wow, site goes down right as its being discussed....

If you're relying on RAs or DHCPv6 for server networks then you have bigger problems, not unlike rogue DHCP servers in IPv4.

It would be more constructive to use whatever energy needed to pressure legacy IPv4 holders to give-up their space to start planning a move to v6 or at least a dual-stack architecture. This is like people complaining there's still momentum left in the cassette tape when CDs have been around for years. Postponing the inevitable doesn't stop the inevitable from happening.

already done my friend

Not a answer to your question per se, but I ran into a very similar problem when I moved to a new apartment 2 years ago. Rather than upgrade everything to 802.11n (and suffer the whole issue of too many wireless cooks in the pot as everyone now has their own access point) I got two Homeplug v2 adapters and moved my router to my office. Cable modem connects to my coax, which is then plugged into a Homeplug. The 2nd Homeplug then goes to the WAN interface on my house router. Works like a charm and I can still use wired connections for all my workstations.

Just a thought. I would have considered the 802.11n route but there's way too much activity in my area to make that feasible for 8+ machines (my 802.11g access point does work well for the 2-3 wireless devices I use regularly though, especially now that my access point is in my office and spaced further away from my neighbors' APs).

To be fair, it isn't mentioned anywhere in the pamphlet you receive with the iPhone or iPod, its buried within the iTunes website terms-and-conditions (at least last time I checked). If there were a warning label you had to pull-off each new iDevice I'd be right there with you, but you really have to look for it to find the iTunes lockout timeout (at least you did before this story broke).

That being said I'm generally not a believer of ignorance-as-a-defense, but I can certainly see why Apple would change this behavior and why the FTC would look into it.

No its not, its providing an ALTERNATIVE to what might become bad behavior.

VoIP over mobile is an entirely different beast than VoIP over wireline. The OP is right, there's a lot of kinks to be worked-out yet, particularly surrounding jitter/bufferbloat.

Don't know about you, but I got my 2.3 OTA update last week :)

Then again, I bought the phone straight from Google

My Android phone does all these, and is ARM-based.

Most modern religions did exactly this with the same core tenants a LONG time ago.

three drums and a cymbal fall off a cliff

To computer security geeks, PCI is and always will be the ...what are you doing Dave? ...this is highly irregular

You don't, by any chance, work for the Marketing Division of Sirius Cybernetics do you?