<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-lamps-attestation-freshness" target="https://datatracker.ietf.org/doc/html/draft-ietf-lamps-attestation-freshness-09">
   <front>
      <title>Requesting a Freshness Nonce for Attestation Evidence in Certificate Signing Requests</title>
      <author initials="H." surname="Tschofenig" fullname="Hannes Tschofenig">
         <organization>Siemens</organization>
      </author>
      <author initials="H." surname="Brockhaus" fullname="Hendrik Brockhaus">
         <organization>Siemens</organization>
      </author>
      <author initials="J." surname="Mandel" fullname="Joe Mandel">
         <organization>AKAYLA, Inc.</organization>
      </author>
      <author initials="S." surname="Turner" fullname="Sean Turner">
         <organization>sn3rd</organization>
      </author>
      <date month="October" day="17" year="2026" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-lamps-attestation-freshness-09" />
   
</reference>
