header
  pvno                        REQUIRED
    -- MUST be 3 to indicate CMP v3 in all cases where EnvelopedData
    --   is supported and expected to be used in the current
    --   PKI management operation
    -- MUST be 3 to indicate CMP v3 in certConf messages when using
    --   the hashAlg field
    -- MUST be 2 to indicate CMP v2 in all other cases
    -- For details on version negotiation, see [RFC9480]
  sender                      REQUIRED
    -- Contains a name representing the originator, which also
    --   protects the message
    -- For signature-based protection, MUST be the subject field of
    --   the CMP protection certificate
    -- For MAC-based protection, MUST contain a name the PKI
    --   management entity can use to identify the shared secret
    --   information. This name MUST be placed in the commonName
    --   field of the directoryName choice.
    -- In a multihop scenario, the receiving entity cannot rely
    --   on the correctness of the sender field.
  recipient                   REQUIRED
    -- SHOULD be the name of the intended recipient; otherwise, the
    --   NULL-DN MUST be used
    -- In the first message of a PKI management operation, SHOULD be
    --   the subject DN of the CA the PKI management operation is
    --   requested from
    -- In all other messages, SHOULD contain the value of the sender
    --   field of the previous message in the same PKI management
    --   operation
    -- The recipient field shall be handled gracefully by the
    --   receiving entity, because in a multihop scenario, its
    --   correctness cannot be guaranteed.
  messageTime                 OPTIONAL
    -- MUST be present if the confirmWaitTime field is present
    -- MUST be the time at which the message was produced, if present
    -- MAY be set by a PKI management entity to provide the current
    --   time
    -- MAY be used by the end entity for time synchronization if the
    --   response was received within a short time frame
  protectionAlg               REQUIRED
    -- MUST be an algorithm identifier indicating the algorithm
    --   used for calculating the protection bits
    -- If it is a signature algorithm, its type MUST be
    --   MSG_SIG_ALG as specified in Section 3 of [RFC9481] and
    --   MUST be consistent with the subjectPublicKeyInfo field of
    --   the CMP protection certificate
    -- If it is a MAC algorithm, its type MUST be MSG_MAC_ALG, as
    --   specified in [RFC9481], Section 6.1
  senderKID                   RECOMMENDED
    -- For signature-based protection, MUST be used and contain the
    --   value of the SubjectKeyIdentifier if present in the CMP
    --   protection certificate
    -- For MAC-based protection, MUST be used and contain the same
    --   name as in the commonName field of the sender field
  transactionID               REQUIRED
    -- In the first message of a PKI management operation, MUST be
    --   128 bits of random data to minimize the probability of
    --   having the transactionID already in use at the server
    -- In all other messages, MUST be the value from the previous
    --   message in the same PKI management operation
  senderNonce                 REQUIRED
    -- MUST be cryptographically secure and fresh 128 random bits
  recipNonce                  RECOMMENDED
    -- If this is the first message of a transaction, MUST be absent
    -- If this is a delayed response message, MUST be present and
    --   contain the value of the senderNonce of the respective
    --   request message in the same transaction
    -- In all other messages, MUST be present and contain the value
    --   of the senderNonce of the previous message in the same
    --   transaction
  generalInfo                 OPTIONAL
    implicitConfirm           OPTIONAL
    -- RECOMMENDED in ir/cr/kur/p10cr messages,
    -- OPTIONAL in ip/cp/kup response messages, and
    -- PROHIBITED in other types of messages
    -- Added to request messages to request omission of the certConf
    --   message
    -- Added to response messages to grant omission of the certConf
    --   message
    -- See [RFC4210], Section 5.1.1.1.
      ImplicitConfirmValue   REQUIRED
    -- ImplicitConfirmValue MUST be NULL
    confirmWaitTime           OPTIONAL
    -- RECOMMENDED in ip/cp/kup messages if implicitConfirm is
    --   not included
    -- PROHIBITED if implicitConfirm is included
    -- See [RFC4210], Section 5.1.1.2.
      ConfirmWaitTimeValue    REQUIRED
    -- ConfirmWaitTimeValue MUST be a GeneralizedTime value
    --   specifying the point in time up to which the PKI management
    --   entity will wait for the certConf message.  The accepted
    --   length of the waiting period will vary by use case.
    certProfile               OPTIONAL
    -- MAY be present in ir/cr/kur/p10cr and in genm messages of type
    --   id-it-certReqTemplate
    -- MUST be omitted in all other messages
    -- See [RFC9480].
      CertProfileValue        REQUIRED
    -- MUST contain a sequence of one UTF8String element
    -- MUST contain the name of a certificate profile

