<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.bdnr-rats-trustworthy-credentials" target="https://datatracker.ietf.org/doc/html/draft-bdnr-rats-trustworthy-credentials-01">
   <front>
      <title>Trustworthy Enrollment of Secure Credentials</title>
      <author initials="M." surname="Novak" fullname="Mark Novak">
         <organization>J.P. Morgan Chase</organization>
      </author>
      <author initials="M." surname="Richardson" fullname="Michael Richardson">
         <organization>Sandelman Software Works</organization>
      </author>
      <author initials="H." surname="Birkholz" fullname="Henk Birkholz">
         <organization>Franhaufer Inst.</organization>
      </author>
      <date month="July" day="6" year="2026" />
      <abstract>
	 <t>   To be written last

   There is a large class of &quot;RATS-Unaware&quot; Relying Parties (RUPs) that
   Attesters nevertheless need to interoperate with.  Existing deployed
   services, which precede the introduction of Remote Attestation, are
   often difficult to change/update in significant ways due to
   regulatory and cryptographic review policies.  Yet there are
   significant advantages if clients can be incrementally updated in the
   trustworthiness of the platform.

   This document details a protocol by which the trusthworthiness of an
   Attesters is reviewed as part of the process of it being provided
   with some form of an Identity Document (a key, or a credential) to
   authenticate to RUPs.

   This specification illustrates how the RATS Architecture can be
   applied to interoperate with RUPs by providing Attesters with such
   Identity Documents.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-bdnr-rats-trustworthy-credentials-01" />
   
</reference>
