The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: John Cowan <cowan@ccil.org>
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>,
	The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Research Datakit notes
Date: Sun, 26 Jun 2022 06:35:52 -0700	[thread overview]
Message-ID: <20220626133552.GJ28639@mcvoy.com> (raw)
In-Reply-To: <CAD2gp_Q_WQySZJWXenqysLvFckQWptLoO=X3THMSVaBqDSewPg@mail.gmail.com>

On Sun, Jun 26, 2022 at 09:07:49AM -0400, John Cowan wrote:
> On Sat, Jun 25, 2022 at 10:20 PM Noel Chiappa <jnc@mercury.lcs.mit.edu>
> wrote:
> 
> 
> > it had things called 'flows' which were half way between pure
> > datagrams (i.e. no setup - you just stick the right destination address in
> > the
> > header and send it off) and VCs (read the RFCs if you want to kow why),
> >
> 
> In that connection I have always admired Padlipsky's RFC 962, which
> exploits the existing TCP architecture to do just this.  So simple, so
> easy, so Unixy.

I knew Mike, interesting dude.  His "The Elements of Networking Style" is
a very fun read but also, for me, just getting to understand networking,
it snapped a bunch of stuff into focus.  I think you have to read it
at just the right spot in your career and I did.  Great little book and
full of jabs like "If you know what you are doing, 3 layers are enough.
If you don't, 7 aren't."

  reply	other threads:[~2022-06-26 13:36 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-26  2:19 Noel Chiappa
2022-06-26  9:46 ` steve jenkin
2022-06-26 20:35   ` Erik Fair
2022-06-26 21:53     ` Steve Jenkin
2022-06-26 10:16 ` Paul Ruizendaal via TUHS
2022-06-26 13:07 ` John Cowan
2022-06-26 13:35   ` Larry McVoy [this message]
2022-06-26 13:58     ` John Cowan
  -- strict thread matches above, loose matches on Subject: below --
2022-06-28 15:50 Noel Chiappa
2022-06-28 21:32 ` Lawrence Stewart
2022-06-27 21:40 Noel Chiappa
2022-06-27 22:40 ` George Michaelson
2022-06-27  0:43 Noel Chiappa
2022-06-27  3:00 ` Erik Fair
2022-06-25 23:01 [TUHS] " Paul Ruizendaal
2022-06-25 23:09 ` [TUHS] " Larry McVoy
2022-06-25 23:57   ` Rob Pike
2022-06-26  1:17     ` Paul Ruizendaal
2022-07-02  2:51       ` Grant Taylor via TUHS
2022-07-02  2:57         ` Larry McVoy
2022-06-28 10:38     ` Derek Fawcus
2022-06-28 12:36       ` Rob Pike
2022-06-28 12:45         ` Rob Pike
2022-06-28 13:33           ` Dan Cross
2022-06-28 21:19             ` Lawrence Stewart
2022-06-28 21:34               ` Richard Salz
2022-06-29  6:07                 ` Stuart Remphrey
2022-06-28 16:11           ` Tom Teixeira
2022-06-28 18:28           ` John Floren
2022-06-28 12:47         ` Rich Morin
2022-06-28 13:13           ` Marc Donner
2022-06-28 14:41             ` Clem Cole
2022-06-28 15:54               ` Tom Teixeira
2022-06-28 17:05             ` Adam Thornton
2022-06-28 17:43               ` John Labovitz
2022-06-26  1:41 ` Anthony Martin
2022-06-26  9:52   ` Ralph Corderoy
2022-06-26 11:04   ` Paul Ruizendaal
2022-06-29 20:21   ` Paul Ruizendaal

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=20220626133552.GJ28639@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=cowan@ccil.org \
    --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).