From: Paul Winalski <paul.winalski@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] OSI stack (Was: Posters)
Date: Wed, 6 Feb 2019 13:22:08 -0500 [thread overview]
Message-ID: <CABH=_VQ18owDCwCuiHX8Ns8YsK6Q2c6eqtQP1FSDkntonTBKVg@mail.gmail.com> (raw)
In-Reply-To: <20190206174913.E518318C07B@mercury.lcs.mit.edu>
On 2/6/19, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
> > On Wed, Feb 06, 2019 at 10:16:24AM -0700, Warner Losh wrote:
>
> > In many ways, it was a classic second system effect because they were
> > trying to fix everything they thought was wrong with TCP/IP at the time
>
> I'm not sure this part is accurate: the two efforts were contemporaneous; and
> my impression was they were trying to design the next step in networking, based
> on _their own_ analysis of what was needed.
That's my recollection as well. The OSI effort was dominated by the
European telcos, nearly all of which were government-run monopolies.
They were as much (if not more) interested in protecting their own
turf as in developing the next step in networking. A lot of the
complexity came from the desire to be everything to everybody. As is
often the case, the result was being nothing to nobody.
Phase V of DEC's networking product (DECnet) supported X.25 as an
alternative to DEC's proprietary transport/routing layer. I had to
install this on one of our VAXen so we could test DECmail, our
forthcoming X.400 product. I remember X.25 being excessively
complicated and a bear to set up compared to Phase IV DECnet (the
proprietary protocol stack).
-Paul W.
next prev parent reply other threads:[~2019-02-06 18:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 17:49 Noel Chiappa
2019-02-06 18:22 ` Paul Winalski [this message]
2019-02-06 20:47 ` Kevin Bowling
2019-02-07 18:07 ` Grant Taylor via TUHS
2019-02-07 18:22 ` Andy Kosela
2019-02-07 18:33 ` [TUHS] [COFF] " Dan Cross
2019-02-07 18:50 ` [TUHS] " Larry McVoy
-- strict thread matches above, loose matches on Subject: below --
2019-02-07 19:04 Noel Chiappa
2019-02-07 1:03 Noel Chiappa
2019-02-07 0:45 Noel Chiappa
2019-02-07 0:02 Noel Chiappa
2019-02-07 0:11 ` Kevin Bowling
2019-02-06 23:18 Noel Chiappa
2019-02-06 23:40 ` Kevin Bowling
2019-02-06 23:52 ` Larry McVoy
2019-02-07 0:04 ` Kevin Bowling
2019-02-04 20:29 Noel Chiappa
2019-02-04 21:13 ` Bakul Shah
2019-02-04 21:34 ` Clem Cole
2019-02-05 18:01 ` Grant Taylor via TUHS
2019-02-03 18:49 Norman Wilson
2019-02-03 15:02 Noel Chiappa
2019-02-03 16:51 ` Grant Taylor via TUHS
[not found] ` <CANCZdfq5PM9jFEi9=geC+CTnveXs5CprN7b+ku+s+FYzw1yQBw@mail.gmail.com>
2019-02-06 17:16 ` Warner Losh
2019-02-06 17:23 ` Larry McVoy
2019-02-06 23:37 ` George Michaelson
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=_VQ18owDCwCuiHX8Ns8YsK6Q2c6eqtQP1FSDkntonTBKVg@mail.gmail.com' \
--to=paul.winalski@gmail.com \
--cc=jnc@mercury.lcs.mit.edu \
--cc=tuhs@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).