<?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: Is OTN really the way forward?</title>
	<atom:link href="http://mccanntelecom.com/is-otn-really-the-way-forward/feed" rel="self" type="application/rss+xml" />
	<link>http://mccanntelecom.com/is-otn-really-the-way-forward</link>
	<description>European Telecommunications Markets and Events....from the trenches</description>
	<lastBuildDate>Thu, 10 May 2012 14:40:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Fred Stringer</title>
		<link>http://mccanntelecom.com/is-otn-really-the-way-forward/comment-page-1#comment-12</link>
		<dc:creator>Fred Stringer</dc:creator>
		<pubDate>Tue, 17 Nov 2009 15:45:12 +0000</pubDate>
		<guid isPermaLink="false">http://demo.mccanntelecom.com/?p=4#comment-12</guid>
		<description>John, 
OK now I get your point. And yes I encountered the same thinking when we produced the xGE DWDM interfaces. The target application was metro/regional networks where passive DWDM systems were typically in place. There was always customers in the market asking for OTN framing in these interfaces. In my opinion there was two reasons for those requests: 
a) OTN was successful in the long distance optical networks therefore it most be useful here too, and 
b)perception that Ethernet alone can NOT be maintained with effective troubleshooting. 
 
I&#039;m afraid we are not past the maintenance of Ethernet perception problem. Awhile ago when EFM (802.3ah) and CFM (802.1ag) were being deployed I searched for tutorials on Ethernet OAM and the enhancements these features provided. I did not find much, reinforcing the perception that Ethernet has little OAM capability, which I don&#039;t believe to be the case. Admittedly, the support mechanisms are different than SDH/SONET.  
 
I can&#039;t tell you how many times I&#039;ve heard of point to point xGE WAN Phy deployments only because there it has OAM terminology and features familiar to the operations staff. 
 
Living with Ethernet still has many perception hurdles especially in the carrier market space. 
 
cheers 
Fred </description>
		<content:encoded><![CDATA[<p>John,<br />
OK now I get your point. And yes I encountered the same thinking when we produced the xGE DWDM interfaces. The target application was metro/regional networks where passive DWDM systems were typically in place. There was always customers in the market asking for OTN framing in these interfaces. In my opinion there was two reasons for those requests:<br />
a) OTN was successful in the long distance optical networks therefore it most be useful here too, and<br />
b)perception that Ethernet alone can NOT be maintained with effective troubleshooting. </p>
<p>I&#039;m afraid we are not past the maintenance of Ethernet perception problem. Awhile ago when EFM (802.3ah) and CFM (802.1ag) were being deployed I searched for tutorials on Ethernet OAM and the enhancements these features provided. I did not find much, reinforcing the perception that Ethernet has little OAM capability, which I don&#039;t believe to be the case. Admittedly, the support mechanisms are different than SDH/SONET.  </p>
<p>I can&#039;t tell you how many times I&#039;ve heard of point to point xGE WAN Phy deployments only because there it has OAM terminology and features familiar to the operations staff. </p>
<p>Living with Ethernet still has many perception hurdles especially in the carrier market space. </p>
<p>cheers<br />
Fred</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mccannte</title>
		<link>http://mccanntelecom.com/is-otn-really-the-way-forward/comment-page-1#comment-11</link>
		<dc:creator>mccannte</dc:creator>
		<pubDate>Sat, 14 Nov 2009 00:15:55 +0000</pubDate>
		<guid isPermaLink="false">http://demo.mccanntelecom.com/?p=4#comment-11</guid>
		<description>Fred, from a FEC perspective you&#039;re absolutely right, increasing reach is obviously very useful.  I also do see the advantages of OTN from a multiservice grooming perspective in the long haul.   
 
My main point here (obviously not made clearly ;-)) was to counter a number of Vendors claims that Metro/Access gear must evolve to be OTN compliant and to push OTN as a service delivery technology.  I just do not see the point of OTN in an IP/Ethernet based service network. 
 