protection
    -- If present, the same kind of protection MUST be used for all
    --   messages of that PKI management operation.
    -- MUST be present, except if protection is not possible for
    --   error messages as described in Section 3.6.4
    -- For signature-based protection, MUST contain the signature
    --   calculated using the CMP protection key of the entity
    --   protecting the message
    -- For MAC-based protection, MUST contain a MAC calculated using
    --   the shared secret information
    -- The protection algorithm used MUST be given in the
    --   protectionAlg field.

extraCerts
    -- MUST be present for signature-based protection and contain the
    --   CMP protection certificate together with its chain for the
    --   first request and response message of a PKI management
    --   operation.  MAY be omitted in certConf, PKIConf, pollReq,
    --   and pollRep messages.  The first certificate in this field
    --   MUST be the CMP protection certificate followed by its
    --   chain, where each element should directly certify the one
    --   immediately preceding it.
    -- MUST be present in ip, cp, and kup messages and contain the
    --   chain of a newly issued certificate.
    -- Self-signed certificates should be omitted from extraCerts and
    --   MUST NOT be trusted based on their inclusion in any case

Error Message -- error

Field                         Value

header
    -- As described in Section 3.1

body
    -- The message indicating the error that occurred
  error                       REQUIRED
    pKIStatusInfo             REQUIRED
      status                  REQUIRED
    -- MUST have the value "rejection"
      statusString            OPTIONAL
    -- This field should contain any human-readable text for
    --   debugging, for logging, or to display in a GUI
      failInfo                OPTIONAL
    -- MAY be present and contain the relevant PKIFailureInfo bits

protection                    RECOMMENDED
    -- As described in Section 3.2

extraCerts                    RECOMMENDED
    -- As described in Section 3.3

                         start
                           |
                           | send ir/cr/kur/p10cr/rr/genm
                           v
                 waiting for response
                           v
+--------------------------+--------------------------+
|                          |                          |
| receives ip/cp/kup with  | received ip/cp/kup/error | received
| status "accepted" or     | with status "waiting"    | rp/genp or
| "grantedWithMods"        |                          | ip/cp/kup/
|                          v                          | error
|             +-------> polling                       | with status
|             |            |                          | "rejection"
|             | received   | send                     |
|             | pollRep    | pollReq                  |
|             |            v                          |
|             |   waiting for response                |
|             |            v                          |
|             +------------+--------+                 |
|                          |        |                 |
|       received ip/cp/kup |        | received        |
|   with status "accepted" |        | rp/genp or      |
|     or "grantedWithMods" |        | ip/cp/kup/error |
|                          |        | with status     |
+---------->+<-------------+        | "rejection"     |
            v                       |                 |
+-----------+-----+                 |                 |
|                 |                 |                 |
| implicitConfirm | implicitConfirm |                 |
| granted         | not granted     |                 |
|                 |                 |                 |
|                 | send certConf   |                 |
|                 v                 |                 |
|        waiting for pkiConf*)      |                 |
|                 |                 |                 |
|                 | received        |                 |
|                 v pkiConf         v                 |
+---------------->+------->+<-------+<----------------+
                           |
                           v
                          end
			  

Step# EE                                  PKI management entity
  1   format ir
  2                      ->   ir      ->
  3                                        handle or
                                             forward ir
  4                                        format or receive ip
  5                                        possibly grant
                                             implicitConfirm
  6                      <-   ip      <-
  7   handle ip

-----------------  if implicitConfirm not granted  -----------------

  8   format certConf
  9                      ->   certConf ->
 10                                        handle or
                                             forward certConf
 11                                        format or receive pkiConf
 12                      <-   pkiConf  <-
 13   handle pkiConf
                    

Initialization Request -- ir

Field                         Value

header
    -- As described in Section 3.1

