Re: Next Steps on DAD Improvements
神明達哉 <jinmei@wide.ad.jp> Thu, 11 June 2015 18:41 UTC
Return-Path: <jinmei.tatuya@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 4E6971B2C77 for <ipv6@ietfa.amsl.com>; Thu, 11 Jun 2015 11:41:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level:
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 Mo1oNnVBX104 for <ipv6@ietfa.amsl.com>; Thu, 11 Jun 2015 11:41:34 -0700 (PDT)
Received: from mail-yk0-x22b.google.com (mail-yk0-x22b.google.com [IPv6:2607:f8b0:4002:c07::22b]) (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 020BB1B2C6F for <ipv6@ietf.org>; Thu, 11 Jun 2015 11:41:34 -0700 (PDT)
Received: by yken206 with SMTP id n206so6641571yke.2 for <ipv6@ietf.org>; Thu, 11 Jun 2015 11:41:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=sdnA4bTEYaumy6gAd/2s4tGuQJ3yOhy36nFegwWb26E=; b=l1d7hMGMrvJo1q9G173hJdsSTq4z/vLUl24+p1LPlWXTjj3V8nnJv4Hn+fHErUDCs8 5FLFkIECilCaePYcfxpEaEttQpCVLz2OA6DhWQoQmr0sn8Y4/D1Y1/4oAqGMb8/LPITK 9TRhILm31J56pVJXD3Q7e5cvaYofnDiC1WKPreWw9Z3iAbknbFzVNIbjaAzx7XWxMHqT FfR1HyE2iXR8VbtR5ajzdpNhMdcHE4jWRKp1z440JfrMdHpWxqeSNRE5BPejA+RkQvfs PcCdr0qDFu7WGG2YF4CGAB9myk8Pi8z+3KgjeIQtkQSi9uUBuB158/0JFJV0HqhPR0Tc nZ1A==
MIME-Version: 1.0
X-Received: by 10.170.90.5 with SMTP id h5mr13584754yka.26.1434048093453; Thu, 11 Jun 2015 11:41:33 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.37.48.131 with HTTP; Thu, 11 Jun 2015 11:41:33 -0700 (PDT)
In-Reply-To: <8CD12D24-FFB3-4F92-9E13-B4D9A40F3B3A@gmail.com>
References: <8CD12D24-FFB3-4F92-9E13-B4D9A40F3B3A@gmail.com>
Date: Thu, 11 Jun 2015 11:41:33 -0700
X-Google-Sender-Auth: UfDIuMdnw3fPbyVhS3A0FYxGSQ0
Message-ID: <CAJE_bqcKxR2cw1DH1hvafkszNwrapS9LL9aU4rXYx9nP44uv2g@mail.gmail.com>
Subject: Re: Next Steps on DAD Improvements
From: 神明達哉 <jinmei@wide.ad.jp>
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/IC5LRMZ5BXy8SAmfSE7ZJG3Fgfo>
Cc: IPv6 List <ipv6@ietf.org>
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, 11 Jun 2015 18:41:35 -0000
At Mon, 8 Jun 2015 13:02:06 -0700, Bob Hinden <bob.hinden@gmail.com> wrote: > At the 6man WG meeting in Dallas there was discussion on what to do (if anything) about duplicate address detection. The background on this is documented in https://datatracker.ietf.org/doc/draft-yourtchenko-6man-dad-issues/ > > Should we work on the robustness and efficiency issues of DAD? [...] > The chair would like your feedback on this issue and if there is > interest we will schedule an agenda slot in Prague. I think it makes sense to work on these, as the dad-issues draft sensibly explains that at least some of operational assumptions at the time of original DAD design may not be valid. Of course, we'll still have to assess which part of the issues are sufficiently substantial to be solved, and consider pros and cons of each particular solution to each particular (sub-)issue. I assume "work on" includes these assessment and considerations. -- JINMEI, Tatuya
- Next Steps on DAD Improvements Bob Hinden
- Re: Next Steps on DAD Improvements James Woodyatt
- Re: Next Steps on DAD Improvements Brian E Carpenter
- Re: Next Steps on DAD Improvements Lorenzo Colitti
- Re: Next Steps on DAD Improvements Pascal Thubert (pthubert)
- Re: Next Steps on DAD Improvements Lorenzo Colitti
- Re: Next Steps on DAD Improvements Brian E Carpenter
- RE: Next Steps on DAD Improvements JOSHI, SHRINIVAS ASHOK (SHRINIVAS ASHOK)
- RE: Next Steps on DAD Improvements Greg Daley
- Re: Next Steps on DAD Improvements Lorenzo Colitti
- Re: Next Steps on DAD Improvements Ole Troan
- RE: Next Steps on DAD Improvements Greg Daley
- Re: Next Steps on DAD Improvements Lorenzo Colitti
- Re: Next Steps on DAD Improvements Ole Troan
- Re: Next Steps on DAD Improvements Lorenzo Colitti
- Re: Next Steps on DAD Improvements Ole Troan
- Re: Next Steps on DAD Improvements Lorenzo Colitti
- Re: Next Steps on DAD Improvements Tim Chown
- Re: Next Steps on DAD Improvements Lorenzo Colitti
- Re: Next Steps on DAD Improvements Tim Chown
- RE: Next Steps on DAD Improvements Hemant Singh (shemant)
- Re: Next Steps on DAD Improvements Mark ZZZ Smith
- Re: Next Steps on DAD Improvements 神明達哉
- Re: Next Steps on DAD Improvements Erik Nordmark
- Re: Next Steps on DAD Improvements Erik Nordmark
- RE: Next Steps on DAD Improvements Pascal Thubert (pthubert)
- Re: Next Steps on DAD Improvements Sowmini Varadhan
- RE: Next Steps on DAD Improvements Samita Chakrabarti
- Re: Next Steps on DAD Improvements Bob Hinden