Re: New Version Notification for draft-chakrabarti-nordmark-6man-efficient-nd-05.txt

神明達哉 <jinmei@wide.ad.jp> Sun, 02 March 2014 16:40 UTC

Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33A7A1A096D for <ipv6@ietfa.amsl.com>; Sun, 2 Mar 2014 08:40:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.922
X-Spam-Level: *
X-Spam-Status: No, score=1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
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 CaVbGKvgmBF6 for <ipv6@ietfa.amsl.com>; Sun, 2 Mar 2014 08:40:56 -0800 (PST)
Received: from mail-we0-x22c.google.com (mail-we0-x22c.google.com [IPv6:2a00:1450:400c:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id BBF221A0960 for <ipv6@ietf.org>; Sun, 2 Mar 2014 08:40:55 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id u56so2207813wes.3 for <ipv6@ietf.org>; Sun, 02 Mar 2014 08:40:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=jbFeNpC4W3uocld1by6lYKQ5LsLjrk4LfkYGsY2DEg8=; b=k600XHXU8RRjCGwTUn+Pk/MhptiqLqfo+4fipmi2pP8O5OqFTwNPOX2egfThXPLY+2 o3pah8PCao4myKLlDj2Zxoox0CXr2nqRhqNVMlJep9TgVvGddWuuaYEFQ/pXa2PodJpV QFVWG0er6HTIBM4DNeCO6qikx4U9WzrHC8ukaQI0Wpsz+w5j93cO7HoYru3+cuwPwhAW ojdVfVjOD7aQsiUjXg2OtT1Hr/dlK6k2XH52WuYSsMvTJ/UyqRGeOV8OlpqBHsISYb/Z clNK0g5NwePsRVjdgvAoal0s7mVirfmGRPaRnhh1uqQNRvsFbVfYrSDjHHit2rwV/JB5 Fggg==
MIME-Version: 1.0
X-Received: by 10.180.24.134 with SMTP id u6mr11455650wif.41.1393778452775; Sun, 02 Mar 2014 08:40:52 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.120.167 with HTTP; Sun, 2 Mar 2014 08:40:52 -0800 (PST)
In-Reply-To: <5311DA0F.5070106@sonic.net>
References: <20140214235734.2509.63069.idtracker@ietfa.amsl.com> <52FF115C.30001@acm.org> <CAJE_bqdOiO2zyCvxsO4sEW+9ZMb0DoOyscNWP1=jedrBbbBkEA@mail.gmail.com> <530FA94B.3050802@acm.org> <CAJE_bqdF2-nH7GaC+j6PnRagDC0jDj0c0me6MOC6AsHNvDaedQ@mail.gmail.com> <5311DA0F.5070106@sonic.net>
Date: Sun, 02 Mar 2014 16:40:52 +0000
X-Google-Sender-Auth: M1j2zdLg_GiJRV5-QAw-8r2QfJM
Message-ID: <CAJE_bqe+db_ojg_3hMkHOo2LCK7cuWmjMa=RgzF5UnWo2q7znQ@mail.gmail.com>
Subject: Re: New Version Notification for draft-chakrabarti-nordmark-6man-efficient-nd-05.txt
From: 神明達哉 <jinmei@wide.ad.jp>
To: Erik Nordmark <nordmark@sonic.net>
Content-Type: text/plain; charset="ISO-8859-1"
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/Yx-8QtiJQAw5ttEscZX1rfUpZGI
Cc: Erik Nordmark <nordmark@acm.org>, IETF IPv6 <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 02 Mar 2014 16:40:57 -0000

At Sat, 01 Mar 2014 14:01:03 +0100,
Erik Nordmark <nordmark@sonic.net> wrote:

> To have a unicast RA prior to having registered the link-local address,
> the router needs to use the SLLA option in the RS - this would be the
> same mechanism as in the draft for sending errors to NS/AROs.

What if the link-local address is a duplicate and that's because the
link-layer address is a duplicate?  If the unicast RA is supposed to
include an ARO whose status field is 1 and be sent to the (duplicate)
link-local address, it's not guaranteed the RA is delivered to the
node that sent the RS.

The same question applies to the NS/NA exchange attempting to replace
the traditional DAD.

--
JINMEI, Tatuya