<?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/"
	xmlns:go='http://ns.gigaom.com/'
xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: BellSouth pushes DSL hard</title>
	<atom:link href="http://gigaom.com/2005/08/02/bellsouth-pushes-dsl-hard/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2005/08/02/bellsouth-pushes-dsl-hard/</link>
	<description></description>
	<lastBuildDate>Sat, 11 Feb 2012 12:44:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Om Malik&#8217;s Broadband Blog &#187; A US Broadband Slowdown Ahead?</title>
		<link>http://gigaom.com/2005/08/02/bellsouth-pushes-dsl-hard/#comment-105863</link>
		<dc:creator><![CDATA[Om Malik&#8217;s Broadband Blog &#187; A US Broadband Slowdown Ahead?]]></dc:creator>
		<pubDate>Mon, 05 Sep 2005 22:02:31 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/2005/08/02/bellsouth-pushes-dsl-hard/#comment-105863</guid>
		<description><![CDATA[[...] With many millions still reluctant to spend more money for broadband connections, the recent introduction of budget DSL plans by Verizon, BellSouth and SBC indicates that the bells are trying to goose up those numbers. An industry insider recently told me that it is more of a defensive move, an attempt to lock in voice customers before they switch to cable-based voice services. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] With many millions still reluctant to spend more money for broadband connections, the recent introduction of budget DSL plans by Verizon, BellSouth and SBC indicates that the bells are trying to goose up those numbers. An industry insider recently told me that it is more of a defensive move, an attempt to lock in voice customers before they switch to cable-based voice services. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Om Malik</title>
		<link>http://gigaom.com/2005/08/02/bellsouth-pushes-dsl-hard/#comment-105862</link>
		<dc:creator><![CDATA[Om Malik]]></dc:creator>
		<pubDate>Wed, 03 Aug 2005 04:56:13 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/2005/08/02/bellsouth-pushes-dsl-hard/#comment-105862</guid>
		<description><![CDATA[what i meant was that they are not bullshitting about ADSL2plus, and this is an upgrade that gets us one step closer to it]]></description>
		<content:encoded><![CDATA[<p>what i meant was that they are not bullshitting about ADSL2plus, and this is an upgrade that gets us one step closer to it</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank Bulk</title>
		<link>http://gigaom.com/2005/08/02/bellsouth-pushes-dsl-hard/#comment-105861</link>
		<dc:creator><![CDATA[Frank Bulk]]></dc:creator>
		<pubDate>Wed, 03 Aug 2005 04:31:04 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.wordpress.com/2005/08/02/bellsouth-pushes-dsl-hard/#comment-105861</guid>
		<description><![CDATA[I don&#039;t think you need ADSL2+ to get 6 Mbps downstream.  Yes, at short distances you&#039;re likely to get higher speeds, but I believe the ADSL standard gives you 8 Mbps on the downstream.
Some good numbers are here:
http://en.wikipedia.org/wiki/Asymmetric_Digital_Subscriber_Line

Frank]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t think you need ADSL2+ to get 6 Mbps downstream.  Yes, at short distances you&#8217;re likely to get higher speeds, but I believe the ADSL standard gives you 8 Mbps on the downstream.<br />
Some good numbers are here:<br />
<a href="http://en.wikipedia.org/wiki/Asymmetric_Digital_Subscriber_Line" rel="nofollow">http://en.wikipedia.org/wiki/Asymmetric_Digital_Subscriber_Line</a></p>
<p>Frank</p>
]]></content:encoded>
	</item>
</channel>
</rss>

