Hi Diego, thank you for your answer too.
However there are two points I would like to point out. First, the mac-layer ack is in fact the TSCH ack, that travels on the air during the same timeslot of the data packet. It is sent if the data packet is unicast, either on shared or on dedicated cells. The 6P ACK I'm proposing is NOT a TSCH ack, it is a data packet sent from A to B and it requires its own TSCH ack from B to A. Second, I'm totally not aligned on "...dedicated cells are for data and shared cells for any kind of signalling and/or negotiation." and I believe this is not the distinction between those types of cells. Shared or dedicated cells can be used either for signaling and/or data. 'Minimal'. as an example, has got a single shared cell. One can run minimal without any other more sophisticated scheduling technique just using that shared cell for both signaling and data. The same is possible if someone uses a dynamic schedule and uses also dedicated cells. I don't see any reason for forbidding dedicated cells to vehiculate both signaling and data. The difference is that in shared cells there's contention. I would add that it could be possible to piggyback 6P signaling with data from upper layers, if there is space in the MTU. It is the encapsulation that makes the distinction between data and 6P signaling. Data go encapsulated within the IEEE802.15.4e packet payload, while 6P goes into the payload IEs, and these two payloads can coexist in the same IEEE802.15.4e frame. Thoughts? Nicola
_______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
