IPv6 Summit 2014: Wells Fargo adopting IPv6

Channel:Rocky Mountain IPv6 Taskforce · Length:56:57 · Published:2015-10-08 · Views:240

Watch on YouTube

Summary

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.

Why HN recommends it

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.

See this talk from Wells Fargo as an example — HN, 2025

Networking & internet infrastructure · Systems & security (other)

Subtitles (excerpt)

alright so it's my privilege to introduce you guys to John Burns into a Wayne Smith from Wells Fargo Wells Fargo has done a great job of implementing ipv6 within their network and it's another one of those great success stories right one of the major themes and in in this conference this year has been putting ipv6 to work and we've really tried to showcase some really great scenarios where people have been successful deploying ipv6 in finding some rocky roads in in the middle and it certainly Wells Fargo is going to talk a little bit about that today so I'd like to introduce John Burns John's is a network engineer and architect with over 20 years of experience in designing and deploying large-scale networks at financial institutions and that's no small task as you all know these include First Union wachovia bank of america and wells fargo he currently leads the design for secure connectivity in network foundational services within the infrastructure architecture team at Wells Fargo he includes his role as lead architect for ipv6 he holds ccie 2357 so he's been there for a long long time and has served on the cisco ipv6 deployment council and enterprise technical advisory board in the I Triple E

On 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: * [VIDEO] — throw0101b, 2025-07
> 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: * [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] — throw0101c, 2024-04
Tell that to T-Mobile US: * [LINK] Wells Fargo: * [VIDEO] Microsoft: * [LINK] * [LINK] Google: * [LINK] LinkedIn (pre-Microsoft): * [LINK] — throw0101c, 2024-04
> 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: * [VIDEO] The main 'advantage' IP… — throw0101c, 2024-04
> 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: * [VIDEO] — throw0101b, 2023-11

Related videos