Hello Diego:
Thanks for this great argumentation. I agree that you are following the 6p
design but disagree with that design in the first place.
I see value in a clear layer separation where the TSCH specifics are separated
from the bandwidth calculations.
We could also see the functional
Pascal,
The question here is who is doing cell accounting.
AFAIK, 6P had to guarantee transactions and SF had to
do the accounting by directly managing the cells by their
identification. This is explained (at least) on the example
from Figure 4, section 4.1.1, step 1, on page 6 of the
Hell Diego,
My point is that a SF should operate on a number of units of transmissions,
which happen to be cells in our case.
SF should indicate to 6top that there is a need to change for more of less of
these units.
But the fact that one of these units is mapped to a particular slot offset /
Dear all,
following the indications of Suresh raised today at the conf call, please
see the discussion thread that followed from Charlie's review of the
minimal draft. Sorry for not having posted this to the ML before.
the latest version of the draft is in the bitbucket repository ( See it
Connection details
* Date: 7-8am Pacific:
http://www.worldtimebuddy.com/?qm=1=100,12,5392171,1850147=100=2016-05-13=14-15
* Webex link:
https://cisco.webex.com/ciscosales/j.php?MTID=md64a0958ae4154c0553f056bf42b756a
* Webex recording:
Dear all,
During today's webex call, I presented a slide where
the comments below were going to be addressed on the next
version of the draft.
However, I raised the point about:
Ø 4. Rules for CellList
Why is this here? Which cell are allocated is not SF0 ‘s business,
Dear all,
I proposed today to add a new type of error
for CellList proposal during the transaction. The idea
follows the solution proposed today at the Webex call
by Xavi to define a lock when two concurrent cell
requests arrive to the node.
For example, if node B requests a cell from
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IPv6 over the TSCH mode of IEEE 802.15.4e of
the IETF.
Title : 6TiSCH 6top Scheduling Function Zero (SF0)
Authors : Diego Dujovne
