Re: I-D Action: draft-ietf-6man-dad-proxy-07.txt

Karl Auer <kauer@biplane.com.au> Tue, 09 April 2013 22:11 UTC

Return-Path: <kauer@biplane.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB17921F9958 for <ipv6@ietfa.amsl.com>; Tue, 9 Apr 2013 15:11:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_21=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZmHIuGeUANmG for <ipv6@ietfa.amsl.com>; Tue, 9 Apr 2013 15:11:36 -0700 (PDT)
Received: from ipmail04.adl6.internode.on.net (ipmail04.adl6.internode.on.net [IPv6:2001:44b8:8060:ff02:300:1:6:4]) by ietfa.amsl.com (Postfix) with ESMTP id D5B7321F9616 for <ipv6@ietf.org>; Tue, 9 Apr 2013 15:11:34 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap0BAJKRZFGWZX+7/2dsb2JhbAANRIM8RMBzgS2DEwEBAQSBCQsYLlcZiBurHpNcjxsWgysDiEaPVIpViDY
Received: from eth4284.nsw.adsl.internode.on.net (HELO [192.168.1.202]) ([150.101.127.187]) by ipmail04.adl6.internode.on.net with ESMTP; 10 Apr 2013 07:41:33 +0930
Message-ID: <1365545491.28058.311.camel@karl>
Subject: Re: I-D Action: draft-ietf-6man-dad-proxy-07.txt
From: Karl Auer <kauer@biplane.com.au>
To: ipv6@ietf.org
Date: Wed, 10 Apr 2013 08:11:31 +1000
In-Reply-To: <20130409174845.2651.57733.idtracker@ietfa.amsl.com>
References: <20130409174845.2651.57733.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-Mailer: Evolution 3.2.3-0ubuntu6
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 09 Apr 2013 22:11:36 -0000

On Tue, 2013-04-09 at 10:48 -0700, internet-drafts@ietf.org wrote:
> Abstract:
>    The document describes a proxy based mechanism [...]
>    Based on the DAD signalling, the first hop router
>    stores in a Binding Table all known IPv6 addresses used on a point-
>    to-multipoint domain (e.g.  VLAN).  When a node performs DAD for an
>    address already used by another node, the first hop router replies
>    instead of this last one.

Coming late to this but - DAD NS frames are sent to solicited node
multicast addresses, so how is the first hop router seeing them?
IPv6-aware (MLD snooping) switches won't forward the DAD NS frames
except to members of the SNM group...?

What am I missing?

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)
http://www.biplane.com.au/kauer
http://twitter.com/kauer389

GPG fingerprint: B862 FB15 FE96 4961 BC62 1A40 6239 1208 9865 5F9A
Old fingerprint: AE1D 4868 6420 AD9A A698 5251 1699 7B78 4EEE 6017