<?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-30T19:14:00+00:00</dc:date>

	
	<item>
		<title> Best Practices for Implementing IPv6 and Avoiding Traffic Exposures (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20120605_best_practices_implementing_ipv6_and_avoiding_traffic_exposures</guid>
		<link>https://circleid.com/posts20120605_best_practices_implementing_ipv6_and_avoiding_traffic_exposures</link>
		<description><![CDATA[There has been a lot of discussion lately about the potential for IPv6 to create security issues. While there are definitely some security risks of IPv6 deployment, a carefully considered implementation plan can help mitigate against security risks. As we approach World IPv6 Launch tomorrow, I thought it prudent to share the below described incident that iDefense recently observed. <a href="https://circleid.com/posts20120605_best_practices_implementing_ipv6_and_avoiding_traffic_exposures">More...</a>]]></description>
		<dc:date>2026-04-30T12:14:00-07:00</dc:date>
	</item>
	

	</channel>
</rss>