body
    -- The request of the EE for a new certificate
  ir                          REQUIRED
    -- MUST contain a sequence of one CertReqMsg
    -- If more certificates are required, further PKI management
    --   operations needs to be initiated
    certReq                   REQUIRED
      certReqId               REQUIRED
    -- MUST be 0
      certTemplate            REQUIRED
        version               OPTIONAL
    -- MUST be 2 if supplied
        subject               REQUIRED
    -- The EE's identity MUST be carried in the subject field
    --   and/or the subjectAltName extension.
    -- If subject name is present only in the subjectAltName
    --   extension, then the subject field MUST be NULL-DN
        publicKey             OPTIONAL
    -- MUST be present if local key generation is used
    -- MAY be absent if central key generation is requested
          algorithm           OPTIONAL
    -- MUST be present if local key generation is used and MUST
    --   include the subject public key algorithm identifier
    -- MAY be present if central key generation is requested and,
    --   if present, informs the KGA of algorithm and parameter
    --   preferences regarding the to-be-generated key pair
          subjectPublicKey    REQUIRED
    -- MUST contain the public key to be certified in case of local
    --   key generation
    -- MUST be a zero-length BIT STRING if central key generation
    --   is requested
        extensions            OPTIONAL
    -- MAY include end-entity-specific X.509 extensions of the
    --   requested certificate, like subject alternative name, key
    --   usage, and extended key usage
    -- The subjectAltName extension MUST be present if the EE subject
    --   name includes a subject alternative name.
    popo                      OPTIONAL
    -- MUST be present if local key generation is used
    -- MUST be absent if central key generation is requested
      signature               OPTIONAL
    -- MUST be used by an EE if the key can be used for signing, and
    --   if used, it MUST have the type POPOSigningKey
        poposkInput           PROHIBITED
    -- MUST NOT be used; it is not needed because subject and
    --   publicKey are both present in the certTemplate
        algorithmIdentifier   REQUIRED
    -- The signature algorithm MUST be consistent with the publicKey
    --   algorithm field of the certTemplate
        signature             REQUIRED
    -- MUST contain the signature value computed over the DER-encoded
    --   certReq
      raVerified              OPTIONAL
    -- MAY be used by an RA after verifying the proof-of-possession
    --   provided by the EE

protection                    REQUIRED
    -- As described in Section 3.2

extraCerts                    REQUIRED
    -- As described in Section 3.3


Initialization Response -- ip

Field                         Value

header
    -- As described in Section 3.1

body
    -- The response of the CA to the request as appropriate
  ip                          REQUIRED
    caPubs                    OPTIONAL
    -- MAY be used if the certifiedKeyPair field is present
    -- If used, it MUST contain only a trust anchor, e.g., root
    --   certificate, of the certificate contained in certOrEncCert
    response                  REQUIRED
    -- MUST contain a sequence of one CertResponse
      certReqId              REQUIRED
    -- MUST be 0
      status                  REQUIRED
    -- PKIStatusInfo structure MUST be present
        status                REQUIRED
    -- positive values allowed: "accepted", "grantedWithMods"
    -- negative values allowed: "rejection"
    -- "waiting" only allowed with a polling use case as described
    --   in Section 4.4
        statusString          OPTIONAL
    -- MAY be any human-readable text for debugging, for logging, or
    --   to display in a GUI
        failInfo              OPTIONAL
    -- MAY be present if status is "rejection"
    -- MUST be absent if status is "accepted" or "grantedWithMods"
      certifiedKeyPair        OPTIONAL
    -- MUST be present if status is "accepted" or "grantedWithMods"
    -- MUST be absent if status is "rejection"
        certOrEncCert         REQUIRED
    -- MUST be present if status is "accepted" or "grantedWithMods"
          certificate         REQUIRED
    -- MUST be present when certifiedKeyPair is present
    -- MUST contain the newly enrolled X.509 certificate
        privateKey            OPTIONAL
    -- MUST be absent in case of local key generation or "rejection"
    -- MUST contain the encrypted private key in an EnvelopedData
    --   structure as specified in Section 4.1.6 in case the
    --   private key was generated centrally

protection                    REQUIRED
    -- As described in Section 3.2

extraCerts                    REQUIRED
    -- As described in Section 3.3
    -- MUST contain the chain of the certificate present in
    --   certOrEncCert
    -- Duplicate certificates MAY be omitted


Certificate Confirmation -- certConf

Field                         Value

header
    -- As described in Section 3.1

body
    -- The message of the EE sends a confirmation to the PKI
    --   management entity to accept or reject the issued
    --   certificates
  certConf                    REQUIRED
    -- MUST contain a sequence of one CertStatus
    CertStatus                REQUIRED
      certHash                REQUIRED
    -- The hash algorithm to use MUST be the hash algorithm indicated
    --   in the below hashAlg field.  If the hashAlg field is not
    --   set, it MUST be the hash algorithm defined by the algorithm
    --   identifier of the certificate signature or the dedicated
    --   hash algorithm defined in [RFC9481] for the used certificate
    --   signature algorithm.
      certReqId               REQUIRED
    -- MUST be 0
      statusInfo              OPTIONAL
    -- PKIStatusInfo structure should be present
    -- Omission indicates acceptance of the indicated certificate
        status                REQUIRED
    -- positive values allowed: "accepted"
    -- negative values allowed: "rejection"
        statusString          OPTIONAL
    -- MAY be any human-readable text for debugging, for logging, or
    --   to display in a GUI
        failInfo              OPTIONAL
    -- MAY be present if status is "rejection"
    -- MUST be absent if status is "accepted"
      hashAlg                 OPTIONAL
    -- The hash algorithm to use for calculating the above certHash
    -- If used, the pvno field in the header MUST be cmp2021 (3).
    --   For backward compatibility, use of this field is
    --   NOT RECOMMENDED if the hash algorithm to use can be
    --   identified by other means; see above.

