<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Operators on Wirez</title><link>https://wirez.top/tags/operators/</link><description>Recent content in Operators on Wirez</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 11 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wirez.top/tags/operators/index.xml" rel="self" type="application/rss+xml"/><item><title>RIPE Infrastructure: Securing Baltic Networks Now</title><link>https://wirez.top/posts/ripe-infrastructure-securing-baltic-networks-now/</link><pubDate>Wed, 11 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/ripe-infrastructure-securing-baltic-networks-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 nearly 20,000 members as of late 2024, the &lt;a href="https://www.ripe.net/" target="_blank" rel="noopener noreferrer">RIPE NCC&lt;/a> anchors Baltic internet governance through direct operator support. &lt;a href="https://www.ripe.net/membership/payment/charging-scheme-2026-estimator/" target="_blank" rel="noopener noreferrer">RIPE&amp;#039;s charging scheme 2026 estimator&lt;/a>&lt;/p></description></item><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>APNIC IPv6 /32 vs /36: Why I Back the Larger Block</title><link>https://wirez.top/posts/apnic-ipv6-32-vs-36-why-i-back-the-larger-block/</link><pubDate>Tue, 24 Feb 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/apnic-ipv6-32-vs-36-why-i-back-the-larger-block/</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">&lt;a href="https://www.apnic.net/" target="_blank" rel="noopener noreferrer">APNIC&lt;/a> serves over four billion people, yet debates persist on reducing minimum &lt;strong>IPv6 address&lt;/strong> blocks to a /36. &lt;a href="https://blog.apnic.net/2026/01/20/ip-addresses-through-2025/" target="_blank" rel="noopener noreferrer">APNIC&amp;#039;s ip addresses through 2025&lt;/a>&lt;/p></description></item></channel></rss>