<?xml version="1.0" encoding="utf-8"?>

<?xml-model href="rfc7991bis.rnc"?>  <!-- Required for schema validation and schema-aware editing -->
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- This third-party XSLT can be enabled for direct transformations in XML processors, including most browsers -->

<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<!-- If further character entities are required then they should be added to the DOCTYPE above.
     Use of an external entity file is not recommended. -->
<rfc
  xmlns:xi="http://www.w3.org/2001/XInclude"
  category="info"
  docName="draft-kdyxy-rats-tdx-eat-profile-00"
  ipr="trust200902"
  obsoletes=""
  updates=""
  submissionType="independent"
  xml:lang="en"
  version="3">
  <front>
    <title abbrev="TDX EAT profile">EAT profile for Intel® Trust Domain Extensions (TDX) attestation result</title>
    <seriesInfo name="Internet-Draft" value="draft-kdyxy-rats-tdx-eat-profile-00"/>
    <author fullname="Greg Kostal" initials="G." surname="Kostal">
      <organization>Microsoft</organization>
      <address>
        <email>gkostal@microsoft.com</email>  
      </address>
    </author>
    <author fullname="Sindhuri Dittakavi" initials="S." surname="Dittakavi">
      <organization>Microsoft</organization>
      <address>
        <email>sindhuri.dittakavi@microsoft.com</email>  
      </address>
    </author>
    <author fullname="Raghuram Yeluri" initials="R." surname="Yeluri">
      <organization>Intel</organization>
      <address>
        <email>raghuram.yeluri@intel.com</email>  
      </address>
    </author>
    <author fullname="Haidong Xia" initials="H." surname="Xia">
      <organization>Intel</organization>
      <address>
        <email>haidong.xia@intel.com</email>  
      </address>
    </author>
    <author fullname="Jerry Yu" initials="J." surname="Yu">
      <organization>Intel</organization>
      <address>
        <email>jerry.yu@intel.com</email>  
      </address>
    </author>
    <date year="2023"/>
    <area>Security</area>
    <workgroup>Remote ATtestation ProcedureS</workgroup>
    <keyword>Internet-Draft</keyword>
    <abstract>
      <t>Intel® Trust Domain Extensions (TDX) introduces architectural elements designed for the deployment of hardware-isolated virtual machines (VMs) known as trust domains (TDs). TDX is designed to provide a secure and isolated environment for running sensitive workloads or applications. This Entity Attestation Token (EAT) profile outlines claims for an Intel TDX attestation result which facilitate the establishment of trust between a relying party and the environment. </t>
    </abstract>
  </front>
  <middle>   
    <section>
      <name>Introduction</name>
      <t>This profile outlines claims for an Intel® Trust Domain Extensions <xref target="TDX"/> attestation result, 
        generated as an Entity Attestation Token <xref target="EAT"/> in a signed JSON Web Token <xref target="JWT"/> 
        format using JOSE header. It doesn't contain nested tokens or a detached EAT bundle. The profile allows signing 
        of the JWT token using RSA cryptographic algorithm. To facilitate verification of the signed JWT tokens, the 
        verifier can expose the trusted token signing certificates using an OpenID metadata endpoint. In accordance 
        with the standards outlined in the JSON Web Signature <xref target="JWS"/> specification, the receiver of the 
        profile can use the certificate with key ID (kid) matching the kid parameter in the attestation token header 
        for performing signature verification.</t>
    </section>
    <section>
        <name>Requirements Language</name>
        <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
          "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT
          RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
          interpreted as described in BCP 14 <xref target="RFC2119"/>
          <xref target="RFC8174"/> when, and only when, they appear in
          all capitals, as shown here.</t>
    </section>
     <section>
        <name>TDX profile claims</name>
       <t>This profile encompasses claims from the IETF JWT specification, the EAT specification and Intel's TDX specification.</t>
    <section>
        <name>JWT claims</name>
        <t>The complete definitions of the following claims are available in the <xref target="JWT"/> specification.</t>
         <dl newline="true">
          <dt>iat</dt>
          <dd>The "iat" (issued at) claim identifies the time at which the JWT was issued.</dd>
          <dt>exp</dt>
          <dd>The "exp" (expiration time) claim identifies the expiration time on or after which the JWT MUST NOT be accepted for processing.</dd>
          <dt>iss</dt>
          <dd>The "iss" (issuer) claim identifies the principal that issued the JWT.</dd>
          <dt>jti</dt>
          <dd>The "jti" (JWT ID) claim provides a unique identifier for the JWT.</dd>
          <dt>nbf</dt>
          <dd>The "nbf" (not before) claim identifies the time before which the JWT MUST NOT be accepted for processing.</dd>
         </dl>
     </section>
    <section>
        <name>EAT claims</name>   
       <t>The complete definitions of the following claims are available in the <xref target="EAT"/> specification.</t>
         <dl newline="true">
          <dt>eat_profile</dt>
          <dd>The "eat_profile" claim identifies an EAT profile by either a URL or an OID.</dd>
          <dt>dbgstat</dt>
          <dd>The "dbgstat" claim applies to entity-wide or submodule-wide debug facilities of the entity like <xref target="JTAG"/> and diagnostic hardware built into chips.</dd>
          <dt>intuse</dt>
          <dd>The "intuse" claim provides an indication to an EAT consumer about the intended usage of the token.</dd>
          <dt>eat_nonce</dt>
          <dd>An EAT nonce is either a byte or text string or an array of byte or text strings.  The array option supports multistage EAT verification and consumption.</dd>
         </dl>
    </section>
    <section>
        <name>TDX claims</name>
       <t>The complete definitions of the following claims are available in section A.3.2 TD Quote Body of <xref target="TDX-DCAP-Quoting-Library"/>.</t>
          <dl newline="true">
          <dt>tdx_mrsignerseam</dt>
          <dd>A 96-character hexadecimal string that represents a byte array of length 48 containing the measurement of the TDX module signer.</dd>
          <dt>tdx_mrseam</dt>
          <dd>A 96-character hexadecimal string that represents a byte array of length 48 containing the measurement of the TDX module.</dd>
          <dt>tdx_mrtd</dt>
          <dd>A 96-character hexadecimal string that represents a byte array of length 48 containing the measurement of the initial contents of the TDX.</dd>
          <dt>tdx_rtmr0</dt>
          <dd>A 96-character hexadecimal string that represents a byte array of length 48 containing the runtime extendable measurement register.</dd>
          <dt>tdx_rtmr1</dt>
          <dd>A 96-character hexadecimal string that represents a byte array of length 48 containing the runtime extendable measurement register.</dd>
          <dt>tdx_rtmr2</dt>
          <dd>A 96-character hexadecimal string that represents a byte array of length 48 containing the runtime extendable measurement register.</dd>
          <dt>tdx_rtmr3</dt>
          <dd>A 96-character hexadecimal string that represents a byte array of length 48 containing the runtime extendable measurement register.</dd>
          <dt>tdx_mrconfigid</dt>
          <dd>A 96-character hexadecimal string that represents a byte array of length 48 containing the software-defined ID for non-owner-defined configuration of the TDX, e.g., runtime or Operating System (OS) configuration.</dd>
          <dt>tdx_mrowner</dt>
          <dd>A 96-character hexadecimal string that represents a byte array of length 48 containing the software-defined ID for the TDX's owner.</dd>
          <dt>tdx_mrownerconfig</dt>
          <dd>A 96-character hexadecimal string that represents a byte array of length 48 containing the software-defined ID for owner-defined configuration of the TDX, e.g., specific to the workload rather than the runtime or OS.</dd>
          <dt>tdx_report_data</dt>
          <dd>A 128-character hexadecimal string that represents a byte array of length 64. In this context, the TDX has the flexibility to include 64 bytes of custom data in a TDX Report. For instance, this space can be used to hold a nonce, a public key, or a hash of a larger block of data.</dd>
          <dt>tdx_seam_attributes</dt>
          <dd>A 16 character hexadecimal string that represents a byte array of length 8 containing additional configuration of the TDX module.</dd>
          <dt>tdx_tee_tcb_svn</dt>
          <dd>A 32 character hexadecimal string that represents a byte array of length 16 describing Trusted Computing Base (TCB) Security Version Numbers (SVNs) of the TDX.</dd>
          <dt>tdx_xfam</dt>
          <dd>A 16 character hexadecimal string that represents a byte array of length 8 containing a mask of CPU extended features that the TDX is allowed to use.</dd>
          <dt>tdx_seamsvn</dt>
          <dd>A number that represents the Intel TDX module SVN. The complete definition of the claim is available in section 3.1 SEAM_SIGSTRUCT: INTEL® TDX MODULE SIGNATURE STRUCTURE of the <xref target="TDX-SEAM-Loader-Interface"/> specification.</dd>
          <dt>tdx_td_attributes</dt>
          <dd>A 16 character hexadecimal string that represents a byte array of length 8. These are the attributes associated with the Trust Domain (TD).  The complete definitions of the claims mentioned below are available in section A.3.4. TD Attributes of <xref target="TDX-DCAP-Quoting-Library"/>.</dd>
          <dt>tdx_td_attributes_debug</dt>
          <dd>A boolean value that indicates whether the TD runs in TD debug mode (set to 1) or not (set to 0). In TD debug mode, the CPU state and private memory are accessible by the host VMM.</dd>
          <dt>tdx_td_attributes_key_locker</dt>
          <dd>A boolean value that indicates whether the TD is allowed to use Key Locker.</dd>
         <dt>tdx_td_attributes_perfmon</dt>
          <dd>A boolean value that indicates whether the TD is allowed to use Perfmon and PERF_METRICS capabilities.</dd>
         <dt>tdx_td_attributes_protection_keys</dt>
          <dd>A boolean value that indicates whether the TD is allowed to use Supervisor Protection Keys.</dd>
         <dt>tdx_td_attributes_septve_disable</dt>
          <dd>A boolean value that determines whether to disable EPT violation conversion to #VE on TD access of PENDING pages.</dd>
          </dl>
     </section>
    <section>
        <name>Attester claims</name>
       <dl newline="true">
          <dt>attester_advisory_ids</dt>
          <dd>Array of Advisory IDs referring to Intel security advisories that provide insight into the reason(s) for the value of tcbStatus of the platform TCB level being evaluated. See advisoryIDs in <xref target="TDX-API-Portal"/>.</dd>
          <dt>attester_tcb_status</dt>
          <dd>A string value that represents the TCB level status of the platform being evaluated. See tcbStatus in <xref target="TDX-API-Portal"/>.</dd>
       </dl>
    </section>
    </section>
    <section anchor="IANA">
      <name>IANA Considerations</name>   
            <section>
        <name>JWT claims registered by this document</name>
   <t>This specification adds the following values to the "JSON Web Token