protection                    REQUIRED
    -- As described in Section 3.2
    -- MUST use the same credentials as in the first request message
    --   of this PKI management operation

extraCerts                    RECOMMENDED
    -- As described in Section 3.3
    -- MAY be omitted if the message size is critical and the PKI
    --   management entity caches the CMP protection certificate from
    --   the first request message of this PKI management operation


PKI Confirmation -- pkiConf

Field                         Value

header
    -- As described in Section 3.1

body
  pkiconf                     REQUIRED
    -- The content of this field MUST be NULL

protection                    REQUIRED
    -- As described in Section 3.2
    -- MUST use the same credentials as in the first response
    --   message of this PKI management operation

extraCerts                    RECOMMENDED
    -- As described in Section 3.3
    -- MAY be omitted if the message size is critical and the EE has
    --   cached the CMP protection certificate from the first
    --   response message of this PKI management operation

    controls
      type                    RECOMMENDED
    -- MUST be the value id-regCtrl-oldCertID, if present
      value
        issuer                REQUIRED
        serialNumber          REQUIRED
    -- MUST contain the issuer and serialNumber of the certificate
    --   to be updated

Certification Request -- p10cr

Field                         Value

header
    -- As described in Section 3.1

body
    -- The request of the EE for a new certificate using a PKCS #10
    --   certificate request
  p10cr                       REQUIRED
    certificationRequestInfo  REQUIRED
      version                 REQUIRED
    -- MUST be 0 to indicate PKCS #10 v1.7
      subject                 REQUIRED
    -- The EE subject name MUST be carried in the subject field
    --   and/or the subjectAltName extension.
    -- If subject name is present only in the subjectAltName
    --   extension, then the subject field MUST be NULL-DN
      subjectPKInfo           REQUIRED
        algorithm             REQUIRED
    -- MUST include the subject public key algorithm identifier
        subjectPublicKey      REQUIRED
    -- MUST include the public key to be certified
      attributes              OPTIONAL
    -- MAY include end-entity-specific X.509 extensions of the
    --   requested certificate like subject alternative name,
    --   key usage, and extended key usage
    -- The subjectAltName extension MUST be present if the EE
    --   subject name includes a subject alternative name.
    signatureAlgorithm        REQUIRED
    -- The signature algorithm MUST be consistent with the
    --   subjectPKInfo field.
    signature                 REQUIRED
    -- MUST contain the self-signature for proof-of-possession

protection                    REQUIRED
    -- As described in Section 3.2

