Dave Molta

Tags: , , , , , , , , , , , , , , , , , , , , , , , ,

Channel: Other, Networking & Mgmt, Data Protection, Wireless

See more from this blogger

Air Time: Wi-Fi and Commoditization

Quick! What do soybeans, pork bellies and natural gas have in common? If your answer involves your favorite local diner, you're way off track. These are major commodities bought and sold on international exchanges every day. Commodities are a good thing; they imply an expectation of quality and availability along with price competition. What's not to like about that?

It's commonplace to hear pundits talk about the commoditization of IT. And while there may be a lot more variation among notebook computers than soybean bushels, the prevailing wisdom is that technology commoditization is also beneficial. However, there are times when commodity technology impedes progress and establishes an ugly legacy with complex challenges. Wi-Fi is the latest example.

All Hail Ethernet!

If commodity Wi-Fi is arguably bad, then an opposing example is Ethernet, which stands as a testament to the power of open standards, the economies of siliconization and the market power of mass adoption. Despite the sage advice once given me by an IBM salesman--that the laws of physics would prevent Ethernet from ever exceeding 10 Mbps--the technology has been continuously enhanced over the years. It dominates not only the LAN but, increasingly, metro networks as well. It's interesting that, in an era of MAC-layer switching, very little of the original contention-based Ethernet specification is relevant. Still, it's the poster child for all the good that comes out of standards and commoditized technology.

While the incredible success of Ethernet speaks well for the value of commoditization, what happens if a technology reaches this stage prematurely, in a form that inhibits future progress? Like any legacy system incapable of meeting current, let alone future, needs, it begs to be replaced by something different, but doing so presents enormous obstacles.


Page:  1 | 2 |3 |Next Page »

Related Reading


More Insights




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.
 

Research and Reports

Storage Virtualization Guide
May 2012

Network Computing: May 2012

TechWeb Careers