Mališa Vučinić <[email protected]> wrote: > I've just adopted this "TLS" approach: key_usage and algorithm are merged, > and a new column "Algorithm" was added in the registry to explicitly state > the link-layer techno / algorithm in use. I believe this is quite enough > for our purposes and simplifies the CBOR decoder that needs to be > implemented. We are back to integers now, and I allow both unsigned and > negative in order to have larger 1-byte ranges in the registry.
> The changes are at:
>
https://bitbucket.org/6tisch/draft-ietf-6tisch-minimal-security/commits/15133e113e2efaa3c42d5f844f12c28100e5f17b
Good.
Tero, I am thinking that when 802.15.4 puts out the AES256 support, that
there will have to be an IETF document that adds things here. Are there
other things (in other WGs) that will also need updating? It would be good
to start an internet-draft to collect things.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] [email protected] http://www.sandelman.ca/ | ruby on rails [
signature.asc
Description: PGP signature
_______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
