Tero, I'm cautious in embracing a standard without understanding benefits and overhead:
Where can I download the 802.15.9 spec? All I can find is https://www.ietf.org/proceedings/84/slides/slides-84-roll-3.pdf What is the scope of 802.15.9? It is presented as a Key Management solution, yet you suggest to use 802.15.9's mechanisms for (i) IE space and (ii) fragmentation. It looks to me like we would be exploiting a tiny fraction of a much more involved standard, but have to include the full memory footprint. How much flash/RAM memory is a 802.15.9 implementation? Thomas On Fri, Sep 25, 2015 at 2:00 PM, Tero Kivinen <[email protected]> wrote: > Thomas Watteyne writes: > > We need to discuss this point urgently, and do the work to ask the > > IEEE for carve out some IE space for IETF/6TISCH if applicable. > > There is Vendor specific IE space for both header and payload IEs. > Those can be used provided IETF has OUI allocated from RAC. The > 802.15.9 uses ethertypes, so you can allocate one of ethertypes for > generic, or you can ask for an number from 802.15.9 specific range. > > I think for this the 802.15.9 would be better, as it would also > provide the fragmentation and multiplexing layer, meaning you are not > restricted to 127 byte limit. > -- > [email protected] >
_______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