Claims" registry established by the JWT specification</t>
         <t>IANA is requested to register the following claims.</t>
  <artwork>-----------------------------------------------</artwork>
  <t>Claim Name: tdx_mrsignerseam</t>
  <t>Claim Description: TDX module signer</t>
  <t>Specification Document(s): This document</t>
 <artwork>-----------------------------------------------</artwork>
  <t>Claim Name: tdx_mrseam</t>
  <t>Claim Description: Measurement of the TDX module</t>
  <t>Specification Document(s): This document</t>
 <artwork>-----------------------------------------------</artwork>
 <t>Claim Name: tdx_mrtd</t>
  <t>Claim Description: Measurement of the TDX initial contents</t>
  <t>Specification Document(s): This document</t>
  <artwork>-----------------------------------------------</artwork>
 <t>Claim Name: tdx_rtmr0</t>
  <t>Claim Description: Runtime extendable measurement register</t>
  <t>Specification Document(s): This document</t>
 <artwork>-----------------------------------------------</artwork>
 <t>Claim Name: tdx_rtmr1</t>
  <t>Claim Description: Runtime extendable measurement register</t>
  <t>Specification Document(s): This document</t>
<artwork>-----------------------------------------------</artwork>
<t>Claim Name: tdx_rtmr2</t>
  <t>Claim Description: Runtime extendable measurement register</t>
  <t>Specification Document(s): This document</t>
