Malisa and I, when editing the documents this week came across a concern that we had. It involves the traffic between the Join Proxy (JP), and the Join Registrar/Coordinator (JRC, formerly known as JCE).
This is regular traffic, and is would flow through the mesh as would any other traffic. Only the JP and JRC would know it was join traffic, and if the JRC is not-within the LLN (beyond the DODAG root), then the DODAG root wouldn't be able to identify the join traffic. In a smarter-than-minimal network a specific track could be allocated for this traffic. The specific concern I have with minimal is that there could be surges in join traffic (from newly activated pledges, some of which could be malicious). That minimal might react by allocating new cells for the extra traffic, and this might be a bad thing. I can't say that I know what the right behaviour is. Clearly the network should not be allocating cells that it needs for more important things, and I think that 6p can do deny things appropriately. But the intermediate nodes might not recognize the traffic as join traffic, and might allocate anyway. Is there a way we can mark join traffic so that this doesn't happen? Either explicitely (DSCP perhaps?), or implicitely (this cell is join traffic). -- Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