extraCerts                    REQUIRED
    -- As described for the underlying PKI management operation

        privateKey            REQUIRED
    -- MUST be an EnvelopedData structure, as specified in
    --   Section 6 of CMS [RFC5652]
          version             REQUIRED
    -- MUST be 2 for recipientInfo type KeyAgreeRecipientInfo and
    --   KeyTransRecipientInfo
    -- MUST be 0 for recipientInfo type PasswordRecipientInfo
          recipientInfos      REQUIRED
    -- MUST contain a sequence of one RecipientInfo, which MUST be
    --   ktri of type KeyTransRecipientInfo (see Section 4.1.6.1),
    --   kari of type KeyAgreeRecipientInfo (see Section 4.1.6.2), or
    --   pwri of type PasswordRecipientInfo (see Section 4.1.6.3)
          encryptedContentInfo
                              REQUIRED
            contentType       REQUIRED
    -- MUST be id-signedData
            contentEncryptionAlgorithm
                              REQUIRED
    -- MUST be the algorithm identifier of the algorithm used for
    --   content encryption
    -- The algorithm type MUST be PROT_SYM_ALG as specified in
    --   [RFC9481], Section 5
            encryptedContent  REQUIRED
    -- MUST be the SignedData structure, as specified in Section 5
    -- of CMS [RFC5652] and [RFC8933], in encrypted form
              version         REQUIRED
    -- MUST be 3
              digestAlgorithms
                              REQUIRED
    -- MUST contain a sequence of one AlgorithmIdentifier element
    -- MUST be the algorithm identifier of the digest algorithm
    --   used for generating the signature and match the signature
    --   algorithm specified in signatureAlgorithm; see [RFC8933]
              encapContentInfo
                              REQUIRED
    -- MUST contain the content that is to be signed
                eContentType  REQUIRED
    -- MUST be id-ct-KP-aKeyPackage as specified in [RFC5958]
                eContent      REQUIRED
    -- MUST be of type AsymmetricKeyPackage and
    -- MUST contain a sequence of one OneAsymmetricKey element
                  version     REQUIRED
    -- MUST be 1 (indicating v2)
                  privateKeyAlgorithm
                              REQUIRED
    -- The privateKeyAlgorithm field MUST contain the algorithm
    --   identifier of the asymmetric key pair algorithm
                  privateKey  REQUIRED
                  publicKey   REQUIRED
    -- MUST contain the public key corresponding to the private key
    --   for simplicity and consistency with v2 of OneAsymmetricKey
              certificates    REQUIRED
    -- MUST contain the certificate for the private key used to sign
    --   the signedData content, together with its chain
    -- The first certificate in this field MUST be the KGA
    --   certificate used for protecting this content
    -- Self-signed certificates should not be included and MUST NOT
    --   be trusted based on their inclusion in any case
                signerInfos   REQUIRED
    -- MUST contain a sequence of one SignerInfo element
                version       REQUIRED
    -- MUST be 3
                sid           REQUIRED
                  subjectKeyIdentifier
                              REQUIRED
    -- MUST be the subjectKeyIdentifier of the KGA certificate
                digestAlgorithm
                              REQUIRED
    -- MUST be the same as in the digestAlgorithms field of
    --   encryptedContent
                signedAttrs   REQUIRED
    -- MUST contain an id-contentType attribute containing the value
    --   id-ct-KP-aKeyPackage
    -- MUST contain an id-messageDigest attribute containing the
    --   message digest of eContent
    -- MAY contain an id-signingTime attribute containing the time
    --   of a signature.  It SHOULD be omitted if the transactionTime
    --   field is not present in the PKIHeader.
    -- For details on the signed attributes, see Sections 5.3 and
    --   11 of CMS [RFC5652] and [RFC8933]
                signatureAlgorithm
                              REQUIRED
    -- MUST be the algorithm identifier of the signature algorithm
    --   used for calculation of the signature bits
    -- The signature algorithm type MUST be MSG_SIG_ALG, as
    --   specified in [RFC9481], Section 3, and MUST be consistent
    --   with the subjectPublicKeyInfo field of the KGA certificate
                signature     REQUIRED
    -- MUST be the digital signature of the encapContentInfo

            ktri              REQUIRED
    -- MUST be KeyTransRecipientInfo as specified in Section 6.2.1
    --   of CMS [RFC5652]
              version         REQUIRED
    -- MUST be 2
              rid             REQUIRED
    -- MUST contain the subjectKeyIdentifier of the CMP protection
    --   certificate, if available, in the rKeyId choice, and the
    --   subjectKeyIdentifier MUST equal the senderKID in the
    --   PKIHeader.
    -- If the CMP protection certificate does not contain a
    --   subjectKeyIdentifier, the issuerAndSerialNumber choice MUST
    --   be used.
              keyEncryptionAlgorithm
                              REQUIRED
    -- MUST be the algorithm identifier of the key transport
    --   algorithm.  The algorithm type MUST be KM_KT_ALG as
    --   specified in [RFC9481], Section 4.2
              encryptedKey    REQUIRED
    -- MUST be the encrypted content-encryption key

            kari              REQUIRED
    -- MUST be KeyAgreeRecipientInfo as specified in Section
    --   6.2.2 of CMS [RFC5652]
              version         REQUIRED
    -- MUST be 3
              originator      REQUIRED
    -- MUST contain the subjectKeyIdentifier of the CMP protection
    --   certificate, if available, in the subjectKeyIdentifier
    --   choice, and the subjectKeyIdentifier MUST equal the
    --   senderKID in the PKIHeader.
    -- If the CMP protection certificate does not contain a
    --   subjectKeyIdentifier, the issuerAndSerialNumber choice MUST
    --   be used.
              ukm             RECOMMENDED
    -- MUST be used when 1-Pass Elliptic Curve Menezes-Qu-Vanstone
    --   (ECMQV) is used; see [RFC5753]
    -- SHOULD be present to ensure uniqueness of the key
    --   encryption key
              keyEncryptionAlgorithm
                              REQUIRED
    -- MUST be the algorithm identifier of the key agreement
    --   algorithm
    -- The algorithm type MUST be KM_KA_ALG as specified in
    --   [RFC9481], Section 4.1
    -- The parameters field of the key agreement algorithm MUST
    --   contain the key wrap algorithm.  The algorithm type
    --   MUST be KM_KW_ALG as specified in [RFC9481], Section 4.3
              recipientEncryptedKeys
                              REQUIRED
    -- MUST contain a sequence of one RecipientEncryptedKey
                rid           REQUIRED
    -- MUST contain the subjectKeyIdentifier of the CMP protection
    --   certificate, if available, in the rKeyId choice, and the
    --   subjectKeyIdentifier MUST equal the senderKID in the
    --   PKIHeader.
    -- If the CMP protection certificate does not contain a
    --   subjectKeyIdentifier, the issuerAndSerialNumber choice MUST
    --   be used
                  encryptedKey
                              REQUIRED
    -- MUST be the encrypted content-encryption key

            pwri              REQUIRED
    -- MUST be PasswordRecipientInfo as specified in
    --   Section 6.2.4 of CMS [RFC5652]
              version         REQUIRED
    -- MUST be 0
              keyDerivationAlgorithm
                              REQUIRED
    -- MUST be the algorithm identifier of the key derivation
    --   algorithm
    -- The algorithm type MUST be KM_KD_ALG as specified in
    --   [RFC9481], Section 4.4
              keyEncryptionAlgorithm
                              REQUIRED
    -- MUST be the algorithm identifier of the key wrap algorithm
    -- The algorithm type MUST be KM_KW_ALG as specified in
    --   [RFC9481], Section 4.3
              encryptedKey    REQUIRED
    -- MUST be the encrypted content-encryption key

