The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: George Michaelson <ggm@algebras.org>
To: Warner Losh <imp@bsdimp.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>,
	Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [TUHS] OSI stack (Was: Posters)
Date: Thu, 7 Feb 2019 09:37:57 +1000	[thread overview]
Message-ID: <CAKr6gn2eYhD++5DLzMRqo44WGK5_ki598_4RVVWof2A_TF_v1A@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfp8qHwFRno253gKAtKoX9iFz8W3neGMhrokKrWr+dN3OA@mail.gmail.com>

Alive and well in LDAP as a syntactic form. So, strongly alive in
functional systems worldwide, and in X.509 certificates.

As a typed entity in email addresses? NOPE.

-G

On Thu, Feb 7, 2019 at 3:17 AM Warner Losh <imp@bsdimp.com> wrote:
>
>
>
> On Mon, Feb 4, 2019 at 8:43 PM Warner Losh <imp@bsdimp.com> wrote:
>>
>>
>>
>> On Sun, Feb 3, 2019, 8:03 AM 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?
>>
>>
>> Posters like this :). OSI was massively over specified...
>
>
> oops. Hit the list limit.
>
> Posters like this:
>
> https://people.freebsd.org/~imp/20190203_215836.jpg
>
> which show just how over-specified it was. I also worked at The Wollongong Group back in the early 90's and it was a total dog on the SysV 386 machines that we were trying to demo it on. A total and unbelievable PITA to set it up, and crappy performance once we got it going. Almost bad enough that we didn't show it at the trade show we were going to....  And that was just the lower layers of the stack plus basic name service. x.400 email addresses were also somewhat overly verbose. 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 without really, truly knowing the differences between actual problems and mere annoyances and how to properly weight the severity of the issue in coming up with their solutions.
>
> So x.400 vs smtp mail addresses: "G=Warner;S=Losh;O=WarnerLoshConsulting;PRMD=bsdimp;A=comcast;C=us" vis "imp@bsdimp.com"
>
> (assuming I got all the weird bits of the x.400 address right, it's been a long time and google had no good examples on the first page I could just steal...) The x.400 addresses were so unwieldy that a directory service was added on top of them x.500, which was every bit as baroque IIRC.
>
> TP4 might not have been that bad, but all the stuff above it was kinda crazy...
>
> Warner

  parent reply	other threads:[~2019-02-06 23:38 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-03 15:02 Noel Chiappa
2019-02-03 16:51 ` Grant Taylor via TUHS
2019-02-03 23:33 ` [TUHS] Signal/noise (Was: OSI stack (Was: Posters)) Mantas Mikulėnas
2019-02-04  0:10   ` 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 [this message]
2019-02-03 18:49 Norman Wilson
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-06 17:49 Noel Chiappa
2019-02-06 18:22 ` Paul Winalski
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:50     ` Larry McVoy
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-07  0:02 Noel Chiappa
2019-02-07  0:11 ` Kevin Bowling
2019-02-07  0:45 Noel Chiappa
2019-02-07  1:03 Noel Chiappa
2019-02-07 19:04 Noel Chiappa

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=CAKr6gn2eYhD++5DLzMRqo44WGK5_ki598_4RVVWof2A_TF_v1A@mail.gmail.com \
    --to=ggm@algebras.org \
    --cc=imp@bsdimp.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).