Re: [v6ops] ref Hosts dont MLD to join LL groups

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 23 July 2015 11:43 UTC

Return-Path: <alexandru.petrescu@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 BF7FC1AC438 for <v6ops@ietfa.amsl.com>; Thu, 23 Jul 2015 04:43:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level:
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 C5gEDHmGYXJR for <v6ops@ietfa.amsl.com>; Thu, 23 Jul 2015 04:43:34 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F23EA1AC43B for <v6ops@ietf.org>; Thu, 23 Jul 2015 04:43:24 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t6NBhKxf022422; Thu, 23 Jul 2015 13:43:20 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 480D82048EF; Thu, 23 Jul 2015 13:46:57 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 3E7B020279C; Thu, 23 Jul 2015 13:46:57 +0200 (CEST)
Received: from [127.0.0.1] ([132.166.84.9]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t6NBhJYq004685; Thu, 23 Jul 2015 13:43:20 +0200
To: Ole Troan <otroan@employees.org>
References: <55AE42A4.8020908@gmail.com> <5CD05758-D7B7-476D-9936-E5A1D0614AF8@employees.org>
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Message-ID: <55B0D356.7070505@gmail.com>
Date: Thu, 23 Jul 2015 13:43:18 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <5CD05758-D7B7-476D-9936-E5A1D0614AF8@employees.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/oFexCOx6dvrmmMMuOxMhUI0ikUI>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] ref Hosts dont MLD to join LL groups
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 23 Jul 2015 11:43:36 -0000


Le 22/07/2015 14:27, Ole Troan a écrit :
>> Regarding the mic discussion about unicast RAs a SHOULD.
>>
>> I have been directed that the reference saying that Hosts dont MLD
>> to join multicast groups is RFC3810:
>>
>> "  The link-scope all-nodes multicast address, (FF02::1), is
>> handled as a special case.  On all nodes -- that is all hosts and
>> routers, including multicast routers -- listening to packets
>> destined to the all-nodes multicast address, from all sources, is
>> permanently enabled on all interfaces on which multicast listening
>> is supported.  No MLD messages are ever sent regarding neither the
>> link-scope all-nodes multicast address, nor any multicast address
>> of scope 0 (reserved) or 1 (node-local).”
>
> I do wonder if we should expand that exception to all link-scope
> multicast addresses.
>

I would beg to disagree.

If we expand that to all link-scoped groups, may lead to dismantling 
IPv6 dependence on 33::1 - ff:ff:ff:ff:ff would be sufficient.

My oppinion would rather be to modify the MLD RFC to mandate MLD joins 
for all scopes.

Ethernet has primitives for joining the corresponding link-layer groups, 
and in some cases they are used. Maybe all should use them.

> the bridge implementors I speak to tell me that they don’t have
> enough state to do MLD snooping for link-local scoped multicast
> addresses anyway...

This may be dumb from my side, but why dont bridge implementers use 
link-layer multicast?  They shouldnt implement MLD, and not snoop it. 
The Hosts should send the necessary link-layer multicast joins 
(triggered by themselves sending MLD REPORT for these groups) to the 
bridge addresses.

Alex

> cheers, Ole
>