The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] In memoriam: Jon Postel
Date: Tue, 16 Oct 2018 07:13:07 -0400 (EDT)	[thread overview]
Message-ID: <20181016111307.26DD318C08D@mercury.lcs.mit.edu> (raw)

    > From: Dave Horsfall

    > We lost Jon Postel, regarded as the Father of the Internet

Vint and Bob Kahn might disagree with that that... :-)

    > (due to his many RFCs)

You need to distinguish between the many for which he was an editor (e.g. IP,
TCP, etc), and the (relatively few, compared to the others) which he actually
wrote himself, e.g. RFC-925, "Multi-LAN address resolution".

Not that he didn't make absolutely huge contributions, but we should be
accurate.

	Noel


             reply	other threads:[~2018-10-16 11:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-16 11:13 Noel Chiappa [this message]
2018-10-29  1:48 ` Dave Horsfall
  -- strict thread matches above, loose matches on Subject: below --
2018-10-16  4:35 Dave Horsfall
2018-10-16 14:01 ` Kaveh Ranjbar 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=20181016111307.26DD318C08D@mercury.lcs.mit.edu \
    --to=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).