On Sep 7, 2014, at 3:50 PM, Brian E Carpenter <brian.e.carpenter@xxxxxxxxx> wrote: > If they really are interesting problems, it might be more to the > point to analyse them over on v6ops. Given the number of large > IPv6 deployments that don't have such problems, it seems like > this particular deployment hit an unfortunate combination of > implementation issues. That is worth understanding (for example, > how large is the layer 2 network that leads to the MLD listener > report overload?). Apparently the issue is that although they have isolated various L3 networks with quite reasonable client loads, they are using a hybrid L2/L3 virtualized switch environment that winds up not properly containing the MLD multicasts. And they have a lot of buggy machines that keep temporary addresses around longer than they should.