<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.fossati-tls-attestation" target="https://datatracker.ietf.org/doc/html/draft-fossati-tls-attestation-03">
   <front>
      <title>Using Attestation in Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)</title>
      <author initials="H." surname="Tschofenig" fullname="Hannes Tschofenig">
         </author>
      <author initials="Y." surname="Sheffer" fullname="Yaron Sheffer">
         <organization>Intuit</organization>
      </author>
      <author initials="P." surname="Howard" fullname="Paul Howard">
         <organization>Arm Limited</organization>
      </author>
      <author initials="I." surname="Mihalcea" fullname="Ionuț Mihalcea">
         <organization>Arm Limited</organization>
      </author>
      <author initials="Y." surname="Deshpande" fullname="Yogesh Deshpande">
         <organization>Arm Limited</organization>
      </author>
      <date month="March" day="13" year="2023" />
      <abstract>
	 <t>   Attestation is the process by which an entity produces evidence about
   itself that another party can use to evaluate the trustworthiness of
   that entity.

   In use cases that require the use of remote attestation, such as
   confidential computing or device onboarding, an attester has to
   convey evidence or attestation results to a relying party.  This
   information exchange may happen at different layers in the protocol
   stack.

   This specification provides a generic way of passing evidence and
   attestation results in the TLS handshake.  Functionality-wise this is
   accomplished with the help of key attestation.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-fossati-tls-attestation-03" />
   
</reference>
