Network World
Saturday, November 22, 2008
DNSstuff.com
Get information about your IP
IP Information
50+ On-demand DNS and network tools

Community: LANs & WANs

Navigation

An interesting subject

It is interesting that you mention SNA - I did work in/with IBM (SNA) systems but also Hitachi, Ericsson, Tandem and Memorex (ITT actually) 1280 controllers until the developers did walk out after a mismanagement (what else?). Ericsson was a huge player in SNA world in Europe until - the same story, a mismanagement?

Now, the worst company breaking SNA standards was, you guess it, IBM. Maybe for competitive reasons (definitely not because lack of skills, the architects and developers were - are first class), one day our controllers, terminals, printers just didn't work. I had all the fun showing that the IBM host, whatever was breaking the standard. I still have a lot of IBM friends from that time - it was a friendly competition which we all enjoyed - really!

So - standards are good as long as they don't get mixed with marketing. Is that possible? A real standard looks a lot like some used in multimedia - a container standard where everyone can add their own extension and to compete that way. I personally hate when someone breaks a set standard, you can't reach the developer (as it used to be), you try to reverse engineer what and why happened, and so on. And this seems to be more a rule today - especially in any standard which has anything to do with security or, even worse, a competing product.

Another problem with standards today is, they are just too big (even SNA "bible" was nothing) and full of loopholes. It almost seems that IT is taking the model from lawyers - instead of putting clear and short ground rules to place, current standards (6000+ pages anybody) would take years to clear even the obvious problems and even then have loopholes?

Selecting a product or a vendor based on standards - depends. Standards are not just technical - rules, regulations, laws, country standards, de facto standards, etc are also standards. And "standards" change. So, if the company has resources to deal with all the changes and "small" vendor exceptions, it doesn't really matter but if the company doesn't have the resources (or interest) the old saying "nobody gets fired by buying IBM" has a meaning. It's a cost issue. Right or wrong, another issue!

Click to read the article this is in response to.

Standards Smandards

0

A standard is something someone mentions in a document or report but has no actual process or intention of ever putting into practice. Actual Standards would render obsolete the current Wild West practices employed by most IT organizations and technology executives.

Standards

0

There are definitions of what a "standard" is. In addition, there are various types of standards e.g. Legal, International, National, Industry, DeFacto (already mentioned), open, closed, etc.

Yes, the standards process can be contentiously long.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <i> <b> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <blockquote> <br /> <br> <p>
  • Lines and paragraphs break automatically.
  • You can use BBCode tags in the text.
  • Web page addresses and e-mail addresses turn into links automatically.

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.

Advertisement: