The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] V7 Addendem [ really lawyers and AT&T consent decree ]
Date: Tue, 12 Dec 2017 08:59:14 -0500 (EST)	[thread overview]
Message-ID: <20171212135914.EE38218C087@mercury.lcs.mit.edu> (raw)

    > From: George Michaelson

    > I didn't mean to disrespect the people who did the models or the
    > protocol or standards work btw.

Oh, I personally have no problem with you saying hard things about this work,
as long as it's what you really think. One never finds the truth unless one is
willing to look hard, neh? And I'm pretty sure Dave Clark (who was a leading
light in IntServ) would be OK with you doing so too (I worked very closely
with him for years, to the point where I deputized for him at meetings).

I honestly don't remember exactly what my take was on IntServ and RSVP; I'd
have to go look. I recollect seeing the case that _if resources were limited_,
certain classes of application (I guess we called them 'inelastic') would need
reservations to work properly. So I was probably susceptible to the argument
that 'if we've got bandwidth to light our <insert flammable objects> with, we
don't need resource reservation'. And I remember being not _thrilled_ with
RSVP, but I don't recall exactly why.

But, as, you said, wrong list. Maybe internet-history:

  http://mailman.postel.org/mailman/listinfo/internet-history

if you did want to delve into it.

	Noel


             reply	other threads:[~2017-12-12 13:59 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 13:59 Noel Chiappa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-12-12  2:04 Noel Chiappa
2017-12-12  2:17 ` George Michaelson
2017-12-12  1:28 Noel Chiappa
2017-12-12  1:42 ` George Michaelson
2017-12-11 19:23 Noel Chiappa
2017-12-12 16:04 ` Random832
2017-12-06  0:33 [TUHS] V7 Addendem Warner Losh
2017-12-06  1:07 ` Warren Toomey
2017-12-06 16:11   ` Random832
2017-12-06 16:15     ` Jon Steinhart
2017-12-06 18:39       ` Clem Cole
2017-12-06 18:49         ` [TUHS] V7 Addendem [ really lawyers and AT&T consent decree ] Jon Steinhart
2017-12-06 18:53           ` Warner Losh
2017-12-06 18:58             ` Jon Steinhart
2017-12-06 18:54           ` Clem Cole
2017-12-06 19:20             ` William Pechter
2017-12-07 14:26               ` Ron Natalie
2017-12-06 19:23           ` William Corcoran
2017-12-06 20:30             ` Kurt H Maier
2017-12-06 23:59               ` George Michaelson
2017-12-07 14:03               ` Ron Natalie
2017-12-07 15:34                 ` William Corcoran
2017-12-07  5:08             ` Jon Steinhart
2017-12-07 15:09               ` Larry McVoy
2017-12-11 18:17           ` Paul Winalski
2017-12-11 18:39             ` Clem Cole
2017-12-12  0:27               ` Steve Johnson
2017-12-13 17:09                 ` Jason Stevens
2017-12-13 17:05               ` Jason Stevens
2017-12-11 20:11             ` William Cheswick
2017-12-11 23:26               ` Arthur Krewat

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=20171212135914.EE38218C087@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    /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).