Commentary on the Design of the Authenticated-Enveloped-Data Content Type
draft-schaad-smime-aed-rant-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Jim Schaad | ||
| Last updated | 2015-03-25 (Latest revision 2011-04-06) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
html
xml
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-schaad-smime-aed-rant-02.txt
https://www.ietf.org/archive/id/draft-schaad-smime-aed-rant-02.txt
Abstract
The Authenticated-Enveloped-Data Content Type allows for the use of Authenticated-Enveloped modes with block cipher algorithms. At the time of the original design there was discussion about the relative location of the authenticated attributes and the encrypted content in the ASN.1 structure. With the benefits of implementation experience I revisit the discussion made at the time and re-evaluate the decision made.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)