[ih] When did "32" bits for IP register as "not enough"?

[Joe Touch]

FWIW, there was a version of OSI that anyone could get from UPenn. While I was a grad student there (88-92), I ended up handling requests, which involved making a tape in the format of the requester’s choosing (9-track, 8mm, etc.) and packing it up with a few “ISO/OSI” enamel pins and shipping it out. I recall only 2-3 such requests, though.

Joe

> On Feb 18, 2019, at 4:14 PM, Andrew Russell <arussell at arussell.org> wrote:
> 
> I’d be very interested to learn the identity of that vendor, and equally interested to hear educated guesses. 
> 
> Andy 
> 
>> On Feb 18, 2019, at 6:26 PM, Scott O. Bradner <sob at sobco.com> wrote:
>> 
>> 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 
>> produced & released along the same line as the Berkeley TCP/IP code but at the very last minute the vendor that
>> was going to provide the code, one that sold OSI code to vendors, backed out because they thought it would
>> be bad for their business model - the discussion might have been different if Dennis had succeeded, instead
>> that vendor’s business died along with the OSI protocols
>> 
>> Scott
>> 
>>> On Feb 18, 2019, at 5:06 PM, Dave Crocker <dhc at dcrocker.net> wrote:
>>> 
>>> On February 18, 2019 11:42:12 AM PST, Clem Cole <clemc at ccc.com> wrote:
>>> 
>>> 
>>> On Sat, Feb 16, 2019 at 5:58 PM Brian E Carpenter <brian.e.carpenter at gmail.com> wrote:
>>> They, like many other companies, had been told by many officials
>>> in the USA and Europe (and a bit later in Asia) that OSI would be
>>> a government procurement requirement. That triggered a lot of
>>> investment in product development.
>>> 
>>> https://en.wikipedia.org/wiki/Government_Open_Systems_Interconnection_Profile
>>> 
>>> Plus large manufacturing firms such as GM and Boeing were drinking the coolaid with their MAP/TOP push
>>> 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).  
>>> 
>>> 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.
>>> 
>>> In the end, MAP/GOSIP et al went away - because why would you guy something that cost more and in the end, did less?
>>> ᐧ
>>> 
>>> 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.
>>> -- 
>>> Dave Crocker
>>> bbiw.net
>>> 
>>> via phone
>>> _______
>>> internet-history mailing list
>>> internet-history at postel.org
>>> http://mailman.postel.org/mailman/listinfo/internet-history
>>> Contact list-owner at postel.org for assistance.
>> 
>> 
>> _______
>> internet-history mailing list
>> internet-history at postel.org
>> http://mailman.postel.org/mailman/listinfo/internet-history
>> Contact list-owner at postel.org for assistance.
> 
> 
> _______
> internet-history mailing list
> internet-history at postel.org
> http://mailman.postel.org/mailman/listinfo/internet-history
> Contact list-owner at postel.org for assistance.