<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ranges on Wirez</title><link>https://wirez.top/tags/ranges/</link><description>Recent content in Ranges on Wirez</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 01 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wirez.top/tags/ranges/index.xml" rel="self" type="application/rss+xml"/><item><title>Legacy IRR filtering fails operators today</title><link>https://wirez.top/posts/legacy-irr-filtering-fails-operators-today/</link><pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/legacy-irr-filtering-fails-operators-today/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">Legacy IRR filtering fails because a single ASN cannot define distinct prefix sets for different neighbors. This architectural rigidity forces operators to apply loose, universal filters that expose networks to unauthorized route leaks and mis-originations. Italo Cunha highlights that maintaining sixteen &lt;strong>route6 objects&lt;/strong> just to announce a &lt;strong>/44 IPv6 prefix&lt;/strong> at &lt;strong>/48 granularity&lt;/strong> exemplifies the unmanageable overhead plaguing current &lt;strong>AS-set&lt;/strong> deployments.&lt;/p></description></item></channel></rss>