# Worth Reading: BGP Unnumbered in 2025

DevFeed: [Worth Reading: BGP Unnumbered in 2025](<https://devfeed.tech/articles/worth-reading-bgp-unnumbered-in-2025-11176.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2025/04/worth-reading-bgp-unnumbered-2025/>)

Published: 2025-04-24T06:06:00Z

Content type: article

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [BGP](<https://devfeed.tech/topics/bgp.md>), [interoperability](<https://devfeed.tech/topics/interoperability.md>), [datacenter](<https://devfeed.tech/topics/datacenter.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [interoperability](<https://devfeed.tech/tags/interoperability.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>), [worth-reading](<https://devfeed.tech/tags/worth-reading.md>)

## AI overview

The article recommends a post about BGP Unnumbered implementations on Nokia, Juniper, and Bird. It highlights an interoperability issue involving RFC 8950, RFC 2545, and the requirement for a global IPv6 next hop in BGP updates when EBGP runs on interfaces without global IPv6 addresses.

## Source excerpt

Gabriel sent me a pointer to a blog post by Rudolph Bott describing the details of BGP Unnumbered implementations on Nokia, Juniper, and Bird. Even more interestingly, Rudolph points out the elephant I completely missed: RFC 8950 refers to RFC 2545, which requires a GUA IPv6 next hop in BGP updates (well, it uses the SHALL wording, which usually means "troubles ahead"). What do you do if you're running EBGP on an interface with no global IPv6 addresses? As expected, vendors do different things, resulting in another fun interoperability exercise. Read more ...