<artwork>-----------------------------------------------</artwork>
<t>Claim Name: tdx_rtmr3</t>
  <t>Claim Description: Runtime extendable measurement register</t>
  <t>Specification Document(s): This document</t>
 <artwork>-----------------------------------------------</artwork>
<t>Claim Name: tdx_mrconfigid</t>
  <t>Claim Description: Software-defined ID for non-owner-defined configuration of the TDX</t>
  <t>Specification Document(s): This document</t>
<artwork>-----------------------------------------------</artwork>
<t>Claim Name: tdx_mrowner</t>
  <t>Claim Description: Software-defined ID for the TDX's owner</t>
  <t>Specification Document(s): This document</t>
<artwork>-----------------------------------------------</artwork>
<t>Claim Name: tdx_mrownerconfig</t>
  <t>Claim Description: Software-defined ID for owner-defined configuration of the TDX</t>
  <t>Specification Document(s): This document</t>
<artwork>-----------------------------------------------</artwork>
<t>Claim Name: tdx_report_data</t>
  <t>Claim Description: Custom data in the TDX Report</t>
  <t>Specification Document(s): This document</t>
<artwork>-----------------------------------------------</artwork>
<t>Claim Name: tdx_seam_attributes</t>
  <t>Claim Description: Additional configuration of the TDX module</t>
  <t>Specification Document(s): This document</t>
