From: Mikael Abrahamsson <swmike@swm.pp.se>
To: David Lang <david@lang.hm>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [Bulk] Re: Motivating commercial entities? tell the sales manager (fwd)
Date: Tue, 10 Mar 2015 08:03:47 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.02.1503100756570.20507@uplift.swm.pp.se> (raw)
In-Reply-To: <alpine.DEB.2.02.1503090837590.26262@nftneq.ynat.uz>
On Mon, 9 Mar 2015, David Lang wrote:
> On Mon, 9 Mar 2015, Mikael Abrahamsson wrote:
>
>> They need to make sure multicast works much better than it does today. IPv6
>> relies on it.
>
> why does IPv6 rely on multicast?
Because that's how it was designed back in the 90ties, as an evolution to
how IPv4 was designed in the 70-ties and 80-ties. On a wired LAN, this is
extremely efficient.
> 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.
That depends on how you do the multicast. Some enterprise solutions will
treat multicast as unicast and send the multicast packets as wifi-unicast
to each station subscribed to that group. That's one way of working around
the problem.
> If this is a fundamental requirement of IPv6, I see it more likely that
> it will mean the avoidance of IPv6 on wireless networks rather than an
> avoidance of wireless networks in order to use IPv6
IPv4 relies on broadcast and that has the same problem. However, IPv6 has
more multicast than IPv4 has broadcast which makes the problem worse.
IEEE/wifi alliance are trying to replace wired networks, that means they
need to make sure things work as well in Wifi as it does in wired
networks. They're not doing a great job with this.
https://tools.ietf.org/html/draft-vyncke-6man-mcast-not-efficient-01
https://tools.ietf.org/html/draft-desmouceaux-ipv6-mcast-wifi-power-usage-00
https://tools.ietf.org/html/draft-yourtchenko-colitti-nd-reduce-multicast-00
People are working in the IETF to try to see what can be done. What does
IEEE do?
--
Mikael Abrahamsson email: swmike@swm.pp.se
prev parent reply other threads:[~2015-03-10 7:03 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
2015-03-10 7:03 ` Mikael Abrahamsson [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/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.1503100756570.20507@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=bloat@lists.bufferbloat.net \
--cc=david@lang.hm \
/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