--- title: SwiNOG 40: Application-Based Source Routing with SRv6 «... description: A review of a SwiNOG 40 presentation on application-based source routing using SRv6, eBPF, and an Intent-Based Networking system for dynamic per-application... canonical: https://daily.dev/posts/swinog-40-application-based-source-routing-with-srv6-ipspace-net-blog-gympedpfq twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: SwiNOG 40: Application-Based Source Routing with SRv6 « ipSpace.net blog | daily.dev og:description: A review of a SwiNOG 40 presentation on application-based source routing using SRv6, eBPF, and an Intent-Based Networking system for dynamic per-application... og:url: https://daily.dev/posts/swinog-40-application-based-source-routing-with-srv6-ipspace-net-blog-gympedpfq og:image: https://api.daily.dev/og/posts/gYmPeDpFq.png og:image:alt: SwiNOG 40: Application-Based Source Routing with SRv6 « 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. # SwiNOG 40: Application-Based Source Routing with SRv6 « ipSpace.net blog **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 2 min read · 0 upvotes · 0 comments ## Summary A review of a SwiNOG 40 presentation on application-based source routing using SRv6, eBPF, and an Intent-Based Networking system for dynamic per-application traffic steering. The approach uses SRv6 headers added by eBPF on client hosts, guided by a centralized intent-based controller, eliminating host-to-network signaling and periodic path refreshments compared to RSVP-based traffic engineering. The key drawback identified is the path liveliness problem: if a path fails, no mechanism notifies the application to switch paths, since there is no host-to-network signaling. The author cautiously acknowledges this as one of the few scenarios where SRv6 might genuinely make sense, while questioning scalability and failure reaction time. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is the path liveliness problem with SRv6 source routing? When an application uses a fixed SRv6 path across the network and that path becomes unavailable, nothing notifies the application to switch to another path. Because there is no host-to-network signaling, the network has no way to inform the host that its chosen segment route is down. This is an old problem dating back to Token Ring Source Route Bridging, and it remains unsolved in SRv6-based application traffic steering. _Network engineers evaluating SRv6 deployments track failure-handling trade-offs like this on daily.dev._ ### How does SRv6-based traffic steering compare to RSVP-based traffic engineering in terms of scalability? SRv6-based application traffic steering scales significantly better than RSVP-based TE because it eliminates host-to-network signaling, periodic path refreshments, and extra per-path state in the network. All path computation happens in the intent-based system, keeping the data plane stateless. The trade-off is losing the feedback loop that RSVP provides when paths fail. _Teams choosing between traffic engineering approaches find architecture comparisons like this on daily.dev._ ## Similar posts on daily.dev - [BGP-Free Network Core with SRv6 « ipSpace.net blog](https://daily.dev/posts/bgp-free-network-core-with-srv6-ipspace-net-blog-9bbn88wub) · ipSpace.net Blog · 0 upvotes · 0 comments - [IPng Networks](https://daily.dev/posts/ipng-networks-u37jx9af5) · IPng Networks · 0 upvotes · 0 comments - [SRv6: From 5G networks to AI infrastructure—a journey of innovation](https://daily.dev/posts/srv6-from-5g-networks-to-ai-infrastructure-a-journey-of-innovation-dgebr25fq) · Cisco · 0 upvotes · 0 comments - [Configuring SRv6 on Junos \(Locator and IGP\) « ipSpace.net blog](https://daily.dev/posts/configuring-srv6-on-junos-locator-and-igp-ipspace-net-blog-bhavnkj81) · ipSpace.net Blog · 0 upvotes · 0 comments - [How NetworkManager uses eBPF to support CLAT and IPv6-mostly](https://daily.dev/posts/how-networkmanager-uses-ebpf-to-support-clat-and-ipv6-mostly-fiiow2hx2) · Red Hat Developer · 0 upvotes · 0 comments --- Tags: [#linux](https://daily.dev/tags/linux) [View this post on daily.dev](https://daily.dev/posts/swinog-40-application-based-source-routing-with-srv6-ipspace-net-blog-gympedpfq) ```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":"SwiNOG 40: Application-Based Source Routing with SRv6 « ipSpace.net blog","url":"https://daily.dev/posts/swinog-40-application-based-source-routing-with-srv6-ipspace-net-blog-gympedpfq","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/swinog-40-application-based-source-routing-with-srv6-ipspace-net-blog-gympedpfq"},"datePublished":"2026-08-11T08:56:02.151Z","dateModified":"2026-08-11T09:24:04.348Z","description":"A review of a SwiNOG 40 presentation on application-based source routing using SRv6, eBPF, and an Intent-Based Networking system for dynamic per-application...","image":"https://media.daily.dev/image/upload/s--HRgLpUt6--/f_auto/v1722860399/public/Placeholder%2003","thumbnailUrl":"https://media.daily.dev/image/upload/s--HRgLpUt6--/f_auto/v1722860399/public/Placeholder%2003","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/swinog-40-application-based-source-routing-with-srv6-ipspace-net-blog-gympedpfq","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"linux","timeRequired":"PT2M"} {"@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":"SwiNOG 40: Application-Based Source Routing with SRv6 « ipSpace.net blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/swinog-40-application-based-source-routing-with-srv6-ipspace-net-blog-gympedpfq#faq","mainEntity":[{"@type":"Question","name":"What is the path liveliness problem with SRv6 source routing?","acceptedAnswer":{"@type":"Answer","text":"When an application uses a fixed SRv6 path across the network and that path becomes unavailable, nothing notifies the application to switch to another path. Because there is no host-to-network signaling, the network has no way to inform the host that its chosen segment route is down. This is an old problem dating back to Token Ring Source Route Bridging, and it remains unsolved in SRv6-based application traffic steering. Network engineers evaluating SRv6 deployments track failure-handling trade-offs like this on daily.dev."}},{"@type":"Question","name":"How does SRv6-based traffic steering compare to RSVP-based traffic engineering in terms of scalability?","acceptedAnswer":{"@type":"Answer","text":"SRv6-based application traffic steering scales significantly better than RSVP-based TE because it eliminates host-to-network signaling, periodic path refreshments, and extra per-path state in the network. All path computation happens in the intent-based system, keeping the data plane stateless. The trade-off is losing the feedback loop that RSVP provides when paths fail. Teams choosing between traffic engineering approaches find architecture comparisons like this on daily.dev."}}]} ```