<?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: Immenstar and the Quad OLT</title>
	<atom:link href="http://www.nyquistcapital.com/2006/06/02/immenstar-and-the-quad-olt/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nyquistcapital.com/2006/06/02/immenstar-and-the-quad-olt/</link>
	<description>More Signal. Less Noise.</description>
	<lastBuildDate>Thu, 02 Apr 2009 12:29:57 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Cortina Acquires Immenstar at Nyquist Capital</title>
		<link>http://www.nyquistcapital.com/2006/06/02/immenstar-and-the-quad-olt/#comment-455</link>
		<dc:creator>Cortina Acquires Immenstar at Nyquist Capital</dc:creator>
		<pubDate>Mon, 26 Feb 2007 20:19:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.nyquistcapital.com/2006/06/02/immenstar-and-the-quad-olt/#comment-455</guid>
		<description>[...] This acquisition is surprising. Cortina previously focused more on the core of the network and has either built or acquired products designed to enable the next generation of WAN equipment for carrier applications. Immenstar is tightly focused on fiber to the home chipsets, a much more access oriented application. I suspect that Cortina is looking to couple it&#8217;s carrier class ethernet solutions with Immenstar&#8217;s high density OLT solution. Still, it is not a pretty fit. [...]</description>
		<content:encoded><![CDATA[<p>[...] This acquisition is surprising. Cortina previously focused more on the core of the network and has either built or acquired products designed to enable the next generation of WAN equipment for carrier applications. Immenstar is tightly focused on fiber to the home chipsets, a much more access oriented application. I suspect that Cortina is looking to couple it&#8217;s carrier class ethernet solutions with Immenstar&#8217;s high density OLT solution. Still, it is not a pretty fit. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FTTHblog &#187; New Commentary on Immenstar</title>
		<link>http://www.nyquistcapital.com/2006/06/02/immenstar-and-the-quad-olt/#comment-454</link>
		<dc:creator>FTTHblog &#187; New Commentary on Immenstar</dc:creator>
		<pubDate>Thu, 15 Jun 2006 20:10:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.nyquistcapital.com/2006/06/02/immenstar-and-the-quad-olt/#comment-454</guid>
		<description>[...] A somewhat dissenting view is given by commenter &quot;Glen K.&quot; following a post in Nyquist Condition: [...]</description>
		<content:encoded><![CDATA[<p>[...] A somewhat dissenting view is given by commenter &quot;Glen K.&quot; following a post in Nyquist Condition: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glen K.</title>
		<link>http://www.nyquistcapital.com/2006/06/02/immenstar-and-the-quad-olt/#comment-453</link>
		<dc:creator>Glen K.</dc:creator>
		<pubDate>Fri, 02 Jun 2006 21:48:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.nyquistcapital.com/2006/06/02/immenstar-and-the-quad-olt/#comment-453</guid>
		<description>Ultimately, uplinks from all OLTs in a shelf go to one aggregation device (either a switch in the same chassis or an external device). Statistical multiplexing across 4 OLTs may have some advantages, but it falls short to stat-muxing across all OLTs in a shelf. The latter is achieved by having a DBA with a fast response time to changes in instantaneous uplink bandwidth.  This will work, whether the OLT are integrated or standalone.

I think the main driver for quad OLT is cost reduction and increase in port density. This, however, should be approached as an optimization problem. Increasing OLT integration increases number of subscribers that would be affected by a blade mulfunction/replacement/reset.</description>
		<content:encoded><![CDATA[<p>Ultimately, uplinks from all OLTs in a shelf go to one aggregation device (either a switch in the same chassis or an external device). Statistical multiplexing across 4 OLTs may have some advantages, but it falls short to stat-muxing across all OLTs in a shelf. The latter is achieved by having a DBA with a fast response time to changes in instantaneous uplink bandwidth.  This will work, whether the OLT are integrated or standalone.</p>
<p>I think the main driver for quad OLT is cost reduction and increase in port density. This, however, should be approached as an optimization problem. Increasing OLT integration increases number of subscribers that would be affected by a blade mulfunction/replacement/reset.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
