The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: [TUHS] ISO, OSI, and DECnet (was Re:  If not Linux, then what?)
Date: Wed, 28 Aug 2019 12:50:36 -0400	[thread overview]
Message-ID: <CABH=_VTKJQ-+0h-PwbNta1CAgtO=8quGV9RonWDP64MoteeG9Q@mail.gmail.com> (raw)

On 8/28/19, Clem Cole <clemc@ccc.com> wrote:
> On Wed, Aug 28, 2019 at 2:46 AM Peter Jeremy <peter@rulingia.com> wrote:
>
> Tru64 talked to DECnet Phase X (I don't remember which one, maybe 4 or 5),
> which had become an ISO/OSI stack by that point for political reasons
> inside of Digital (the OSI vs TCP war reminded me of the Pascal vs C and
> VMS vs UNIX wars - all very silly in retrospect, but I guess it was really
> about who got which $s for development).

It was DECnet Phase V that was based on the ISO/OSI stack.  IIRC, at
the time the European telcos were pushing OSI, it had become an ISO
standard, etc. etc.  It was also pretty easy to compatibly slide the
legacy proprietary DECnet Phase IV adaptive routing and virtual
circuit layers into the OSI stack.

TCP won the war, of course.  The risk with international standards
fashioned out of whole cloth by a committee (as opposed to being a
regularization of existing practice) is that the marketplace may
choose to ignore the "standard".  OSI and the Ada programming language
are cases in point.

-Paul W.

             reply	other threads:[~2019-08-28 16:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28 16:50 Paul Winalski [this message]
2019-08-28 17:24 ` Larry McVoy
2019-08-28 17:45   ` Jon Forrest
2019-08-28 17:50     ` Larry McVoy
2019-08-28 18:17   ` Kurt H Maier
2019-08-28 19:29     ` SPC
2019-08-29  0:29       ` George Michaelson
2019-08-29 14:54       ` Jason Stevens
2019-08-30  9:32         ` Wesley Parish
2019-08-30 13:59           ` Clem Cole
2019-08-31 23:38         ` Grant Taylor via TUHS

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CABH=_VTKJQ-+0h-PwbNta1CAgtO=8quGV9RonWDP64MoteeG9Q@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=clemc@ccc.com \
    --cc=tuhs@minnie.tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).