IETF Logo Mail Archive

RE: MLD snooping of solicted-node multicast (Was: Re: New Version Notification for draft-halpern-6man-nd-pre-resolve-addr-00.txt

Dmitry Anipko <Dmitry.Anipko@microsoft.com> Fri, 17 January 2014 19:41 UTC

Return-Path: <Dmitry.Anipko@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F4451AE168 for <ipv6@ietfa.amsl.com>; Fri, 17 Jan 2014 11:41:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 oMfpZKgxZzXX for <ipv6@ietfa.amsl.com>; Fri, 17 Jan 2014 11:41:11 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0243.outbound.protection.outlook.com [207.46.163.243]) by ietfa.amsl.com (Postfix) with ESMTP id 930741AE0F3 for <ipv6@ietf.org>; Fri, 17 Jan 2014 11:41:11 -0800 (PST)
Received: from SN2PR03MB077.namprd03.prod.outlook.com (10.255.175.153) by SN2PR03MB080.namprd03.prod.outlook.com (10.255.175.156) with Microsoft SMTP Server (TLS) id 15.0.847.13; Fri, 17 Jan 2014 19:40:57 +0000
Received: from SN2PR03MB077.namprd03.prod.outlook.com ([169.254.14.253]) by SN2PR03MB077.namprd03.prod.outlook.com ([169.254.14.253]) with mapi id 15.00.0847.008; Fri, 17 Jan 2014 19:40:57 +0000
From: Dmitry Anipko <Dmitry.Anipko@microsoft.com>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: RE: MLD snooping of solicted-node multicast (Was: Re: New Version Notification for draft-halpern-6man-nd-pre-resolve-addr-00.txt
Thread-Topic: MLD snooping of solicted-node multicast (Was: Re: New Version Notification for draft-halpern-6man-nd-pre-resolve-addr-00.txt
Thread-Index: AQHPDmY2hGYF66RRbk+N6Vv6p523J5qDMmwwgAATMeCABOYbYIAAiLsAgAABWYCAAJJtcIAACBgAgAACmS6AAAcxAIAAAL0g
Date: Fri, 17 Jan 2014 19:40:56 +0000
Message-ID: <35d4e6f484974024bfe4e00b4e51ca8f@SN2PR03MB077.namprd03.prod.outlook.com>
References: <20140111004402.10451.90724.idtracker@ietfa.amsl.com> <BF6E0BD839774345977891C597F8B50C5CE74C@eusaamb109.ericsson.se> <72381AF1F18BAE4F890A0813768D992817FCA84E@sdcexchms.au.logicalis.com> <892FB91E-311D-4A50-A38B-4972F70847AB@employees.org> <CAKD1Yr2CLUmTYTNAj2_bkP=f3xeBCZ2g=9Sr0D-GvtRgxmfC3g@mail.gmail.com> <2c30d818adc447b2a0ca3a7f0556ee65@SN2PR03MB077.namprd03.prod.outlook.com> <CAKD1Yr1kZ74DWnzFMxfm=NGxxGG8uKVTD3oA4xSay5LPpCdf6w@mail.gmail.com> <5e8d384f3009492fbe3992d82176aa26@SN2PR03MB077.namprd03.prod.outlook.com> <CAKD1Yr0cV1R9WzR0rHgC9A80vaQ+GDdtZ0aKOQdxfrhALULd4Q@mail.gmail.com>
In-Reply-To: <CAKD1Yr0cV1R9WzR0rHgC9A80vaQ+GDdtZ0aKOQdxfrhALULd4Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2001:4898:80e0:ee43::2]
x-forefront-prvs: 0094E3478A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(689001)(679001)(779001)(199002)(377454003)(189002)(51694002)(24454002)(2656002)(16236675002)(50986001)(47976001)(87266001)(56776001)(77982001)(81542001)(54316002)(85306002)(19580395003)(83322001)(49866001)(19580405001)(87936001)(47736001)(4396001)(19609705001)(31966008)(54356001)(19300405004)(80976001)(53806001)(79102001)(74706001)(76576001)(77096001)(74316001)(81686001)(65816001)(81816001)(81342001)(46102001)(59766001)(47446002)(74502001)(51856001)(74662001)(56816005)(33646001)(74366001)(15975445006)(92566001)(85852003)(90146001)(80022001)(76482001)(69226001)(74876001)(15202345003)(63696002)(93136001)(76786001)(76796001)(93516002)(83072002)(3826001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:SN2PR03MB080; H:SN2PR03MB077.namprd03.prod.outlook.com; CLIP:2001:4898:80e0:ee43::2; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en;
Content-Type: multipart/alternative; boundary="_000_35d4e6f484974024bfe4e00b4e51ca8fSN2PR03MB077namprd03pro_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
Cc: 6man WG <ipv6@ietf.org>, Ing-Wher Chen <ing-wher.chen@ericsson.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2014 19:41:14 -0000

>> We should clarify that such behaviour is broken and that saying, "it works in IPv4, so we should just use DHCPv6 for address assignment so that we can force the host to have only one address" is not a solution.

Agree with you.

From: Lorenzo Colitti [mailto:lorenzo@google.com]
Sent: Friday, January 17, 2014 11:37 AM
To: Dmitry Anipko
Cc: Ole Troan; Ing-Wher Chen; 6man WG
Subject: Re: MLD snooping of solicted-node multicast (Was: Re: New Version Notification for draft-halpern-6man-nd-pre-resolve-addr-00.txt

On Fri, Jan 17, 2014 at 11:14 AM, Dmitry Anipko <Dmitry.Anipko@microsoft.com<mailto:Dmitry.Anipko@microsoft.com>> wrote:

>>A more precise statement would be that the number of solicited-node groups scales linearly with the number of IPv6 addresses assigned to hosts,

Agreed. And generally, number of addresses can be more than 2-3 (because of multiple prefixes, and because of multiple suffixes due to privacy extensions).
Indeed. But in the common case of a wifi network where devices come and go frequently, you'll typically have only a link-local, a global, and one temporary address. If you use EUI-64 the link-local and the global will be on the same group.


We have recently seen issues in some APs, where they were not able to handle multiple addresses per host, because of some state maintained per host (that's not a justification that host should not have multiple addresses, but I just wanted to note that today there are issues in some cases related to that).
We should clarify that such behaviour is broken and that saying, "it works in IPv4, so we should just use DHCPv6 for address assignment so that we can force the host to have only one address" is not a solution.

v2.20.3 | Report a Bug | By Email