Hi WG, Thomas Werner and I wrote draft-richardson-anima-jose-voucher last year. The draft-ietf-anima-brski-async-enroll-02 document wants to do everything with JOSE signed JSON rather than CMS signed JSON. (I continue to argue that COSE-signed-CBOR will be better if doing things over native BTLE)
The document does not do any YANG work! What do we need to do get the document adopted? It has no dependancies, but async-enroll depends upon it. The hardest part was decided between JWS Compact Serialization and JWS JSON Serialization. We use Compact, which comes as three base64URL encoded pieces. Fries, Steffen <[email protected]> wrote: > o Defined call flow and objects for interactions in use case2. > Object format based on draft for JOSE signed voucher artifacts and > aligned the remaining objects with this approach in Section 5.2.3 -- 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
