<?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: Internet Neutrality and the Verizon Wireless-Naral Flap</title>
	<atom:link href="http://blog.cdt.org/2007/09/28/internet-neutrality-and-the-verizon-wireless-naral-flap/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.cdt.org/2007/09/28/internet-neutrality-and-the-verizon-wireless-naral-flap/</link>
	<description>Digital Policy in Process</description>
	<lastBuildDate>Fri, 16 Oct 2009 17:02:16 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: PolicyBeta - Blog Archive - Recent Neutrality Scuffles Highlight Need for Transparency</title>
		<link>http://blog.cdt.org/2007/09/28/internet-neutrality-and-the-verizon-wireless-naral-flap/comment-page-1/#comment-3148</link>
		<dc:creator>PolicyBeta - Blog Archive - Recent Neutrality Scuffles Highlight Need for Transparency</dc:creator>
		<pubDate>Mon, 29 Oct 2007 15:34:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cdt.org/2007/09/28/internet-neutrality-and-the-verizon-wireless-naral-flap/#comment-3148</guid>
		<description>[...] weeks have seen two scuffles relevant to the Internet neutrality debate. Verizon Wireless initially refused to facilitate certain automatic text messages from the abortion rights group NARAL on the ground that they were &#8220;controversial,&#8221; even [...]</description>
		<content:encoded><![CDATA[<p>[...] weeks have seen two scuffles relevant to the Internet neutrality debate. Verizon Wireless initially refused to facilitate certain automatic text messages from the abortion rights group NARAL on the ground that they were &#8220;controversial,&#8221; even [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
