From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id bb5a577c for ; Thu, 7 Feb 2019 00:46:34 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id 48DF09B8AD; Thu, 7 Feb 2019 10:46:33 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 5F7F19B8A2; Thu, 7 Feb 2019 10:46:01 +1000 (AEST) Received: by minnie.tuhs.org (Postfix, from userid 112) id 2D47E9B8A2; Thu, 7 Feb 2019 10:45:59 +1000 (AEST) Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by minnie.tuhs.org (Postfix) with ESMTPS id 83E8D9B8A1 for ; Thu, 7 Feb 2019 10:45:58 +1000 (AEST) Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 99A8118C07B; Wed, 6 Feb 2019 19:45:57 -0500 (EST) To: tuhs@tuhs.org Message-Id: <20190207004557.99A8118C07B@mercury.lcs.mit.edu> Date: Wed, 6 Feb 2019 19:45:57 -0500 (EST) From: jnc@mercury.lcs.mit.edu (Noel Chiappa) Subject: Re: [TUHS] OSI stack (Was: Posters) X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: jnc@mercury.lcs.mit.edu Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" > From: Larry McVoy > TCP/IP was the first wide spread networking stack that you could get > from a pile of different vendors, Sun, Dec, SGI, IBM's AIX, every kernel > supported it. Well, not quite - X.25 was also available on just about everything. TCP/IP's big advantage over X.25 was that it worked well with LAN's, whereas X.25 was pretty specific to WAN's. Although the wide range of TCP/IP implementations available, as well as the multi-vendor support, and its not being tied to any one vendor, was a big help. (Remember, I said the "_principle_ reason for TCP/IP's success" [emphasis added] was the size of the community - other factors, such as these, did play a role.) The wide range of implementations was in part a result of DARPA's early switch-over - every machine out there that was connected to the early Internet (in the 80s) had to get a TCP/IP, and DARPA paid for a lot of them (e.g. the BBN one for VAX Unix that Berkeley took on). The TOPS-20 one came from that source, a whole bunch of others (many now extinct, but...). MIT did one for MS-DOS as soon as the IBM PC came out (1981), and that spun off to a business (FTP Software) that was quite successful for a while (Windows 95 was, IIRC, the first uSloth product with TCP/IP built in). Etc, etc. Noel