Now that I take a look at the post again, I didn&#039;t do a good job of qualifying my statement. </description>
		<content:encoded><![CDATA[<p>Fred, from a FEC perspective you&#039;re absolutely right, increasing reach is obviously very useful.  I also do see the advantages of OTN from a multiservice grooming perspective in the long haul.   </p>
<p>My main point here (obviously not made clearly <img src='http://mccanntelecom.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> ) was to counter a number of Vendors claims that Metro/Access gear must evolve to be OTN compliant and to push OTN as a service delivery technology.  I just do not see the point of OTN in an IP/Ethernet based service network. </p>
<p>Now that I take a look at the post again, I didn&#039;t do a good job of qualifying my statement.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mccannte</title>
		<link>http://mccanntelecom.com/is-otn-really-the-way-forward/comment-page-1#comment-10</link>
		<dc:creator>mccannte</dc:creator>
		<pubDate>Sat, 14 Nov 2009 00:06:22 +0000</pubDate>
		<guid isPermaLink="false">http://demo.mccanntelecom.com/?p=4#comment-10</guid>
		<description>Fred, you&#039;re right....I&#039;m an IP guy and therefore usually overlook the advantages of a FEC.   
 
The main point behind the post (and perhaps not clearly stated) was to question the opinion that OTN has a place in the Access/Service portions of a Carrier&#039;s network.  I just do not see any advantage of OTN technology in service delivery and I&#039;m seeing a number of Vendors push this (and therefore some Carriers are starting to insist that their Metro boxes be OTN compliant). 
 
From a grooming perspective OTN has clear advantages in mixed use networks (OC-whatever + Fiber Channel + Ethernet) on the long haul, but in the metro or even in the European Country Networks, I just don&#039;t see the need..... </description>
		<content:encoded><![CDATA[<p>Fred, you&#039;re right&#8230;.I&#039;m an IP guy and therefore usually overlook the advantages of a FEC.   </p>
<p>The main point behind the post (and perhaps not clearly stated) was to question the opinion that OTN has a place in the Access/Service portions of a Carrier&#039;s network.  I just do not see any advantage of OTN technology in service delivery and I&#039;m seeing a number of Vendors push this (and therefore some Carriers are starting to insist that their Metro boxes be OTN compliant). </p>
<p>From a grooming perspective OTN has clear advantages in mixed use networks (OC-whatever + Fiber Channel + Ethernet) on the long haul, but in the metro or even in the European Country Networks, I just don&#039;t see the need&#8230;..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fred Stringer</title>
		<link>http://mccanntelecom.com/is-otn-really-the-way-forward/comment-page-1#comment-9</link>
		<dc:creator>Fred Stringer</dc:creator>
		<pubDate>Fri, 13 Nov 2009 23:35:11 +0000</pubDate>
		<guid isPermaLink="false">http://demo.mccanntelecom.com/?p=4#comment-9</guid>
		<description>John, 
I think it is important to point out that OTN technology is very widely deployed. It is in most OEO Optical Transponders which are an element of long distance DWDM systems. What is new to the market is moving that technology to interface modules  of routers and switches and providing Optical Network Elements like ROADMs a colored wavelength. 
 One of the big advantages to OTN framing is the FEC (Forwarding Error Correction). The error correction solves with code some very hard physics problems and yields several db of gain for reach and/or hops. 
I think the question of &quot;OTN Interfaces&quot; in routers and switches is a bit different from the question of the OTN standards and technology. There is continual effort on various enhanced FECs with several deployed today. Given that &quot;green field&quot; implementations where you get to start with all new fiber are rather rare I&#039;d expect the OTN technology to be deployed and enhanced significantly for many years.  
A good question is, where will it be deployed? I think the answer varies with distance and the topology of the optical network. It is not clear to me that the Ethernet evolution obviates OTN technology. </description>
		<content:encoded><![CDATA[<p>John,<br />
I think it is important to point out that OTN technology is very widely deployed. It is in most OEO Optical Transponders which are an element of long distance DWDM systems. What is new to the market is moving that technology to interface modules  of routers and switches and providing Optical Network Elements like ROADMs a colored wavelength.<br />
 One of the big advantages to OTN framing is the FEC (Forwarding Error Correction). The error correction solves with code some very hard physics problems and yields several db of gain for reach and/or hops.<br />
I think the question of &quot;OTN Interfaces&quot; in routers and switches is a bit different from the question of the OTN standards and technology. There is continual effort on various enhanced FECs with several deployed today. Given that &quot;green field&quot; implementations where you get to start with all new fiber are rather rare I&#39;d expect the OTN technology to be deployed and enhanced significantly for many years.<br />
A good question is, where will it be deployed? I think the answer varies with distance and the topology of the optical network. It is not clear to me that the Ethernet evolution obviates OTN technology.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

