“people's reaction of just disable IPv6 is exactly why IPv6 has not gotten very far. I had hoped that it was getting better when everybody's phone was kind of depending on it to avoid carrier grade NAT, but it seems like we only care about it on the phone and we've not applied any of those lessons to the rest of the internet.”

…wouldn't be as obviously, it's just broken as this. So yeah, this is a very terrible driver feature, which is almost certainly a bug. I don't think there's much value in ever setting that flow label to zero. It's probably trying to do more with it and screwing it up. But that's pretty terrible.

…major network interface manufacturers doing something as bloody Johnson stupid as resetting flow labels to zero. Like Alan said, that's got to be a bug. There's no valid reason for it. And frankly, it strikes me as a very much romper room bug that really never should have made it out of the shop.

know, Alan, you also perhaps accidentally raised another really good question, which is when you've got one tech giant like Intel that's delivering software and software updates via the Windows catalog, which Microsoft controls, at what point does Microsoft step in and take ownership and say, no…

Yeah. And I also wonder how tempted Azure and Amazon and so are to change their load balancer to patch around this problem so that people can at least still use their computers that have this broken software on it, but at the same time, not have to ruin all their load balancing and run around with…

I'm going to guess they weren't very tempted at all to patch around this issue because since it was only IPv6, it was probably only affecting about the third or fourth nine of their traffic.