Re: I-D Action: draft-ietf-6man-resilient-rs-02.txt

Erik Nordmark <nordmark@acm.org> Thu, 30 January 2014 06:22 UTC

Return-Path: <nordmark@acm.org>
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 C7F461A041A for <ipv6@ietfa.amsl.com>; Wed, 29 Jan 2014 22:22:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] 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 NuR2mgIcb1OJ for <ipv6@ietfa.amsl.com>; Wed, 29 Jan 2014 22:22:55 -0800 (PST)
Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) by ietfa.amsl.com (Postfix) with ESMTP id C37EE1A02F3 for <ipv6@ietf.org>; Wed, 29 Jan 2014 22:22:55 -0800 (PST)
Received: from [10.0.1.44] (184-23-158-201.dsl.dynamic.sonic.net [184.23.158.201]) (authenticated bits=0) by c.mail.sonic.net (8.14.4/8.14.4) with ESMTP id s0U6MnWp003419 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 29 Jan 2014 22:22:49 -0800
Message-ID: <52E9EFB9.9000402@acm.org>
Date: Wed, 29 Jan 2014 22:22:49 -0800
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Erik Kline <ek@google.com>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: I-D Action: draft-ietf-6man-resilient-rs-02.txt
References: <20131021233827.32495.34424.idtracker@ietfa.amsl.com> <CAKD1Yr2eBffHBA-xSepNaJQ-az56F01pgry5sdRbTRC0VMhf_w@mail.gmail.com> <CAKD1Yr2CWsysF8XD8MxiKF9rZnhxWrUO9L6-RrwETGQGEqOuzw@mail.gmail.com> <6299FD64-01A9-4F19-B271-9891AFCA3269@gmail.com> <CAAedzxrTu9L_JDktjrZh74YN6hT06dMGody6AfuQC3xewjWQ5w@mail.gmail.com>
In-Reply-To: <CAAedzxrTu9L_JDktjrZh74YN6hT06dMGody6AfuQC3xewjWQ5w@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Sonic-ID: C;Ujgc8XaJ4xGTc+ozIE/FGg== M;8CRB8XaJ4xGTc+ozIE/FGg==
Cc: draft-ietf-6man-resilient-rs@tools.ietf.org, IETF IPv6 Mailing List <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: Thu, 30 Jan 2014 06:22:57 -0000

On 1/29/14 11:34 AM, Erik Kline wrote:
>> A host on a multicast-capable link on which "unsolicited multicast Router Advertisements are never sent" will have to use the same transmission behavior as a host on a non-multicast-capable link, so that the host can learn of changes in the link prefixes in a timely fashion.
> Not necessarily.
>
> Consider the situation in a which a router responds to multicast RSs
> with unicast RAs.  The host may in fact continue to receive unicast
> RAs periodically.
Erik,

In such an approach when would the router stop unicasting RAs to a 
particular address? Forever? Until NUD fails? What is the host was gone 
for 30 seconds without the host noticing and as a result the router saw 
a NUD failure.

Without clear details one can't say 1) whether this will work and 2) 
weather it would save any resources.

Note (in case it isn't obvious) that a router can respond to a RS with a 
unicast RA - that is already allowed by 4861 and its predecessors.

    Erik