The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Mantas Mikulėnas" <grawity@gmail.com>
To: TUHS <tuhs@tuhs.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: [TUHS] Signal/noise (Was: OSI stack (Was: Posters))
Date: Mon, 4 Feb 2019 01:33:43 +0200	[thread overview]
Message-ID: <CAPWNY8Wx87Qx+gP+bm-YskuGbvu1pXoh2=rWafA50u8zWxSY-w@mail.gmail.com> (raw)
In-Reply-To: <20190203150237.A869418C07A@mercury.lcs.mit.edu>

On Sun, Feb 3, 2019 at 5:03 PM Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
>
>     > From: Warner Losh
>
>     > a bunch of OSI/ISO network stack posters (thank goodness that didn't
>     > become standard, woof!)
>
> Why? The details have faded from my memory, but the lower 2 layers of the
> stack (CLNP and TP4) I don't recall as being too bad. (The real block to
> adoption was that people didn't want to get snarled up in the ISO standards
> process.)
>
> It at least managed (IIRC) to separate the concepts of, and naming for, 'node'
> and 'network interface' (which is more than IPv6 managed, apparently on the
> grounds that 'IPv4 did it that way', despite lengthy pleading that in light of
> increased understanding since IPv4 was done, they were separate concepts and
> deserved separate namespaces). Yes, the allocation of the names used by the
> path selection (I use that term because to too many people, 'routing' means
> 'packet forwarding') was a total dog's breakast (allocation by naming
> authority - the very definition of 'brain-damaged') but TCP/IP's was not any
> better, really.
>
> Yes, the whole session/presentation/application thing was ponderous and probably
> over-complicated, but that could have been ditched and simpler things run
> directly on TP4.
>
> {And apologies for the non-Unix content, but at least it's about computers,
> unlike all the postings about Jimmy Page's guitar; typical of the really poor
> S/N on this list.)
>

With apologies for the outburst:

When I first subscribed to tuhs several years ago (even though I don't
really belong in here; I'm younger than even Linux, much less any of
the Unixen), I *very much* enjoyed reading the various stories about
UUCP, about Sun, about X11, VMS, ARPAnet – often first-hand tales, no
less.

So I don't know what counts as 'signal' on this list versus 'noise',
but I'd much rather read a million posts about OSI, CLNP and other
networks – a history lesson and information that's been getting scarce
in general – than kill/mute yet another thread full of generic "boo M$
Windoze" drivel that I can already find on Reddit.

Thanks,

-- 
Mantas Mikulėnas

  parent reply	other threads:[~2019-02-03 23:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-03 15:02 [TUHS] OSI stack (Was: Posters) Noel Chiappa
2019-02-03 16:51 ` Grant Taylor via TUHS
2019-02-03 23:33 ` Mantas Mikulėnas [this message]
2019-02-04  0:10   ` [TUHS] Signal/noise (Was: OSI stack (Was: Posters)) Arthur Krewat
2019-02-04  0:54   ` Grant Taylor via TUHS
2019-02-04  2:23   ` [TUHS] Signal/noise Warren Toomey
2019-02-04  2:37     ` Larry McVoy
2019-02-04  2:57       ` Bakul Shah
2019-02-04  3:26         ` Warner Losh
2019-02-04  3:26         ` Dan Cross
2019-02-04  4:55         ` Dave Horsfall
2019-02-04  6:20         ` Jon Steinhart
     [not found] ` <CANCZdfq5PM9jFEi9=geC+CTnveXs5CprN7b+ku+s+FYzw1yQBw@mail.gmail.com>
2019-02-06 17:16   ` [TUHS] OSI stack (Was: Posters) 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='CAPWNY8Wx87Qx+gP+bm-YskuGbvu1pXoh2=rWafA50u8zWxSY-w@mail.gmail.com' \
    --to=grawity@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).