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 15:03 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 342503A0484 for <ipv6@ietfa.amsl.com>; Thu, 12 Mar 2020 08:03:47 -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 wvvOp8ZeX9Wh for <ipv6@ietfa.amsl.com>; Thu, 12 Mar 2020 08:03:45 -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 39B533A047D for <ipv6@ietf.org>; Thu, 12 Mar 2020 08:03:45 -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 DFA7C8061F; Thu, 12 Mar 2020 16:03:38 +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> <b1859f3e-5519-5573-0a52-0fa88efeb99e@si6networks.com> <m1jCP2D-0000GrC@stereo.hq.phicoh.net>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <f50145fa-e1f3-4e20-f4e7-877f61440833@si6networks.com>
Date: Thu, 12 Mar 2020 12:03:29 -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: <m1jCP2D-0000GrC@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/MJH5YPQMiaMe6TbCzMNFHA639Fk>
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 15:03:47 -0000

On 12/3/20 11:42, Philip Homburg wrote:
> In your letter dated Thu, 12 Mar 2020 11:33:39 -0300 you wrote:
>> 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.
> 
> Please write drafts that actually work when implemented. 

Please be constructive.


> If you know that
> the values in your draft can causes failures why put them in?

Any values that you put may cause trouble under given circumstances. For 
instance, you could be simply unlucky and have all multicasted RAs that 
are sent to be lots. There's *nothing* that warrants that that's not the 
case.

So, in engineering, we always operate on probability and statistics.



>> 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 is specifically allowed
> 
>>    + that they spread PIOs among multiple RA messages, *and*
> 
> Also allowed

There's a recommendation that you SHOULD send all information in the 
smallest possible number of packets. You're supposend to go against 
SHOULDs if you really know what you are doing.


> 
>>    + one of such messages with PIOs get lost
> 
> It is safe to assume that every once in a while a RA gets losts.

It is also allowed for an arbitrarily large number of packets to get lost.



[...]
>> 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)
> 
> Sending unicast RAs is way more complex than my algorithm, so I don't see
> the point.

Could you explain the complexity of sending a unicast RS?

I don't know how you consider the the measuring part of your algorithm 
any more simpler thatn firing a unicast RS.

Besides, your alggorithm does make assumptions about how information in 
RAs is spread, and also about packet loss. Why are you fine with those 
assumptions?

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