<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Startup to Intro Lower Cost Alternative to ROADMs</title>
	<link>http://www.wdmblog.com/startup-to-intro-lower-cost-alternative-to-roadms/</link>
	<description>The technology and business of wavelength division multiplexing telecommunications.</description>
	<pubDate>Thu, 20 Nov 2008 23:34:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.2</generator>

	<item>
 		<title>Comment on Startup to Intro Lower Cost Alternative to ROADMs by: WDMBlog &#187; Is the Market Ready for Edge-ROADMs</title>
		<link>http://www.wdmblog.com/startup-to-intro-lower-cost-alternative-to-roadms/#comment-581</link>
		<pubDate>Wed, 19 Jul 2006 17:52:20 +0000</pubDate>
		<guid>http://www.wdmblog.com/startup-to-intro-lower-cost-alternative-to-roadms/#comment-581</guid>
					<description>[...] This Telephony article debates whether carriers are ready for edge-ROADMs. The first of this product breed was recently introduced by startup Nistica. The concensus from people interviewed in the article is that, aside from niche applications, there is no need yet to deploy edge-ROAMS; the argument being that the costs are still high and the particular requirements of edge networks do not match up with the remote reconfigurability advantages of ROADMs.   Filed under: ROADMs  Comments: [...]</description>
		<content:encoded><![CDATA[	<p>[&#8230;] This Telephony article debates whether carriers are ready for edge-ROADMs. The first of this product breed was recently introduced by startup Nistica. The concensus from people interviewed in the article is that, aside from niche applications, there is no need yet to deploy edge-ROAMS; the argument being that the costs are still high and the particular requirements of edge networks do not match up with the remote reconfigurability advantages of ROADMs.   Filed under: ROADMs  Comments: [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
