<no hat, but wanting to see more movement on this> On 23 Mar 2016, at 14:01, Tero Kivinen wrote:
> Valery Smyslov writes: >>> It matters when you use things like 802.15.9. IEEE 802.15.9 provides a >>> method to transport IKEv2 messages over IEE Std 802.15.4. In typical >>> PHY of the 802.15.4 the max frame size is 127 bytes, which leaves >>> about 96 bytes for the 802.15.9 for payload. Normal 300 byte IKEv2 >>> packet will require about 3-4 fragments sent in 3-4 frames. Each of >>> those frames will be acknowledged, and there might be timing >>> constrains how often they can be sent (for example in TSCH network >>> this might be once per second at max, when using 10ms slot time, and >>> slotframe size of 100). >>> >>> If we raise the MAC size from 8 to 16, that will cause 8% probability >>> that we need one more frame to send that last part... >> >> That's a good reason. Shouldn't this (or similar) explanation be >> added to the draft? > > Perhaps. How much of current information we want to put in the > document. The things are changing all the time, and it might be true > now for IoT, but might not be true in few years. Isn't enough to just > say that currently this algorithm might be used for IoT. That seems to be the right way to go. --Paul Hoffman _______________________________________________ IPsec mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipsec
