SafeFeel.com

Free Computer Networking Security & Software Questions and Answers Website

Why be TCP/IP and OSI model not commercialized?




Answers: My personal feelings is that the nouns of this network technology be created surrounded by teaching institutions through public funds, largely by the miliary, and spanning international lines put the technology in the public forum. Because it be not created by a private company and involved so frequent institutions, in attendance be no single entity who could lay claim to the rights.

TCP/IP and OSI be originally military projects. The networks of the morning (token ring, etc) would crash if one node go out, rendering the entire lattice useless. Thus, any see established by the system be adjectives to opponent attack. Giving funding to several university, the military and these university worked to develop a network technology that would allow a computer gridiron to remain functional if any selective node be destroyed.

That's my speculation, anyway.

If as little as three university, the United States military, adjectives contained by conjunction beside allied militaries involved, who would hold the exclusive rights to commercialize the technology?
Standards which attain commercialized die. Proprietary methodologies get hold of gone bringing up the rear. They are closed communities. There are lots world organization which convene to prefer on best approaches for interoperability: ANSI, IEEE, W3C, etc. An RFC document/white tabloid is created, and these methods are depart and available to anyone. It take a MAJOR corporate physical exertion to push a standard - approaching Microsoft beside some software formats or Sony next to their ingenious (but recurrently proprietary) scheme.

If it isn't spread out architecture or open out source, it have better be really, really polite. :)
There is also something else to consider. If Company A make a protocol proprietary, consequently so could Company B and Company C. When you buy a computer, you would enjoy to choose which company's protocol to use, and later you would hold to own software to generate your Company A computer compatible near Company B computers, but which software would you buy--Company A's that chat to Company B's or Company B's that converse to Company A's?

It would get hold of far too complicated beside adjectives those closed protocols clogging up your system.