Re: [v6ops] Interesting problems with using IPv6

Erik Nordmark <> Mon, 15 September 2014 22:09 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id D5BC91A87F0 for <>; Mon, 15 Sep 2014 15:09:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Ia6HuFqHMw22 for <>; Mon, 15 Sep 2014 15:08:59 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2153A1A87C4 for <>; Mon, 15 Sep 2014 15:08:59 -0700 (PDT)
Received: from [] ([]) (authenticated bits=0) by (8.14.9/8.14.9) with ESMTP id s8FM8sOC001507 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 15 Sep 2014 15:08:55 -0700
Message-ID: <>
Date: Mon, 15 Sep 2014 15:08:53 -0700
From: Erik Nordmark <>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Brian E Carpenter <>, Mikael Abrahamsson <>
References: <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVY3x7atgBirB3kAwa5Zf2HNAzJQ92EiSZ1u3w1rs50fiudkPd3TiEmsG5uCLLfYRbWpVpTeRnEXQHJILylCRzl4
X-Sonic-ID: C;Giep4SQ95BGJ4jZXoK8kYw== M;KB9r4iQ95BGJ4jZXoK8kYw==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Cc: IPv6 Operations <>
Subject: Re: [v6ops] Interesting problems with using IPv6
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 15 Sep 2014 22:09:01 -0000

On 9/15/14, 1:20 PM, Brian E Carpenter wrote:
> On 15/09/2014 17:04, Mikael Abrahamsson wrote:
>> On Mon, 15 Sep 2014, Brian E Carpenter wrote:
>>> was MLD snooping (i.e. a layer violation by L2 switches). Even so,
>> This is the first time I have seen anyone calling MLD/IGMP snooping a
>> "layer violation by L2 switches" (I'm interpreting this as you thinking
>> it's negative, do tell if this is not the case).
> Yes, layer violations have this nasty habit of coming back and
> biting you, and this is an example.


I don't think we have sufficient data on the contributions of the 
different factors that resulted in triggering the implementation 
problems in this case.

The overloading of IGMP for to both feed L3 multicast routing 
information into routers and to feed L2 multicast information into IGMP 
snooping switches (which was faithfully carries forward into MLD) 
certainly is part of the picture. That results in the routers seeing MLD 
reports for link-local groups, which the routers do not care about.

But even if we had a non-overloaded approach (with L2 multicast 
membership being propagated by IEEE *Multiple Registration Protocol* 
(*MRP*) instead of IGMP/MLD snooping), the L2 switches would still be 
overloaded with so many temporary addresses and associated 
solicited-node multicast addresses.

Of course, I've never seen a host which implements MRP, but that is 
separate from the implied architectural question about which part of the 
blame should be placed on overloading (or layer violations if you prefer 
that term) in this case.


>> How else is L2 equipment going to make intelligent decisions about
>> multicast forwarding within an L2?
> They're not. That's why DEC Gigaswitches had ARP throttling, for example,
> to control broadcast storms. It's unavoidable if you build big L2
> networks. I learnt not to do that.
>      Brian
> _______________________________________________
> v6ops mailing list