<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:admin="http://webns.net/mvcb/"
	xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
	xmlns:content="http://purl.org/rss/1.0/modules/content/">

	<channel>

	<title>&#45; CircleID</title>
	<link>https://www.circleid.com/blogs/</link>
	<description>Postings from  on CircleID</description>
	<dc:language>en</dc:language>
	<dc:rights>Copyright 2026, unless where otherwise noted.</dc:rights>
	<dc:date>2026-04-14T18:21:00+00:00</dc:date>

	
	<item>
		<title> Building a More Secure Routing System: Verisign's Path to RPKI (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20230605-building-a-more-secure-routing-system-verisigns-path-to-rpki</guid>
		<link>https://circleid.com/posts20230605-building-a-more-secure-routing-system-verisigns-path-to-rpki</link>
		<description><![CDATA[At Verisign, we believe that continuous improvements to the safety and security of the global routing system are critical for the reliability of the internet. As such, we've recently embarked on a path to implement Resource Public Key Infrastructure (RPKI) within our technology ecosystem as a step toward building a more secure routing system. In this blog, we share our ongoing journey toward RPKI adoption and the lessons we've learned as an operator of critical internet infrastructure. <a href="https://circleid.com/posts20230605-building-a-more-secure-routing-system-verisigns-path-to-rpki">More...</a>]]></description>
		<dc:date>2026-04-14T11:21:00-07:00</dc:date>
	</item>
	

	</channel>
</rss>