A new Request for Comments is now available in online RFC libraries.

        
        RFC 9810

        Title:      Internet X.509 Public Key Infrastructure 
                    -- Certificate Management Protocol (CMP) 
        Author:     H. Brockhaus,
                    D. von Oheimb,
                    M. Ounsworth,
                    J. Gray
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2025
        Mailbox:    [email protected],
                    [email protected],
                    [email protected],
                    [email protected]
        Pages:      116
        Obsoletes:  RFC 4210, RFC 9480
        Updates:    RFC 5912

        I-D Tag:    draft-ietf-lamps-rfc4210bis-18.txt

        URL:        https://www.rfc-editor.org/info/rfc9810

        DOI:        10.17487/RFC9810

This document describes the Internet X.509 Public Key Infrastructure
(PKI) Certificate Management Protocol (CMP).  Protocol messages are
defined for X.509v3 certificate creation and management. CMP provides
interactions between client systems and PKI components such as a
Registration Authority (RA) and a Certification Authority (CA).

This document adds support for management of certificates containing
a Key Encapsulation Mechanism (KEM) public key and uses EnvelopedData
instead of EncryptedValue. This document also includes the updates
specified in Section 2 and Appendix A.2 of RFC 9480.

This document obsoletes RFC 4210, and together with RFC 9811, it also
obsoletes RFC 9480. Appendix F of this document updates Section 9 of
RFC 5912.

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

Reply via email to