<?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-03-31T21:29:00+00:00</dc:date>

	
	<item>
		<title> New gTLD Fees Threaten the Diversity of the Name Space (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20141003_new_gtld_fees_threaten_the_diversity_of_the_name_space</guid>
		<link>https://circleid.com/posts20141003_new_gtld_fees_threaten_the_diversity_of_the_name_space</link>
		<description><![CDATA[The great promise of the new gTLD programme is not that it will spawn dozens of .COM clones, but rather that it will lead to the creation of a global constellation of unique names embraced by specific interest groups. As an ICANN community, our challenge now is to ensure that the policy framework we've created to manage new gTLDs advances that vision by not penalising the very sorts of domains that the programme was designed to encourage. <a href="https://circleid.com/posts20141003_new_gtld_fees_threaten_the_diversity_of_the_name_space">More...</a>]]></description>
		<dc:date>2026-03-31T14:29:00-07:00</dc:date>
	</item>
	

	</channel>
</rss>