On Tue, Jul 17, 2018 at 10:25 PM Tero Kivinen wrote:
> If JRC restarts and looses track who is in the network, then it cannot
> send updaes, as it does not know who is in the network. I.e., in that
> case all nodes need to rejoin.
>
How do we detect that JRC restarted at 6LBR if JRC is in the Cl
On Wed, Jul 18, 2018 at 2:36 AM Tengfei Chang
wrote:
> Hi Malisa and Tero,
>
> Thanks for answering my question! It is clear to me!
>
> I don't fully understand. Do you mean in which case would a node send
>> another Join Request, if it has already completed the join process sometime
>> before an
Hi Malisa and Tero,
Thanks for answering my question! It is clear to me!
I don't fully understand. Do you mean in which case would a node send
> another Join Request, if it has already completed the join process sometime
> before and obtained the L2 encryption keys?
>
My question is exactly what
Mališa Vučinić writes:
> Hence I have two questions:
> 1. in what case JRC or some entity will send such packet?
>
> For example if a JRC detects that some node in the network
> misbehaves, generates large amount of traffic, is misconfigured or
> similar. The JRC would then simply need to
Hi Tengfei,
Thanks for your review! See my responses and proposed resolutions inline.
Mališa
On Mon, Jul 9, 2018 at 3:44 PM Tengfei Chang wrote:
> Hi Malisa,
>
> I just reviewed the draft and have several comments below.
>
> *Comment 1: *
> *--*
> In section 9.3.2 when desc
Hi Malisa,
I just reviewed the draft and have several comments below.
*Comment 1: *
*--*
In section 9.3.2 when describing link-layer key set:
*When 6LBR receives this*
*parameter, it MUST remove any old keys it has installed from the*
*previous key set and immediately install
