From: Dave Taht <dave.taht@gmail.com>
To: "Eggert, Lars" <lars@netapp.com>
Cc: Ross Callon <rcallon@juniper.net>,
Alaric Moore <alaricmeister@gmail.com>,
bloat <bloat@lists.bufferbloat.net>,
"aqm@ietf.org" <aqm@ietf.org>, Lixia Zhang <lixia@cs.ucla.edu>
Subject: Re: [Bloat] [aqm] Nugget from IETF-1 proceedings
Date: Fri, 17 Jan 2014 08:28:51 -0500 [thread overview]
Message-ID: <CAA93jw71vVCzhOUqzdE-omSaxMYq6wqmTZaaj0F5TPcj+qP__A@mail.gmail.com> (raw)
In-Reply-To: <BC39A23A-1A4F-4B24-8CC5-9A63ECF6B650@netapp.com>
On Fri, Jan 17, 2014 at 3:46 AM, Eggert, Lars <lars@netapp.com> wrote:
> Nothing new under the sun. Proceedings from the very first IETF meeting, held 28 years ago today:
>
> "Nagle presented his 'fair queuing' scheme, in which gateways maintain separate queues for each sending host. In this way, hosts with pathological implementations can not usurp more than their fair share of the gateway’s resources. This invoked spirited and interested discussion. Zhang pointed out that this was a subtle change in architecture away from a pure datagram network. Callon reminded everyone that he had written a paper advocating a connection oriented Internet Protocol several years ago."
>
> https://www.ietf.org/proceedings/01.pdf, page 5
It actually starts at page 88.
Reading the rest was great. Wow. What a wonderful piece of history!
Thank you for digging that up!
Seeing the problems they were trying to solve at the time was very revealing.
"1000 nodes running at 9600 baud, with one outage every 5 minutes will
only use 20% of the bandwidth for routing information"
And nagles preso retains many cogent points, although I guess "source
quench" was all the rage at the time.
> Lars
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
parent reply other threads:[~2014-01-17 13:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <BC39A23A-1A4F-4B24-8CC5-9A63ECF6B650@netapp.com>]
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw71vVCzhOUqzdE-omSaxMYq6wqmTZaaj0F5TPcj+qP__A@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=alaricmeister@gmail.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=lars@netapp.com \
--cc=lixia@cs.ucla.edu \
--cc=rcallon@juniper.net \
/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