Algorithms for Cryptographic Message Syntax (CMS) Protection of Symmetric Key Package Content Types
Note: This ballot was opened for revision 00 and is now closed.
(Tim Polk) Yes
(Jari Arkko) No Objection
(Ron Bonica) No Objection
(Stewart Bryant) No Objection
(Gonzalo Camarillo) No Objection
(Ralph Droms) No Objection
(Lars Eggert) No Objection
(Adrian Farrel) 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?
(Russ Housley) (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/