<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Objects on Wirez</title><link>https://wirez.top/tags/objects/</link><description>Recent content in Objects 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/objects/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><item><title>RPKI in 2025: Why Path Validation Matters Now</title><link>https://wirez.top/posts/rpki-in-2025-why-path-validation-matters-now/</link><pubDate>Fri, 20 Feb 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/rpki-in-2025-why-path-validation-matters-now/</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">With Unique &lt;a href="https://datatracker.ietf.org/doc/html/rfc9582" target="_blank" rel="noopener noreferrer">ASPA&lt;/a> Customer ASIDs surging 539% in 2025 per RPKIViews. Org data, the industry has decisively pivoted from simple origin checks to thorough path validation. Readers will examine how &lt;strong>RPKI&lt;/strong> evolved from a niche preference to a critical infrastructure component, underpinned by a 23% increase in ROA objects reaching over 344,000 entries according to ARIN and RIPE NCC trust anchors. &lt;a href="https://www.arin.net/vault/blog/2017/10/31/implementing-rpki-its-easier-than-you-think/" target="_blank" rel="noopener noreferrer">ARIN&amp;#039;s implementing rpki its easier than you think&lt;/a> We dissect the mechanics of &lt;strong>validation performance&lt;/strong>, noting that despite a 20% growth in total cache size, optimized implementations like rpki-client reduced wall time validation runs by 23% on standard hardware. The analysis further details the strategic imperative for &lt;strong>ASPA objects&lt;/strong>, where all Regional Internet Registries have committed to full service availability by late 2026.&lt;/p></description></item><item><title>RPKI path security: The shift past origin checks</title><link>https://wirez.top/posts/rpki-path-security-the-shift-past-origin-checks/</link><pubDate>Sun, 01 Feb 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/rpki-path-security-the-shift-past-origin-checks/</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">A 539% surge in Unique &lt;a href="https://datatracker.ietf.org/doc/html/rfc9582" target="_blank" rel="noopener noreferrer">ASPA&lt;/a> Customer ASIDs proves the &lt;strong>RPKI database&lt;/strong> has shifted from simple origin checks to complex path validation.&lt;/p></description></item></channel></rss>