General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "dpreed@deepplum.com" <dpreed@deepplum.com>
To: "Dave Taht" <dave.taht@gmail.com>
Cc: "Mikael Abrahamsson" <swmike@swm.pp.se>,
	"Cake List" <cake@lists.bufferbloat.net>,
	"bloat" <bloat@lists.bufferbloat.net>,
	"Make-Wifi-fast" <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Bloat] [Make-wifi-fast] Van Jacobson's slides on timing wheels at netdevconf
Date: Mon, 23 Jul 2018 13:26:50 -0400 (EDT)	[thread overview]
Message-ID: <1532366810.49039544@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw4-uXSz1WXFikN1SFwt4fiMM8XZHZY_rMZCbZPAz-kFkg@mail.gmail.com>

Dave Taht wrote:
> I think the ietf should just rename itself to being DCTF (the data
> center task force) and let some other org arise to take care of the
> internet.
 
:-)

Internetworking is not really what DC's are about. But it's an indication of where investors want to spend their money.

The real "internetworking" challenges are happening, as always, where ownership/control domains make central planning, design and control difficult or impossible.

That is, at the "edges" not the "core". DC's are just another kind of "core".

Wireless (especially ad hoc connectivity wireless) and "IoT" (if done with the sensibility of internetworking at its core) are where internetworking matters.

That's why congestion control and performance are such open-ended problems in internetworking - you need a higher level of abstraction above the "hard standards" like Ethernet, etc. because you can't solve those problems "locally" in the hard-standardized-devices. (that's an "end-to-end argument" - you can't fully solve many internetworking problems in a subnetwork or router).

It's why I don't go to IETF. The attendees have their heads screwed on with crossed threads.



  reply	other threads:[~2018-07-23 17:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-20 14:09 [Bloat] " Dave Taht
2018-07-20 14:47 ` [Bloat] [Make-wifi-fast] " Luca Muscariello
2018-07-21 14:38   ` Jonathan Morton
2018-07-23 12:52     ` Mikael Abrahamsson
2018-07-23 15:36       ` Dave Taht
2018-07-23 17:26         ` dpreed [this message]
2018-07-21 13:19 ` [Bloat] " Matthias Tafelmeier

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=1532366810.49039544@apps.rackspace.com \
    --to=dpreed@deepplum.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=swmike@swm.pp.se \
    /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