This document specifies a content type for encrypted key packages. It
is a choice of: EnvelopedData, EncryptedData, or AuthEnvelopedData. The
rationale for it's use is based on the CMS content constraints
documented in draft-housley-cms-content-constraints-extn. This document
also defines an attribute that provides a hint as to which key should be
used to decrypt the content when the EncryptedData choice is used.
The specification includes two normative references to I-Ds that will be
published as Informational RFCs (they are currently in the RFC Editor
draft-ietf-pkix-new-asn1; draft-ietf-smime-new-asn1. Both have been
added to the downref registry.
Working Group Summary
This document is not the product of an IETF Working Group.
The document is short, but provides enough background to explain why why
the content type is needed.
Carl Wallace is the document Shepherd. Tim Polk is the
responsible Security Area AD.
RFC Editor Note
In section 5, please make the following substitution
All OIDs are registered in an arc delegated by IANA to the SMIME
All OIDs are registered in an arc delegated by RSADSI to the SMIME