--- title: BGP Labeled Unicast Interoperability Challenges «... description: BGP Labeled Unicast (SAFI-4) has serious interoperability problems across vendor implementations. RFC 8277 Section 5 explicitly acknowledges that different... canonical: https://daily.dev/posts/bgp-labeled-unicast-interoperability-challenges-ipspace-net-blog-uobzbohjm twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: BGP Labeled Unicast Interoperability Challenges « ipSpace.net blog | daily.dev og:description: BGP Labeled Unicast (SAFI-4) has serious interoperability problems across vendor implementations. RFC 8277 Section 5 explicitly acknowledges that different... og:url: https://daily.dev/posts/bgp-labeled-unicast-interoperability-challenges-ipspace-net-blog-uobzbohjm og:image: https://api.daily.dev/og/posts/UObzBohjM.png og:image:alt: BGP Labeled Unicast Interoperability Challenges « ipSpace.net blog og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # BGP Labeled Unicast Interoperability Challenges « ipSpace.net blog **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 3 min read · 0 upvotes · 0 comments ## Summary BGP Labeled Unicast (SAFI-4) has serious interoperability problems across vendor implementations. RFC 8277 Section 5 explicitly acknowledges that different implementations handle the coexistence of SAFI-1 (unlabeled) and SAFI-4 (labeled) routes in incompatible ways: Arista EOS treats them as independent ('ships in the night'), while Cisco IOS treats them as comparable and selects one best route. Cisco IOS also auto-converts between SAFI-1 and SAFI-4, a capability not easily replicated on Arista EOS. RFC 8277 itself warns that these differences may make interoperability difficult or impossible in multi-vendor deployments. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do Cisco IOS and Arista EOS differ in handling BGP SAFI-1 and SAFI-4 routes on the same session? Arista EOS treats SAFI-1 and SAFI-4 routes as completely independent ('ships in the night'), maintaining both simultaneously. Cisco IOS treats them as comparable and selects a single best route — either SAFI-1 or SAFI-4, not both. Cisco IOS also automatically converts between SAFI-1 and SAFI-4 routes; no equivalent knob exists on Arista EOS. _Network engineers building multi-vendor BGP-LU fabrics track vendor behavior gaps like this on daily.dev._ ### What does RFC 8277 say about interoperability between SAFI-1 and SAFI-4 BGP routes? RFC 8277 Section 5 explicitly warns that different implementations handle coexisting SAFI-1 and SAFI-4 routes for the same prefix in incompatible ways, and that these differences may result in unexpected behavior or lack of interoperability. In some cases, it may be difficult or impossible to achieve desired policies with certain implementations or combinations of implementations. _Architects evaluating BGP Labeled Unicast for multi-vendor networks follow standards developments like RFC 8277 on daily.dev._ ## Similar posts on daily.dev - [Multivendor SR-MPLS « ipSpace.net blog](https://daily.dev/posts/multivendor-sr-mpls-ipspace-net-blog-qekokwduk) · ipSpace.net Blog · 0 upvotes · 0 comments - [The Never-Ending IPv6 Loopback Prefix Saga « ipSpace.net blog](https://daily.dev/posts/the-never-ending-ipv6-loopback-prefix-saga-ipspace-net-blog-4nlhgh10l) · ipSpace.net Blog · 0 upvotes · 0 comments - [BGP-Free Core with SR-MPLS « ipSpace.net blog](https://daily.dev/posts/bgp-free-core-with-sr-mpls-ipspace-net-blog-h7kronzy3) · ipSpace.net Blog · 0 upvotes · 0 comments --- Tags: [#bgp](https://daily.dev/tags/bgp) [View this post on daily.dev](https://daily.dev/posts/bgp-labeled-unicast-interoperability-challenges-ipspace-net-blog-uobzbohjm) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"BGP Labeled Unicast Interoperability Challenges « ipSpace.net blog","url":"https://daily.dev/posts/bgp-labeled-unicast-interoperability-challenges-ipspace-net-blog-uobzbohjm","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/bgp-labeled-unicast-interoperability-challenges-ipspace-net-blog-uobzbohjm"},"datePublished":"2026-08-11T08:52:09.397Z","dateModified":"2026-08-11T09:01:48.065Z","description":"BGP Labeled Unicast (SAFI-4) has serious interoperability problems across vendor implementations. RFC 8277 Section 5 explicitly acknowledges that different...","image":"https://media.daily.dev/image/upload/s--OHB84bZF--/f_auto/v1722860399/public/Placeholder%2010","thumbnailUrl":"https://media.daily.dev/image/upload/s--OHB84bZF--/f_auto/v1722860399/public/Placeholder%2010","isAccessibleForFree":true,"articleSection":"ipSpace.net Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"ipSpace.net Blog","logo":"https://media.daily.dev/image/upload/s--xS7E82MT--/f_auto,q_auto/v1786438303/logos/ipspace?_a=BAMAMicg0","url":"https://daily.dev/sources/ipspace"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/bgp-labeled-unicast-interoperability-challenges-ipspace-net-blog-uobzbohjm","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"bgp","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"ipSpace.net Blog","item":"https://daily.dev/sources/ipspace"},{"@type":"ListItem","position":3,"name":"BGP Labeled Unicast Interoperability Challenges « ipSpace.net blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/bgp-labeled-unicast-interoperability-challenges-ipspace-net-blog-uobzbohjm#faq","mainEntity":[{"@type":"Question","name":"How do Cisco IOS and Arista EOS differ in handling BGP SAFI-1 and SAFI-4 routes on the same session?","acceptedAnswer":{"@type":"Answer","text":"Arista EOS treats SAFI-1 and SAFI-4 routes as completely independent ('ships in the night'), maintaining both simultaneously. Cisco IOS treats them as comparable and selects a single best route — either SAFI-1 or SAFI-4, not both. Cisco IOS also automatically converts between SAFI-1 and SAFI-4 routes; no equivalent knob exists on Arista EOS. Network engineers building multi-vendor BGP-LU fabrics track vendor behavior gaps like this on daily.dev."}},{"@type":"Question","name":"What does RFC 8277 say about interoperability between SAFI-1 and SAFI-4 BGP routes?","acceptedAnswer":{"@type":"Answer","text":"RFC 8277 Section 5 explicitly warns that different implementations handle coexisting SAFI-1 and SAFI-4 routes for the same prefix in incompatible ways, and that these differences may result in unexpected behavior or lack of interoperability. In some cases, it may be difficult or impossible to achieve desired policies with certain implementations or combinations of implementations. Architects evaluating BGP Labeled Unicast for multi-vendor networks follow standards developments like RFC 8277 on daily.dev."}}]} ```