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

Fernando Gont <fgont@si6networks.com> Wed, 11 March 2020 03:29 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 9C37A3A1059 for <ipv6@ietfa.amsl.com>; Tue, 10 Mar 2020 20:29:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 wiLPe5Z764HR for <ipv6@ietfa.amsl.com>; Tue, 10 Mar 2020 20:29:14 -0700 (PDT)
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 247213A1057 for <ipv6@ietf.org>; Tue, 10 Mar 2020 20:29:13 -0700 (PDT)
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 C92ED80831; Wed, 11 Mar 2020 04:29:09 +0100 (CET)
Subject: Re: I-D Action: draft-gont-6man-slaac-renum-02.txt
To: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>, ipv6@ietf.org
References: <158191113600.5878.10760004246455372944@ietfa.amsl.com> <35f3e826-81ce-d505-3c27-def73983d291@gmail.com> <CAMGpriVTPPcc9bKuKANp1BLnDLU2gmmeq9yfcNFm+sZaNtgoBg@mail.gmail.com> <m1j9lU7-0000JCC@stereo.hq.phicoh.net> <m1jA9CY-0000F8C@stereo.hq.phicoh.net> <299db2f5-3dad-ebe4-a5b4-76d1d6e942a1@si6networks.com> <m1jBGe0-0000KrC@stereo.hq.phicoh.net> <66be9d89-2e38-4e91-3186-a09fa13df82a@si6networks.com> <m1jBcDq-0000J1C@stereo.hq.phicoh.net>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <eef3908a-c02f-87c7-fcc8-b676ee68571a@si6networks.com>
Date: Wed, 11 Mar 2020 00:20:45 -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: <m1jBcDq-0000J1C@stereo.hq.phicoh.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/SWvGEC9kt-btSDrVa3c5TSliFLE>
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: Wed, 11 Mar 2020 03:29:17 -0000

On 10/3/20 07:34, Philip Homburg wrote:
> In your letter dated Mon, 9 Mar 2020 13:48:34 -0300 you wrote:
>> That is correct. I'd say, though, that the guess is based on empirical
>> evidence. I haven't seen any implementation that intentionally splis the
>> contents of RAs among multiple RAs.
> 
> I'm very much against a standard where one part of the standard imposes
> no limits, and then another part implictly assumes that there is infact
> a limit.

I'm not necessarily arguing against this, but this happens all over the 
place. e.g., there is no limit regarding how many addresses a host can 
configure. But in practice, there are. That said, I see your point, and 
we'll work



> If your code needs a limit on the number of RAs uses by a router to
> announces all prefixes, then this draft should explictly set such a limit.

At least the deprecation part, is an optimization.



[....]
>> #1 is of utmost importance. But if the algorithm fails, you just
>> unpreferred the address. -- Yes, there might be undesirable oscillations
>> of the preferred address,but nothing has brokon down.
> 
> If the host knows a stale address then deprecating a good address may cause
> the host to use the stale address which does break things.

Could you please elaborate?



>> #2 is what might cause breakage. In such case you can increase
>> LTA_RAS_INVALID, at the expense of maintaining potentially-invalid
>> addresses for longer.
> 
> You cannot expect a random user of a phone to increase LTA_RAS_INVALID,
> the draft doesn't even say that LTA_RAS_INVALID needs be configurable, so it
> may be hardcoded in the OS.

What I was meaning is that we, as a WG, can set such variables to 
whatever value we think fits.

I realize that the draft does not say those should be configurable. We 
will make this clear in the next rev.

(The bottom-line is that I'm debating the document and of course open to 
changes and improvements)



>> This is the first time I see you objecting to the algorithm, but my
>> memory might be failing. Could you provide a ref to any previous post,
>> such that if there were other things that you raised, we can try to
>> address them? (and also to figure out what happened with my mail system).
> 
> I found a message where you respond to me raising the issue:
> https://mailarchive.ietf.org/arch/msg/ipv6/_oe8GMNO70uxaBYWcJQgtX869MY/

To be honest, I didn't remember such exchange, but have re-read it. -- I 
will come back with more on this in a later email...

Thanks!

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