Light Reading Mobile – Telecom News, Analysis, Events, and Research

1:25 PM -- The real problem with Tellabs' GPON efforts is twofold.

First, the press release was right. There's the customer problem. Verizon Communications Inc. just wants the stuff to be delivered more cheaply than Tellabs Inc. can make it. When carriers take a big risk, they have to pass that risk on to everyone in the food chain.

Second, Tellabs can't seem to source a good ONT (optical network terminal), the customer premises gear, that both works well and allows it to make some money after the sale to Verizon is complete. That might be as much of an industry problem as it is an issue of Tellabs screwing up.

Keep in mind: There haven't been a whole heck of a lot of optics breakthroughs happening at the customer premises side of the access business. There are some packaging innovations here and there, but nothing that truly drops the cost of making ONTs through the floor. The most urgent concern in that area is simply to make stuff cheaply, and for that, people just send more jobs to China.

That's called administration, not innovation.

Anyway, good for Tellabs for picking its battles and not trying to be everything to everyone. Lots of under-$10-billion market cap companies in telecom could learn a thing or two from Ciena Corp. in that regard.

Ciena tried to own the metro network at one time. Now it's quite happy picking its spots and winning a few high-margin skirmishes on the outskirts of the larger wars among the larger equipment vendors.

Tellabs can do the same sort of cherry-picking in access. And maybe that will require a renewed investment in other access areas, and not a full-scale abandonment, as many have wanted.

— Phil Harvey, The Editor, Light Reading

GPONdering the Tellabs access dilemma
April 02, 2008 | Phil Harvey |


Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 
Related Videos
White Papers SPONSORED CONTENT
Featured