From: Andy Kosela <akosela@andykosela.com>
To: Grant Taylor <gtaylor@tnetconsulting.net>
Cc: TUHS <tuhs@minnie.tuhs.org>, COFF <coff@minnie.tuhs.org>
Subject: Re: [TUHS] OSI stack (Was: Posters)
Date: Thu, 7 Feb 2019 12:22:14 -0600 [thread overview]
Message-ID: <CALMnNGgimhHrCLR4sLfD3-fhhSxm45gyhfSUbDV8VMJsEqxCbA@mail.gmail.com> (raw)
In-Reply-To: <0572e855-9aac-337f-4f1b-66dda3839e14@spamtrap.tnetconsulting.net>
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
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.
--Andy
[-- Attachment #2: Type: text/html, Size: 1210 bytes --]
next prev parent reply other threads:[~2019-02-07 18:23 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
2019-02-06 20:47 ` Kevin Bowling
2019-02-07 18:07 ` Grant Taylor via TUHS
2019-02-07 18:22 ` Andy Kosela [this message]
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=CALMnNGgimhHrCLR4sLfD3-fhhSxm45gyhfSUbDV8VMJsEqxCbA@mail.gmail.com \
--to=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).