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

        RFC 10002

        Title:      Certificate Management over CMS (CMC)
        Author:     J. Mandel, Ed.,
                    S. Turner, Ed.
        Status:     Proposed Standard
        Stream:     IETF
        Date:       July 2026
        Mailbox:    [email protected],
                    [email protected]
        Pages:      91
        Obsoletes:  RFC 5272, RFC 6402


        I-D Tag:    draft-ietf-lamps-rfc5272bis-11

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

        DOI:        10.17487/RFC10002

This document defines the base syntax for CMC, a Certificate Management 
protocol using the Cryptographic Message Syntax (CMS). This protocol addresses 
two immediate needs within the Internet Public Key Infrastructure (PKI) 
community:

   1.  The need for an interface to public key certification products
       and services based on CMS and PKCS #10 (Public Key Cryptography
       Standard), and

   2.  The need for a PKI enrollment protocol for encryption-only keys
       due to algorithm or hardware design.


CMC also requires the use of the transport document (RFC 10003) and the 
requirements usage document (RFC 10004) along with this document for a full 
definition.

This document obsoletes RFCs 5272 and 6402.

This document is a product of the Limited Additional Mechanisms for PKIX and 
SMIME Working Group of the IETF.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and
suggestions for improvements. 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/series/rfc-download/

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

_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to