@techreport{ietf-lamps-attestation-freshness-09,
    number =    {draft-ietf-lamps-attestation-freshness-09},
    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-attestation-freshness/09/},
    author =    {Hannes Tschofenig and Hendrik Brockhaus and Joe Mandel and Sean Turner},
    title =     {{Requesting a Freshness Nonce for Attestation Evidence in Certificate Signing Requests}},
    pagetotal = 34,
    year =      2026,
    month =     oct,
    day =       17,
    abstract =  {When an end entity includes attestation statements in a Certificate Signing Request (CSR), the freshness of the conveyed Evidence often needs to be established. A common mechanism is a nonce that is obtained from a Relying Party or Verifier and included by the Attester in the Evidence. This document specifies how an end entity requests such an attestation freshness nonce from an RA/CA when using certificate lifecycle management protocols. It defines message formats and protocol bindings for the conveyance of nonce request and response messages in the Certificate Management Protocol (CMP), Enrollment over Secure Transport (EST), and Certificate Management over CMS (CMC), including optional type-specific information needed to produce fresh Evidence for inclusion in a CSR.},
}