Would BRSKI-AE want to do CoAPS instead of HTTPS? Or in addition to HTTPS?
I propose to leave base HTTPS BRSKI as-is, and then do whatever renames you like by merging BRSKI-AE into constrained-voucher, and all all of the asynchronous efforts over CoAP. This has the interesting possibilities of supporting BRSKI-AE CoAP over BTLE, NFC, and SMS. (not necessarily with an IP layer) -- Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
