<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Addressing &#8211; Noise</title>
	<atom:link href="https://noise.getoto.net/tag/addressing/feed/" rel="self" type="application/rss+xml" />
	<link>https://noise.getoto.net</link>
	<description>The collective thoughts of the interwebz</description>
	<lastBuildDate>Fri, 07 Nov 2025 14:00:00 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.2</generator>
	<item>
		<title>DIY BYOIP: a new way to Bring Your Own IP prefixes to Cloudflare</title>
		<link>https://noise.getoto.net/2025/11/07/diy-byoip-a-new-way-to-bring-your-own-ip-prefixes-to-cloudflare/</link>
		
		<dc:creator><![CDATA[Ash Pallarito]]></dc:creator>
		<pubDate>Fri, 07 Nov 2025 14:00:00 +0000</pubDate>
				<category><![CDATA[Addressing]]></category>
		<category><![CDATA[Aegis]]></category>
		<category><![CDATA[BYOIP]]></category>
		<category><![CDATA[CDN]]></category>
		<category><![CDATA[Cloudflare Gateway]]></category>
		<category><![CDATA[Egress]]></category>
		<category><![CDATA[IPv4]]></category>
		<category><![CDATA[ipv6]]></category>
		<category><![CDATA[Magic Transit]]></category>
		<category><![CDATA[RPKI]]></category>
		<category><![CDATA[Smart Shield]]></category>
		<category><![CDATA[Spectrum]]></category>
		<category><![CDATA[апи]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=9136ab38e278ee11172269dca257ad91</guid>

					<description><![CDATA[Announcing a new self-serve API for Bring Your Own IP (BYOIP), giving customers unprecedented control and flexibility to onboard, manage, and use their own IP prefixes with Cloudflare's services.]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Your IPs, your rules: enabling more efficient address space usage</title>
		<link>https://noise.getoto.net/2025/05/19/your-ips-your-rules-enabling-more-efficient-address-space-usage/</link>
		
		<dc:creator><![CDATA[Mark Rodgers]]></dc:creator>
		<pubDate>Mon, 19 May 2025 13:00:00 +0000</pubDate>
				<category><![CDATA[Addressing]]></category>
		<category><![CDATA[BYOIP]]></category>
		<category><![CDATA[CDN]]></category>
		<category><![CDATA[IPv4]]></category>
		<category><![CDATA[Magic Transit]]></category>
		<category><![CDATA[Spectrum]]></category>
		<category><![CDATA[апи]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=680a08029e5c603a0805d22be4056363</guid>

					<description><![CDATA[IPv4 is expensive, and moving network resources around is hard. Previously, when customers wanted to use multiple Cloudflare services, they had to bring a new address range.]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>HTTPS-only for Cloudflare APIs: shutting the door on cleartext traffic</title>
		<link>https://noise.getoto.net/2025/03/20/https-only-for-cloudflare-apis-shutting-the-door-on-cleartext-traffic/</link>
		
		<dc:creator><![CDATA[Suleman Ahmad]]></dc:creator>
		<pubDate>Thu, 20 Mar 2025 13:00:00 +0000</pubDate>
				<category><![CDATA[Addressing]]></category>
		<category><![CDATA[https]]></category>
		<category><![CDATA[research]]></category>
		<category><![CDATA[Security Week]]></category>
		<category><![CDATA[апи]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=62895d3f0eee0a3fb2a92beeac33a654</guid>

					<description><![CDATA[We are closing the cleartext HTTP ports entirely for Cloudflare API traffic. This prevents the risk of clients unintentionally leaking their secret API keys in cleartext during the initial request.]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>How we prevent conflicts in authoritative DNS configuration using formal verification</title>
		<link>https://noise.getoto.net/2024/11/08/how-we-prevent-conflicts-in-authoritative-dns-configuration-using-formal-verification/</link>
		
		<dc:creator><![CDATA[James Larisch]]></dc:creator>
		<pubDate>Fri, 08 Nov 2024 14:00:00 +0000</pubDate>
				<category><![CDATA[Addressing]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[Formal Methods]]></category>
		<category><![CDATA[research]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=eed169f11976f3f0eeaf2b39a4940ee9</guid>

					<description><![CDATA[We describe how Cloudflare uses a custom Lisp-like programming language and formal verifier (written in Racket and Rosette) to prevent logical contradictions in our authoritative DNS nameserver’s behavior.]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/

Object Caching 30/127 objects using Memcached
Page Caching using Disk: Enhanced 
Lazy Loading (feed)
Database Caching using Memcached

Served from: noise.getoto.net @ 2025-12-11 04:48:31 by W3 Total Cache
-->