Re: I-D Action: draft-gont-6man-slaac-renum-02.txt

Fernando Gont <fgont@si6networks.com> Thu, 05 March 2020 20:41 UTC

Return-Path: <fgont@si6networks.com>
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 2B0073A0B8B for <ipv6@ietfa.amsl.com>; Thu, 5 Mar 2020 12:41:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.85
X-Spam-Level:
X-Spam-Status: No, score=-0.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 xC_6ugengWTK for <ipv6@ietfa.amsl.com>; Thu, 5 Mar 2020 12:41:54 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93AFE3A0AD1 for <ipv6@ietf.org>; Thu, 5 Mar 2020 12:41:54 -0800 (PST)
Received: from [192.168.0.10] (unknown [181.45.84.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 4599080076; Thu, 5 Mar 2020 21:41:45 +0100 (CET)
Subject: Re: I-D Action: draft-gont-6man-slaac-renum-02.txt
To: Erik Kline <ek.ietf@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: 6man <ipv6@ietf.org>
References: <158191113600.5878.10760004246455372944@ietfa.amsl.com> <35f3e826-81ce-d505-3c27-def73983d291@gmail.com> <CAMGpriVTPPcc9bKuKANp1BLnDLU2gmmeq9yfcNFm+sZaNtgoBg@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <a7aa5c32-abba-50da-47b3-2876da35da47@si6networks.com>
Date: Thu, 05 Mar 2020 01:51:20 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAMGpriVTPPcc9bKuKANp1BLnDLU2gmmeq9yfcNFm+sZaNtgoBg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/kSmBuzKgjF5O9BJ2qWmouB0ylc4>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 05 Mar 2020 20:41:59 -0000

Hello, Erik,

On 5/3/20 01:29, Erik Kline wrote:
> Is the 4.4 stuff really what we want?  I kinda think there might be 
> other options.

The stuff in Section 4.4 follows the principle of "do smarts at hosts", 
in this case, *without explicit signalling* from routers.  This allows 
hosts to recover from stale information even with current/legacy routers.



> For example, something like an ND Option that routers can include in 
> their NA (they already set the IsRouter flag).

The stuff in Section 4.4 doesn't exclude options like this. In fact, 
it's complementary.



> If this option 
> represented a kind of "generation number", then hosts could notice when 
> it changed during regular NUD (they don't need to wait for an RA, which 
> they might have already missed for one reason or another) and start a 
> countdown timer to send a unicast RS to check for changes.

Indeed that might be doable. However, Section 4.4 is stuff that if a 
host implements, it can already benefit from without having to wait for 
routers to be updated.

Thanks!

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492