<?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-06">
   <front>
      <title>Nonce-based Freshness for Remote Attestation in Certificate Signing Requests (CSRs) for the Certification Management Protocol (CMP), for Enrollment over Secure Transport (EST), and for Certificate Management over CMS (CMC)</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="April" day="20" year="2026" />
      <abstract>
	 <t>   When an end entity includes attestation statements in a Certificate
   Signing Request (CSR), this document is specifically concerned with
   establishing the freshness of Evidence statements among that
   attestation data.  Current attestation technology commonly achieves
   this using nonces.

   This document outlines the process through which nonces are supplied
   to the end entity by an RA/CA for inclusion in Evidence, leveraging
   the Certificate Management Protocol (CMP), Enrollment over Secure
   Transport (EST), and Certificate Management over CMS (CMC).

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