Yeah, that turned out to be one of the big problems with IPv6 address aggregation - sounds great in the ivory tower, doesn't meet the needs of real customers, which is too bad, because every company that wants their own AS and routable address block is demanding a resource from every backbone router in the world.

IPv6's solution to the problem was to allow interfaces to have multiple IPv6 addresses, so you'd have advertise address 2001:AAAA:xyzw:: on Carrier A and 2001:BBBB:abcd:: on Carrier B, both of which can reach your premises routers and firewalls, and if a backhoe or router failure takes out your access to Carrier A, people can still reach your Carrier B address. Except, well, your DNS server needs to update pretty much instantly, and browsers often cache DNS results for a day or more, so half your users won't be able to reach your website, and address aggregation means that you didn't get your own BGP AS to announce route changes with, but hey, your outgoing traffic will still be fine.

My back-of-a-napkin solution to this a few years ago was that there's an obvious business model for a few ISP to conspire to jointly provide dual-homing. For instance, if you've got up to 256 carriers, 00 through FF, each pair aa and bb can use BGP to advertise a block 2222:aabb:/32 to the world, and have customer 2222:aabb:xyzw::/48, so the global BGP tables get 32K routes for the pairs of ISPs, and each pair of ISPs shares another up-to-64K routes with each other using either iBGP or other local routing protocols to deal with their customers actual dual homing. (Obviously you can vary the number of ISPs, size of the dual-homed blocks, amount of prefix for this application (since :2222: may be too long, etc.)

IPv6 was originally supposed to solve a whole lot of problems - not only did it have longer addresses (which ISPs need to avoid having to deploy customers on NAT, and in general to avoid running out of address spaces and crashing into the "Here Be Dragons" sign at the edge), but it was also supposed to solve a whole lot of other problems, like route aggregation, security, multihoming, automatic addressing, etc.

A lot of that turned out to be wishful thinking, e.g. the hard part about IPSEC tunnels is the key exchange and authentication, not building the tunnels, route aggregation didn't really work out because enterprises weren't willing to use carrier addresses instead of their own, and small carriers also wanted their own addresses instead of sharing their upstream's address space, or if it wasn't wishful thinking, it was addressing problems that IPv4 found other solutions for, like DHCP for automatic addressing.

And while NAT is a hopeless botch, it does provide a simple-minded stateful firewall as default behaviour, while IPv6 users need explicit firewalling to get the same security with real addresses (which they needed to do anyway, but especially if you're using tunnels, you have to be sure to put it in all the right places.

Back when I was closer to the ISP business, the general plan of most consumer ISPs was to start supporting IPv6 (once they had all their hardware and operations support systems able to manage it - it's amazing how many moving parts there are), and migrate most users to dual-stack, with NAT for IPv4 plus native IPv6, or else to use NAT IPv4 with tunneled IPv6.

Comcast may have lots of other issues as an ISP, such as banning customers from running server at home, and monthly usage caps (if they still do that), but they were ahead of most other US consumer ISPs on taking IPv6 seriously.

(My ISP supports IPv6 over tunnels, but doesn't run native dual-stack, at least on telco DSL. And I really should get around to actually trying it out, but I haven't...)

Anonymous Coward was asking if the "old SATA drives" referred to old SSD drives that use SATA (which wouldn't be too surprising if it were almost as fast), or old rotating hard disks that use SATA (which would be really surprising to find it faster than SSD.) Google results for the X25-m say yes, it's an SSD, just a bit older one that uses SATA instead of PCIe.

The original material talked about salaries and job titles; it didn't say how much investment it took to develop the skills to get those titles. Some of those skills are things you can add quickly; others take a long time or access to appropriate work environments. (For instance, learning PHP is quick, and Ruby on Rails isn't that hard either. But while you can learn SQL and MySQL pretty quickly, becoming a DBA really needs access to real-world databases and workloads that you're involved in administering.)

I started playing with Arduinos a couple of years ago. You ordered them by mail order at the time. Eventually Radio Shack started carrying them, which made it easier for anybody to pick one up (and while I live in Silicon Valley, if I needed a few resistors or LEDs or simple components to go with them, it was often easier to stop at Radio Shack than Fry's or mailorder.) Now they're fighting over the name, and Radio Shack is going out of business.

Typically the booth babe at RSA's booth at the RSA show is Rivest (I don't think I've seen Shamir or Adleman there.) Usually he's been working on something interesting and is having fun showing it off, but he's also there for fanboi value.

They were a really clear indicator that the occasional companies that hired them seriously didn't understand their audience, and hadn't brought anybody who knew anything technical to their booth, probably not even any marketing people who understood the product, so you could pretty much skip them, because they were pretty much always useless as well as unprofessional.

On the other hand, you can totally bribe us with chocolate or especially coffee, and we might sit through your silly magician act for a raffle ticket for an iThing as long as there was technical content at your booth, and we'll pick up blinky tchotchkes with your logo on them. The woman I'd rather talk to at your booth is the one who developed the cool product, or can explain it well.

When my company's been at trade shows in the area, about half their staff are booth-running professionals, rather than product-related, from the people who set the thing up and make sure all the marketing content is there to the people who herd customers in, figure out what they're interested in (even if it's just at the buzzword level), bring them over to the right part of the booth or find the right person if they need to, scan your contact info, get the speakers on and off the stage, etc., and about half are either main-office or local people who know something about whatever we're trying to sell. They seem to do a good job on the mechanics of it (I've occasionally ended up as local booth staff), and they're seriously good at respecting the audience.

They're the ones over in the NSA booth, showing off the cool Enigma machine, and handing out other spook agency trinkets. Sometimes other groups of Feds are there (Homeland Security or whoever), and they don't understand that, unlike the NSA who are evil but cool, they're evil but not cool.

Never did - here's the Wikipedia about the Indiana Pi Bill. The crackpot proposed a bill that would acknowledge his collection of R33lY k3wl mathematical discoveries and let Indiana schools teach them free (in return for royalties from other user, if I'm reading it right), it snuck past the Indiana House, and a Professor Waldo told the Indiana Senate how bogus it was. It was close to passing there anyway, but one senator pointed out that it's not the Senate's job to establish mathematical truth. And now you know Where Waldo Was.

Back in the 60s, my father-in-law ran a weekly paper in his small town. It eventually got shut down by the police on some bogus excuse; the actual reason was that he wasn't just writing that the mayor was taking bribes, but had the bad taste to say who they were from and what for. Corruption does also exist in the US, and so does censorship. (I didn't see much censorship when I lived in New Jersey, though - just corruption.)

The Iraqis got their chemical weapons from the US for use against Iran. The US still hasn't destroyed their own CBW program products (though they do occasionally retire old unstable chemical weapons, as they've done recently.)

And both the US and Russians still have their hoards of smallpox, pretending they need to keep them to develop vaccines in case the other side uses theirs to attack, even though cowpox ("vaccinia") is good enough for a vaccine and not good enough for a weapon.

Pakistan has nuclear weapons (and India has the Mahatma Gandhi Memorial Nuclear Bombs as well), but aside from their border conflicts around Kashmir (for which the nukes make war less likely but more risky), their big invasion problem is non-governmental forces like Taliban, for whom nukes are really no use at all.

And Israel, of course, has the bomb (probably also the hydrogen bomb), but you're not allowed to say that in discussions about whether Iran can make one also. Wouldn't be a total surprise if the Saudis had it too.

When I'm talking on the phone, the timer for the screen-lock should NOT be running. I frequently have calls that last more than 15 minutes, often set the phone down and use headphones during the call, and it's really annoying that after I hang up, the phone's locked. (If somebody else calls me when me phone's locked, locking when the call's done is fine, but not when I'm the one who made the call or the phone was unlocked when the call came in.)

I'm running 4.4.2 on a Samsung. The phone is provided by $DAYJOB, so they specify which locking options are available (face-unlock isn't), but otherwise it's pretty vanilla. The code used to require 8 digits, now it seems to be text-input instead; both require me to put on my reading glasses to unlock the phone, especially because the numerical unlocker was really bad at touch-screen control, so I had to look at every digit I pressed and count how many actually got detected. Keypress beeps help, unless you're trying to unlock the phone after silencing it, which I often do, but those have a non-zero time lag after the keypress before it notices it should beep, and you can't always tell 1 beep from N beeps. I can now use Swype, which I couldn't when the requirement was all-digits, but it's not much of an improvement since my password isn't a dictionary word, though I suppose I could set it to "qwertyuiop" or "asdfghjkl".