[rfc-dist] RFC 6032 on Cryptographic Message Syntax (CMS) Encrypted Key Package Content Type

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Mon Dec 13 12:31:56 PST 2010


A new Request for Comments is now available in online RFC libraries.

        
        RFC 6032

        Title:      Cryptographic Message Syntax (CMS) Encrypted 
                    Key Package Content Type 
        Author:     S. Turner, R. Housley
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2010
        Mailbox:    turners at ieca.com, 
                    housley at vigilsec.com
        Pages:      11
        Characters: 22725
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-turner-encryptedkeypackagecontenttype-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6032.txt

This document defines the Cryptographic Message Syntax (CMS)
encrypted key package content type, which can be used to encrypt a
content that includes a key package, such as a symmetric key package
or an asymmetric key package.  It is transport independent.  CMS can
be used to digitally sign, digest, authenticate, or further encrypt
this content type.  It is designed to be used with the CMS Content
Constraints (CCC) extension, which does not constrain the
EncryptedData, EnvelopedData, and AuthEnvelopedData.  [STANDARDS-TRACK]

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC




More information about the rfc-dist mailing list