<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>DOCSIS 3.0 &#187; Motorola</title>
	<atom:link href="http://www.docsis-30.com/tag/motorola/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.docsis-30.com</link>
	<description>Superfast Internet Transmission</description>
	<lastBuildDate>Mon, 14 Sep 2009 10:13:59 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Looking Beyond DOCSIS 3.0</title>
		<link>http://www.docsis-30.com/looking-beyond-docsis-30/</link>
		<comments>http://www.docsis-30.com/looking-beyond-docsis-30/#comments</comments>
		<pubDate>Thu, 30 Oct 2008 07:34:44 +0000</pubDate>
		<dc:creator>polszewski</dc:creator>
				<category><![CDATA[DOCSIS resource]]></category>
		<category><![CDATA[CMTS]]></category>
		<category><![CDATA[Constant HD]]></category>
		<category><![CDATA[Motorola]]></category>

		<guid isPermaLink="false">http://www.docsis-30.com/?p=122</guid>
		<description><![CDATA[DOCSIS 3.0 won&#8217;t be nirvana for the cable industry, according to the opening keynote speaker today at a Light Reading DOCSIS 3.0 conference in Denver. &#8220;We&#8217;re still limited in the upstream channel,&#8221; said Rouzbeh Yassini, CEO of YAS Broadband Ventures. &#8220;Good job, but no cigar yet. Even 35 Mbps upstream is still not enough.&#8221; Yassini [...]]]></description>
			<content:encoded><![CDATA[<p>DOCSIS 3.0 won&#8217;t be nirvana for the cable industry, according to the opening keynote speaker today at a Light Reading DOCSIS 3.0 conference in Denver.</p>
<p>&#8220;We&#8217;re still limited in the upstream channel,&#8221; said Rouzbeh Yassini, <a href="http://vc.hotstocked.com/companies/y/yas-broadband-ventures-3714.html" target="_blank">CEO of YAS Broadband Ventures</a>. &#8220;Good job, but no cigar yet. Even <strong>35 Mbps</strong> upstream is still not enough.&#8221;</p>
<p>Yassini said <strong>100 Mbps</strong> shared downstream speeds achieved with DOCSIS 3.0 are peaks, not constants, and today&#8217;s applications need constant bit rates.</p>
<p>&#8220;If you want to have multiple services and high definition (<strong>HD</strong>) video, it&#8217;s not the ultimate answer as far as our network capacity goes,&#8221; Yassini said. &#8220;<strong>Constant HD</strong> needs a constant bit rate.&#8221;</p>
<p>Sometimes called the <strong>&#8220;godfather&#8221;</strong> of DOCSIS for his role in shepherding the original specification, Yassini stirred things up a bit with his comments.</p>
<p>&#8220;I thought Rouzbeh (Yassini) was a bit harsh in terms of the upstream,&#8221; said Michael Cookish, a senior director of <strong>CMTS</strong> product management at Motorola. Cookish agreed that 100 Mbps upstream speeds would be demanded in the commercial services arena within three to five years, but that it would be doable.</p>
<p>To reach the necessary upstream speeds, Cookish recommended: (1) migrate to <a href="http://en.wikipedia.org/wiki/DOCSIS" target="_blank">DOCSIS 2.0</a>; (2) add <strong>upstream channels</strong>; and (3) <strong>split nodes</strong>.</p>
<p>As for why consumers will need such high speeds, next generation broadband applications were mentioned, including security systems, building temperature controls and digital signage.</p>
<p>source: cable360.net</p>
]]></content:encoded>
			<wfw:commentRss>http://www.docsis-30.com/looking-beyond-docsis-30/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
