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

News Analysis  

Optical SDN Could Require Vendor-Specific Help

May 14, 2013 | Craig Matsumoto |
NEW YORK -- Packet-Optical Transport Evolution 2013 -- The photonic angle to software-defined networking (SDN) is going to require vendor-specific technologies rather than one industry-standard approach, according to Glenn Wellbrock, the director in charge of Verizon's optical-network architecture.

Wellbrock's talk, which kicked off the POTE conference Tuesday morning, brought a dose of carrier reality to what was certain to be an SDN-heavy day.

His goes against the grain of SDN's promise, where a few, possibly homogeneous controllers rule the network -- but then again, optical transport gear isn't like the rest of the network. The transport layer deals with the physical properties of light, a very analog problem. An SDN controller can't tell, for instance, that a particular span should be avoided because its polarization-mode dispersion is too high.

Moreover, many of the controllable variables in the optical network are vendor-specific. Vendors are trying to stand out by using their own versions of forward error correction, for instance.

Standards are already being hammered out for SDN in the transport layer, but those efforts mostly target the OTN switching layer. Wellbrock was talking about the photonic layer, "Layer 0," as it's called (and that's the term Wellbrock used).

Specifically, he's concerned about reconfigurable optical add-drop multiplexers (ROADMs). For years, Verizon has preached a dream of ROADM networks that are colorless, directionless and contentionless and that run on a flexible grid. All of that freedom would give the operator more options for where to direct wavelengths to go and when those commands could be issued. In turn, that would address concerns that the optical network is too expensive and too slow to configure.

All of a sudden, though Layers 1 through 3 are being blessed with that kind of flexibility, as SDN promises the ability to program network paths and provision services on the fly. Wellbrock's concern is that the optical layer could be left behind as all these other layers improve.

"If they just optimize the upper layers and forget about the physical layer, especially the transport, we're going to be in the same boat two or three years from now, where we ask, 'How do I get it cheaper?'"

The answer doesn't require creating anything new, Wellbrock said. Rather, it's a matter of telling the upper layers what's available at the packet layer: where the possible endpoints are and what bandwidth they can handle, and what the connectivity map connecting them looks like.

But that implementation has to be vendor-specific, Wellbrock argued. One answer would be to use the element management system (EMS). The SDN controller would talk to the EMS, which would make the necessary changes in the ROADMs.

This is all predicated on those "CDC" (or "CDCF") ROADMs becoming a reality, because that would create the optical switching that SDN would control, "but that reality is coming in 2014," Wellbrock said.

As an aside, Wellbrock mentioned that bandwidth-on-demand -- one SDN application that many vendors tend to gravitate toward -- doesn't interest Verizon. Users wouldn't ask for it until emergencies crop up, so Verizon would likely have to build up extra capacity to accommodate the service -- and building excess, unused capacity is exactly the kind of thing Wellbrock is trying to avoid.

For more

— 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.
 

Going Soft at MWC

SPONSORED BY
White Papers SPONSORED CONTENT
Featured
Spanning Tree
An Ethernet protocol that checks a network for loops