<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">OSI is the network of the future and always will be.<div class=""><br class=""></div><div class="">RB<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Feb 18, 2019, at 6:20 PM, Scott O. Bradner <<a href="mailto:sob@sobco.com" class="">sob@sobco.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">and OSI (i.e. GOSIP) was a procurement requirement for a while (at least for government funded projects and some big companies)<br class="">and pushed as the future by most trade and rags and industry analysts (mostly the same ones that later pushed ATM as the future)<br class=""><br class="">Scott<br class=""><br class=""><br class=""><blockquote type="cite" class="">On Feb 18, 2019, at 8:15 PM, Richard Bennett <<a href="mailto:richard@bennett.com" class="">richard@bennett.com</a>> wrote:<br class=""><br class="">ISO/OSI was backed by the Commerce Department, but TCP was the darling of the Defense Department.<br class=""><br class="">RB<br class=""><br class=""><blockquote type="cite" class="">On Feb 18, 2019, at 5:26 PM, Scott O. Bradner <<a href="mailto:sob@sobco.com" class="">sob@sobco.com</a>> wrote:<br class=""><br class="">agree - it did not get much - even with Marshall’s book behind it - maybe big companies were not comfortable in betting their <br class="">future on small-company code - but that is just a guess<br class=""><br class="">one thing different about what Dennis was trying to do - he would have had a government-blessed implementation<br class="">which would allow the governments that were pushing OSI (like the US) something to point at to justify their<br class="">regulations<br class=""><br class="">Scott<br class=""><br class=""><br class=""><blockquote type="cite" class="">On Feb 18, 2019, at 7:07 PM, Clem cole <<a href="mailto:clemc@ccc.com" class="">clemc@ccc.com</a>> wrote:<br class=""><br class="">Scott Point taken but what about Marshall Rose’s ISODE: <a href="https://en.m.wikipedia.org/wiki/ISO_Development_Environment" class="">https://en.m.wikipedia.org/wiki/ISO_Development_Environment</a><br class=""><br class="">It was available but never got any traction as far as I can tell. <br class=""><br class="">Clem<br class=""><br class="">Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite. <br class=""><br class="">On Feb 18, 2019, at 6:26 PM, Scott O. Bradner <<a href="mailto:sob@sobco.com" class="">sob@sobco.com</a>> wrote:<br class=""><br class=""><blockquote type="cite" class="">Dennis Jennings tells a story relating to this topic - he said that he was involved in an effort to get a set of OSI code <br class="">produced & released along the same line as the Berkeley TCP/IP code but at the very last minute the vendor that<br class="">was going to provide the code, one that sold OSI code to vendors, backed out because they thought it would<br class="">be bad for their business model - the discussion might have been different if Dennis had succeeded, instead<br class="">that vendor’s business died along with the OSI protocols<br class=""><br class="">Scott<br class=""><br class=""><blockquote type="cite" class="">On Feb 18, 2019, at 5:06 PM, Dave Crocker <<a href="mailto:dhc@dcrocker.net" class="">dhc@dcrocker.net</a>> wrote:<br class=""><br class="">On February 18, 2019 11:42:12 AM PST, Clem Cole <<a href="mailto:clemc@ccc.com" class="">clemc@ccc.com</a>> wrote:<br class=""><br class=""><br class="">On Sat, Feb 16, 2019 at 5:58 PM Brian E Carpenter <<a href="mailto:brian.e.carpenter@gmail.com" class="">brian.e.carpenter@gmail.com</a>> wrote:<br class="">They, like many other companies, had been told by many officials<br class="">in the USA and Europe (and a bit later in Asia) that OSI would be<br class="">a government procurement requirement. That triggered a lot of<br class="">investment in product development.<br class=""><br class=""><a href="https://en.wikipedia.org/wiki/Government_Open_Systems_Interconnection_Profile" class="">https://en.wikipedia.org/wiki/Government_Open_Systems_Interconnection_Profile</a><br class=""><br class="">Plus large manufacturing firms such as GM and Boeing were drinking the coolaid with their MAP/TOP push<br class="">https://en.wikipedia.org/wiki/Manufacturing_Automation_Protocol which was OSI based (plus those folks did not believe in Ethernet - they were sure it would not work on a manufacturing floor). <br class=""><br class="">But as I said, economics won out. The HW they promoted was just too expensive and the SW never really matured. As others pointed out, the cost of an OSI implementation was huge. Even teleco standards like X.25 ended up not being worth it. Just not enough people bought them to make it so it was worth it.<br class=""><br class="">In the end, MAP/GOSIP et al went away - because why would you guy something that cost more and in the end, did less?<br class="">ᐧ<br class=""><br class="">I suggest that what won out was usability in the large and in the small. The Internet supplied an actual and large installed base of connected users. OSI really never did. And the Iinternet tools were useul and reasonably easy to use. The OSI tools were not.<br class="">-- <br class="">Dave Crocker<br class="">bbiw.net<br class=""><br class="">via phone<br class="">_______<br class="">internet-history mailing list<br class="">internet-history@postel.org<br class="">http://mailman.postel.org/mailman/listinfo/internet-history<br class="">Contact list-owner@postel.org for assistance.<br class=""></blockquote><br class=""><br class="">_______<br class="">internet-history mailing list<br class=""><a href="mailto:internet-history@postel.org" class="">internet-history@postel.org</a><br class="">http://mailman.postel.org/mailman/listinfo/internet-history<br class="">Contact list-owner@postel.org for assistance.<br class=""></blockquote></blockquote><br class=""><br class="">_______<br class="">internet-history mailing list<br class=""><a href="mailto:internet-history@postel.org" class="">internet-history@postel.org</a><br class="">http://mailman.postel.org/mailman/listinfo/internet-history<br class="">Contact list-owner@postel.org for assistance.<br class=""></blockquote><br class="">—<br class="">Richard Bennett<br class="">High Tech Forum Founder<br class="">Ethernet & Wi-Fi standards co-creator<br class=""><br class="">Internet Policy Consultant<br class=""><br class=""></blockquote><br class=""></div></div></blockquote></div><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">—<br class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Richard Bennett<br class=""><a href="http://hightechforum.org" class="">High Tech Forum</a> Founder</div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Ethernet & Wi-Fi standards co-creator</div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""></div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Internet Policy Consultant</div></div></div>
</div>
<br class=""></div></body></html>