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

Gert Doering <gert@space.net> Sat, 14 November 2015 19:27 UTC

Return-Path: <gert@Space.Net>
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 94A4A1AD365 for <v6ops@ietfa.amsl.com>; Sat, 14 Nov 2015 11:27:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] 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 s15450tnV_P1 for <v6ops@ietfa.amsl.com>; Sat, 14 Nov 2015 11:27:44 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 795EC1AD362 for <v6ops@ietf.org>; Sat, 14 Nov 2015 11:27:44 -0800 (PST)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 155D262EFF for <v6ops@ietf.org>; Sat, 14 Nov 2015 20:27:41 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id BB67260736 for <v6ops@ietf.org>; Sat, 14 Nov 2015 20:27:40 +0100 (CET)
Received: (qmail 65131 invoked by uid 1007); 14 Nov 2015 20:27:40 +0100
Date: Sat, 14 Nov 2015 20:27:40 +0100
From: Gert Doering <gert@space.net>
To: "Hemant Singh \(shemant\)" <shemant@cisco.com>
Message-ID: <20151114192740.GN89490@Space.Net>
References: <38D33D99-5075-4A52-9B57-9FEC9B088EF0@delong.com> <dcc3058655eb45319b5f2431db9667b0@XCH-RTP-005.cisco.com> <8A25D382-C4C6-4FBA-B5FF-D10BD4F398A9@delong.com> <158e13b7080a494cb3503476dc378a1e@XCH-RTP-005.cisco.com> <EFB44958-1C5D-4F08-9859-275489392B3D@delong.com> <a4050b82cc954ac8b25f50dc985451c9@XCH-RTP-005.cisco.com> <20151114181240.GI89490@Space.Net> <04d5779d611a4c5abd7db9093b991f81@XCH-RTP-005.cisco.com> <20151114185052.GM89490@Space.Net> <288282e703ee45d1940da65afb49e2c8@XCH-RTP-005.cisco.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dZflLWwKqQHwno8z"
Content-Disposition: inline
In-Reply-To: <288282e703ee45d1940da65afb49e2c8@XCH-RTP-005.cisco.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/TVxynY8r4Y5EYe0EqHaPoB4hR74>
Cc: v6ops@ietf.org
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: Sat, 14 Nov 2015 19:27:46 -0000

Hi,

On Sat, Nov 14, 2015 at 07:14:28PM +0000, Hemant Singh (shemant) wrote:
> I will be out for next few hours.  I will reply to any mails after that.   I don't have any issue to disable DAD for  a lo interface.  Jinmei wants due diligence because rfc4862 is being changed and the 6man WG has to take a look.  The draft is not just a v6ops issue any more.   I also have another issue in that if DAD is disabled, what else makes sense to disable on the lo interface so that the interface has even more reduced processing to deal with. 

You do not need to disable DAD on lo.  Do it all you want.

But don't do DAD for interface A address on interface B.  This is the point
everybody has been making.

So, if you have an address on lo, there is no reason to do DAD for that
on eth0, eth1, pos3/4, or anything else in your box - as you wouldn't
do DAD for the eth0 address on eth1.

Unrelated interfaces.

And on lo0, there is no other party to conflict with, so do DAD if you 
want, or do not do DAD.  Nobody cares.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279