Re: [v6ops] Interesting problems with using IPv6

Fernando Gont <fgont@si6networks.com> Wed, 10 September 2014 21:34 UTC

Return-Path: <fgont@si6networks.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 920521A0194 for <v6ops@ietfa.amsl.com>; Wed, 10 Sep 2014 14:34:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-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 jXAnSHyfF3jk for <v6ops@ietfa.amsl.com>; Wed, 10 Sep 2014 14:34:47 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C57C1A0184 for <v6ops@ietf.org>; Wed, 10 Sep 2014 14:34:47 -0700 (PDT)
Received: from [2001:5c0:1400:a::14b] by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fgont@si6networks.com>) id 1XRpXF-0005td-BF; Wed, 10 Sep 2014 23:34:41 +0200
Message-ID: <5410C3D7.9020401@si6networks.com>
Date: Wed, 10 Sep 2014 18:34:15 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>, v6ops@ietf.org
References: <1410082125488.85722@surrey.ac.uk> <540CB702.3000605@gmail.com> <20140908183339.GB98785@ricotta.doit.wisc.edu> <540E26D9.3070907@gmail.com> <540E7DC3.8060408@gont.com.ar> <540EAA55.7000207@gmail.com> <540F0BCF.1060905@gont.com.ar> <540F3432.5030702@innovationslab.net> <540F9DF1.50402@si6networks.com> <541041C5.4030109@innovationslab.net>
In-Reply-To: <541041C5.4030109@innovationslab.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/wwekI1DRi72UyPOPSIvc6pFGmpc
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: Wed, 10 Sep 2014 21:34:50 -0000

Hi, Brian,

On 09/10/2014 09:19 AM, Brian Haberman wrote:
>>>> Not to mention that there are nodes that default t running MLDv2 *for
>>>> this* (way overkill, IMO)
>>>
>>> Why is MLDv2 overkill?
>>
>> If you're just going to use MLD for ND, MLDv2 is unnecessarily complex
>> -- whole different game if you're using non-link-local multicast, of course.
> 
> I disagree.  When sending MLD Reports for NDP, you don't need to involve
> the complexity of MLDv2 source filters.  You simply send a group-only
> Report message.

That would still means that you'd have to implement it. For small
devices, that might be an issue. And, given how many implementations got
ND (which is rather way simpler) wrong one way or another, I wouldn't be
surprised to see some interesting behaviors if one were to play with
(crafted) MLDv3 packets.

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492