Re: To DAD or not to DAD?

Bob Hinden <bob.hinden@gmail.com> Thu, 19 February 2015 21:03 UTC

Return-Path: <bob.hinden@gmail.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 947C21A01A5 for <ipv6@ietfa.amsl.com>; Thu, 19 Feb 2015 13:03:58 -0800 (PST)
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 DSfU1ydH7NgP for <ipv6@ietfa.amsl.com>; Thu, 19 Feb 2015 13:03:56 -0800 (PST)
Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 784DD1A0120 for <6man@ietf.org>; Thu, 19 Feb 2015 13:03:56 -0800 (PST)
Received: by mail-ig0-f180.google.com with SMTP id b16so12512737igk.1 for <6man@ietf.org>; Thu, 19 Feb 2015 13:03:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=2MXbMfz3tkIqTFAWmL4w1RqKXEZNQ4g5s/MSgYNCamo=; b=Fd5ylO8fdphlEO23CheOmxduLSfTHYwoMtpKt1GwAflZRVsh2ZF0F4R76mgMmREBTA OLBp+r/L9/hrlF9qcwQoDbUBaR+UiLZIh+meKpWC9euP8p/mlW4S27Z/v8ImhIMX6Ve9 hfkARIiiYTtWtX2Hz+NUI/FJQw6viun4qWjC7/VexAkwyAAYGYtSGbaxqkkK71Io38y6 eESW8jtFQKuw9suA28vG1gRJauJGXtB+JCORqYHG0p1Pdo25b2ATJDfu0KYbAXWiHP0I bi5jinrdqEG+PrP4ZLX6all6ah3TVb6kQkqb0Y+0JWI+5Y8uxHbXCMYOksmSlvUUlTFl TfvA==
X-Received: by 10.43.34.137 with SMTP id ss9mr8557089icb.11.1424379835760; Thu, 19 Feb 2015 13:03:55 -0800 (PST)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPSA id m7sm6700986iom.12.2015.02.19.13.03.53 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Feb 2015 13:03:54 -0800 (PST)
Subject: Re: To DAD or not to DAD?
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_E62669CB-5FEE-48C0-91D1-C1D1D9365E87"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail 2.5b5
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <54E4EC1A.3080303@acm.org>
Date: Thu, 19 Feb 2015 13:03:43 -0800
Message-Id: <DE018987-A4A3-47DF-B2CD-DA021622F341@gmail.com>
References: <54E4EC1A.3080303@acm.org>
To: Erik Nordmark <nordmark@acm.org>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/fc7Q4zzau7uJdUc9CHRUMW80nkM>
Cc: "6man@ietf.org" <6man@ietf.org>, Bob Hinden <bob.hinden@gmail.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: Thu, 19 Feb 2015 21:03:58 -0000

Erik,

With no hats on.

> On Feb 18, 2015, at 11:46 AM, Erik Nordmark <nordmark@acm.org> wrote:
> 
> 
> Hello,
> 
> Back in November the efficient-nd design team presented slides (http://www.ietf.org/proceedings/91/slides/slides-91-6man-11.pdf)
> and a document was produced on the DAD problems (https://datatracker.ietf.org/doc/draft-yourtchenko-6man-dad-issues/)
> 
> The key questions in the design team report was what to do about DAD. But we haven't had any discussion on this on the list and I'd like to get some feedback from the WG to we can move forward.
> 
> The slides offered these options:
> 1. Deprecate DAD - it is expensive and duplicates are not common

I think we know that duplicates are not common with IEEE EUI based IIDs.  In the case of duplicates at the L2 on a LAN, there is a bigger problem for the network operator to solve.  I don’t think DAD brings very much in this case.

> 2. Only send and receive DAD for manually configured addresses

I note we are in the process of moving away from IEEE EUI based IIDs to software generated pseudorandom numbers.  Lots of good reasons to do that, but I don’t think we know how well this new software will work in regard to duplicates.  It should work fine, but there will be bugs and possibly increased duplicates if different algorithms are chosen.  For this reason, I think that we should continue using DAD for software generated IIDs, at least until we get more operational experience.


> 3. Improve DAD
> 3a. Better at detecting duplicates (partition-join, etc)
> 3b. Less network and host impact (allow sleep schedule)
> 4. Do nothing a. aka go to the beach ;-)
> 
> The 3a vs. 3b implicitly refers to the list of issues in draft-yourtchenko-6man-dad-issues.

> 
> Given that the beach is kind of cold this time of year, we can remove the 4th choice from the list.
> More seriously, the WG needs to decide how to move forward with DAD.

I agree.

> 
> Would it be helpful to present draft-yourtchenko-6man-dad-issues in Dallas? Or can we have an email discussion without/prior to such a presentation?
> 

Yes, for both.

Thanks,
Bob


> Regards,
>    Erik
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------