A new Request for Comments is now available in online RFC libraries.
RFC 9883
Title: An Attribute for Statement of
Possession of a Private Key
Author: R. Housley
Status: Standards Track
Stream: IETF
Date: October 2025
Mailbox: [email protected]
Pages: 17
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-lamps-private-key-stmt-attr-09.txt
URL: https://www.rfc-editor.org/info/rfc9883
DOI: 10.17487/RFC9883
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.
This document is a product of the Limited Additional Mechanisms for PKIX and
SMIME Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
_______________________________________________
rfc-dist mailing list -- [email protected]
To unsubscribe send an email to [email protected]
http://www.rfc-editor.org
