2 drafts in 20min, you're on a roll!
On Mon, Jul 2, 2018 at 7:31 PM Jonathan Muñoz
wrote:
>
> -- Forwarded message --
> From:
> Date: 2018-07-02 19:29 GMT+02:00
> Subject: New Version Notification for draft-munoz-6tisch-examples-03.txt
> To: Jonathan Muñoz , Dominique Barthel <
-- Forwarded message --
From:
Date: 2018-07-02 19:29 GMT+02:00
Subject: New Version Notification for draft-munoz-6tisch-examples-03.txt
To: Jonathan Muñoz , Dominique Barthel <
dominique.bart...@orange.com>
A new version of I-D, draft-munoz-6tisch-examples-03.txt
has been
A new version of I-D, draft-munoz-6tisch-multi-phy-nodes-00.txt
has been successfully submitted by Jonathan Munoz and posted to the
IETF repository.
Name: draft-munoz-6tisch-multi-phy-nodes
Revision: 00
Title: Problem Statement for Generalizing 6TiSCH to Multiple PHYs
-- Forwarded message --
From:
Date: Mon, Jul 2, 2018 at 6:37 PM
Subject: New Version Notification for draft-chang-6tisch-msf-02.txt
To: Malisa Vucinic , Simon Duquennoy ,
Xavier Vilajosana , Diego Dujovne <
diego.dujo...@mail.udp.cl>, Tengfei Chang
A new version of I-D,
Hi Randy,
RFC8180 proposes some configurations so vendors can bootstrap the network,
this is for example the fact that a minimal cell exists. The content of EBs
is defined in the 802.15.4 spec and as long as an implementation fulfills
the standard a vendor node should be able to handle EBs. IEs
So there are no known interop issues with non-RPL minimal deployments if
different vendors choose their own EB policies?
Thx,
R.
From: Xavi Vilajosana Guillen
Sent: Monday, July 2, 2018 9:01:23 AM
To: Turner, Randy
Cc: tisch
Subject: Re: [6tisch] 6TiSCH
Hi Randy,
thanks for your comment! When RPL is used, the EBs use the Dagrank(rank) as
join metric. In this way we match the routing topology with the timing
topology. When RPL is not used, there is no such need as the join metric is
only based in a depth counter. When a node has not acquired a
