Light Reading Mobile – Telecom News, Analysis, Events, and Research
Valley Wonk  
Craig Matsumoto

Coherent Turns 5

March 14, 2013 | Craig Matsumoto |
This week marked the fifth anniversary of Nortel Networks announcing its coherent technology.

Mike Adams (who's now a vice president at Ciena Corp.) clued me in on it Thursday. Sure enough, it was mid-March 2008 when Ryan Lawler (who's now doing things like interviewing Will Arnett) wrote: Nortel Trots Out 40Gig.

We didn't call it "coherent" then. Nortel was emphasizing the name of the modulation scheme, the oh-so-catchy dual-polarization quadrature phase-shift keying (DP-QPSK).

Not everyone believed in coherent from the get-go, Adams remembers -- and why not? Nortel's would be one of many different, incompatible 40Gbit/s schemes to emerge for optical line-side transmission.

But Nortel got some carriers on board quickly. And months later, coherent detection became the de facto 100Gbit/s standard when the OIF set its 100Gbit/s framework, including the choice of DP-QPSK as the sole modulation format. (See Nortel Rolls On With 40-Gig and OIF Steps In to Fill the 100G Void.)

Now at the 2013 OFC/NFOEC, coherent is all we'll talk about, although there'll be some quadrature amplitude modulation (QAM) to go along with the DP-QPSK.

We did give Nortel a lot of credit for trailblazing 100Gbit/s coherent (at least, that's how I remember it), but the five-year mark still provided a nice excuse to pause and reflect for a minute. Now back to OFC/NFOEC planning.

— Craig Matsumoto, Managing Editor, Light Reading



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.
 
More Valley Wonk
The Case for Flexibility Beyond 100G
Comcast joins Google in asking for a flexible-rate optical standard, rather than 400G or terabit, but that's easier said than done
Virtualization Takes the Stage at Interop
Cisco, Juniper and other more traditional Interop speakers might get overshadowed by the forces of virtualization
SDN Still Needs a Gathering Like ONS
The Open Networking Summit has climbed the hype curve, but the conference should cling to its roots as a techie discussion forum for software-defined networking
What OpenDaylight Really Wants to Do
The coalition's chairman says all these companies plan to further the SDN cause and don't have a 'nefarious' angle
Cisco Sees Daylight for SDN
Big vendors are reportedly banding together to unify SDN's approach but is it more about steering the conversation?
Related Content
Most Popular
Read
White Papers SPONSORED CONTENT
Featured
Resource Library SPONSORED CONTENT