<artwork>-----------------------------------------------</artwork>
<t>Claim Name: tdx_tee_tcb_svn</t>
  <t>Claim Description: Trusted Computing Base (TCB) Security Version Numbers (SVNs) of the TDX</t>
  <t>Specification Document(s): This document</t>
<artwork>-----------------------------------------------</artwork>
<t>Claim Name: tdx_xfam</t>
  <t>Claim Description: Mask of CPU extended features that the TDX is allowed to use</t>
  <t>Specification Document(s): This document</t>
<artwork>-----------------------------------------------</artwork>
<t>Claim Name: tdx_seamsvn</t>
  <t>Claim Description: The TDX module Security Version Number (SVN)</t>
  <t>Specification Document(s): This document</t>
<artwork>-----------------------------------------------</artwork>
<t>Claim Name: tdx_td_attributes</t>
  <t>Claim Description: Attributes associated with the Trust Domain (TD)</t>
  <t>Specification Document(s): This document</t>
<artwork>-----------------------------------------------</artwork>
<t>Claim Name: tdx_td_attributes_debug</t>
  <t>Claim Description: Indicates whether the TD runs in TD debug mode (set to 1) or not (set to 0)</t>
  <t>Specification Document(s): This document</t>
<artwork>-----------------------------------------------</artwork>
<t>Claim Name: tdx_td_attributes_key_locker</t>
  <t>Claim Description: Indicates whether the TD is allowed to use Key Locker</t>
  <t>Specification Document(s): This document</t>
<artwork>-----------------------------------------------</artwork>
<t>Claim Name: tdx_td_attributes_perfmon</t>
  <t>Claim Description: Indicates whether the TD is allowed to use Perfmon and PERF_METRICS capabilities</t>
  <t>Specification Document(s): This document</t>
<artwork>-----------------------------------------------</artwork>
<t>Claim Name: tdx_td_attributes_protection_keys</t>
  <t>Claim Description: Indicates whether the TD is allowed to use Supervisor Protection Keys</t>
  <t>Specification Document(s): This document</t>
