From: David Lang <david@lang.hm>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [Bulk] Re: Motivating commercial entities? tell the sales manager (fwd)
Date: Mon, 9 Mar 2015 09:04:10 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1503090857350.24246@nftneq.ynat.uz> (raw)
In-Reply-To: <20150309154330.GA4134@sesse.net>
On Mon, 9 Mar 2015, Steinar H. Gunderson wrote:
> On Mon, Mar 09, 2015 at 08:40:52AM -0700, David Lang wrote:
>> why does IPv6 rely on multicast?
>>
>> multicast is never going to work that well on a busy wireless
>> network, especially one that's encrypted with a different key to
>> each station.
>
> It relies on multicast the same way IPv4 relies on broadcast
> (ARP, DHCP). If you like broadcast better than multicast, you're
> free to simply treat it as such.
DHCP only needs to get to the dhcp server(s), not to all nodes. It's unusual for
the DHCP server to be wireless rather than wired
For ARP, it only needs to get to other wireless nodes if you are doing wireless
<-> wireless communication, which is relatively rare. And even there, the access
point can 'cheat' if it has an ARP entry for the IP and reply directly rather
than contacting every wireless node.
Explicit multicast, where the devices that want to listen to the multicast have
to tell the access point that they want to listen to a particular multicast
aren't too bad. It's the same overhead as unicast to each node. But this doesn't
scale to lots of wireless nodes using multicast.
It's fairly common for wireless networks to not allow wireless <-> wireless
communication, which cuts this off entirely.
David Lang
next prev parent reply other threads:[~2015-03-09 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 20:46 Koen Holtman
2015-03-09 8:29 ` Mikael Abrahamsson
2015-03-09 15:40 ` David Lang
2015-03-09 15:43 ` Steinar H. Gunderson
2015-03-09 16:04 ` David Lang [this message]
2015-03-10 7:03 ` Mikael Abrahamsson
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=alpine.DEB.2.02.1503090857350.24246@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.net \
--cc=sgunderson@bigfoot.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