Hi Qin,
Hmm, in your example, node A can resolve the inconsistency without
using the generation counter by sending CLEAR to node B after the
timeout occurs. Node A could use STATUS or STATUS+LIST before sending
CLEAR in order to confirm inconsistency if the schedule generation
inconsistency detec
Hi Yasuyuki,
I'm not sure I fully understand you.
Let's assume node A wants to ADD cells with nodeB in 2-step transaction. After
nodeA sends ADD Request to nodeB, the Timeout of nodeA is set. nodeB receives
the ADD Request, adds the cells to its schedule and sends Response back to
nodeA at same
The IPv6 over the TSCH mode of IEEE 802.15.4e (6tisch) Working Group will hold
a multi-day virtual interim meeting.
Session 1:
2017-01-06 07:00 to 08:00 US/Pacific
Session 2:
2017-01-20 07:00 to 08:00 US/Pacific
Session 3:
2017-02-03 07:00 to 08:00 US/Pacific
Session 4:
2017-02-17
IESG Secretary wrote:
> The IPv6 over the TSCH mode of IEEE 802.15.4e (6tisch) Working Group
> will hold a virtual interim meeting on 2016-12-09 at 15:00 UTC.
> Agenda: Progress on security and 6top documents
> Information about remote participation:
>
https://cisco.webex.co
Thanks Xavi for publishing this.
Suresh' comment highlighted that some editorial issues which were fixed in
-17. You will see that the structure has changed (section were shuffled).
Although the diff looks impressive, none of the technical content shoud be
different. We appreciate you flagging any
