Matthew Kirkland, a network automation engineer at Meta, presents Meta's experience in removing IPv4 addressing from its Edge Network Infrastructure, detailing the motivations, challenges, and future plans. He explains the transition from dual-stack infrastructure to IPv6-only using RFC 5549, highlighting issues encountered with traceroute, internal tooling, BGP policies, ECMP, and vendor inconsistencies. Kirkland also discusses the complexities of implementing v6-only in the peering layer with ISIS and segment routing, and future goals of extending v6-only to the core network. The presentation concludes with a Q&A session, addressing questions about the effort's complexity, IPv4 address conservation, performance differences between IPv6 and IPv4, and potential solutions for unnumbered interfaces.
Sign in to continue reading, translating and more.
Continue