4 ms·

IPv4 is like legacy code that got extended and dependencies added. Everybody is using it, because everybody is kind of comfortable with it and it mostly works/

IPv4 is like legacy code that got extended and dependencies added. Everybody is using it, because everybody is kind of comfortable with it and it mostly works/ people know all the workarounds for its quirks. IPv6 is like the same code with a major refactor. One of the big unwieldy databases (NAT) was dropped because it turns out you don't need it if the system is smarter overall. Also, autoconfiguration works reasonably well now. For most usecases the subnetting also got much easier as you can just slap a /64 on any realistic network without hesitation. You just have to do a relatively small step to use it.

sebazzz 3y ago
NAT is more like the add-on that most network operators don’t decide to employ for IPv6-only networks anymore, but NAT by itself is not part of IPv4. You can NAT IPv6 networks perfectly fine - but for IPv4 it is often a necessary evil when private network ranges overlap or you need to represent a single IP to the outside world.
pif 3y ago
You are describing the client point of view. But, from the server point of view, IPv6 is like a newer, better version... that cannot run alone! IPv6 can work side by side with IPv4 on the servers, but it cannot replace IPv4. Thus, don't act surprised when companies wonder "Why bother?"!
- kaliszad 3y ago
  You can run "IPv6-mostly". https://news.ycombinator.com/item?id=40039899 https://news.ycombinator.com/item?id=40039899
- throw0101c 3y ago
  > IPv6 can work side by side with IPv4 on the servers, but it cannot replace IPv4. Facebook is famously IPv6-only internally (and as of 2016, 60% of user traffic was IPv6-only): * https://www.internetsociety.org/resources/deploy360/2014/case-study-facebook-moving-to-an-ipv6-only-internal-network/ https://www.internetsociety.org/resources/deploy360/2014/cas... * https://engineering.fb.com/2017/01/17/production-engineering/legacy-support-on-ipv6-only-infra/ https://engineering.fb.com/2017/01/17/production-engineering... * https://www.youtube.com/watch?v=lU_24f6Wr7E https://www.youtube.com/watch?v=lU_24f6Wr7E Microsoft and Google are IPv6-only single-stack (or moving in that direction) on their internal corporate networks: * https://www.arin.net/blog/2019/04/03/microsoft-works-toward-ipv6-only-single-stack-network/ https://www.arin.net/blog/2019/04/03/microsoft-works-toward-... * https://www.youtube.com/watch?v=nd0vgU6WbPo https://www.youtube.com/watch?v=nd0vgU6WbPo * https://www.youtube.com/watch?v=hb98hAb5_W8 https://www.youtube.com/watch?v=hb98hAb5_W8 Also Wells Fargo: * https://www.youtube.com/watch?v=EzTWjNUb4H4 https://www.youtube.com/watch?v=EzTWjNUb4H4 The main 'advantage' IPv4 has is inertia.
  - pif 3y ago
    > The main 'advantage' IPv4 has is inertia. That's correct, but it was an idiocy to underestimate it. Reality always wins.

sebazzz 3y ago

NAT is more like the add-on that most network operators don’t decide to employ for IPv6-only networks anymore, but NAT by itself is not part of IPv4. You can NAT IPv6 networks perfectly fine - but for IPv4 it is often a necessary evil when private network ranges overlap or you need to represent a single IP to the outside world.

pif 3y ago

You are describing the client point of view. But, from the server point of view, IPv6 is like a newer, better version... that cannot run alone! IPv6 can work side by side with IPv4 on the servers, but it cannot replace IPv4. Thus, don't act surprised when companies wonder "Why bother?"!

kaliszad 3y ago
You can run "IPv6-mostly". https://news.ycombinator.com/item?id=40039899 https://news.ycombinator.com/item?id=40039899
throw0101c 3y ago
> IPv6 can work side by side with IPv4 on the servers, but it cannot replace IPv4. Facebook is famously IPv6-only internally (and as of 2016, 60% of user traffic was IPv6-only): * https://www.internetsociety.org/resources/deploy360/2014/case-study-facebook-moving-to-an-ipv6-only-internal-network/ https://www.internetsociety.org/resources/deploy360/2014/cas... * https://engineering.fb.com/2017/01/17/production-engineering/legacy-support-on-ipv6-only-infra/ https://engineering.fb.com/2017/01/17/production-engineering... * https://www.youtube.com/watch?v=lU_24f6Wr7E https://www.youtube.com/watch?v=lU_24f6Wr7E Microsoft and Google are IPv6-only single-stack (or moving in that direction) on their internal corporate networks: * https://www.arin.net/blog/2019/04/03/microsoft-works-toward-ipv6-only-single-stack-network/ https://www.arin.net/blog/2019/04/03/microsoft-works-toward-... * https://www.youtube.com/watch?v=nd0vgU6WbPo https://www.youtube.com/watch?v=nd0vgU6WbPo * https://www.youtube.com/watch?v=hb98hAb5_W8 https://www.youtube.com/watch?v=hb98hAb5_W8 Also Wells Fargo: * https://www.youtube.com/watch?v=EzTWjNUb4H4 https://www.youtube.com/watch?v=EzTWjNUb4H4 The main 'advantage' IPv4 has is inertia.
- pif 3y ago
  > The main 'advantage' IPv4 has is inertia. That's correct, but it was an idiocy to underestimate it. Reality always wins.