Digital Signatures on RFC and Internet-Draft Documents
draft-housley-rfc-and-id-signatures-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Russ Housley | ||
| Last updated | 2016-12-04 (Latest revision 2016-06-02) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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 is available in these formats:
Abstract
This document specifies the conventions for digital signatures on RFCs and Internet-Draft documents. For Internet-Drafts, the Cryptographic Message Syntax (CMS) is used to create a detached signature, which is stored in a separate companion file so that no existing utilities are impacted by the addition of the digital signature. For RFCs, an embedded digital signature is included in Portable Document Format (PDF) files types in addition to the detached signature in a separate companion file. This document (once approved) obsoletes RFC 5485.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)