Hacker News new | ask | show | jobs
by throw0101a 69 days ago
Facebook is (AIUI) 100% IPv6-only on their internal network, and has been for many years:

* https://engineering.fb.com/2017/01/17/production-engineering...

* https://www.internetsociety.org/blog/2014/09/facebook-launch...

IPv4 is actually the "leftover" stuff they have to deal with at the front end.

But they are an eye-balls heavy service, with a lot of mobile devices, which also tend to be IPv6-native.

2 comments

It also just takes actual policy will. Somebody has to actually say "No" when the supplier who promised an IPv6 product says afterwards actually they meant IPv6 "ready" and they should have put an asterisk because really only the next version will be "ready", and er, so the product they've delivered doesn't actually work with IPv6 but that's fine right?

"No". Not every human is psychologically prepared to do that. They want to acquiesce, to go along to get along, you need somebody to be firm. "No".

I have found that it is incredibly satisfying to whip out the “no” card.

I have also found that an uncomfortable number of people do not consider it appropriate in any way shape or form. Even when it’s ultimately your call and no one else’s.

Folks don’t really like waves. They like looking at them from the shore, but freak out when it’s their turn to hang 10

Suppliers doing that kind of trick is what really killed GOSIP, and why the new v6 mandates in USGOV do not allow waivers for vendors, only for individual specific use cases
Just wait until someone starts remembering the other archaic terms like ‘fraud’, ‘indictment’, etc.
From my time there, this is for the internal prod network. Corporate networking was dual stack (which was pretty useful because it was common for v4 or v6 to break, but usually not at the same time)