Clarifying RPKI use of CMS SignerInfo"
draft-michaelson-signerinfo-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | George G. Michaelson , Geoff Huston | ||
| Last updated | 2014-08-11 (Latest revision 2014-02-07) | ||
| 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
RFC6485 section 2 mandated a single CMS OID sha256withRSAEncryption from RFC4055 for use in the CMS SignerInfo field. This draft updates RFC6485 and extends it to permit the correct CMS use which includes an option of rsaEncryption for the SignerInfo field.
Authors
George G. Michaelson
Geoff Huston
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)