<artwork>-----------------------------------------------</artwork>
<t>Claim Name: tdx_td_attributes_septve_disable</t>
  <t>Claim Description: Determines whether to disable EPT violation conversion to #VE on TD access of PENDING pages</t>
  <t>Specification Document(s): This document</t>
<artwork>-----------------------------------------------</artwork>
<t>Claim Name: attester_advisory_ids</t>
  <t>Claim Description: Intel security advisories that provide insight into the reason(s) for the value of tcbStatus of the platform TCB level being evaluated</t>
  <t>Specification Document(s): This document</t>
<artwork>-----------------------------------------------</artwork>
<t>Claim Name: attester_tcb_status</t>
  <t>Claim Description: TCB level status of the platform being evaluated</t>
  <t>Specification Document(s): This document</t>
  <artwork>-----------------------------------------------</artwork>
      </section>
    </section>
    <section anchor="Security">
      <name>Security Considerations</name>
      <t>This specification re-uses the EAT and JWT specifications.  Hence, the security and privacy considerations of those specifications apply here as well.</t>
       <t>Additionally, the security considerations as described in <xref target="TDX-Security-Guidance"/> apply here too.</t>
    </section>
  </middle>
  <back>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
         <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
        <reference anchor="EAT" target="https://datatracker.ietf.org/doc/html/draft-ietf-rats-eat">
          <front>
            <title>The Entity Attestation Token (EAT)</title>
            <author fullname="Laurence Lundblade" initials="L." surname="Lundblade">
              <organization>Security Theory LLC</organization>
            </author>
            <author fullname="Giridhar Mandyam" initials="G." surname="Mandyam">
              <organization>Qualcomm Technologies Inc.</organization>
            </author>
            <author fullname="Jeremy O'Donoghue" initials="J." surname="O'Donoghue">
              <organization>Qualcomm Technologies Inc.</organization>
            </author>
            <author fullname="Carl Wallace" initials="C." surname="Wallace">
              <organization>Red Hound Software, Inc.</organization>
            </author>
            <date day="30" month="June" year="2023"/>
            </front>
        </reference>
         <reference anchor="JWT" target="https://datatracker.ietf.org/doc/html/rfc7519">
          <front>
            <title> JSON Web Token (JWT)</title>
            <author fullname="Michael B. Jones" initials="M." surname="Jones">
              <organization>Security Theory LLC</organization>
            </author>
            <author fullname="John Bradley" initials="J." surname="Bradley">
              <organization>Qualcomm Technologies Inc.</organization>
            </author>
            <author fullname="Nat Sakimura" initials="N." surname="Sakimura">
              <organization>Qualcomm Technologies Inc.</organization>
            </author>
            <date month="May" year="2015"/>
            </front>
        </reference>
         <reference anchor="JWS" target="https://datatracker.ietf.org/doc/html/rfc7515">
          <front>
            <title>JSON Web Signature (JWS)</title>
           <author fullname="Michael B. Jones" initials="M." surname="Jones">
              <organization>Security Theory LLC</organization>
            </author>
            <author fullname="John Bradley" initials="J." surname="Bradley">
              <organization>Qualcomm Technologies Inc.</organization>
            </author>
            <author fullname="Nat Sakimura" initials="N." surname="Sakimura">
              <organization>Qualcomm Technologies Inc.</organization>
            </author>
            <date month="May" year="2015"/>
            </front>
        </reference>
        <reference anchor="TDX" target="https://www.intel.com/content/www/us/en/developer/tools/trust-domain-extensions/overview.html">
          <front>
            <title>Intel® Trust Domain Extensions</title>
            <author>
              <organization>Intel</organization>
            </author>
            <date month="Feb" year="2023"/>
          </front>
        </reference>
          <reference anchor="TDX-API-Portal" target="https://api.portal.trustedservices.intel.com/documentation">
          <front>
            <title>Intel® SGX and Intel® TDX Registration Service for Scalable Platforms</title>
            <author>
              <organization>Intel</organization>
            </author>
            <date month="Feb" year="2023"/>
          </front>
        </reference>
         <reference anchor="TDX-DCAP-Quoting-Library" target="https://download.01.org/intel-sgx/latest/dcap-latest/linux/docs/Intel_TDX_DCAP_Quoting_Library_API.pdf">
          <front>
            <title>Intel® Trust Domain Extensions Data Center Attestation Primitives (Intel® TDX DCAP): Quote Generation Library and Quote Verification Library</title>
            <author>
              <organization>Intel</organization>
            </author>
            <date month="Aug" year="2023"/>
          </front>
        </reference>
         <reference anchor="TDX-SEAM-Loader-Interface" target="https://cdrdv2.intel.com/v1/dl/getContent/733584">
          <front>
            <title>Intel® Trust Domain Extensions - SEAM Loader (SEAMLDR) Interface Specification</title>
            <author>
              <organization>Intel</organization>
            </author>
            <date month="Mar" year="2022"/>
          </front>
        </reference>
      </references>
      <references>
        <name>Informative References</name>
        <reference anchor="JTAG" target="https://ieeexplore.ieee.org/document/5412866">
        <front>
          <title>IEEE Standard for Reduced-Pin and Enhanced-Functionality Test Access Port and Boundary-Scan Architecture</title>
          <author >
            <organization></organization>
          </author>
          <date year="2010" month="February"/>
        </front>
      </reference>
         <reference anchor="MAA" target="https://learn.microsoft.com/en-us/azure/attestation/overview">
          <front>
            <title>Microsoft Azure Attestation</title>
            <author>
              <organization>Microsoft</organization>
            </author>
            <date month="Mar" year="2021"/>
          </front>
        </reference>
        <reference anchor="TA" target="https://www.intel.com/content/www/us/en/security/trust-authority.html">
          <front>
            <title>Intel® Trust Authority</title>
            <author>
              <organization>Intel</organization>
            </author>
            <date month="Oct" year="2023"/>
          </front>
        </reference>
        <reference anchor="MAA-EAT-Profile" target="https://learn.microsoft.com/en-us/azure/attestation/trust-domain-extensions-eat-profile">
          <front>
            <title>EAT profile of Microsoft Azure Attestation</title>
            <author>
              <organization>Microsoft</organization>
            </author>
            <date month="Oct" year="2023"/>
          </front>
        </reference>
        <reference anchor="TA-EAT-Profile" target="https://portal.trustauthority.intel.com/eat_profile">
          <front>
            <title>EAT profile of Intel® Trust Authority</title>
            <author>
              <organization>Intel</organization>
            </author>
            <date month="Oct" year="2023"/>
          </front>
        </reference>
        <reference anchor="TDX-Security-Guidance" target="https://www.intel.com/content/www/us/en/developer/tools/trust-domain-extensions/documentation.html#security-guidance">
          <front>
            <title>Intel TDX Security Guidance</title>
            <author>
              <organization>Intel</organization>
            </author>
            <date month="Feb" year="2023"/>
          </front>
        </reference>
      </references>
    </references>
    <section anchor="Appendix">
      <name>Examples</name>
      <section>
        <name>TDX attestation token by Intel® Trust Authority</name>
       <t>Below is a sample TDX attestation token generated by Intel® Trust Authority <xref target="TA"/> which includes claims from this EAT profile. The definitions of the token claims can be found in <xref target="TA-EAT-Profile"/>.</t>
 <artwork><![CDATA[
      {
  "alg": "PS384",
  "jku": "https://portal.trustauthority.intel.com/certs"
,
  "kid": "1881f519948621f7aeb538a8a5896bb3fb7c271c3522081c5dd7af1a683bac
          f6d90a63e82ade85c00321781591dfdf3d",
  "typ": "JWT"
}.{
  "tdx_tee_tcb_svn": "02010600000000000000000000000000",
  "tdx_mrseam": "360304d34a16aace0a18e09ad2d07d2b9fd3c174378e5bf10838807
          9827f89ff62acc5f8c473dd40706324834e202946",
  "tdx_mrsignerseam": "000000000000000000000000000000000000000000000000
          000000000000000000000000000000000000000000000000",
  "tdx_seam_attributes": "0000000000000000",
  "tdx_td_attributes": "0000000000000000",
  "tdx_xfam": "e718060000000000",
  "tdx_mrtd": "75f3acc2e1dfc3acf404d7eaa69a2eefcd0475a0dd6516ef5ba3cb8
          3399c61b4aa1c638e3622bb650a514bfc6e858886",
  "tdx_mrconfigid": "0000000000000000000000000000000000000000000000000
          00000000000000000000000000000000000000000000000",
  "tdx_mrowner": "0000000000000000000000000000000000000000000000000000
          00000000000000000000000000000000000000000000",
  "tdx_mrownerconfig": "0000000000000000000000000000000000000000000000
          00000000000000000000000000000000000000000000000000",
  "tdx_rtmr0": "000000000000000000000000000000000000000000000000000000
          000000000000000000000000000000000000000000",
  "tdx_rtmr1": "000000000000000000000000000000000000000000000000000000
          000000000000000000000000000000000000000000",
  "tdx_rtmr2": "000000000000000000000000000000000000000000000000000000
          000000000000000000000000000000000000000000",
  "tdx_rtmr3": "000000000000000000000000000000000000000000000000000000
          000000000000000000000000000000000000000000",
  "tdx_report_data": "7e3b88c09ed42bad38c146f542fbee862411878fa33a3fdf
          bffd2ad549db279200000000000000000000000000000000000000000000
          00000000000000000000",
  "tdx_seamsvn": 2,
  "tdx_td_attributes_debug": false,
  "tdx_td_attributes_septve_disable": false,
  "tdx_td_attributes_protection_keys": false,
  "tdx_td_attributes_key_locker": false,
  "tdx_td_attributes_perfmon": false,
  "tdx_is_debuggable": false,
  "tdx_collateral": {
    "qeidcerthash": "b2ca71b8e849d5e799451b4bfe43159a0ee548032cecb2c0e4
          79bf6ee3f39fd1",
    "qeidcrlhash": "f454dc1b9bd4ce36c04241e2c8c37a2ae26b077f2c66b919843
          365318a59332c",
    "qeidhash": "665b5e4a8c34c24935448629894302b0bc8a054f25e43333021dd8
          c93e9211be",
    "quotehash": "be3de7edd324a21cb73f8ba3d8ea5bd704bd27809dd6f0c8de152
          5511845389c",
    "tcbinfocerthash": "b2ca71b8e849d5e799451b4bfe43159a0ee548032cecb2c
          0e479bf6ee3f39fd1",
    "tcbinfocrlhash": "f454dc1b9bd4ce36c04241e2c8c37a2ae26b077f2c66b919
          843365318a59332c",
    "tcbinfohash": "7c2b91b9aaaf0a9823f17bb6b31403fffee7fe0b658b41d9e80
          2c6de8569096d"
  },
  "attester_runtime_data": {
     "test-claim-name": "test-claim-value"
  },
  "policy_ids_matched": [
    {
      "id": "094f9b2d-5477-4607-8a5f-bd33388c60c7",
      "version": "v4"
    }
  ],
  "attester_tcb_status": "UpToDate",
  "attester_type": "TDX",
  "verifier_instance_ids": [
    "64edd3d8-be70-4d03-9cb5-e5575107c87d",
    "56b8f9df-f6c5-4302-8142-321985f269c4",
    "5f6d8e1e-288a-409e-ad3f-3670f00a426c",
    "c82f8048-ea8b-4407-9365-3990bb646e3e"
  ],
  "dbgstat": "disabled",
  "eat_profile": "https://portal.trustauthority.intel.com/eat_profile"
,
  "intuse": "generic",
  "ver": "1.0.0",
  "exp": 1696973571,
  "jti": "ac2ca0de-e271-4878-a56f-59e5e6b8c328",
  "iat": 1696973271,
  "iss": "Intel Trust Authority",
  "nbf": 1696973271
}
     ]]></artwork>
      </section>
       <section>
        <name>TDX attestation token by Microsoft Azure Attestation</name>
      <t>Below is a sample TDX attestation token generated by Microsoft Azure Attestation <xref target="MAA"/> which includes claims from this EAT profile. The definitions of the token claims can be found in <xref target="MAA-EAT-Profile"/>.</t>
        <artwork><![CDATA[
  {
   "attester_tcb_status": "UpToDate",
   "dbgstat": "disabled",
   "eat_profile": "https://aka.ms/maa-eat-profile-tdxvm",
   "exp": 1697600807,
   "iat": 1697572007,
   "intuse": "generic",
   "iss": "https://maasand001.eus.attest.azure.net",
   "jti": "fb5021d13a90f5b3f5642b30d8103715c8d76ee05c9062923a04af35d0
          347ade",
   "nbf": 1697572007,
   "tdx_mrconfigid": "00000000000000000000000000000000000000000000000
          0000000000000000000000000000000000000000000000000",
   "tdx_mrowner": "00000000000000000000000000000000000000000000000000
          0000000000000000000000000000000000000000000000",
   "tdx_mrownerconfig": "00000000000000000000000000000000000000000000
          0000000000000000000000000000000000000000000000000000",
   "tdx_mrseam": "2fd279c16164a93dd5bf373d834328d46008c2b693af9ebb865
          b08b2ced320c9a89b4869a9fab60fbe9d0c5a5363c656",
   "tdx_mrsignerseam": "000000000000000000000000000000000000000000000
          000000000000000000000000000000000000000000000000000",
   "tdx_mrtd": "5be56d418d33661a6c21da77c9503a07e430b35eb92a0bd042a6b
          3c4e79b3c82bb1c594e770d0d129a0724669f1e953f",
   "tdx_report_data": "93c6db49f2318387bcebdad0275e206725d948f9000d90
          0344aa44abaef1459600000000000000000000000000000000000000000
          00000000000000000000000",
   "tdx_rtmr0": "0000000000000000000000000000000000000000000000000000
          00000000000000000000000000000000000000000000",
   "tdx_rtmr1": "0000000000000000000000000000000000000000000000000000
          00000000000000000000000000000000000000000000",
   "tdx_rtmr2": "0000000000000000000000000000000000000000000000000000
          00000000000000000000000000000000000000000000",
   "tdx_rtmr3": "0000000000000000000000000000000000000000000000000000
          00000000000000000000000000000000000000000000",
   "tdx_seam_attributes": "0000000000000000",
   "tdx_seamsvn": 3,
   "tdx_td_attributes": "0000000000000000",
   "tdx_td_attributes_debug": false,
   "tdx_td_attributes_key_locker": false,
   "tdx_td_attributes_perfmon": false,
   "tdx_td_attributes_protection_keys": false,
   "tdx_td_attributes_septve_disable": false,
   "tdx_tee_tcb_svn": "03000600000000000000000000000000",
   "tdx_xfam": "e718060000000000",
   "x-ms-attestation-type": "tdxvm",
   "x-ms-compliance-status": "azure-compliant-cvm",
   "x-ms-policy-hash": "B56nbp5slhw66peoRYkpdq1WykMkEworvdol08hnMXE",
   "x-ms-runtime": {
      "test-claim-name": "test-claim-value"
   },
   "x-ms-ver": "1.0"
} 
     ]]></artwork>
       </section>
    </section>
    <section anchor="Acknowledgements" numbered="false">
      <name>Acknowledgements</name>
      <t>Thanks to Dave Thaler for offering guidance in drafting and publishing the profile.</t>
    </section>
 </back>
</rfc>
