Re: To DAD or not to DAD?
Hesham Soliman <hesham@elevatemobile.com> Fri, 20 February 2015 00:22 UTC
Return-Path: <hesham@elevatemobile.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 061FF1A1A88 for <ipv6@ietfa.amsl.com>; Thu, 19 Feb 2015 16:22:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] 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 kLBJn4j-KUUG for <ipv6@ietfa.amsl.com>; Thu, 19 Feb 2015 16:22:36 -0800 (PST)
Received: from smtp.netregistry.net (smtp.netregistry.net [202.124.241.204]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 265581A1A8F for <6man@ietf.org>; Thu, 19 Feb 2015 16:22:35 -0800 (PST)
Received: from [203.219.211.243] (port=51194 helo=[192.168.0.3]) by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.69 #1 (Debian)) id 1YObMW-0002hd-Pu; Fri, 20 Feb 2015 11:22:33 +1100
User-Agent: Microsoft-MacOutlook/14.4.7.141117
Date: Fri, 20 Feb 2015 11:22:08 +1100
Subject: Re: To DAD or not to DAD?
From: Hesham Soliman <hesham@elevatemobile.com>
To: Erik Nordmark <nordmark@acm.org>, "6man@ietf.org" <6man@ietf.org>
Message-ID: <D10CC6F8.5B508%hesham@elevatemobile.com>
Thread-Topic: To DAD or not to DAD?
References: <54E4EC1A.3080303@acm.org> <D10B6C10.5B347%hesham@elevatemobile.com> <54E61297.5020507@acm.org>
In-Reply-To: <54E61297.5020507@acm.org>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
X-Authenticated-User: hesham@elevatemobile.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/UclpOCJewhb2_6RAjyX3qglbyNE>
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, 20 Feb 2015 00:22:39 -0000
> >Hesham, > >Might make sense to read draft-yourtchenko-6man-dad-issues. Of the 11+ >issues/sections I think there are only two that are about efficiency. => That’s right, I did read it before opening my mouth :). I only commented on efficiencies because it stuck in my head after looking at your slides. I think I made more comments on other issues in another email to Ole. I see those issues falling into 4 categories: 1. Increasing the scope of DAD’s support (e.g. supporting partitions/joins, multi-link subnets ..etc), which were known “out of scope” features before. 2. Problems which are not true because we have documented solutions for them (e.g. delays before using an address) 3. Strange link layer behaviour. There is only one issue that struck me there related to link layers that appear to be up but are not really up because they’re running STP (issue 3), which strikes me as a misleading “link up” indication, which can cause more problems than just DAD. 4. Implementation bugs (issue 5 only) I guess as always YMMV on whether a valid problem is worth solving (i.e. category 1 above) and the group decides that based on experiences. I only commented on the ones that I didn’t agree with as problems. DISCLAIMER: Ole sent a few links in addition to the draft, which I haven’t read yet. > >For instance, if we depend on DAD it would make sense for it to have >better tolerance against partions/join on the link. => Right, that falls under category 1. For me that depends on data showing how serious a problem this is. Personally I don’t know. > >One of the potential solutions might to treat large wireless systems >(WiFi ;-) as point-to-point links. >But before getting into solutions I think it would be good for the WG to >look over the set of issues with DAD. => Agreed. We need to be on the same wavelength when it comes to the actual problems. Hesham > > Erik > >> >> So IMHO yes collisions should be rare but I just don’t see DAD as this >> major cost given the tools we have in various scenarios. So go to the >> beach! It’s warm here so the beach is fine in the southern hemisphere :) >> >> Hesham >>> -------------------------------------------------------------------- >>> IETF IPv6 working group mailing list >>> ipv6@ietf.org >>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 >>> -------------------------------------------------------------------- >> >> >
- Re: To DAD or not to DAD? Erik Nordmark
- Re: To DAD or not to DAD? James Woodyatt
- To DAD or not to DAD? Erik Nordmark
- RE: To DAD or not to DAD? Hosnieh Rafiee
- Re: To DAD or not to DAD? Hesham Soliman
- Re: To DAD or not to DAD? Brian E Carpenter
- Re: To DAD or not to DAD? Mark ZZZ Smith
- Re: To DAD or not to DAD? Alejandro Acosta
- Re: To DAD or not to DAD? Ole Troan
- Re: To DAD or not to DAD? Hesham Soliman
- Re: To DAD or not to DAD? Ole Troan
- Re: To DAD or not to DAD? Hesham Soliman
- Re: To DAD or not to DAD? Ole Troan
- RE: To DAD or not to DAD? STARK, BARBARA H
- Re: To DAD or not to DAD? Erik Nordmark
- Re: To DAD or not to DAD? Bob Hinden
- Re: To DAD or not to DAD? Alexandru Petrescu
- Re: To DAD or not to DAD? Erik Nordmark
- Re: To DAD or not to DAD? Brian E Carpenter
- Re: To DAD or not to DAD? Ole Troan
- Re: To DAD or not to DAD? Erik Nordmark
- Re: To DAD or not to DAD? Hesham Soliman
- Re: To DAD or not to DAD? Erik Nordmark
- Re: To DAD or not to DAD? Francis Dupont
- RE: To DAD or not to DAD? Greg Daley
- Re: To DAD or not to DAD? James Woodyatt
- Re: To DAD or not to DAD? Mark ZZZ Smith
- Re: To DAD or not to DAD? t.petch
- Re: To DAD or not to DAD? dictionary of meaningfu… Alexandru Petrescu
- Re: To DAD or not to DAD? Francis Dupont
- Re: To DAD or not to DAD? dictionary of meaningfu… Warren Kumari
- Re: To DAD or not to DAD? Erik Nordmark
- RE: To DAD or not to DAD? Samita Chakrabarti
- Re: To DAD or not to DAD? Hesham Soliman
- RE: To DAD or not to DAD? Hemant Singh (shemant)
- Re: To DAD or not to DAD? James Woodyatt
- Re: To DAD or not to DAD? Fernando Gont
- RE: To DAD or not to DAD? Pascal Thubert (pthubert)
- Re: To DAD or not to DAD? Eric Vyncke (evyncke)
- Re: To DAD or not to DAD? Erik Nordmark
- RE: To DAD or not to DAD? Hemant Singh (shemant)
- Re: To DAD or not to DAD? Hesham Soliman
- RE: To DAD or not to DAD? Hemant Singh (shemant)
- Re: To DAD or not to DAD? Erik Nordmark
- Re: To DAD or not to DAD? Hesham Soliman
- RE: To DAD or not to DAD? Hemant Singh (shemant)
- RE: To DAD or not to DAD? Hemant Singh (shemant)
- Re: To DAD or not to DAD? James Woodyatt
- RE: To DAD or not to DAD? Hemant Singh (shemant)