Michael Richardson writes: > So, you don't need to use the EUI-64, but you do need to have a > mapping of short-address to EUI-64.
Yes. Address formats in the frame can use any device addressing modes, i.e. none, short or extended, and this is what is actually used when the frame is sent. The incoming frame security processing will fetch the DeviceDescriptor for the remote device using the addressing fields in the frame. The DeviceDescriptor contains extended address of the device, and also the short address if it is known. For non-TSCH cases it also includes the FrameCounter, but for TSCH case we do not use that for anything, as we use ASN as frame counter. > How does such a mapping become known? >From the same way you got the short address. When you want to talk to somebody, you need to somehow know how to address him. Normally you go to some service which returns you that information. I.e. you talk to some service asking who is the temperature sensor in this network, and you get reply back saying it is device with short address of 0x1234 and with extended address of 12-34-56-78-87-65-43-21. Or you could separate service, where you can send the short address, and get extended address back. As you are normally talking with same neighbours all the time, this means you "waste" these 8-bytes on the air only once, while you are doing resource lookup. I do not know what resource lookup method 6tisch is going to use, do we have something defined for that already? > How can any of this work in the field today? I have no idea, as none of this is part of 802.15.4... -- [email protected] _______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
