Re: SLAAC renum -- revised algorithm (Fwd: New Version Notification for draft-gont-6man-slaac-renum-04.txt)

Fernando Gont <fgont@si6networks.com> Thu, 12 March 2020 14:34 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 156D33A0A4E for <ipv6@ietfa.amsl.com>; Thu, 12 Mar 2020 07:34:02 -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 RXOkdbqLp8li for <ipv6@ietfa.amsl.com>; Thu, 12 Mar 2020 07:34:00 -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 203813A0A46 for <ipv6@ietf.org>; Thu, 12 Mar 2020 07:34:00 -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 C48FF80831; Thu, 12 Mar 2020 15:33:56 +0100 (CET)
Subject: Re: SLAAC renum -- revised algorithm (Fwd: New Version Notification for draft-gont-6man-slaac-renum-04.txt)
To: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>, ipv6@ietf.org
References: <158393319617.1552.258016943645564875@ietfa.amsl.com> <52e89429-c29e-b10a-718d-a90c61ed0cde@si6networks.com> <m1jCNdS-0000IyC@stereo.hq.phicoh.net>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <b1859f3e-5519-5573-0a52-0fa88efeb99e@si6networks.com>
Date: Thu, 12 Mar 2020 11:33:39 -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: <m1jCNdS-0000IyC@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/HTU-ajvovEINEcNGrwAUi3kortQ>
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, 12 Mar 2020 14:34:09 -0000

On 12/3/20 10:12, Philip Homburg wrote:
> In your letter dated Wed, 11 Mar 2020 10:38:43 -0300 you wrote:
>> The original algorithm (Algorithm #1) is now Section 4.5.1, while the
>> new algorithm (Algorithm #2) is in Section 4.5.2.
> 
> I think your new algorithm fails if a router sends two prefixes in two
> RAs and one RA gets lost.
> 
> Note RFC 4861 says (Section 6.2.1):
> MaxRtrAdvInterval
>                       The maximum time allowed between sending
>                       unsolicited multicast Router Advertisements from
>                       the interface, in seconds.  MUST be no less than 4
>                       seconds and no greater than 1800 seconds.
> 
> So if one RA gets lost, the next one may come only after 1800 seconds.

Yes, this is noted in the I-D where we say LTA_IVALID_DEFAULT could be 
1800 seconds if we wanted to be more conservative.

I see a number of possible ways forward:

1) Keep "as is", since in order for this to happen, this woudl require:
   + that implementations use a non-defualt value for MaxRtrAdvInterval, 
*and*

   + that they spread PIOs among multiple RA messages, *and*

   + one of such messages with PIOs get lost


2) Increase LTA_INVALID_DEFAULT to 1800, as noted in the I-D. I wouldn't 
mind, although this comes at the expense of reduced responsiveness

3) Keep the current default timer, but not that an implementation may 
want to send a unicast RA to the router when expiration is imminent 
(this is probably in RFC4861, already)

Thoughts?



> I forgot one issue, a router may send two RAs, one with a ULA, and one
> with a routable prefix. If the routable prefix accidentally gets deprecated,
> then the host loses connectivity.

This is a good point, and we will fix it (thanks!). Essentially, this 
behavior should be triggered by "RAs that contain one PIO that 
advertises a non-ULA prefix".

Or, even better, ULA addresses should be deprecated by PIOs that carry 
other ULA prefixes (but not the currently used one), where global 
addresses should be deprecated by "RAs that carry PIOs that advertise 
global prefixes, but not the currently used ones".

Thoughts?

Thanks!

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