From: Dan Cross <crossd@gmail.com>
To: Andy Kosela <akosela@andykosela.com>
Cc: TUHS <tuhs@minnie.tuhs.org>, COFF <coff@minnie.tuhs.org>,
Grant Taylor <gtaylor@tnetconsulting.net>
Subject: Re: [TUHS] [COFF] OSI stack (Was: Posters)
Date: Thu, 7 Feb 2019 13:33:05 -0500 [thread overview]
Message-ID: <CAEoi9W4VDeV-hXtqd_3tBKCACT-F6s5Kya3wgEzB1=npnM-uOg@mail.gmail.com> (raw)
In-Reply-To: <CALMnNGgimhHrCLR4sLfD3-fhhSxm45gyhfSUbDV8VMJsEqxCbA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
On Thu, Feb 7, 2019 at 1:22 PM Andy Kosela <akosela@andykosela.com> wrote:
> On Thursday, February 7, 2019, Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
> wrote:
>
>> Seeing as how this is diverging from TUHS, I'd encourage replies to the
>> COFF copy that I'm CCing.
>>
>> On 02/06/2019 01:47 PM, Kevin Bowling wrote:
>>
>>> There were protocols that fit better in the era like DeltaT with a
>>> simpler state machine and connection handling. Then there was a mad dash
>>> of protocol development in the mid to late ‘80s that were measured by
>>> various metrics to outperform TCP in practical and theoretical space. Some
>>> of these seemed quite nice like XTP and are still in use in niche defense
>>> applications.
>>>
>>
>> $ReadingList++
>
>
> XTP was/is indeed very interesting. It was adopted by US Navy for SAFENET
> and created by Greg Chesson who was active in the early UNIX community.
> Not sure if we have him here on this list though.
>
Sadly, Greg Chesson passed away a couple of years ago after battling cancer
for some time.
- Dan C.
[-- Attachment #2: Type: text/html, Size: 1730 bytes --]
next prev parent reply other threads:[~2019-02-07 18:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 17:49 [TUHS] " 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:33 ` Dan Cross [this message]
2019-02-07 18:50 ` Larry McVoy
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='CAEoi9W4VDeV-hXtqd_3tBKCACT-F6s5Kya3wgEzB1=npnM-uOg@mail.gmail.com' \
--to=crossd@gmail.com \
--cc=akosela@andykosela.com \
--cc=coff@minnie.tuhs.org \
--cc=gtaylor@tnetconsulting.net \
--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).