Step# EE                                  PKI management entity
 1   format rr
 2                      ->   rr      ->
 3                                        handle or forward rr
 4                                        format or receive rp
 5                      <-   rp      <-
 6   handle rp
                

Revocation Request -- rr

Field                         Value

header
    -- As described in Section 3.1

body
    -- The request of the EE to revoke its certificate
  rr                          REQUIRED
    -- MUST contain a sequence of one element of type RevDetails
    -- If more revocations are desired, further PKI management
    --   operations need to be initiated
    certDetails               REQUIRED
    -- MUST be present and is of type CertTemplate
      serialNumber            REQUIRED
    -- MUST contain the certificate serialNumber attribute of the
    --   certificate to be revoked
      issuer                  REQUIRED
    -- MUST contain the issuer attribute of the certificate to be
    --   revoked
    crlEntryDetails           REQUIRED
    -- MUST contain a sequence of one reasonCode of type CRLReason
    --   (see [RFC5280], Section 5.3.1)
    -- If the reason for this revocation is not known or shall not
    --   be published, the reasonCode MUST be 0 (unspecified)
protection                    REQUIRED
    -- As described in Section 3.2 and using the private key related
    --   to the certificate to be revoked

extraCerts                    REQUIRED
    -- As described in Section 3.3


Revocation Response -- rp

Field                         Value

header
    -- As described in Section 3.1

body
    -- The response of the PKI management entity to the request as
    --   appropriate
  rp                          REQUIRED
    status                    REQUIRED
    -- MUST contain a sequence of one element of type PKIStatusInfo
      status                  REQUIRED
    -- positive value allowed: "accepted"
    -- negative value allowed: "rejection"
      statusString            OPTIONAL
    -- MAY be any human-readable text for debugging, for logging, or
    --   to display in a GUI
      failInfo                OPTIONAL
    -- MAY be present if the status is "rejection"
    -- MUST be absent if the status is "accepted"

protection                    REQUIRED
    -- As described in Section 3.2

extraCerts                    REQUIRED
    -- As described in Section 3.3

Step# EE                                   PKI management entity
 1   format genm
 2                      ->   genm    ->
 3                                        handle or forward genm
 4                                        format or receive genp
 5                      <-   genp    <-
 6   handle genp
           

General Message -- genm

Field                         Value

header
    -- As described in Section 3.1

body
    -- A request by the EE for information
  genm                        REQUIRED
    -- MUST contain a sequence of one element of type
    --   InfoTypeAndValue
    infoType                  REQUIRED
    -- MUST be the OID identifying one of the specific PKI
    --   management operations described below
    infoValue                 OPTIONAL
    -- MUST be as specified for the specific PKI management operation

protection                    REQUIRED
    -- As described in Section 3.2

extraCerts                    REQUIRED
    -- As described in Section 3.3


General Response -- genp

Field                         Value

header
    -- As described in Section 3.1

body
    -- The response of the PKI management entity providing
    --   information
  genp                        REQUIRED
    -- MUST contain a sequence of one element of type
    --   InfoTypeAndValue
    infoType                  REQUIRED
    -- MUST be the OID identifying the specific PKI management
    --   operation described below
    infoValue                 OPTIONAL
    -- MUST be as specified for the specific PKI management operation

