IPv6 Summit 2014: Wells Fargo adopting IPv6
Rocky Mountain IPv6 TaskforceCited 6× on HN, 2021-2025
237 views · 11 years ago · talk · dated
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.
52:31T-Mobile’s path to IPv6 Only
Rocky Mountain IPv6 Taskforce
2K views • 9 years ago
28:21T-Mobile's journey to IPv6
NANOG
1K views • 8 years ago
1:12:47The benefits of deploying IPv6 only
NANOG
9K views • 11 years ago
1:21:16A New Way to look at Networking
Google
52K views • 19 years ago
1:01:39NYCBSDCon 2014: Serving one-third of the Internet via FreeBSD
BSDTV
14K views • 12 years ago
42:26AWS re:Invent 2015 | (NET403) Another Day, Another Billion Packets
Amazon Web Services
55K views • 11 years ago
18:51IPFS Alpha Demo
Juan Benet
272K views • 11 years ago
7:06Putting Google's Network to work for You
Google for Developers
23K views • 12 years ago
1:19:06Netdev 0x16 - Keynote: It's Time to Replace TCP in the Datacenter
netdevconf
5K views • 3 years ago
1:05:24Susan Crawford on Captive Audience: The Telecom Industry & Monopoly Power in the New Gilded Age
Berkman Klein Center for Internet & Society
11K views • 13 years ago
47:18OpenFlow @ Google - Urs Hoelzle, Google
Open Networking Summit
47K views • 14 years ago
1:21:16A New Way to look at Networking
GoogleTalksArchive
26K views • 14 years ago
1:21:20A New Way to look at Networking
Google TechTalks
30K views • 19 years ago
28:31Velocity 2010: James Hamilton, "Datacenter Infrastructure Innovation"
O'Reilly
9K views • 16 years ago
34:42Jared Mauch - Getting Fiber To My Town (NLNOG Live! September 2020)
NLNOG
26K views • 6 years ago
46:23High Volume, Bandwidth Heavy Infrastructure On The Cheap - Kyle Drake
PDX Node
1K views • 9 years ago
48:47Massscanning the Internet - Defcon 22 (2014)
vissago
109K views • 12 years ago
47:51AWS re:Invent 2014: AWS Innovation at Scale with James Hamilton (SPOT301)
Amazon Web Services
70K views • 11 years ago
48:45Matrix 2.0 — How we're making Matrix go voom!
Matrixdotorg
16K views • 3 years ago
40:04ONS 2015: Wednesday Keynote - Amin Vahdat
Open Networking Summit
32K views • 11 years ago
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
> 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.
Tell that to T-Mobile US: * link Wells Fargo: * ▶ this video Microsoft: * link * link Google: * link LinkedIn (pre-Microsoft): * link
> 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
> 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