<?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-00">
   <front>
      <title>Using Attestation in Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)</title>
      <author initials="H." surname="Tschofenig" fullname="Hannes Tschofenig">
         <organization>Arm Limited</organization>
      </author>
      <author initials="T." surname="Fossati" fullname="Thomas Fossati">
         <organization>Arm Limited</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="July" day="11" year="2022" />
      <abstract>
	 <t>   Various attestation technologies have been developed and formats have
   been standardized.  Examples include the Entity Attestation Token
   (EAT) and Trusted Platform Modules (TPMs).  Once attestation
   information has been produced on a device it needs to be communicated
   to a relying party.  This information exchange may happen at
   different layers in the protocol stack.

   This specification provides a generic way of passing attestation
   information in the TLS handshake.

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