protection                    REQUIRED
    -- As described in Section 3.2

extraCerts                    REQUIRED
    -- As described in Section 3.3

      infoValue               OPTIONAL
    -- MUST be absent if no CA certificate is available
    -- MUST be present if CA certificates are available
    --   if present, MUST be a sequence of CMPCertificate

      infoValue               RECOMMENDED
    -- MUST contain the root CA certificate to be updated if needed
    --   for unique identification

      infoValue               OPTIONAL
    -- MUST be absent if no update of the root CA certificate is
    --   available
    -- MUST be present if an update of the root CA certificate
    --   is available and MUST be of type RootCaKeyUpdateContent
        newWithNew            REQUIRED
    -- MUST be present if infoValue is present
    -- MUST contain the new root CA certificate
        newWithOld            REQUIRED
    -- MUST be present if infoValue is present
    -- MUST contain a certificate containing the new public
    --   root CA key signed with the old private root CA key
        oldWithNew            OPTIONAL
    -- MAY be present if infoValue is present
    -- MUST contain a certificate containing the old public
    --   root CA key signed with the new private root CA key

      InfoValue               OPTIONAL
    -- MUST be absent if no requirements are available
    -- MUST be present if the PKI management entity has any
    --   requirements on the contents of the certificate template
        certTemplate          REQUIRED
    -- MUST be present if infoValue is present
    -- MUST contain the required CertTemplate structure elements
    -- The SubjectPublicKeyInfo field MUST be absent
        keySpec               OPTIONAL
    -- MUST be absent if no requirements on the public key are
    --   available
    -- MUST be present if the PKI management entity has any
    --   requirements on the keys generated
    -- MUST contain a sequence of one AttributeTypeAndValue per
    --   supported algorithm with attribute id-regCtrl-algId or
    --   id-regCtrl-rsaKeyLen

      infoValue               REQUIRED
    -- MUST contain a sequence of one CRLStatus element
        source                REQUIRED
    -- MUST contain the dpn choice of type DistributionPointName if
    --   the CRL distribution point name is available
    -- Otherwise, MUST contain the issuer choice identifying the CA
    --   that issues the CRL.  It MUST contain the issuer DN in the
    --   directoryName field of a GeneralName element.
        thisUpdate            OPTIONAL
    -- MUST contain the thisUpdate field of the latest CRL the EE
    --   has gotten from the issuer specified in the given dpn or
    --   issuer field
    -- MUST be omitted if the EE does not have any instance of the
    --   requested CRL

      infoValue               OPTIONAL
    -- MUST be absent if no CRL to be returned is available
    -- MUST contain a sequence of one CRL update from the referenced
    --   source if a thisUpdate value was not given or a more recent
    --   CRL is available

Step# EE                                  PKI management entity
 1   format request
       message
 2                  ->     request     ->
 3                                        handle or forward
                                            request
 4                                        format ip/cp/kup/error
                                            with status "waiting"
                                            response in case no
                                            immediate final response
                                            is available
 5                   <- ip/cp/kup/error <-
 6   handle
       ip/cp/kup/error
       with status
       "waiting"

--------------------------  start polling  --------------------------

 7   format pollReq
 8                     ->    pollReq   ->
 9                                        handle or forward pollReq
10                                        in case the final response
                                            for the original request
                                            is available, continue
                                            with step 14
                                          otherwise, format or
                                            receive pollRep with
                                            checkAfter value
11                     <-    pollRep   <-
12   handle pollRep
13   let checkAfter
       time elapse and
       continue with
       step 7

-----------------  end polling, continue as usual  ------------------

14                                        format or receive
                                            final response on
                                            the original request
15                     <-   response   <-
16   handle final
       response
                    

Response with Status "waiting" -- ip/cp/kup/error

Field                         Value

header
    -- As described in Section 3.1

body
    -- As described for the respective PKI management operation, with
    --   the following adaptations:
      status                  REQUIRED -- in case of ip/cp/kup
      pKIStatusInfo           REQUIRED -- in case of error response
    -- PKIStatusInfo structure MUST be present
        status                REQUIRED
    -- MUST be status "waiting"
        statusString          OPTIONAL
    -- MAY be any human-readable text for debugging, for logging, or
    --   to display in a GUI
        failInfo              PROHIBITED

protection                    REQUIRED
    -- As described in Section 3.2

extraCerts                    OPTIONAL
    -- As described in Section 3.3


Polling Request -- pollReq

Field                         Value

header
    -- As described in Section 3.1

body
    -- The message of the EE asking for the final response or for a
    --   time to check again
  pollReq                     REQUIRED
    certReqId                 REQUIRED
    -- MUST be 0 if referring to a CertResponse element, else -1

