Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Dave Taht <dave@taht.net>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: Hari Balakrishnan <hari@csail.mit.edu>,
	Prateesh Goyal <g.pratish@gmail.com>,
	ECN-Sane <ecn-sane@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>,
	Mohammad Alizadeh <alizadeh@csail.mit.edu>
Subject: Re: [Ecn-sane] [Bloat] abc congestion control on time varying wireless links
Date: Wed, 18 Dec 2019 11:43:58 -0800	[thread overview]
Message-ID: <87v9qd2zcx.fsf@taht.net> (raw)
In-Reply-To: <1576099811.72231884@apps.rackspace.com> (David P. Reed's message of "Wed, 11 Dec 2019 16:30:11 -0500 (EST)")

"David P. Reed" <dpreed@deepplum.com> writes:

> I should explain that my motivation in writing the previous review is twofold:
>
> 1) I think the authors are very capable of doing great and valuable work. And they have in the past done so.
>
> 2) Intellectual honesty, professional honesty, and rigor are values
> that seem to have been declining over the years, in favor of a
> pragmatic sense that anything that can get published is important. (I
> think it has been reinforced by the idea that counting publications in
> good journals is the only metric of scientific contribution that
> counts, even at MIT). To me, this is a VERY important value. I learned
> that from my mentors, Jerry Saltzer and F.J. Corbato, who were
> relentless in making sure publications were worthy.


I think the core-est problem is the major universities cannot get source
licenses to the 5g and wifi stuff at the lowest level. Nor can they get
sufficient hardware IP to make a meaningful contribution anymore.

As a result, the next generation of engineers and scientists have to
make do with interpreting elephant entrails, and building cargo cult
papers for submission to cargo cult journals with cargo cult reviewers
who've not seen real research in the professional lifetime.

I can't help but note that several of the core-est papers in the
bufferbloat effort, couldn't be published - and reviewers still
currently poo-poo packet scheduling ideas (like pacing, fq-ing) in favor
of aqm idea of the month.

I was kind of hopeful, in that Huewei as one of their remediation ideas
for making their 5G stuff more trustable was a promise to make code
available to all. THAT would be breath of fresh air and level the
playing field once again so valid research could resume.

And for all I know, they are doing that... for chinese universities.

About the only thing going on in the computing world that's encouraging
is the rapidly accellerating work on the risc-v.

>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat

      reply	other threads:[~2019-12-18 19:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 19:17 [Ecn-sane] " Dave Taht
2019-12-11 19:19 ` Prateesh Goyal
2019-12-11 19:54   ` Dave Taht
2019-12-11 20:10     ` Dave Taht
2019-12-11 20:12     ` [Ecn-sane] [Bloat] " Jonathan Morton
2019-12-12 21:31       ` Dave Taht
2019-12-11 21:18     ` [Ecn-sane] " David P. Reed
2019-12-11 21:30       ` David P. Reed
2019-12-18 19:43         ` Dave Taht [this message]

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/ecn-sane.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v9qd2zcx.fsf@taht.net \
    --to=dave@taht.net \
    --cc=alizadeh@csail.mit.edu \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dpreed@deepplum.com \
    --cc=ecn-sane@lists.bufferbloat.net \
    --cc=g.pratish@gmail.com \
    --cc=hari@csail.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