%% You should probably cite draft-ietf-lamps-csr-attestation-29 instead of this revision.
@techreport{ietf-lamps-csr-attestation-17,
    number =    {draft-ietf-lamps-csr-attestation-17},
    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-csr-attestation/17/},
    author =    {Mike Ounsworth and Hannes Tschofenig and Henk Birkholz and Monty Wiseman and Ned Smith},
    title =     {{Use of Remote Attestation with Certification Signing Requests}},
    pagetotal = 53,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {A PKI end entity requesting a certificate from a Certification Authority (CA) may wish to offer trustworthy claims about the platform generating the certification request and the environment associated with the corresponding private key, such as whether the private key resides on a hardware security module. This specification defines an attribute and an extension that allow for conveyance of Evidence and Attestation Results in Certificate Signing Requests (CSRs), such as PKCS\#10 or Certificate Request Message Format (CRMF) payloads. This provides an elegant and automatable mechanism for transporting Evidence to a Certification Authority. Including Evidence and Attestation Results along with a CSR can help to improve the assessment of the security posture for the private key, and can help the Certification Authority to assess whether it satisfies the requested certificate profile.},
}