Re: [Roll] WGLC on draft-ietf-roll-unaware-leaves-13

Dear Authors-of-unaware-leaves,

Following are my comments for the draft -13:

1. The draft requires that the first registration (EDAR/EDAC) is
directly handshaked with the 6LBR but all the subsequent refreshes
using DAO/DAO-ACK goes through the Root which in turn generates
anonymous EDAR/EDAC handshaked with the 6LBR.
**Can't we have the 6LR simply use DAO always to Root which generates
the EDAR(with ROVR)/EDAC to 6LBR?** This would simplify the handling
of 6LR. With the updated target option it is now possible to send ROVR
in target option in a backward-compatible fashion. The root is anyways
handling the anonymous EDAR/EDAC and thus has all the required
handling needed to proxy non-anonymous EDAR/EDAC. Also, the
de-registration is also handled through Root which means Root also has
to proxy non-anonymous EDAR/EDAC in that case? The de-registration
case is not clarified in the Figures 7,8,9.

2. The document introduces the term RAN for any RPL aware node which
can act as a parent node for the RUL. But in the document,
subsequently, the term 6LR is used to depict the parent node with
which the RUL attaches. Wondering why? Isn't RAN the appropriate term
to be used?

3. Section 9.2.2: "If a 6LR receives a valid NS(EARO) message with the
"R" flag reset and a Registration Lifetime that is not 0, and the 6LR
was redistributing the Registered Address due to previous NS(EARO)
messages with the flag set, then it MUST stop injecting the address."
In this case, should the 6LR also evict the corresponding NCE?

4. Section 9.2.3: "the Registration Lifetime is adapted from the Path
Lifetime in the TIO by converting the Lifetime Units used in RPL into
units of 60 seconds used in the 6LoWPAN ND messages;"
The unit of lifetime for RPL is not a multiple of 60sec like that of
6lo ND. Thus it is possible that absolute conversion is not possible
in some cases. I guess the implementation should round-up in this
case?

5. Section 5 ... "anonymous message can only increase the lifetime"
... It should be "anonymous message can only update the lifetime"

6. Section 9.1 ... "On the first Address Registration, illustrated in
Figure 5 and Figure 8" ... Figure 8 currently does not show first
address registration.

7. Nits:
Sec 9.2.2 "that is sends in response" -> "that is sent in response"
Sec 10: "unicast to each if the interested children" -> "unicast to
each of the interested children"
Sec 10: "Layer-2 acknoledgement" -> "Layer-2 acknowledgement"
Sec 11: " whereby the it is possible to validate" ->  "whereby it is
possible to validate"
Sec 12.4: "DAO-ACK and RCO" -> "DAO-ACK and DCO"
Appendix A: " Follows the RPI-6LoRH and then the IP-in-IP 6LoRH." ->
Need to be rephrased

Thank you.

Best,
Rahul

On Tue, 7 Apr 2020 at 17:58, Ines Robles
<mariainesrobles=40googlemail.com@dmarc.ietf.org> wrote:
>
> Dear all,
>
> We hope that you all are doing well and stay healthy
>
> This is a kindly reminder of the WGLC for unaware-leaves draft.
>
> It would be great if you could state your opinion on it.
>
> Have a great day and thank you in advance,
>
> Ines, Dominique and Michael
>
> On Wed, Mar 25, 2020 at 5:45 PM <dominique.barthel@orange.com> wrote:
>>
>> Dear all,
>>
>> This is a gentle reminder that we are half-way through the WGLC for draft-ietf-roll-unaware-leaves-13.
>> Please consider reading it and commenting on it.
>> Thanks
>>
>> Dominique
>>
>> De : "mariainesrobles@googlemail..com" <mariainesrobles@googlemail.com>
>> Date : Wednesday 18 March 2020 12:40
>> À : "roll@ietf.org" <roll@ietf.org>
>> Cc : Dominique Barthel <dominique.barthel@orange.com>
>> Objet : WGLC on draft-ietf-roll-unaware-leaves-13
>>
>> Dear all,
>>
>> A Working Group Last Call (WGLC) starts today (03/18) until 04/01 for the draft-ietf-roll-unaware-leaves-13.
>> The draft is available here: https://datatracker.ietf.org/doc/draft-ietf-roll-unaware-leaves/
>> Please review this draft to see if you think that it is ready for publication and send comments to the list stating your view.
>> Thank you very much in advance,
>>
>> Ines and Dominique
>>
>> _________________________________________________________________________________________________________________________
>>
>> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
>> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>>
>> This message and its attachments may contain confidential or privileged information that may be protected by law;
>> they should not be distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and delete this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
>> Thank you.
>>
>> _______________________________________________
>> 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