Xavi> information between the SF of the communicating nodes. The command
Xavi> can be named SIGNAL and 6P will not define the content but only the
Xavi> operation and encapsulation. The content will be defined by the
Xavi> different SFs as an IE.
Xavi> I think that a message like this brings flexibility to SFs to
Xavi> implement configuration operations.
I believe that I'm ignorant of how an SFx gets chosen for an LLN.
Can multiple co-exist in different parts of the LLN?
(I don't think so)
Can the chosen SFx change over time?
I ask because it seems like at least the content must include the SFx
type so that there is no confusion of SFx's IE with SFy's IE.
--
Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ 6tisch mailing list 6tisch@ietf.org https://www.ietf.org/mailman/listinfo/6tisch
