Hi Carsten,
> Hence, it seems to me that we should recommend that routers do not use these features between them. As a minimum, a router node entering a 6LoWPAN needs to learn about the compression context in use in this 6LoWPAN. Unless the routing protocol is configured to strictly stay within the 6LoWPAN, I have no idea how to do this in a routing protocol. [Mathilde] Well distributing context is an optional feature of 6lowpan-ND. I was trying mainly to clarify the registration part. In addition, it seems possible to work that out with current routing protocols for LLN. If it was not the case, the RS/RA could be used to learn network parameters only. This generates quite some overhead traffic but it might be the only solution. (As a more general observation, your line of reasoning would ultimately mean all kinds of IPv6 routers should never do ND. This is not what the IPv6 design has decided to do.) [Mathilde] This is not my line of reasoning at all, rather I'm trying to understand if the registration concept makes sense between routers. If not, this means that: - We might need to endure the cost of an initial multicast NS for address resolution (unless the routing protocol messages carry SLLAO) - In networks where DAD is needed, we might need to decouple DAD from registration as specified today Best, Mathilde
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 6lowpan mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lowpan
