<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: .ORG traffic testing for a charge?</title>
	<atom:link href="http://www.domaineditorial.com/2006/10/20/org-traffic-testing-for-a-charge/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.domaineditorial.com/2006/10/20/org-traffic-testing-for-a-charge/</link>
	<description></description>
	<lastBuildDate>Wed, 27 Jan 2010 17:15:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: &#187; No more .ORG traffic tasting (DomainEditorial.com)</title>
		<link>http://www.domaineditorial.com/2006/10/20/org-traffic-testing-for-a-charge/comment-page-1/#comment-95</link>
		<dc:creator>&#187; No more .ORG traffic tasting (DomainEditorial.com)</dc:creator>
		<pubDate>Sat, 03 Mar 2007 05:43:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.domaineditorial.com/archives/2006/10/20/org-traffic-testing-for-a-charge/#comment-95</guid>
		<description>[...] The .ORG registry will be charging an excess deletion fee as of May 26th, 2007 in order to stop domain tasting. The fee of $0.05 per domain will be charged for grace period deletions of more than 90% of the registered domains. PIR, the operator of the .ORG registry had proposed this change in August of 2006 - it was approved by ICANN. [...]</description>
		<content:encoded><![CDATA[<p>[...] The .ORG registry will be charging an excess deletion fee as of May 26th, 2007 in order to stop domain tasting. The fee of $0.05 per domain will be charged for grace period deletions of more than 90% of the registered domains. PIR, the operator of the .ORG registry had proposed this change in August of 2006 &#8211; it was approved by ICANN. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
