%% You should probably cite draft-ietf-lamps-rfc4210bis-09 instead of this revision.
@techreport{ietf-lamps-rfc4210bis-03,
    number =    {draft-ietf-lamps-rfc4210bis-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-lamps-rfc4210bis/03/},
    author =    {Hendrik Brockhaus and David von Oheimb and Mike Ounsworth and John Gray},
    title =     {{Internet X.509 Public Key Infrastructure -- Certificate Management Protocol (CMP)}},
    pagetotal = 118,
    year =      2022,
    month =     oct,
    day =       24,
    abstract =  {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 includes the updates on RFC 4210 specified by CMP Updates {[}RFCAAAA{]} Section 2 and Appendix A.2 maintaining backward compatibility with CMP version 2 wherever possible and obsoleted both documents. Updates to CMP version 2 are: improving crypto agility, extending the polling mechanism, adding new general message types, and adding extended key usages to identify special CMP server authorizations. Introducing version 3 to be used only for changes to the ASN.1 syntax, which are: support of EnvelopedData instead of EncryptedValue and hashAlg for indicating a hash AlgorithmIdentifier in certConf messages.},
}