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

"Hemant Singh (shemant)" <shemant@cisco.com> Sat, 14 November 2015 19:03 UTC

Return-Path: <shemant@cisco.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 E37D11AD059 for <v6ops@ietfa.amsl.com>; Sat, 14 Nov 2015 11:03:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 4HuZVA-2Qvje for <v6ops@ietfa.amsl.com>; Sat, 14 Nov 2015 11:03:01 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B205F1AD04E for <v6ops@ietf.org>; Sat, 14 Nov 2015 11:03:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1521; q=dns/txt; s=iport; t=1447527781; x=1448737381; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=LDU1cM8RCa2VrHKdQrNFY2TpmIBDyJok9ggFhAkewFY=; b=VUNUTWvHmsqUZVxJ/wNEsIuZ3bYJP+E7XUxqUr2T7+b1LstfEgEFOVe4 T2nLhbRT7k2ANE8FQKodEso32w5knXSijyuAohJOap6FaMYipPUN+9/yb iXIE4AEcuCgawBX71iXbQvaZt5HhqBcm/WC8/pVVELAB2A5GoqkYX6kQH 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ACAgBQhEdW/4YNJK1egzuBQga+RwENg?= =?us-ascii?q?WSGEAKBKzgUAQEBAQEBAYEKhDQBAQEDATo/DAQCAQgRBAEBHwkHMhQJCAIEDgU?= =?us-ascii?q?IiB4Itn0BAQEBAQEBAQEBAQEBAQEBAQEBAQEYi1KEKhEBhH0FlkgBjR+BYoRAk?= =?us-ascii?q?jiDcQEfAQFCghEdgVZyhAo6gQcBAQE?=
X-IronPort-AV: E=Sophos;i="5.20,294,1444694400"; d="scan'208";a="50551940"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 14 Nov 2015 19:03:00 +0000
Received: from XCH-RTP-003.cisco.com (xch-rtp-003.cisco.com [64.101.220.143]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id tAEJ305r021258 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 14 Nov 2015 19:03:00 GMT
Received: from xch-rtp-005.cisco.com (64.101.220.145) by XCH-RTP-003.cisco.com (64.101.220.143) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Sat, 14 Nov 2015 14:02:59 -0500
Received: from xch-rtp-005.cisco.com ([64.101.220.145]) by XCH-RTP-005.cisco.com ([64.101.220.145]) with mapi id 15.00.1104.000; Sat, 14 Nov 2015 14:03:00 -0500
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: Gert Doering <gert@space.net>
Thread-Topic: [v6ops] DAD again [was: draft-ietf-v6ops-host-addr-availability discussion]
Thread-Index: AQHRFohEbga31qC+rEetrILg3VHRBZ6LRgsAgAa8AYCAAnb/AIAFJeaAgAAIg4CAAEiPQIAAXDaA//+8puCAAJNfgP//ymfwgABnY4D//75MIAAMrMUAAAokG4D//7ZcAIAAThMA///AA4CAAE9HQIAA4EYAgABMFPD//76YAIAAU2XA
Date: Sat, 14 Nov 2015 19:03:00 +0000
Message-ID: <421a65641cb64b45abd75a911a877b0f@XCH-RTP-005.cisco.com>
References: <F5469EDB-E8E3-459A-ACF0-C9B2F11A8968@delong.com> <1c64119717ac4cc5a1e88dc8175af92f@XCH-RTP-005.cisco.com> <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>
In-Reply-To: <20151114185052.GM89490@Space.Net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.243.16]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/sru7rvN4bqB4tzYrYuJilcS2TXY>
Cc: "v6ops@ietf.org" <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:03:03 -0000


-----Original Message-----
From: Gert Doering [mailto:gert@space.net] 
Sent: Saturday, November 14, 2015 1:51 PM
To: Hemant Singh (shemant)
Cc: Gert Doering; Owen DeLong; v6ops@ietf.org
Subject: Re: [v6ops] DAD again [was: draft-ietf-v6ops-host-addr-availability discussion]


>But: the outbound interface will NOT use the lo0 source address for the ND activity.  It will use the *interface* IP for ND, and the link-local one for that.

I already said that in my previous email.

>Surely you're not asking for a router to do DAD for every single IPv6 address that could be coming *through* that router?

No.    A router forwards packets and if the router egress interfaces fails L2-destination lookup, the interface issues a L2 address resolution.   Note, however, once a source IPv6 address of a lo interface is active to send data and the downstream LAN segment somehow has a dup, the dup issue cannot be fixed unless the router support ND Proxy which can respond.

>> I did issue "clear ipv6 neigh" on my router to clear the neighbor cache to force a ND address resolution.  The ND address resolution NS can use the link-local address or the global address of the outbound interface for sourcing the NS.

>"the global address of the outbound interface" is NOT the lo0 source address.

Right - what is your point?  Please also see rfc5942 and section 6.  No source IPv6 address in a ND message can be used to make on on-link determination.

Hemant