Browse Prior Art Database

Cryptographic Message Syntax (CMS) (RFC3369)

IP.com Disclosure Number: IPCOM000009618D
Original Publication Date: 2002-Aug-01
Included in the Prior Art Database: 2002-Sep-05

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Housley: AUTHOR

Abstract

This document describes the Cryptographic Message Syntax (CMS). This syntax is used to digitally sign, digest, authenticate, or encrypt arbitrary message content.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 2% of the total text.

Network Working Group                                         R. Housley

Request for Comments: 3369                              RSA Laboratories

Obsoletes: 2630, 3211                                        August 2002

Category: Standards Track

                   Cryptographic Message Syntax (CMS)

Status of this Memo

   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.

Copyright Notice

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

Abstract

   This document describes the Cryptographic Message Syntax (CMS).  This

   syntax is used to digitally sign, digest, authenticate, or encrypt

   arbitrary message content.

Table of Contents

   1.   Introduction ................................................  3

   1.1  Changes Since RFC 2630 ......................................  3

   1.2  Terminology .................................................  4

   2.   General Overview ............................................  4

   3.   General Syntax ..............................................  5

   4.   Data Content Type ...........................................  5

   5.   Signed-data Content Type ....................................  6

   5.1  SignedData Type .............................................  7

   5.2  EncapsulatedContentInfo Type ................................  9

   5.2.1  Compatibility with PKCS #7 ................................  9

   5.3  SignerInfo Type ............................................. 11

   5.4  Message Digest Calculation Process .......................... 13

   5.5  Signature Generation Process ................................ 14

   5.6  Signature Verification Process .............................. 14

   6.   Enveloped-data Content Type ................................. 14

   6.1  EnvelopedData Type .......................................... 16

   6.2  RecipientInfo Type .......................................... 18

   6.2.1  KeyTransRecipientInfo Type ................................ 19

   6.2.2  KeyAgreeRecipientInfo Type ................................ 20

   6.2.3  KEKRecipientInfo Type ..................................... 22

Housley                     Standards Track                     [Page 1]

RFC 3369              Cryptographic Message Syntax           August 2002

   6.2.4  PasswordRecipientInfo Type ................................ 23

   6.2.5  OtherRecipientInfo Type ................................... 24

   6.3  Content-encryption Process ....................................