IPv6 Summit 2014: Wells Fargo adopting IPv6
Rocky Mountain IPv6 TaskforceCited 6× on HN, 2021–2025
talk · intermediate · 2021–2025 on HN
Wells Fargo engineers walk through the bank's four-year IPv6 journey at the North American IPv6 Summit 2014. They cover motivation, approach, achievements and observations.
HN cites it in IPv6 threads as an example of a large adopter, especially for address-space collisions after mergers and conflicts in 10/8.
Up next
9 mo on HNHarder Drive: Hard drives we didn't want or need
suckerpinch
12 HN recommender · 2022–2025
9 mo on HNThis Video Is Sponsored By ███ VPN
Tom Scott
9 HN recommender · 2019–2026
6 mo on HNA New Way to look at Networking
Google
6 HN recommender · 2011–2018
6 mo on HNNet Neutrality: Last Week Tonight with John Oliver (HBO)
LastWeekTonight
7 HN recommender · 2014–2017
4 mo on HNCharacters, Symbols and the Unicode Miracle - Computerphile
Computerphile
4 HN recommender · 2014–2025
5 mo on HN8 Frames in 16ms: Rollback Networking in Mortal Kombat and Injustice 2
GDC Festival of Gaming
4 HN recommender · 2020–2025
4 mo on HNA New Way to look at Networking
GoogleTalksArchive
4 HN recommender · 2012–2025
4 mo on HNWhy SpaceX is Making Starlink
Real Engineering
4 HN recommender · 2019–2020
3 mo on HNAWS re:Invent 2015 | (NET403) Another Day, Another Billion Packets
Amazon Web Services
3 HN recommender · 2017–2020
3 mo on HNEmail Hates the Living
m
3 HN recommender · 2015–2022
3 mo on HNRicardo Signes - 闇のEメール伝説
yapcasia
3 HN recommender · 2011–2021
3 mo on HNDefeating Ssl Using Sslstrip (Marlinspike Blackhat)
TheSecurityTube
3 HN recommender · 2014–2018
6 comments from Hacker News
> Not sure why you'd need more than 10/8 Large organizations have moved to IPv6 because they, and everyone else, are using 10/8, and so when mergers and acquisitions happen trying to connect the networks together becomes a nightmare. See this talk from Wells Fargo as an example: * ▶ this video
> I have yet to meet an infrastructure engineer or even hear of one who switched to IPv6 on purpose because they thought it was better. T-Mobile US: * link Wells Fargo: * ▶ this video Microsoft * link * link Google: * link LinkedIn: * link Facebook is famously IPv6-only internally (and as of 2016, 60% of user traffic was over IPv6): * link * link * link
Tell that to T-Mobile US: * link Wells Fargo: * ▶ this video Microsoft: * link * link Google: * link LinkedIn (pre-Microsoft): * link
> 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): * link * link * link Microsoft and Google are IPv6-only single-stack (or moving in that direction) on their internal corporate networks: * link * link * link Also Wells Fargo: * ▶ this video The main 'advantage' IPv4 has is inertia.
> There’s (IMO) a much better reason: so your endpoints can have globally unique addresses. Complications with address space collisions (esp. M&A) was one of the reasons give in this Wells Fargo presentation from 2014: * ▶ this video
> What is the sales pitch you would bring to the CEO of a Fortune 500? When you buy or merge companies, and they both have RFC 1918 addresses, you'll probably have a conflict between the two entities. You'll probably have to implement NAT with-in your own network and hope the two sides don't have to talk to each other that much. (Or you completely re-IP the acquisition.) With IPv6, either the companies will be using their own PI IPv6 space and/or they will be using unique ULA prefixes, so the chance of conflicts will be very small. This at least was one of the business cases for Wells Fargo, "the fourth largest bank in the United States by total assets and is one of the largest as ranked by bank deposits and market capitalization": * ▶ this video