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

News Analysis  

OpenFlow Taps the Brakes

June 11, 2012 | Craig Matsumoto |

The recent 1.3.0 release of the OpenFlow Switch Specification will be the last big revision for a while, as the Open Networking Foundation (ONF) gives vendors a chance to catch up.

"There were so many things the market needed beyond 1.0 and 1.1 that we wanted quickly to produce 1.2 and 1.3. Now that we have done so, we don't feel the need to keep cranking out new versions quite so fast," ONF Executive Director Dan Pitt tells Light Reading via email.

Important new features have included IPv6 support (in 1.2) and support for tunneling and quality of service (in 1.3). Big Switch Networks appears to be the first company making use of the tunneling part, as announced last week. (See Big Switch Opens Up Network Tunneling.)

The plan now is "making OpenFlow 1.3.x the anchor for this year," Pitt writes, meaning 1.3 will only get updated for bug fixes. "ONF decided to make the OpenFlow specification more of a stable target for implementers," he adds.

The pause might be welcome, as vendors have been scrambling to declare support for OpenFlow and software-defined networking (SDN) in general. Many are still working with OpenFlow 1.0 and haven't been ready to move to later versions. The 1.1 version, developed before the ONF took over the standard, isn't considered good enough for production usage, and version 1.2 just came out in December.

OpenFlow 1.0 does still have its bugs, Pitt notes, so the ONF plans to release OpenFlow 1.0.1 -- consisting of the 1.0 release plus an errata document. That should happen sometime this month or next, Pitt says.

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.
 
White Papers SPONSORED CONTENT
Featured