Exploring RFC8950:
Insights from the Working Group Chairs
39th Forum Prague: Shaping the Future Blog - 20 November, 2023 | Published - 09 July, 2024
The Internet's evolution is marked by continual adaptation and innovation, ensuring that its infrastructure can support an ever-increasing amount of data and the growing number of connected devices. One such innovation is the transition to using IPv6 next-hops for IPv4 routes at Internet Exchange Points (IXPs), a shift outlined in RFC8950. In response to the recognized need for a deeper exploration of this technology, the RFC8950 Working Group was established. Led by chairs André Grüneberg (BCIX) and Aleksi Suhonen (TREX), this group is addressing the challenges and opportunities presented by this transition.
1. Given the transition to using IPv6 next-hops for IPv4 routes at IXPs as outlined by RFC8950, what are the main technical challenges you foresee in implementing this at scale across various IXPs, and how is the working group planning to address these?
The main technical challenge is the proper interworking of all BGP routers in use by IXP members. Like with all other standards, vendors usually move upon customer requirements. Considering product life-cycle it takes a few years from customer request to full implementation in the field. Luckily IXP members are usually more open to technical novelties (e.g. IPv6 uptake is higher than in enterprise networks). As it stands, IXP members can use RFC8950 today - in bilateral BGP sessions. To make the deployment scale, IXP will need to support RFC8950 on their route servers. This will require some changes to the tool chain and relevant amounts of testing. The same is true for network operators who will also need to adapt their tool chain. The working group members are engaging with network operators, vendors, developers and IXPs to spread awareness of the feature and to help with the implementation.