IETF Logo Mail Archive

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

"Hemant Singh (shemant)" <shemant@cisco.com> Sat, 14 November 2015 18:48 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 E894F1ACED2 for <v6ops@ietfa.amsl.com>; Sat, 14 Nov 2015 10:48:09 -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 PMKUx1eQrN34 for <v6ops@ietfa.amsl.com>; Sat, 14 Nov 2015 10:48:08 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 811571ACEBD for <v6ops@ietf.org>; Sat, 14 Nov 2015 10:48:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1658; q=dns/txt; s=iport; t=1447526888; x=1448736488; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=6LLSeXcqzvLvs0d/qWew8vIvbQB7qKlgN1kA6c7FtJk=; b=Uf8MIgALeYNc+Uy376PI17viXDG4nBoty5RyAnrARPV7phQ8tUN35DWo 0hbPaWSfOdzDVYXI4WV6DJuepRxGtoMOCQGMrRjwirsNYEdVf/xKbEmWn fg8a9TO8Ed+SeHP+GSsPrMhT9iCX2ZYy4/TMUFn8rj3axd57rpCvtR59n E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ABAgCKgEdW/49dJa1egzuBQga+RwENg?= =?us-ascii?q?WSGEAKBKzgUAQEBAQEBAYEKhDQBAQEEOj8MBAIBCBEEAQEfCQcyFAkIAgQOBQi?= =?us-ascii?q?IJro+AQEBAQEBAQEBAQEBAQEBAQEBAQEBGItSiTkFlkgBjR+BYpZ4g3EBHwEBQ?= =?us-ascii?q?oIRHYFWcoREgQcBAQE?=
X-IronPort-AV: E=Sophos;i="5.20,294,1444694400"; d="scan'208";a="49665383"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-2.cisco.com with ESMTP; 14 Nov 2015 18:48:07 +0000
Received: from XCH-RTP-005.cisco.com (xch-rtp-005.cisco.com [64.101.220.145]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id tAEIm7lB012999 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 14 Nov 2015 18:48:07 GMT
Received: from xch-rtp-005.cisco.com (64.101.220.145) by XCH-RTP-005.cisco.com (64.101.220.145) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Sat, 14 Nov 2015 13:48:06 -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 13:48:06 -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///AA4CAAE9HQIAA4EYAgABMFPA=
Date: Sat, 14 Nov 2015 18:48:06 +0000
Message-ID: <04d5779d611a4c5abd7db9093b991f81@XCH-RTP-005.cisco.com>
References: <D76E6E81-419B-459D-AF5F-A6B8781CF445@delong.com> <a562066cf4d14f80aa94de314c27d632@XCH-RTP-005.cisco.com> <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>
In-Reply-To: <20151114181240.GI89490@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/tU08Wq0v9BxGuQiXCGj4xf6hc6A>
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 18:48:10 -0000


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


>This, actually, is a totally meaningless example.

Not it's not since Owen ask that the lo interface is not in the same subnet at the outbound interface, so how is data forwarding working with ND if an address resolution is needed?  I proved data forwarding works.  I sure could have added to the example a log of the ND address resolution but any ND log is very copious due to NUD and thus I skipped the ND log. 

>I can send packets round the world with any source address I choose, and it has no significance for on-link NS or DAD with the *on-link* address of intermediate network segments.

>If you look more closely at your box, you'll see that it will not use the
>2004::1 source address for ND on the next-hop lan interface.

Correct.   This is what my point to Owen was.   The lo interface IPv6 address can be used to source packets out the router, and if the outbound interface has an incomplete or nonexistent entry in the neighbor cache, the outbound interfaces issues a ND address resolution and if the address resolution is completed, the packet is forwarded out.   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.

Hemant

v2.1.27 | Report a Bug | By Email