Hi Erik > I don't see how the additional complexity of oDAD makes anything different > in 6lowpans; as I stated in an earlier email I think it is impossible to detect > duplicate EUI-64's in a 6lowpan.
[Pascal] Yes, I've read that part and I'm afraid I partially disagree. Partially because it depends what you're fighting against. To fight against attacks is difficult and probably requires crypto. OTOH, if the most probably cause of dups is erroneous config or forged hardware, and we are looking at preventing that sort of error, then a simple boot-time random can help tremendously. The simplest method is to place the boot-time random in all registrations. A registration with the wrong random fails. More complex, and slightly more secure, place it in the first registration and then include it in a signature. The consequence is that a device with no permanent memory that reboots will have to wait for the end of its current registration before it can reregister. Once we detect the error, the real trouble is to define the backup strategy. What does the node do then? Pascal _______________________________________________ 6lowpan mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lowpan
