An Attribute for Statement of Possession of a Private Key
RFC 9883
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['PKCS#10']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "R. Housley": changed name from "Russ Housley" to "R. Housley", changed affiliation from "Vigil Security, LLC" to "Vigil Security", cleared country (was "US") |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2025-12-28
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
|
2025-12-22
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2025-10-12
|
(System) | Received changes through RFC Editor sync (created document RFC 9883, created became rfc relationship between draft-ietf-lamps-private-key-stmt-attr and RFC 9883, set abstract to 'This … Received changes through RFC Editor sync (created document RFC 9883, created became rfc relationship between draft-ietf-lamps-private-key-stmt-attr and RFC 9883, set abstract to 'This document specifies an attribute for a statement of possession of a private key by a certificate subject. As part of X.509 certificate enrollment, a Certification Authority (CA) typically demands proof that the subject possesses the private key that corresponds to the to-be-certified public key. In some cases, a CA might accept a signed statement from the certificate subject. For example, when a certificate subject needs separate certificates for signature and key establishment, a statement that can be validated with the previously issued signature certificate for the same subject might be adequate for subsequent issuance of the key establishment certificate.', set pages to 17, set standardization level to Proposed Standard, added RFC published event at 2025-10-12) |
|
2025-10-12
|
(System) | RFC published |