IETF Logo Mail Archive

Re: [v6ops] Interesting problems with using IPv6

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 15 September 2014 20:20 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4001A1A7031 for <v6ops@ietfa.amsl.com>; Mon, 15 Sep 2014 13:20:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6K86BXkGGFzu for <v6ops@ietfa.amsl.com>; Mon, 15 Sep 2014 13:20:56 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C942A1A6FE0 for <v6ops@ietf.org>; Mon, 15 Sep 2014 13:20:56 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id lj1so7265763pab.41 for <v6ops@ietf.org>; Mon, 15 Sep 2014 13:20:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=hZDv1I68gdBNRqrgs3jERrgQNk968FZwhND81O3CU4I=; b=B8K+5AQVZX2m8Yznt8FyPbBoN3oZhfYkE+nhjASlDZSzwJ254sajngoROPUCU3me+1 ndY2Dp8aH08o+XaAtc9LOwHyT6Tw9KBQimlpxXgl0T43xL66D3CKg9DjLrxv0eQExwnq qffi9m5T9JFmsprTzH5hDRyC4cto16mGRUjo6Sqr+Y3ZEL4zsV9fCGteXzR8gv+iOWOz s7DFNLZSzqcrgz8P97l2p5+muH1yXdynSyAEcjKVoiC7VqH8PNplo6UOPCendeoIANHe BAuCeYoBLlzLr0dN1T5TDh+YiJk5scncAiPK7sEU/HrRh13mGvkRRfw4RLFtGcoc7ia0 a6Dg==
X-Received: by 10.68.209.169 with SMTP id mn9mr42353917pbc.37.1410812456506; Mon, 15 Sep 2014 13:20:56 -0700 (PDT)
Received: from [192.168.178.23] (182.197.69.111.dynamic.snap.net.nz. [111.69.197.182]) by mx.google.com with ESMTPSA id jw6sm12129307pbc.79.2014.09.15.13.20.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 15 Sep 2014 13:20:55 -0700 (PDT)
Message-ID: <54174A26.1050206@gmail.com>
Date: Tue, 16 Sep 2014 08:20:54 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
References: <1410082125488.85722@surrey.ac.uk> <540CB702.3000605@gmail.com> <20140908183339.GB98785@ricotta.doit.wisc.edu> <540E26D9.3070907@gmail.com> <1410227735.13436.YahooMailNeo@web162204.mail.bf1.yahoo.com> <540E6299.2050003@gmail.com> <1410743000.11973.YahooMailNeo@web162204.mail.bf1.yahoo.com> <54166EE5.9080007@gmail.com> <alpine.DEB.2.02.1409150702180.14735@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1409150702180.14735@uplift.swm.pp.se>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/DKERpx6DDJ2jPTzbvTe1KE5m6Xo
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Interesting problems with using IPv6
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Sep 2014 20:20:58 -0000

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.

> 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

v2.23.0 | Report a Bug | By Email