[ih] GOSIP & compliance

[Brian E Carpenter]

Not to knock Interop, but you didn't need to go to Interop to know
that TCP/IP was working and OSI wasn't. I didn't even need to step
away from my desk to know that.

The people in my team working on FTAM to FTP and SMTP to X.400
gateways were pretty clear on the point too.

Regards
    Brian Carpenter

On 20-Mar-22 07:09, Miles Fidelman via Internet-history wrote:
> I seem to recall the story that, once Europeans saw the shownet at one
> of the European Interop shows, and realized that TCP/IP was working,
> while OSI was still vaporware... the game was over.
> 
> Dan.. you'd probably be the one to validate this.
> 
> Miles
> 
> Dan Lynch via Internet-history wrote:
>> At Interop we were a teaching organization about interoperability so while we were TCP/IP bigots if the world was going to OSI we would definitely teach that too. Only a few students signed up for the OSI courses. We 
only offered them for a few years. I think by 91 it disappeared. The buyer is king.
>>
>> Dan
>>
>> Cell 650-776-7313
>>
>>> On Mar 18, 2022, at 11:34 AM, Andrew G. Malis via Internet-history <internet-history at elists.isoc.org> wrote:
>>>
>>> It's been a while, but as I recall, as a part of this requirement,
>>> TCP/IP-to-OSI transition plans were necessary. While I was at BBN, I wrote
>>> such a transition plan for the MILNET (or it might have been for the DoD as
>>> a whole, as I said, things are hazy). I'm sure that it just went on a 
shelf
>>> somewhere once the requirement for a plan was met.
>>>
>>> Cheers,
>>> Andy
>>>
>>>
>>>> On Fri, Mar 18, 2022 at 1:02 PM Bob Purvy via Internet-history <
>>>> internet-history at elists.isoc.org> wrote:
>>>>
>>>> I was around for all this, but probably not as much as some of you. So many
>>>> memories fade...
>>>>
>>>> I've been reading this
>>>> <
>>>> https://courses.cs.duke.edu//common/compsci092/papers/govern/consensus.pdf
>>>>> .
>>>> This passage...
>>>>
>>>>
>>>> *By August 1990, federal agencies were required to procure
>>>> GOSIP-compliantproducts. Through this procurement requirement, the
>>>> government intended to stimulate the market for OSI products. However, many
>>>> network administrators resisted the GOSIP procurement policy and continued
>>>> to operate TCP/IP networks, noting that the federal mandate, by specifying
>>>> only procurement, did not prohibit the use of products built around the
>>>> more familiar and more readily available TCP/IP.*
>>>>
>>>> ... in particular stuck out for me. Admins were required to go OSI, but
>>>> somehow it never happened.  Does anyone have any personal stories to 
relate
>>>> about this, either your own or someone else's?
>>>>
>>>> *Disclosure*: I'm writing historical fiction, mostly because that's what I
>>>> want to do. So there won't be any actual names in whatever I write. I'm
>>>> interested in the private choices people make, not the institutions,
>>>> towering figures, and impersonal forces that most historians write about.
>>>> --
>>>> Internet-history mailing list
>>>> Internet-history at elists.isoc.org
>>>> https://elists.isoc.org/mailman/listinfo/internet-history
>>>>
>>> -- 
>>> Internet-history mailing list
>>> Internet-history at elists.isoc.org
>>> https://elists.isoc.org/mailman/listinfo/internet-history
> 
>