Re: I-D Action: draft-ietf-6man-dad-proxy-07.txt
Brian Haberman <brian@innovationslab.net> Fri, 12 April 2013 13:52 UTC
Return-Path: <brian@innovationslab.net>
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 CA01821F8A85 for <ipv6@ietfa.amsl.com>; Fri, 12 Apr 2013 06:52:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 2rOQpHwlzF+R for <ipv6@ietfa.amsl.com>; Fri, 12 Apr 2013 06:52:03 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 4F70821F8A3F for <ipv6@ietf.org>; Fri, 12 Apr 2013 06:52:02 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 42FA188110 for <ipv6@ietf.org>; Fri, 12 Apr 2013 06:52:02 -0700 (PDT)
Received: from clemson.local (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 0E8D414000C for <ipv6@ietf.org>; Fri, 12 Apr 2013 06:52:01 -0700 (PDT)
Message-ID: <51681182.9000303@innovationslab.net>
Date: Fri, 12 Apr 2013 09:52:02 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: I-D Action: draft-ietf-6man-dad-proxy-07.txt
References: <20130409174845.2651.57733.idtracker@ietfa.amsl.com> <1365545491.28058.311.camel@karl>
In-Reply-To: <1365545491.28058.311.camel@karl>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Fri, 12 Apr 2013 13:52:04 -0000
Hi Karl, On 4/9/13 6:11 PM, Karl Auer wrote: > 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? The proxy would have to maintain a list of nodes being proxied. In that case, the proxy can join the solicited-node multicast address for those nodes. Regards, Brian
- Re: I-D Action: draft-ietf-6man-dad-proxy-07.txt Karl Auer
- I-D Action: draft-ietf-6man-dad-proxy-07.txt internet-drafts
- Re: I-D Action: draft-ietf-6man-dad-proxy-07.txt Karl Auer
- Re: I-D Action: draft-ietf-6man-dad-proxy-07.txt Brian Haberman
- Re: I-D Action: draft-ietf-6man-dad-proxy-07.txt Jean-Michel Combes