From: Jason Stevens <jsteve@superglobalmegacorp.com>
To: SPC <spedraja@gmail.com>, "tuhs@minnie.tuhs.org" <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] ISO, OSI, and DECnet (was Re: If not Linux, then what?)
Date: Thu, 29 Aug 2019 22:54:13 +0800 [thread overview]
Message-ID: <1d3d8c9a-7006-4666-b32e-8fa4fc5e9f7c@PU1APC01FT039.eop-APC01.prod.protection.outlook.com> (raw)
In-Reply-To: <CACytpF-E3C+VrFSXat+jKWiCOToyoDB4b5n9Jj723H=qSgxDXg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1871 bytes --]
Although I never have seen OSI in the wild, it was the one great thing about ‘Winsock’ is that it worked over TCP/IP , IPX/SPX, AppletTalk and Decnet. It was fun to convert a BBS from being telnet to some ‘telnet over decnet’ monster I built.
Although I’m guessing OSI would have allowed for common ‘network’ applications to use different network topologies?
I really need to get OSF/1 2.0 installed.
From: SPC
Sent: Thursday, August 29, 2019 3:30 AM
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] ISO, OSI, and DECnet (was Re: If not Linux, then what?)
It's a bit funny (at least for me) because I was talking about DECNET as OSI standard and TCP/IP and OSI differences some days ago to the group of students of a course on network operation that I am teaching.
On the other hand I don't that book about networking. I'd like to get one copy bit I live in Spain. Shipment is not a problem but perhaps to deal with shipping procedures abroad is not what you have in mind :-)
Cordiales saludos / Best Regards / Salutations / Freundliche Grüße
-----
Sergio Pedraja
Senior Technician in Computer Science, Systems Administration, and Information Security. MBA. Qualified occupational trainer.
El mié., 28 ago. 2019 20:24, Kurt H Maier <khm@sciops.net> escribió:
On Wed, Aug 28, 2019 at 10:24:51AM -0700, Larry McVoy wrote:
>
> The great Mike Padlipski said "do you want protocols that look nice or
> protocols that work nice?" in his fantastic book Elements of Networking
> Style [*].
>
This book taught me as much about navigating bureaucracy and the warning
signs of impending death-by-committee as it did about networking. I
keep a copy on my shelf at the office and annoy my staff with it
regularly. It's also a wonderful time capsule that provides a lot of
context about how we got where we are.
khm
[-- Attachment #2: Type: text/html, Size: 3947 bytes --]
next prev parent reply other threads:[~2019-08-29 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 16:50 Paul Winalski
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 [this message]
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=1d3d8c9a-7006-4666-b32e-8fa4fc5e9f7c@PU1APC01FT039.eop-APC01.prod.protection.outlook.com \
--to=jsteve@superglobalmegacorp.com \
--cc=spedraja@gmail.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).