--- title: Is BGP PIC Edge an Oxymoron? « ipSpace.net blog | daily.dev description: A deep technical analysis of whether BGP PIC Edge is conceptually self-contradictory. PIC Edge requires per-prefix (or per-CE) VPN labels to avoid micro-loops... canonical: https://daily.dev/posts/is-bgp-pic-edge-an-oxymoron-ipspace-net-blog-nqezytg03 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Is BGP PIC Edge an Oxymoron? « ipSpace.net blog | daily.dev og:description: A deep technical analysis of whether BGP PIC Edge is conceptually self-contradictory. PIC Edge requires per-prefix (or per-CE) VPN labels to avoid micro-loops... og:url: https://daily.dev/posts/is-bgp-pic-edge-an-oxymoron-ipspace-net-blog-nqezytg03 og:image: https://api.daily.dev/og/posts/nQEzYTG03.png og:image:alt: Is BGP PIC Edge an Oxymoron? « 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. # Is BGP PIC Edge an Oxymoron? « ipSpace.net blog **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 4 min read · 0 upvotes · 0 comments ## Summary A deep technical analysis of whether BGP PIC Edge is conceptually self-contradictory. PIC Edge requires per-prefix (or per-CE) VPN labels to avoid micro-loops during PE-CE link failover, but per-prefix labels undermine the Prefix Independent Convergence goal by requiring individual FIB updates per prefix. Per-CE label allocation (default on Junos, available on IOS XR, FRRouting, and newer IOS XE) could bridge the gap, but Cisco's IOS XE 16.6 documentation explicitly states PIC with per-CE labels is unsupported. The post also covers BGP Best External, BGP Add Path, per-PE route distinguishers, and EVPN limitations for PIC Edge. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why does BGP PIC Edge require per-prefix VPN labels instead of per-VRF labels in MPLS VPN? PIC Edge needs per-prefix (or per-CE) VPN labels because the backup CE route carries a label pointing directly to the PE-CE interface, letting the primary PE send traffic straight to the backup PE-CE interface before BGP convergence completes. With per-VRF labels, a temporary micro-loop forms between the primary and backup PE routers, making PIC Edge non-functional. _Engineers designing MPLS VPN fast-failover architectures track these label allocation trade-offs on daily.dev._ ### Does per-CE label allocation mode support BGP PIC Edge on Cisco IOS XE? Cisco's IOS XE 16.6 documentation explicitly states that PIC with per-CE labels is not supported. Per-CE label allocation is available on IOS XE from at least release 16.6, and is also the default on Junos and available on IOS XR and FRRouting, but not on Nexus OS. The combination of PIC Edge with per-CE labels remains unsupported on IOS XE. _Keeping up with platform-specific MPLS VPN label allocation support is easier when the relevant discussions surface on daily.dev._ ### Why can't EVPN implementations support BGP PIC Edge? Most EVPN implementations use per-VRF label allocation rather than per-prefix or per-CE labels. PIC Edge requires per-prefix or per-CE VPN labels so the backup route label points directly to the PE-CE interface. Without that, switching to the backup path before BGP convergence creates a micro-loop between the primary and backup PE routers. _Developers and network engineers evaluating EVPN versus MPLS VPN for fast failover find relevant comparisons on daily.dev._ ## Similar posts on daily.dev - [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 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 --- Tags: [#bgp](https://daily.dev/tags/bgp) [View this post on daily.dev](https://daily.dev/posts/is-bgp-pic-edge-an-oxymoron-ipspace-net-blog-nqezytg03) ```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":"Is BGP PIC Edge an Oxymoron? « ipSpace.net blog","url":"https://daily.dev/posts/is-bgp-pic-edge-an-oxymoron-ipspace-net-blog-nqezytg03","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/is-bgp-pic-edge-an-oxymoron-ipspace-net-blog-nqezytg03"},"datePublished":"2026-08-11T08:52:01.100Z","dateModified":"2026-08-11T08:55:21.348Z","description":"A deep technical analysis of whether BGP PIC Edge is conceptually self-contradictory. PIC Edge requires per-prefix (or per-CE) VPN labels to avoid micro-loops...","image":"https://media.daily.dev/image/upload/s--VDukGCjf--/f_auto/v1722860399/public/Placeholder%2002","thumbnailUrl":"https://media.daily.dev/image/upload/s--VDukGCjf--/f_auto/v1722860399/public/Placeholder%2002","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/is-bgp-pic-edge-an-oxymoron-ipspace-net-blog-nqezytg03","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"bgp","timeRequired":"PT4M"} {"@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":"Is BGP PIC Edge an Oxymoron? « ipSpace.net blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/is-bgp-pic-edge-an-oxymoron-ipspace-net-blog-nqezytg03#faq","mainEntity":[{"@type":"Question","name":"Why does BGP PIC Edge require per-prefix VPN labels instead of per-VRF labels in MPLS VPN?","acceptedAnswer":{"@type":"Answer","text":"PIC Edge needs per-prefix (or per-CE) VPN labels because the backup CE route carries a label pointing directly to the PE-CE interface, letting the primary PE send traffic straight to the backup PE-CE interface before BGP convergence completes. With per-VRF labels, a temporary micro-loop forms between the primary and backup PE routers, making PIC Edge non-functional. Engineers designing MPLS VPN fast-failover architectures track these label allocation trade-offs on daily.dev."}},{"@type":"Question","name":"Does per-CE label allocation mode support BGP PIC Edge on Cisco IOS XE?","acceptedAnswer":{"@type":"Answer","text":"Cisco's IOS XE 16.6 documentation explicitly states that PIC with per-CE labels is not supported. Per-CE label allocation is available on IOS XE from at least release 16.6, and is also the default on Junos and available on IOS XR and FRRouting, but not on Nexus OS. The combination of PIC Edge with per-CE labels remains unsupported on IOS XE. Keeping up with platform-specific MPLS VPN label allocation support is easier when the relevant discussions surface on daily.dev."}},{"@type":"Question","name":"Why can't EVPN implementations support BGP PIC Edge?","acceptedAnswer":{"@type":"Answer","text":"Most EVPN implementations use per-VRF label allocation rather than per-prefix or per-CE labels. PIC Edge requires per-prefix or per-CE VPN labels so the backup route label points directly to the PE-CE interface. Without that, switching to the backup path before BGP convergence creates a micro-loop between the primary and backup PE routers. Developers and network engineers evaluating EVPN versus MPLS VPN for fast failover find relevant comparisons on daily.dev."}}]} ```