IETF Logo Mail Archive

Re: [v6ops] DAD again [was: draft-ietf-v6ops-host-addr-availability discussion]

Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 13 November 2015 12:56 UTC

Return-Path: <alexandre.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 19EE41A6F0A for <v6ops@ietfa.amsl.com>; Fri, 13 Nov 2015 04:56:45 -0800 (PST)
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 f2PMfqpBA-YL for <v6ops@ietfa.amsl.com>; Fri, 13 Nov 2015 04:56:43 -0800 (PST)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DD0B1A6F07 for <v6ops@ietf.org>; Fri, 13 Nov 2015 04:56:43 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id tADCufgC022199 for <v6ops@ietf.org>; Fri, 13 Nov 2015 13:56:41 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id DEF8320501F for <v6ops@ietf.org>; Fri, 13 Nov 2015 14:02:52 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id DA35B204FFA for <v6ops@ietf.org>; Fri, 13 Nov 2015 14:02:52 +0100 (CET)
Received: from [127.0.0.1] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id tADCudOC024198 for <v6ops@ietf.org>; Fri, 13 Nov 2015 13:56:40 +0100
To: v6ops@ietf.org
References: <8D175A1F-B1AE-44B4-838E-1C853B6C937D@cisco.com> <CAKD1Yr15C-uoxUw0kgWO-d=LmUK8qWGLS7vt+22W+k8xXtDY+g@mail.gmail.com> <2134F8430051B64F815C691A62D9831832F393F1@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831832F3941D@XCH-BLV-504.nw.nos.boeing.com> <563811DF.9020603@gmail.com> <2134F8430051B64F815C691A62D9831832F394F7@XCH-BLV-504.nw.nos.boeing.com> <563821EB.3040508@gmail.com> <2134F8430051B64F815C691A62D9831832F39A09@XCH-BLV-504.nw.nos.boeing.com> <56392B6D.8030703@gmail.com> <2134F8430051B64F815C691A62D9831832F3A88F@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831832F3A97F@XCH-BLV-504.nw.nos.boeing.com> <CAHDzDLBG8xZxUFsAuN-7WuruZcULF1QAS_ch=gD5rGQMZfskow@mail.gmail.com> <2134F8430051B64F815C691A62D9831832F3E8B0@XCH-BLV-504.nw.nos.boeing.com> <CAJE_bqd-1x5EJ=rkebiBFdNds6so5+iNGftiUf+MUu9P1up1bA@mail.gmail.com> <CAKD1Yr1X8UzQ58FeG6PYG9L1MyibV0J-JpcS2hxwzCdV=HizXg@mail.gmail.com> <ad0e90cf5f74407fa5338a7b6130bd1a@XCH-RTP-005.cisco.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <5645DE07.3050605@gmail.com>
Date: Fri, 13 Nov 2015 13:56:39 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <ad0e90cf5f74407fa5338a7b6130bd1a@XCH-RTP-005.cisco.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/ZlpZj2L2TYpWHDk9xNM7swImmKc>
Subject: Re: [v6ops] DAD again [was: draft-ietf-v6ops-host-addr-availability discussion]
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: Fri, 13 Nov 2015 12:56:45 -0000


Le 13/11/2015 13:31, Hemant Singh (shemant) a écrit :
>
>
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Lorenzo
> Colitti Sent: Thursday, November 12, 2015 10:07 PM To: 神明達哉 Cc:
> v6ops@ietf.org Subject: Re: [v6ops] DAD again [was:
> draft-ietf-v6ops-host-addr-availability discussion]
>
>
>> At most we could slightly amend this to ..."MUST be performed on
>> all unicast addresses prior to assigning them to an interface
>> except a loopback interface". Even node-internal interfaces are not
>> >necessarily safe to omit DAD on. For example, in a mobile device
>> the application processor and baseband processor might both be on
>> the same link, and because they are two separate processors
>> >running two separate network stacks, they need to do DAD.
>
> Appendix A of RFC4862 already cautions against a loopback interface
> looping back DAD probes.  Did you have any other reason to disable
> DAD for a loopback interface?  For example, on a router, a loopback
> interface is configured and the IPv6 address on the interface is used
> to source packets.  Why would one not perform DAD for the IPv6
> address used by the loopback interface?

One wouldnt care about DAD on loopback interface, because it's not noise 
on a wire, and it's not time consuming.

Alex

>
> Thanks,
>
> Hemant _______________________________________________ v6ops mailing
> list v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>

v2.23.0 | Report a Bug | By Email