Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!ames!sdcsvax!ucbvax!SUN.COM!melohn
From: melohn@SUN.COM.UUCP
Newsgroups: comp.protocols.tcp-ip
Subject: Re: COS goes with TCP/IP
Message-ID: <8706180716.AA00688@sluggo.wseng.sun.com.com>
Date: Thu, 18-Jun-87 03:16:54 EDT
Article-I.D.: sluggo.8706180716.AA00688
Posted: Thu Jun 18 03:16:54 1987
Date-Received: Sat, 20-Jun-87 01:05:47 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: Sun Microsystems, Mountain View
Lines: 13

In article <8706172248.AA21271@jupiter.bellcore.com> karn@JUPITER.BELLCORE.COM (Phil R. Karn) writes:
>This item appears on page 15 of the June 1987 issue of Data Communications.
>... It seems the decision to go with TCP/IP -- even though
>several COS members, including IBM, Retix, and Touch Communications, for
>example, now offer OSI network/transport-layer products -- was made
>reluctantly, because the vendors whose gear COS researchers wanted (Sun,
>Bridge) do not offer OSI connections.

The article is amusing, but grossly inaccurate, since Sun currently
has a broader offering of OSI products than IBM, Retix, or Touch. Even
so, with many protocols yet to be fully defined, OSI as it stands today
is not complete enough to replace a fully designed and implemented
family of protocols like TCP/IP.