From: <ron@ronnatalie.com>
To: "'Noel Chiappa'" <jnc@mercury.lcs.mit.edu>, <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Origins of PPP
Date: Thu, 5 Dec 2019 14:21:13 -0500 [thread overview]
Message-ID: <0e2901d5aba1$2932ff30$7b98fd90$@ronnatalie.com> (raw)
In-Reply-To: <20191205190546.AE4E418C089@mercury.lcs.mit.edu>
I still remember the laughter at the IETC when someone asked if PPP stood
for "Philip Pindeville's Protocol."
> -----Original Message-----
> From: TUHS <tuhs-bounces@minnie.tuhs.org> On Behalf Of Noel Chiappa
> Sent: Thursday, December 5, 2019 2:06 PM
> To: tuhs@minnie.tuhs.org
> Cc: jnc@mercury.lcs.mit.edu
> Subject: Re: [TUHS] Origins of PPP
>
> > From: Paul Ruizendaal
>
> > I'm looking for the origins of SLIP and PPP on Unix. Both seem to
have
> > been developed long before their RFC's appeared.
>
> You're dealing with an epoch when the IETF motto - "rough consensus and
> running code" - really meant something. Formal RFC's way lagged protocol
> development; they're the last step in the process, pretty much.
>
> If you want to study the history, you'd need to look at Internet Drafts
(if
> they're still online). Failing that, look at the IETF Proceedings; I think
all the
> ones from this period have been scanned in. They won't have the detail
that
> the I-D's would have, but they should give the rough outlines of the
history.
>
> Noel
next prev parent reply other threads:[~2019-12-05 19:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 19:05 Noel Chiappa
2019-12-05 19:21 ` ron [this message]
2019-12-05 19:37 ` Warner Losh
-- strict thread matches above, loose matches on Subject: below --
2019-12-05 10:34 Paul Ruizendaal
2019-12-05 10:58 ` Michael Kjörling
2019-12-05 15:50 ` Richard Salz
2019-12-05 16:39 ` Clem Cole
2019-12-05 19:41 ` Warner Losh
2019-12-05 21:03 ` Clem Cole
2019-12-05 23:09 ` Doug McIntyre
2019-12-06 2:05 ` Lawrence Stewart
2019-12-06 18:31 ` Warner Losh
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='0e2901d5aba1$2932ff30$7b98fd90$@ronnatalie.com' \
--to=ron@ronnatalie.com \
--cc=jnc@mercury.lcs.mit.edu \
--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).