Tero Kivinen <[email protected]> wrote: > Note, that there is work ongoing in the IEEE to add algorithm agility > to the IEEE 802.15.4, i.e., make it possible to use other algorithms > than AES-CCM with 128-bit keys. To make it so that this structure would > also allow that it would be good idea to include algorithm parameter to > the Link-Layer Key structure with only one value of AES-CCM-128 > now.
Can you suggest a name for this field that will be synergize with the the
future 15.4 work?
> Also restructuring the text about the key_value to say "key length
> of the algorithm" instead of fixed 16, i.e., say that ignore this key
> if the length of the key_value does not match the length of the key
> specified by the algorithm.
Being CBOR, the key itself is self-describing in it's length, but I take your
point.
> Makeing this minimal-security draft to only allow AES-CCM-128 and not
> even allow easy extensibility for other algorithms would be bad idea
> now.
Agreed.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] [email protected] http://www.sandelman.ca/ | ruby on rails [
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
