Algorithms for Cryptographic Message Syntax (CMS) Protection of Symmetric Key Package Content Types
draft-turner-cms-symmetrickeypackage-algs-00
Yes
No Objection
Recuse
Note: This ballot was opened for revision 00 and is now closed.
Lars Eggert No Objection
(Tim Polk; former steering group member) Yes
(Adrian Farrel; former steering group member) No Objection
Section 3 Regardless of the key management technique choice, implementations MUST support AES-128 Key Wrap with Padding [RFC5649] as the content encryption algorithm. Implementations SHOULD support AES-256 Key Wrap with Padding [RFC5649] as the content encryption algorithm. Is it sufficiently clear from context that this "MUST" applies only to the case on an implementation that supports EnvelopedData?
(Alexey Melnikov; former steering group member) No Objection
(Dan Romascanu; former steering group member) No Objection
(Gonzalo Camarillo; former steering group member) No Objection
(Jari Arkko; former steering group member) No Objection
(Ralph Droms; former steering group member) No Objection
(Robert Sparks; former steering group member) No Objection
(Ron Bonica; former steering group member) No Objection
(Russ Housley; former steering group member) (was Discuss) No Objection
Global changes: s/key encryption key/key-encryption key/ s/key encryption algorithm/key-encryption algorithm/ s/content encryption key/content-encryption key/ s/content encryption algorithm/content-encryption algorithm/
(Stewart Bryant; former steering group member) No Objection
(Sean Turner; former steering group member) Recuse