<?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> My Top Takeaways from DNS-OARC 24 (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20160406_my_top_takeaways_from_dns_oarc_24</guid>
		<link>https://circleid.com/posts20160406_my_top_takeaways_from_dns_oarc_24</link>
		<description><![CDATA[The 24th DNS-OARC meeting was held last week in Buenos Aires -- a two-day DNS workshop with amazingly good, consistent content. The programme committee are to be congratulated on maintaining a high quality of presentations. Here are my picks of the workshop. They fall into three groups, covering themes I found interesting... These presentations related to the ongoing problem of DNS as a source of reflection attacks, or a victim of attempted DDoS... <a href="https://circleid.com/posts20160406_my_top_takeaways_from_dns_oarc_24">More...</a>]]></description>
		<dc:date>2026-04-30T12:14:00-07:00</dc:date>
	</item>
	
	<item>
		<title> Behind the Curtain: Making IPv6 Work (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20160201_behind_the_curtain_making_ipv6_work</guid>
		<link>https://circleid.com/posts20160201_behind_the_curtain_making_ipv6_work</link>
		<description><![CDATA[Wouldn't it be nice if turning on IPv6 really was 'press one button and the rest is magic' easy? For some things, it is. If you're talking about client-side, enabling an IPv4-only home service on DSL or fibre really can be this simple, because all the heavy lifting is being done inside your ISP: you're not enabling IPv6 in the network, you're turning on the last mile. It was knocking at your door and you just had to let it in. <a href="https://circleid.com/posts20160201_behind_the_curtain_making_ipv6_work">More...</a>]]></description>
		<dc:date>2026-04-30T12:14:00-07:00</dc:date>
	</item>
	
	<item>
		<title> Cyptech Needs You! (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20150413_cyptech_needs_you</guid>
		<link>https://circleid.com/posts20150413_cyptech_needs_you</link>
		<description><![CDATA[In August of last year I wrote in a blog about the importance of cryptech to wide-scale trust in the Internet. For those who don't know about it, http://cryptech.is is a project aiming to design and deploy an openly developed, trustable Hardware Security Module (HSM) which can act both as a keystore (holding your secrets and keeping them private) and as a signing engine. <a href="https://circleid.com/posts20150413_cyptech_needs_you">More...</a>]]></description>
		<dc:date>2026-04-30T12:14:00-07:00</dc:date>
	</item>
	
	<item>
		<title> DNS Resolvers and DNSSEC: Roll Over and Die? (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/postsdns_resolvers_and_dnssec_roll_over_and_die</guid>
		<link>https://circleid.com/postsdns_resolvers_and_dnssec_roll_over_and_die</link>
		<description><![CDATA[Security is great when all the green lights are shining brightly and everything validates as intended, but what happens when you encounter failure? In this work we examine the behaviour of the DNS when security, in the form of DNSSEC is added, and we look at what happens when things do not happen as intended. What triggered this examination was a sudden increase in the traffic generated by secondary servers for the in-addr.arpa reverse zones in December 2009. <a href="https://circleid.com/postsdns_resolvers_and_dnssec_roll_over_and_die">More...</a>]]></description>
		<dc:date>2026-04-30T12:14:00-07:00</dc:date>
	</item>
	

	</channel>
</rss>