===== RFC2315 - Cryptographic Message Syntax =====
[[dido:public:ra:xapend:xapend.b_stds:tech:ietf:start| return to the IETF Standards ]]

<table>
<caption>Cryptographic Message Syntax (PKCS)</caption>
| Title                      | Cryptographic Message Syntax |
| Acronym                    | PKCS |
| Version                    | 1981 |
| Document Number            | RFC2315 |
| Release Date               | March 1998  |
| Reference                  | [[https://tools.ietf.org/html/rfc2315]] |
</table>

  : **Note**: The following is an excerpt from the official IETF RFC. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference.

==== Overview ====

  : //This document describes a general [[dido:public:ra:xapend:xapend.a_glossary:s:syntax|syntax]] for data that may have
    [[dido:public:ra:xapend:xapend.a_glossary:c:cryptography|cryptography]] applied to it, such as [[dido:public:ra:xapend:xapend.a_glossary:d:digital_signature|digital signatures]] and digital
    envelopes. The syntax admits recursion, so that, for example, one
    envelope can be nested inside another, or one party can sign some
    previously enveloped digital data.  It also allows arbitrary
    attributes, such as signing time, to be authenticated along with the
    content of a message, and provides for other attributes such as
    countersignatures to be associated with a signature. A degenerate
    case of the syntax provides a means for disseminating certificates
    and certificate-revocation lists.//


/**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
/* To add a discussion page to this page, comment out the line that says 
  ~~DISCUSSION:off~~
*/
~~DISCUSSION:on|Outstanding Issues~~
~~DISCUSSION:off~~