Section 5 clarify the content of EB and what is sent vs what is already known

Issue #45 resolved
Xavier Vilajosana created an issue

Are operational control and management questions out of scope for this document, such as:

  • when does a node switch from the "minimal 6TiSCH configuration" to some other configuration?

TW> This is not defined, yet. A product can very well use this specification alone. TW> Future specification can detail how this spec can be augmented to schedule more cells in the slotframe. TW> However, we do not want/can specify this at this point.

  • does a node use the configuration parameters it has received through EBs to generate its own EBs or does it use the "minimal 6TiSCH configuration" parameters?

TW> By default, the node uses the information it receives from the EBs, so that become the TW> "minimal 6TiSCH configuration" parameters. Was difference are you making. TW> By default, the node also uses that information to create its own EBs. TW> To make this clearer, my recommendation is to add the following sentence at the TW> very end of Section 5 (under "Frame and Link IE") TW> This specification RECOMMMENDS that the node indicates the same information TW> in the "Frame and Link IE" in the EBs it sends, than the "Frame and Link IE" TW> information it has received in an EB. TW> @Editor, please add the sentence above.

Comments (1)

  1. Log in to comment