<?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-07T16:34:00+00:00</dc:date>

	
	<item>
		<title> DNS-over-HTTPS: Privacy and Security Concerns (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20190906_dns_over_https_the_privacy_and_security_concerns</guid>
		<link>https://circleid.com/posts20190906_dns_over_https_the_privacy_and_security_concerns</link>
		<description><![CDATA[The design of DNS included an important architectural decision: the transport protocol used is user datagram protocol (UDP). Unlike transmission control protocol (TCP), UDP is connectionless, stateless, and lightweight. In contrast, TCP needs to establish connections between end systems and guarantees packet ordering and delivery. DNS handles the packet delivery reliability aspect internally and avoids all of the overhead of TCP. There are two problems this introduces. <a href="https://circleid.com/posts20190906_dns_over_https_the_privacy_and_security_concerns">More...</a>]]></description>
		<dc:date>2026-04-07T09:34:00-07:00</dc:date>
	</item>
	

	</channel>
</rss>