Re: [Roll] Border router failure detection

Hi again Pascal,

On 08/04/2021 16:16, Pascal Thubert (pthubert) wrote:
> Hello Konrad
> 
> About this text
> "
> 
>     Since all DODAG paths lead to the corresponding LBR, detecting its
>     crash by a node entails dropping all parents and adopting an infinite
>     rank, which reflects the node's inability to reach the LBR.  However,
>     achieving this state for all nodes is slow, can generate heavy
>     traffic, and is difficult to implement correctly [Iwanicki16]
>     [Paszkowska19] [Ciolkosz19].
> "
> 
> Please note that this may be what an implementation decides to do, but is by far not my favorite option.
> The alternate is to rest the "G" but and become floating root. The benefit is that the DODAG structure is mostly maintained and that routing inside may persist.
> 
> See https://tools.ietf.org/html/rfc6550#section-18.2.4 for how to configure this.

OK, I think I addressed this in my previous e-mail to you and Michael.

(The next two e-mails will have to wait till tomorrow I am affraid.)

Best,
-- 
- Konrad Iwanicki.

>> -----Original Message-----
>> From: Roll <roll-bounces@ietf.org> On Behalf Of Konrad Iwanicki
>> Sent: mercredi 7 avril 2021 21:37
>> To: Routing Over Low power and Lossy networks <roll@ietf.org>
>> Subject: Re: [Roll] Border router failure detection
>>
>> Dear all,
>>
>> Approximately a year ago, I joined the WG and advertised an extension to
>> RPL that I had been working on for some time with a goal of describing it
>> in a draft. Unfortunately, just when I got the necessary pointers and a
>> few initial comments, the pandemic broke out. The resulting surge of
>> professional and personal obligations made it literally impossible for me
>> to participate in and, at some point, even follow the group's activities,
>> for which I am sorry.
>>
>> However, I did strive to regularly find a little time to get somewhat
>> acquainted with IETF's procedures and write up something that may resemble
>> a draft. I have just submitted it as:
>>
>>      draft-iwanicki-roll-rnfd-00
>>
>> and created a dedicated repository on the group's GitHub.
>>
>> Since I have no experience writing IETF documents, I would really
>> appreciate your collaboration on either turning the text into a true draft
>> or concluding that this should not be done.
>>
>> Please, keep mind in mind that I decided to maximally cut down the
>> original algorithms, so that the extension is as simple as possible
>> without losing key properties. Therefore, it is likely that if the
>> extension as a whole or any of its parts turn out relevant or interesting,
>> still a considerable amount of work may be necessary to have it or them
>> described properly. Your contribution is most welcome.
>>
>> Thanks in advance.
>>
>> Best regards,
>> --
>> - Konrad Iwanicki.
>>
>> _______________________________________________
>> Roll mailing list
>> Roll@ietf.org
>> https://www.ietf.org/mailman/listinfo/roll
> 
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
> 