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

Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> Mon, 09 March 2020 11:32 UTC

Return-Path: <pch-b9D3CB0F5@u-1.phicoh.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 02FD63A0D9D for <ipv6@ietfa.amsl.com>; Mon, 9 Mar 2020 04:32:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.624
X-Spam-Level:
X-Spam-Status: No, score=-1.624 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.274, SPF_HELO_NONE=0.001, SPF_NONE=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 GedmXf37PjVP for <ipv6@ietfa.amsl.com>; Mon, 9 Mar 2020 04:32:28 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC1B03A0D7A for <ipv6@ietf.org>; Mon, 9 Mar 2020 04:32:27 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #157) id m1jBGe0-0000KrC; Mon, 9 Mar 2020 12:32:24 +0100
Message-Id: <m1jBGe0-0000KrC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Cc: Fernando Gont <fgont@si6networks.com>
Subject: Re: I-D Action: draft-gont-6man-slaac-renum-02.txt
From: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
Sender: pch-b9D3CB0F5@u-1.phicoh.com
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>
In-reply-to: Your message of "Fri, 6 Mar 2020 16:24:55 -0300 ." <299db2f5-3dad-ebe4-a5b4-76d1d6e942a1@si6networks.com>
Date: Mon, 09 Mar 2020 12:32:23 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/npsoQbhmDFTMQaUC8P6sTSy91oQ>
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: Mon, 09 Mar 2020 11:32:40 -0000

>> I forgot to mention. The current algorithm in Section 4.4 fails if a
>> router sends multiple RAs with a different prefix in each RA.
>> As far as I know, that behavior is allowed.
>
>Nope. The algorithm can accommodate such behaviour by setting 
>LTA_RAS_UNPREFER and LTA_RAS_INVALID appropriately.
>
>For exampple, with the currently specified default settings, PIOs can be 
>split into two RAs, without the prefixes becoming un-preferred. The 
>values of those configuration variables could be increased as deemed 
>necessary -- albeit at the expense of sacrificing responsiveness.

This doesn't work. LTA_RAS_UNPREFER and LTA_RAS_INVALID are fixed in the
host implementation. So the host has to guess what the router is going
to do. 

We have no limit on what the router can do so any guess is wrong by
definition.

At the same time, responsiveness goes completely down the drain for higher
values. Rendering this draft mostly irrelevant if we set those values to
something 'safe'.

In short, I consider this a bad algorithm. I have said so many times in the
past, so I'm not quite sure why the authors want to continue pushing this.