From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [Bulk] Re: Motivating commercial entities? tell the sales manager (fwd)
Date: Mon, 9 Mar 2015 16:43:30 +0100 [thread overview]
Message-ID: <20150309154330.GA4134@sesse.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1503090837590.26262@nftneq.ynat.uz>
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.
/* Steinar */
--
Homepage: http://www.sesse.net/
next prev parent reply other threads:[~2015-03-09 15:43 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 [this message]
2015-03-09 16:04 ` David Lang
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=20150309154330.GA4134@sesse.net \
--to=sgunderson@bigfoot.com \
--cc=bloat@lists.bufferbloat.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