From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: dpreed@reed.com
Cc: "Aaron Wood" <woody77@gmail.com>,
make-wifi-fast@lists.bufferbloat.net,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
"babel-users@lists.alioth.debian.org"
<babel-users@lists.alioth.debian.org>
Subject: Re: [Make-wifi-fast] [Babel-users] perverse powersave bug with sta/ap mode
Date: Thu, 28 Apr 2016 15:37:43 +0200 [thread overview]
Message-ID: <87oa8tyhug.wl-jch@pps.univ-paris-diderot.fr> (raw)
In-Reply-To: <1461849006.60252745@apps.rackspace.com>
> Multicast is seductive to designers who ignore the realities of
> propagation and channel coding issues, because they think it works one
> way, but the reality is quite different.
Hold on.
Mulsticast is used for two distinct purposes: for broadcast-style
applications (streaming), and for discovery (ARP, ND, mDNS, and of course
the Hello beaconing of routing protocols).
For broadcast-style applications, multicast can be replaced with multiple
unicast streams, as Netflix shows, although this is best done at the
routers rather than at the senders, since this allows building a single
distribution tree without the need for application-layer proxies ("CDNs").
For discovery, multicast is unavoidable -- there's simply no way you're
going to send a unicast to a node that you haven't discovered yet.
-- Juliusz
next prev parent reply other threads:[~2016-04-28 13:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 23:18 [Make-wifi-fast] " Dave Taht
2016-04-26 23:27 ` Aaron Wood
2016-04-26 23:32 ` David Lang
2016-04-28 13:10 ` dpreed
2016-04-28 13:37 ` Juliusz Chroboczek [this message]
2016-04-28 13:43 ` [Make-wifi-fast] [Babel-users] " Toke Høiland-Jørgensen
2016-04-28 14:16 ` dpreed
2016-04-28 14:59 ` Juliusz Chroboczek
2016-04-28 15:44 ` Dave Taht
2016-04-28 16:09 ` Dave Taht
2016-04-28 17:10 ` [Make-wifi-fast] Multicast IHUs [was: perverse powersave bug with sta/ap mode] Juliusz Chroboczek
2016-04-28 17:46 ` Dave Taht
2016-04-28 17:53 ` [Make-wifi-fast] [Babel-users] " Henning Rogge
2016-04-28 18:46 ` [Make-wifi-fast] Multicast IHUs Juliusz Chroboczek
2016-04-28 18:04 ` [Make-wifi-fast] Multicast IHUs [was: perverse powersave bug with sta/ap mode] Dave Taht
2016-04-28 17:28 ` [Make-wifi-fast] Layering " Juliusz Chroboczek
2016-04-28 15:04 ` [Make-wifi-fast] [Cerowrt-devel] [Babel-users] perverse powersave bug with sta/ap mode moeller0
2016-04-28 16:05 ` [Make-wifi-fast] [Babel-users] [Cerowrt-devel] " Henning Rogge
2016-04-28 16:52 ` Dave Taht
2016-04-28 16:59 ` Henning Rogge
2016-04-28 18:54 ` [Make-wifi-fast] [Cerowrt-devel] [Babel-users] " Juliusz Chroboczek
2016-04-28 19:12 ` [Make-wifi-fast] [Babel-users] [Cerowrt-devel] " Henning Rogge
2016-04-28 19:29 ` Juliusz Chroboczek
2016-04-28 19:33 ` Henning Rogge
2016-04-28 19:55 ` Juliusz Chroboczek
2016-04-28 13:33 ` [Make-wifi-fast] [Babel-users] " Juliusz Chroboczek
2016-04-28 13:32 ` Juliusz Chroboczek
2016-05-12 0:28 ` [Make-wifi-fast] " Dave Taht
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oa8tyhug.wl-jch@pps.univ-paris-diderot.fr \
--to=jch@pps.univ-paris-diderot.fr \
--cc=babel-users@lists.alioth.debian.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dpreed@reed.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=woody77@gmail.com \
/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