Re: I-D Action: draft-ietf-mboned-ieee802-mcast-problems-03.txt

Toerless Eckert <[email protected]> Wed, 24 Oct 2018 11:40:04 +0200
Newsgroups gmane.ietf.mboned
Message-ID <20181024094004.xisqqt5p6wsk5i4c@faui48f.informatik.uni-erlangen.de>
As i said on that heated debate, in the absence of anyone having analyzed the
problem in more detail, one may want to start looking at the
battery cost assessment for multicast/broadcast from RFC7772
and then check from spec or implementation knowledge how much
broadcast/multicast RFC3927 generates and extrapolate.

In any case, not seeing either of the two RFCs mentioned in
mcast-problems-03 looks like gaps to be closed. 

The recommendations section of the draft should certainly mention
RFC7772, and i think also that using just a single IP version
instead of dual-stack should be a good option to reduce multicast
(see above for quantification), and that there is little to be
won running RFC3927 when you already have IPv6 routed connectivity.
Just a local heuristic of not running RFC3927 ower infra-wifi if
there i IPv6 sounds like a useful local optimization.

But don't believe just me. I am a card-carrying member of the rfc3927 hater club.
Which is not the fault of rfc3927, but of IPv4 or at least all the
OS i know that can't have both IPv4 link-local and routed on the
same interface.

Toerless


On Wed, Oct 24, 2018 at 08:29:12AM +0200, Mikael Abrahamsson wrote:
> 
> There is a very heated debate in 6man regarding
> https://tools.ietf.org/html/draft-ietf-6man-ipv6only-flag-03
> 
> One of the use-cases is that turning off the IPv4 stack in a device will
> stop it from emitting IPv4 service discovery traffic, DHCPv4 server
> solicitation etc, which are typically broadcast or multicast.
> 
> Can someone who knows a lot more about wifi please comment on whether this
> is a real problem on wifi deployments and actually affects battery powered
> devices, or if this is just a suboptimization? Would large wifi deployments
> benefit from hosts turning off their IPv4 stacks if the wifi is IPv6 only,
> instead of the hosts running their IPv4 stacks in IPv4 link-local mode and
> still emitting service discovery packets and trying to configure their IPv4
> stack with DHCP (which is typically default)?
> 
> -- 
> Mikael Abrahamsson    email: [email protected]
> 
> _______________________________________________
> MBONED mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/mboned

-- 
---
[email protected]

_______________________________________________
MBONED mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/mboned