RFC 8950 already lets an IPv4 route name an IPv6 next hop
RIPE Labs, on October 19, describes using RFC 8950 so an interconnection can drop its IPv4 addresses. The standard itself is from November 2020. Both routers have to agree.
The short version
The October 19 note says operators can advertise IPv4 routes with an IPv6 next hop under RFC 8950, then remove the IPv4 session on a link once that works. The RFC, from November 2020, requires both peers to negotiate the capability. It is not a new standard issued today.
The standard is five years old
RFC 8950, published in November 2020, specifies how multiprotocol BGP can advertise IPv4 reachability, or VPN-IPv4 reachability, with a next hop that belongs to IPv6. It obsoletes RFC 5549. The abstract says peers discover the ability with a BGP capability so deployment can be gradual, without a flag day and without black-holing traffic. October 19 did not publish that text. October 19 pointed at it.what RPKI checks on a route.
Agreement is the safety condition
The RFC says the next-hop address family is identified by the field's length, and that both sides must negotiate. A router that sends an IPv6 next hop to a peer that never agreed is outside the procedure. The capability is the document's answer to that mistake. This page will not reprint a packet diagram. The dependency is the agreement, not a sample capture. Asked directly, What is the Euro-IX repository for? A working group on using IPv6 next hops for IPv4 routes at internet exchange points, including route servers. It is a coordination page, not a measurement of how many exchanges have switched.the networking desk.
What the October 19 note adds
André Grüneberg's RIPE Labs article, dated October 19, 2026, says many transfer networks still take an IPv4 address and an IPv6 address, and that an exchange which outgrows its peering LAN faces a renumbering. He writes that current network operating systems mostly implement RFC 8950, so two neighbors can exchange IPv4 routes on their IPv6 session and later remove the IPv4 session and the IPv4 addresses. He points at a Euro-IX working group for compatibility notes.Futureweb.
An exchange is the crowded case
The Euro-IX charter says unused IPv4 space has run out and that a growing exchange may not find a larger IPv4 subnet for the shared LAN. The proposed relief is IPv6 on that LAN, with IPv4 routes still carried. The charter says most of the change sits with members, while the exchange touches route servers and the odd dispute. A charter is a plan of work. It is not a count of members who have moved.Starlink's spectrum filing is a different network.
Forwarding still needs a MAC address
The RIPE note says the router resolves the next hop to a MAC address, using neighbor discovery when the next hop is IPv6, and then forwards as usual. The packet on the wire can still be IPv4. The new fact is which address the routing protocol used to name the neighbor. That is an interconnection fact, not a new address family for a laptop. Asked directly, Does this renumber the public internet's IPv4 routes? No. It changes the next hop on a link where both routers agree. Customer networks can keep IPv4. The scarcity the note describes is the peering LAN, not every address in a household.when one region is the control plane.
What this page will not retire
It will not say IPv4 routes disappeared on October 19. It will not say every vendor implements the RFC, because the note says most current systems do and leaves room for older ones. It will not invent a percentage of exchanges that have dropped their peering IPv4. The documents are the RFC, the RIPE note, and the working-group charter. Asked directly, What does the RIPE note say an operator can remove later? The IPv4 BGP session on that link, and eventually the IPv4 addresses on the link, after the IPv6 next hop is working. The note says the pace is the operator's.
What a later count would change
A list of route servers that advertise the capability, or a peering LAN that publishes its old and new address plans, would turn the note into an adoption story. Until then, the dependency is that the mechanism has a standard, an operator's how-it-fits essay, and a group chartered to try it at exchanges. Asked directly, When was RFC 8950 published? November 2020. It obsoletes RFC 5549. The October 19 RIPE Labs article is an operator's account of using that standard at interconnections, not a new request for comments.
A previous RIPE essay is not this one
An older RIPE Labs piece, from 2025, described a test autonomous system that uses IPv6 next hops for IPv4. The October 19 article cites that line of work and turns it toward exchange interconnection. They are related notes by the same community. They are not the same page, and this brief files the later one. Asked directly, What do the peers have to negotiate? The extended next-hop capability, so both sides agree before IPv4 routes are sent with an IPv6 next hop. The RFC says the capability is there so there is no flag day and no silent black hole.
What stays on the record
RFC 8950, November 2020, a negotiated capability, an October 19 operator's account of removing IPv4 from a link after the IPv6 next hop works, and a Euro-IX group aimed at exchanges. The address that goes away, if it goes away, is the one on the interconnection, not the customer's. The short answer this page will stand on is this: The October 19 note says operators can advertise IPv4 routes with an IPv6 next hop under RFC 8950, then remove the IPv4 session on a link once that works. The RFC, from November 2020, requires both peers to negotiate the capability. It is not a new standard issued today.
Sources
The reports this brief is filing. Futureweb did not republish them.
Questions
When was RFC 8950 published?
November 2020. It obsoletes RFC 5549. The October 19 RIPE Labs article is an operator's account of using that standard at interconnections, not a new request for comments.
What do the peers have to negotiate?
The extended next-hop capability, so both sides agree before IPv4 routes are sent with an IPv6 next hop. The RFC says the capability is there so there is no flag day and no silent black hole.
What does the RIPE note say an operator can remove later?
The IPv4 BGP session on that link, and eventually the IPv4 addresses on the link, after the IPv6 next hop is working. The note says the pace is the operator's.
What is the Euro-IX repository for?
A working group on using IPv6 next hops for IPv4 routes at internet exchange points, including route servers. It is a coordination page, not a measurement of how many exchanges have switched.
Does this renumber the public internet's IPv4 routes?
No. It changes the next hop on a link where both routers agree. Customer networks can keep IPv4. The scarcity the note describes is the peering LAN, not every address in a household.