protection                    REQUIRED
    -- As described in Section 3.2
    -- MUST use the same credentials as in the first request message
    --   of the PKI management operation

extraCerts                    RECOMMENDED
    -- As described in Section 3.3
    -- MAY be omitted if the message size is critical and the PKI
    --   management entity caches the CMP protection certificate from
    --   the first request message of the PKI management operation


Polling Response -- pollRep

Field                         Value

header
    -- As described in Section 3.1

body
    -- The message indicates the delay after which the EE SHOULD
    --   send another pollReq message for this transaction
  pollRep                     REQUIRED
    certReqId                 REQUIRED
    -- MUST be 0 if referring to a CertResponse element, else -1
    checkAfter                REQUIRED
    -- MUST be the time in seconds to elapse before a new pollReq
    --   should be sent
    reason                    OPTIONAL
    -- MAY be any human-readable text for debugging, for logging, or
    --   to display in a GUI

protection                    REQUIRED
    -- As described in Section 3.2
    -- MUST use the same credentials as in the first response
    --   message of the PKI management operation

extraCerts                    RECOMMENDED
    -- As described in Section 3.3
    -- MAY be omitted if the message size is critical and the EE has
    --   cached the CMP protection certificate from the first
    --   response message of the PKI management operation


Final Response - Any Type of Response Message

Field                         Value

header
    -- MUST be the header, as described for the response message
    --   of the respective PKI management operation

body
    -- The response of the PKI management entity to the initial
    --   request, as described in the respective PKI management
    --   operation

protection                    REQUIRED
    -- MUST be as described for the response message of the
    --   respective PKI management operation

extraCerts                    REQUIRED
    -- MUST be as described for the response message of the
    --   respective PKI management operation

Nested Message - nested

Field                         Value

header
    -- As described in Section 3.1

body
    -- Container to provide additional protection to original
    --   messages and to bundle request messages or alternatively
    --   response messages
  PKIMessages                 REQUIRED
    -- MUST be a sequence of one or more CMP messages

protection                    REQUIRED
    -- As described in Section 3.2, using the CMP protection key of
    --   the PKI management entity

extraCerts                    REQUIRED
    -- As described in Section 3.3

Step# PKI management entity               PKI management entity
 1   format nested
 2                      ->  nested   ->
 3                                        handle or forward nested
 4                                        format or receive response
 5                      <-  response <-
 6   forward response
                    

Step# PKI management entity               PKI management entity
 1   format nested
 2                      ->  nested   ->
 3                                        handle or forward nested
 4                                        format or receive nested
 5                      <-  nested   <-
 6   handle nested
                    

    popo
      raVerified              REQUIRED
    -- MUST have the value NULL and indicates that the PKI
    --   management entity verified the popo of the original message

SEQUENCE {
  SEQUENCE {
    [3] {
      SEQUENCE {}
      }
    [5] {
      SEQUENCE {
        SET {
          SEQUENCE {
            OBJECT IDENTIFIER commonName (2 5 4 3)
            UTF8String ""
            }
          }
        SET {
          SEQUENCE {
            OBJECT IDENTIFIER organizationalUnitName (2 5 4 11)
            UTF8String "myDept"
            }
          }
        SET {
          SEQUENCE {
            OBJECT IDENTIFIER organizationalUnitName (2 5 4 11)
            UTF8String "myGroup"
            }
          }
        }
      }
    [9] {
      SEQUENCE {
        OBJECT IDENTIFIER subjectAltName (2 5 29 17)
        OCTET STRING, encapsulates {
          SEQUENCE {
            [2] "www.myServer.com"
            [7] ""
            }
          }
        }
      SEQUENCE {
        OBJECT IDENTIFIER keyUsage (2 5 29 15)
        BOOLEAN TRUE
        OCTET STRING, encapsulates {
          BIT STRING 3 unused bits
            "10001"B
          }
        }
      SEQUENCE {
        OBJECT IDENTIFIER extKeyUsage (2 5 29 37)
        OCTET STRING, encapsulates {
          SEQUENCE {}
          }
        }
      }
    }
  SEQUENCE {
    SEQUENCE {
      OBJECT IDENTIFIER algId (1 3 6 1 5 5 7 5 1 11)
        SEQUENCE {
          OBJECT IDENTIFIER ecPublicKey (1 2 840 10045 2 1)
          OBJECT IDENTIFIER secp256r1 (1 2 840 10045 3 1 7)
          }
      }
    SEQUENCE {
      OBJECT IDENTIFIER rsaKeyLen (1 3 6 1 5 5 7 5 1 12)
      INTEGER 2048
      }
    }
  }