<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" ipr="trust200902" docName="draft-ietf-rats-eat-media-type-12" number="9782" category="std" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" xml:lang="en" updates="" obsoletes="" prepTime="2025-05-27T19:14:10" indexInclude="true" scripts="Common,Latin" tocDepth="3">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-rats-eat-media-type-12" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc9782" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="EAT Media Types">Entity Attestation Token (EAT) Media Types</title>
    <seriesInfo name="RFC" value="9782" stream="IETF"/>
    <author initials="L." surname="Lundblade" fullname="Laurence Lundblade">
      <organization showOnFrontPage="true">Security Theory LLC</organization>
      <address>
        <email>lgl@securitytheory.com</email>
      </address>
    </author>
    <author initials="H." surname="Birkholz" fullname="Henk Birkholz">
      <organization abbrev="Fraunhofer SIT" showOnFrontPage="true">Fraunhofer Institute for Secure Information Technology</organization>
      <address>
        <postal>
          <street>Rheinstrasse 75</street>
          <city>Darmstadt</city>
          <code>64295</code>
          <country>Germany</country>
        </postal>
        <email>henk.birkholz@ietf.contact</email>
      </address>
    </author>
    <author initials="T." surname="Fossati" fullname="Thomas Fossati">
      <organization showOnFrontPage="true">Linaro</organization>
      <address>
        <email>thomas.fossati@linaro.org</email>
      </address>
    </author>
    <date month="05" year="2025"/>
    <area>SEC</area>
    <workgroup>rats</workgroup>
    <keyword>EAT</keyword>
    <keyword>media type</keyword>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">The payloads used in Remote ATtestation procedureS (RATS) may require an
associated media type for their conveyance, for example, when the payloads are
used in RESTful APIs.</t>
      <t indent="0" pn="section-abstract-2">This memo defines media types to be used for Entity Attestation Tokens (EATs).</t>
    </abstract>
    <boilerplate>
      <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1">
        <name slugifiedName="name-status-of-this-memo">Status of This Memo</name>
        <t indent="0" pn="section-boilerplate.1-1">
            This is an Internet Standards Track document.
        </t>
        <t indent="0" pn="section-boilerplate.1-2">
            This document is a product of the Internet Engineering Task Force
            (IETF).  It represents the consensus of the IETF community.  It has
            received public review and has been approved for publication by
            the Internet Engineering Steering Group (IESG).  Further
            information on Internet Standards is available in Section 2 of 
            RFC 7841.
        </t>
        <t indent="0" pn="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <eref target="https://www.rfc-editor.org/info/rfc9782" brackets="none"/>.
        </t>
      </section>
      <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.2">
        <name slugifiedName="name-copyright-notice">Copyright Notice</name>
        <t indent="0" pn="section-boilerplate.2-1">
            Copyright (c) 2025 IETF Trust and the persons identified as the
            document authors. All rights reserved.
        </t>
        <t indent="0" pn="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<eref target="https://trustee.ietf.org/license-info" brackets="none"/>) in effect on the date of
            publication of this document. Please review these documents
            carefully, as they describe your rights and restrictions with
            respect to this document. Code Components extracted from this
            document must include Revised BSD License text as described in
            Section 4.e of the Trust Legal Provisions and are provided without
            warranty as described in the Revised BSD License.
        </t>
      </section>
    </boilerplate>
    <toc>
      <section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1">
        <name slugifiedName="name-table-of-contents">Table of Contents</name>
        <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1">
          <li pn="section-toc.1-1.1">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.1.2">
              <li pn="section-toc.1-1.1.2.1">
                <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.2.1.1"><xref derivedContent="1.1" format="counter" sectionFormat="of" target="section-1.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-terminology">Terminology</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.2">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-eat-types">EAT Types</xref></t>
          </li>
          <li pn="section-toc.1-1.3">
            <t indent="0" pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-a-media-type-parameter-for-">A Media Type Parameter for EAT Profiles</xref></t>
          </li>
          <li pn="section-toc.1-1.4">
            <t indent="0" pn="section-toc.1-1.4.1"><xref derivedContent="4" format="counter" sectionFormat="of" target="section-4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-examples">Examples</xref></t>
          </li>
          <li pn="section-toc.1-1.5">
            <t indent="0" pn="section-toc.1-1.5.1"><xref derivedContent="5" format="counter" sectionFormat="of" target="section-5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.6">
            <t indent="0" pn="section-toc.1-1.6.1"><xref derivedContent="6" format="counter" sectionFormat="of" target="section-6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.6.2">
              <li pn="section-toc.1-1.6.2.1">
                <t indent="0" pn="section-toc.1-1.6.2.1.1"><xref derivedContent="6.1" format="counter" sectionFormat="of" target="section-6.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-cwt-structured-syntax-suffi"><tt>+cwt</tt> Structured Syntax Suffix</xref></t>
                <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.6.2.1.2">
                  <li pn="section-toc.1-1.6.2.1.2.1">
                    <t indent="0" pn="section-toc.1-1.6.2.1.2.1.1"><xref derivedContent="6.1.1" format="counter" sectionFormat="of" target="section-6.1.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-registry-contents">Registry Contents</xref></t>
                  </li>
                </ul>
              </li>
              <li pn="section-toc.1-1.6.2.2">
                <t indent="0" pn="section-toc.1-1.6.2.2.1"><xref derivedContent="6.2" format="counter" sectionFormat="of" target="section-6.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-media-types">Media Types</xref></t>
              </li>
              <li pn="section-toc.1-1.6.2.3">
                <t indent="0" pn="section-toc.1-1.6.2.3.1"><xref derivedContent="6.3" format="counter" sectionFormat="of" target="section-6.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-application-eatcwt-registra">application/eat+cwt Registration</xref></t>
              </li>
              <li pn="section-toc.1-1.6.2.4">
                <t indent="0" pn="section-toc.1-1.6.2.4.1"><xref derivedContent="6.4" format="counter" sectionFormat="of" target="section-6.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-application-eatjwt-registra">application/eat+jwt Registration</xref></t>
              </li>
              <li pn="section-toc.1-1.6.2.5">
                <t indent="0" pn="section-toc.1-1.6.2.5.1"><xref derivedContent="6.5" format="counter" sectionFormat="of" target="section-6.5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-application-eat-buncbor-reg">application/eat-bun+cbor Registration</xref></t>
              </li>
              <li pn="section-toc.1-1.6.2.6">
                <t indent="0" pn="section-toc.1-1.6.2.6.1"><xref derivedContent="6.6" format="counter" sectionFormat="of" target="section-6.6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-application-eat-bunjson-reg">application/eat-bun+json Registration</xref></t>
              </li>
              <li pn="section-toc.1-1.6.2.7">
                <t indent="0" pn="section-toc.1-1.6.2.7.1"><xref derivedContent="6.7" format="counter" sectionFormat="of" target="section-6.7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-application-eat-ucscbor-reg">application/eat-ucs+cbor Registration</xref></t>
              </li>
              <li pn="section-toc.1-1.6.2.8">
                <t indent="0" pn="section-toc.1-1.6.2.8.1"><xref derivedContent="6.8" format="counter" sectionFormat="of" target="section-6.8"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-application-eat-ucsjson-reg">application/eat-ucs+json Registration</xref></t>
              </li>
              <li pn="section-toc.1-1.6.2.9">
                <t indent="0" pn="section-toc.1-1.6.2.9.1"><xref derivedContent="6.9" format="counter" sectionFormat="of" target="section-6.9"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-coap-content-format-registr">CoAP Content-Format Registrations</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.7">
            <t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="7" format="counter" sectionFormat="of" target="section-7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-references">References</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.7.2">
              <li pn="section-toc.1-1.7.2.1">
                <t indent="0" pn="section-toc.1-1.7.2.1.1"><xref derivedContent="7.1" format="counter" sectionFormat="of" target="section-7.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
              </li>
              <li pn="section-toc.1-1.7.2.2">
                <t indent="0" pn="section-toc.1-1.7.2.2.1"><xref derivedContent="7.2" format="counter" sectionFormat="of" target="section-7.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.8">
            <t indent="0" pn="section-toc.1-1.8.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgments">Acknowledgments</xref></t>
          </li>
          <li pn="section-toc.1-1.9">
            <t indent="0" pn="section-toc.1-1.9.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Addresses</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section anchor="introduction" numbered="true" removeInRFC="false" toc="include" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <t indent="0" pn="section-1-1">Payloads used in Remote ATtestation procedureS (RATS) <xref target="RFC9334" format="default" sectionFormat="of" derivedContent="RATS-ARCH"/> may require an
associated media type for their conveyance, for example, when used in RESTful
APIs (<xref target="fig-api-sd" format="default" sectionFormat="of" derivedContent="Figure 1"/>).</t>
      <figure anchor="fig-api-sd" align="left" suppress-title="false" pn="figure-1">
        <name slugifiedName="name-conveying-rats-conceptual-m">Conveying RATS Conceptual Messages in REST APIs Using EATs</name>
        <artset pn="section-1-2.1">
          <artwork type="svg" align="center" pn="section-1-2.1.1"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="288" width="512" viewBox="0 0 512 288" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
              <path d="M 8,32 L 8,64" fill="none" stroke="black"/>
              <path d="M 24,64 L 24,272" fill="none" stroke="black"/>
              <path d="M 136,32 L 136,64" fill="none" stroke="black"/>
              <path d="M 216,32 L 216,64" fill="none" stroke="black"/>
              <path d="M 256,64 L 256,272" fill="none" stroke="black"/>
              <path d="M 304,32 L 304,64" fill="none" stroke="black"/>
              <path d="M 416,32 L 416,64" fill="none" stroke="black"/>
              <path d="M 488,64 L 488,272" fill="none" stroke="black"/>
              <path d="M 504,32 L 504,64" fill="none" stroke="black"/>
              <path d="M 8,32 L 136,32" fill="none" stroke="black"/>
              <path d="M 216,32 L 304,32" fill="none" stroke="black"/>
              <path d="M 416,32 L 504,32" fill="none" stroke="black"/>
              <path d="M 8,64 L 136,64" fill="none" stroke="black"/>
              <path d="M 216,64 L 304,64" fill="none" stroke="black"/>
              <path d="M 416,64 L 504,64" fill="none" stroke="black"/>
              <path d="M 256,112 L 480,112" fill="none" stroke="black"/>
              <path d="M 264,160 L 488,160" fill="none" stroke="black"/>
              <path d="M 32,208 L 256,208" fill="none" stroke="black"/>
              <path d="M 24,240 L 248,240" fill="none" stroke="black"/>
              <polygon class="arrowhead" points="488,112 476,106.4 476,117.6" fill="black" transform="rotate(0,480,112)"/>
              <polygon class="arrowhead" points="272,160 260,154.4 260,165.6" fill="black" transform="rotate(180,264,160)"/>
              <polygon class="arrowhead" points="256,240 244,234.4 244,245.6" fill="black" transform="rotate(0,248,240)"/>
              <polygon class="arrowhead" points="40,208 28,202.4 28,213.6" fill="black" transform="rotate(180,32,208)"/>
              <g class="text">
                <text x="48" y="52">Relying</text>
                <text x="104" y="52">Party</text>
                <text x="260" y="52">Attester</text>
                <text x="460" y="52">Verifier</text>
                <text x="284" y="84">POST</text>
                <text x="336" y="84">/verify</text>
                <text x="320" y="100">EAT(Evidence)</text>
                <text x="440" y="132">200</text>
                <text x="468" y="132">OK</text>
                <text x="344" y="148">EAT(Attestation</text>
                <text x="444" y="148">Results)</text>
                <text x="180" y="180">POST</text>
                <text x="224" y="180">/auth</text>
                <text x="112" y="196">EAT(Attestation</text>
                <text x="212" y="196">Results)</text>
                <text x="48" y="228">201</text>
                <text x="96" y="228">Created</text>
              </g>
            </svg>
          </artwork>
          <artwork type="ascii-art" align="center" pn="section-1-2.1.2">
.---------------.         .----------.             .----------.
| Relying Party |         | Attester |             | Verifier |
'-+-------------'         '----+-----'             '--------+-'
  |                            | POST /verify               |
  |                            | EAT(Evidence)              |
  |                            +---------------------------&gt;|
  |                            |                     200 OK |
  |                            |   EAT(Attestation Results) |
  |                            |&lt;---------------------------+
  |                 POST /auth |                            |
  |   EAT(Attestation Results) |                            |
  |&lt;---------------------------+                            |
  | 201 Created                |                            |
  +---------------------------&gt;|                            |
  |                            |                            |
  |                            |                            |
</artwork>
        </artset>
      </figure>
      <t indent="0" pn="section-1-3">This memo defines media types to be used for EAT
payloads <xref target="RFC9711" format="default" sectionFormat="of" derivedContent="EAT"/> independently of the RATS Conceptual Message in which they
manifest themselves.  The objective is to give protocol, API, and application
designers a number of readily available and reusable media types for
integrating EAT-based messages in their flows, e.g., when using HTTP
<xref target="BCP56" format="default" sectionFormat="of" derivedContent="BUILD-W-HTTP"/> or the Constrained Application Protocol (CoAP) <xref target="I-D.irtf-t2trg-rest-iot" format="default" sectionFormat="of" derivedContent="REST-IoT"/>.</t>
      <section anchor="terminology" numbered="true" removeInRFC="false" toc="include" pn="section-1.1">
        <name slugifiedName="name-terminology">Terminology</name>
        <t indent="0" pn="section-1.1-1">This document uses the terms and concepts defined in <xref target="RFC9334" format="default" sectionFormat="of" derivedContent="RATS-ARCH"/>.</t>
      </section>
    </section>
    <section anchor="eat-types" numbered="true" removeInRFC="false" toc="include" pn="section-2">
      <name slugifiedName="name-eat-types">EAT Types</name>
      <t indent="0" pn="section-2-1"><xref target="fig-eat-types" format="default" sectionFormat="of" derivedContent="Figure 2"/> illustrates the six EAT wire formats and how they relate to
each other.  <xref target="RFC9711" format="default" sectionFormat="of" derivedContent="EAT"/> defines four of them (CBOR Web Token (CWT), JSON Web Token (JWT), and the detached EAT bundle in
its JSON and CBOR flavours), while <xref target="RFC9781" format="default" sectionFormat="of" derivedContent="UCCS"/> defines the Unprotected CWT Claims Set (UCCS) and Unprotected JWT Claims Sets (UJCS).</t>
      <figure anchor="fig-eat-types" align="left" suppress-title="false" pn="figure-2">
        <name slugifiedName="name-eat-types-2">EAT Types</name>
        <artset pn="section-2-2.1">
          <artwork type="svg" align="center" pn="section-2-2.1.1"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" height="544" width="520" viewBox="0 0 520 544" class="diagram" text-anchor="middle" font-family="monospace" font-size="13px" stroke-linecap="round">
              <path d="M 8,432 L 8,464" fill="none" stroke="black"/>
              <path d="M 72,64 L 72,424" fill="none" stroke="black"/>
              <path d="M 120,48 L 120,64" fill="none" stroke="black"/>
              <path d="M 120,112 L 120,128" fill="none" stroke="black"/>
              <path d="M 120,176 L 120,192" fill="none" stroke="black"/>
              <path d="M 120,240 L 120,256" fill="none" stroke="black"/>
              <path d="M 120,304 L 120,320" fill="none" stroke="black"/>
              <path d="M 120,368 L 120,384" fill="none" stroke="black"/>
              <path d="M 128,432 L 128,464" fill="none" stroke="black"/>
              <path d="M 176,32 L 176,48" fill="none" stroke="black"/>
              <path d="M 176,96 L 176,112" fill="none" stroke="black"/>
              <path d="M 184,160 L 184,176" fill="none" stroke="black"/>
              <path d="M 184,224 L 184,240" fill="none" stroke="black"/>
              <path d="M 184,288 L 184,304" fill="none" stroke="black"/>
              <path d="M 184,352 L 184,368" fill="none" stroke="black"/>
              <path d="M 240,512 L 240,528" fill="none" stroke="black"/>
              <path d="M 272,360 L 272,448" fill="none" stroke="black"/>
              <path d="M 328,496 L 328,512" fill="none" stroke="black"/>
              <path d="M 336,256 L 336,288" fill="none" stroke="black"/>
              <path d="M 352,368 L 352,400" fill="none" stroke="black"/>
              <path d="M 360,496 L 360,528" fill="none" stroke="black"/>
              <path d="M 368,224 L 368,256" fill="none" stroke="black"/>
              <path d="M 368,288 L 368,320" fill="none" stroke="black"/>
              <path d="M 384,128 L 384,256" fill="none" stroke="black"/>
              <path d="M 384,296 L 384,368" fill="none" stroke="black"/>
              <path d="M 384,408 L 384,432" fill="none" stroke="black"/>
              <path d="M 400,64 L 400,256" fill="none" stroke="black"/>
              <path d="M 400,288 L 400,360" fill="none" stroke="black"/>
              <path d="M 416,496 L 416,528" fill="none" stroke="black"/>
              <path d="M 424,368 L 424,400" fill="none" stroke="black"/>
              <path d="M 440,256 L 440,288" fill="none" stroke="black"/>
              <path d="M 472,288 L 472,312" fill="none" stroke="black"/>
              <path d="M 472,352 L 472,368" fill="none" stroke="black"/>
              <path d="M 136,32 L 176,32" fill="none" stroke="black"/>
              <path d="M 88,48 L 120,48" fill="none" stroke="black"/>
              <path d="M 184,48 L 384,48" fill="none" stroke="black"/>
              <path d="M 120,64 L 160,64" fill="none" stroke="black"/>
              <path d="M 136,96 L 176,96" fill="none" stroke="black"/>
              <path d="M 72,112 L 120,112" fill="none" stroke="black"/>
              <path d="M 184,112 L 368,112" fill="none" stroke="black"/>
              <path d="M 120,128 L 160,128" fill="none" stroke="black"/>
              <path d="M 136,160 L 184,160" fill="none" stroke="black"/>
              <path d="M 72,176 L 120,176" fill="none" stroke="black"/>
              <path d="M 192,176 L 240,176" fill="none" stroke="black"/>
              <path d="M 120,192 L 168,192" fill="none" stroke="black"/>
              <path d="M 240,192 L 280,192" fill="none" stroke="black"/>
              <path d="M 304,208 L 352,208" fill="none" stroke="black"/>
              <path d="M 136,224 L 184,224" fill="none" stroke="black"/>
              <path d="M 240,224 L 280,224" fill="none" stroke="black"/>
              <path d="M 72,240 L 120,240" fill="none" stroke="black"/>
              <path d="M 192,240 L 240,240" fill="none" stroke="black"/>
              <path d="M 120,256 L 168,256" fill="none" stroke="black"/>
              <path d="M 336,256 L 440,256" fill="none" stroke="black"/>
              <path d="M 440,272 L 456,272" fill="none" stroke="black"/>
              <path d="M 136,288 L 184,288" fill="none" stroke="black"/>
              <path d="M 336,288 L 440,288" fill="none" stroke="black"/>
              <path d="M 72,304 L 120,304" fill="none" stroke="black"/>
              <path d="M 192,304 L 240,304" fill="none" stroke="black"/>
              <path d="M 120,320 L 168,320" fill="none" stroke="black"/>
              <path d="M 240,320 L 280,320" fill="none" stroke="black"/>
              <path d="M 456,320 L 496,320" fill="none" stroke="black"/>
              <path d="M 304,336 L 352,336" fill="none" stroke="black"/>
              <path d="M 136,352 L 184,352" fill="none" stroke="black"/>
              <path d="M 240,352 L 280,352" fill="none" stroke="black"/>
              <path d="M 456,352 L 496,352" fill="none" stroke="black"/>
              <path d="M 72,368 L 120,368" fill="none" stroke="black"/>
              <path d="M 192,368 L 240,368" fill="none" stroke="black"/>
              <path d="M 352,368 L 424,368" fill="none" stroke="black"/>
              <path d="M 120,384 L 168,384" fill="none" stroke="black"/>
              <path d="M 432,384 L 456,384" fill="none" stroke="black"/>
              <path d="M 352,400 L 424,400" fill="none" stroke="black"/>
              <path d="M 8,432 L 128,432" fill="none" stroke="black"/>
              <path d="M 128,448 L 368,448" fill="none" stroke="black"/>
              <path d="M 8,464 L 128,464" fill="none" stroke="black"/>
              <path d="M 144,496 L 192,496" fill="none" stroke="black"/>
              <path d="M 256,496 L 328,496" fill="none" stroke="black"/>
              <path d="M 360,496 L 416,496" fill="none" stroke="black"/>
              <path d="M 144,528 L 192,528" fill="none" stroke="black"/>
              <path d="M 240,528 L 312,528" fill="none" stroke="black"/>
              <path d="M 360,528 L 416,528" fill="none" stroke="black"/>
              <path d="M 136,32 C 127.16936,32 120,39.16936 120,48" fill="none" stroke="black"/>
              <path d="M 88,48 C 79.16936,48 72,55.16936 72,64" fill="none" stroke="black"/>
              <path d="M 384,48 C 392.83064,48 400,55.16936 400,64" fill="none" stroke="black"/>
              <path d="M 160,64 C 168.83064,64 176,56.83064 176,48" fill="none" stroke="black"/>
              <path d="M 136,96 C 127.16936,96 120,103.16936 120,112" fill="none" stroke="black"/>
              <path d="M 368,112 C 376.83064,112 384,119.16936 384,128" fill="none" stroke="black"/>
              <path d="M 160,128 C 168.83064,128 176,120.83064 176,112" fill="none" stroke="black"/>
              <path d="M 136,160 C 127.16936,160 120,167.16936 120,176" fill="none" stroke="black"/>
              <path d="M 240,176 C 248.83064,176 256,183.16936 256,192" fill="none" stroke="black"/>
              <path d="M 168,192 C 176.83064,192 184,184.83064 184,176" fill="none" stroke="black"/>
              <path d="M 240,192 C 231.16936,192 224,199.16936 224,208" fill="none" stroke="black"/>
              <path d="M 280,192 C 288.83064,192 296,199.16936 296,208" fill="none" stroke="black"/>
              <path d="M 352,208 C 360.83064,208 368,215.16936 368,224" fill="none" stroke="black"/>
              <path d="M 136,224 C 127.16936,224 120,231.16936 120,240" fill="none" stroke="black"/>
              <path d="M 240,224 C 231.16936,224 224,216.83064 224,208" fill="none" stroke="black"/>
              <path d="M 280,224 C 288.83064,224 296,216.83064 296,208" fill="none" stroke="black"/>
              <path d="M 240,240 C 248.83064,240 256,232.83064 256,224" fill="none" stroke="black"/>
              <path d="M 168,256 C 176.83064,256 184,248.83064 184,240" fill="none" stroke="black"/>
              <path d="M 456,272 C 464.83064,272 472,279.16936 472,288" fill="none" stroke="black"/>
              <path d="M 136,288 C 127.16936,288 120,295.16936 120,304" fill="none" stroke="black"/>
              <path d="M 240,304 C 248.83064,304 256,311.16936 256,320" fill="none" stroke="black"/>
              <path d="M 168,320 C 176.83064,320 184,312.83064 184,304" fill="none" stroke="black"/>
              <path d="M 240,320 C 231.16936,320 224,327.16936 224,336" fill="none" stroke="black"/>
              <path d="M 280,320 C 288.83064,320 296,327.16936 296,336" fill="none" stroke="black"/>
              <path d="M 456,320 C 447.16936,320 440,327.16936 440,336" fill="none" stroke="black"/>
              <path d="M 496,320 C 504.83064,320 512,327.16936 512,336" fill="none" stroke="black"/>
              <path d="M 352,336 C 360.83064,336 368,328.83064 368,320" fill="none" stroke="black"/>
              <path d="M 136,352 C 127.16936,352 120,359.16936 120,368" fill="none" stroke="black"/>
              <path d="M 240,352 C 231.16936,352 224,344.83064 224,336" fill="none" stroke="black"/>
              <path d="M 280,352 C 288.83064,352 296,344.83064 296,336" fill="none" stroke="black"/>
              <path d="M 456,352 C 447.16936,352 440,344.83064 440,336" fill="none" stroke="black"/>
              <path d="M 496,352 C 504.83064,352 512,344.83064 512,336" fill="none" stroke="black"/>
              <path d="M 240,368 C 248.83064,368 256,360.83064 256,352" fill="none" stroke="black"/>
              <path d="M 168,384 C 176.83064,384 184,376.83064 184,368" fill="none" stroke="black"/>
              <path d="M 456,384 C 464.83064,384 472,376.83064 472,368" fill="none" stroke="black"/>
              <path d="M 368,448 C 376.83064,448 384,440.83064 384,432" fill="none" stroke="black"/>
              <path d="M 144,496 C 135.16936,496 128,503.16936 128,512" fill="none" stroke="black"/>
              <path d="M 192,496 C 200.83064,496 208,503.16936 208,512" fill="none" stroke="black"/>
              <path d="M 256,496 C 247.16936,496 240,503.16936 240,512" fill="none" stroke="black"/>
              <path d="M 144,528 C 135.16936,528 128,520.83064 128,512" fill="none" stroke="black"/>
              <path d="M 192,528 C 200.83064,528 208,520.83064 208,512" fill="none" stroke="black"/>
              <path d="M 312,528 C 320.83064,528 328,520.83064 328,512" fill="none" stroke="black"/>
              <polygon class="arrowhead" points="480,312 468,306.4 468,317.6" fill="black" transform="rotate(90,472,312)"/>
              <polygon class="arrowhead" points="440,384 428,378.4 428,389.6" fill="black" transform="rotate(180,432,384)"/>
              <polygon class="arrowhead" points="408,360 396,354.4 396,365.6" fill="black" transform="rotate(90,400,360)"/>
              <polygon class="arrowhead" points="392,408 380,402.4 380,413.6" fill="black" transform="rotate(270,384,408)"/>
              <polygon class="arrowhead" points="392,296 380,290.4 380,301.6" fill="black" transform="rotate(270,384,296)"/>
              <polygon class="arrowhead" points="312,336 300,330.4 300,341.6" fill="black" transform="rotate(180,304,336)"/>
              <polygon class="arrowhead" points="312,208 300,202.4 300,213.6" fill="black" transform="rotate(180,304,208)"/>
              <polygon class="arrowhead" points="280,360 268,354.4 268,365.6" fill="black" transform="rotate(270,272,360)"/>
              <polygon class="arrowhead" points="200,368 188,362.4 188,373.6" fill="black" transform="rotate(180,192,368)"/>
              <polygon class="arrowhead" points="200,304 188,298.4 188,309.6" fill="black" transform="rotate(180,192,304)"/>
              <polygon class="arrowhead" points="200,240 188,234.4 188,245.6" fill="black" transform="rotate(180,192,240)"/>
              <polygon class="arrowhead" points="200,176 188,170.4 188,181.6" fill="black" transform="rotate(180,192,176)"/>
              <polygon class="arrowhead" points="192,112 180,106.4 180,117.6" fill="black" transform="rotate(180,184,112)"/>
              <polygon class="arrowhead" points="192,48 180,42.4 180,53.6" fill="black" transform="rotate(180,184,48)"/>
              <polygon class="arrowhead" points="80,424 68,418.4 68,429.6" fill="black" transform="rotate(90,72,424)"/>
              <g class="text">
                <text x="148" y="52">UJCS</text>
                <text x="148" y="116">UCCS</text>
                <text x="152" y="180">JWT</text>
                <text x="260" y="212">Crypto</text>
                <text x="152" y="244">CWT</text>
                <text x="388" y="276">Claims-Set</text>
                <text x="152" y="308">BUN-J</text>
                <text x="260" y="340">Bundle</text>
                <text x="476" y="340">Digest</text>
                <text x="152" y="372">BUN-C</text>
                <text x="388" y="388">submod</text>
                <text x="68" y="452">Nested-Token</text>
                <text x="76" y="516">Legend:</text>
                <text x="168" y="516">Process</text>
                <text x="268" y="516">Wire</text>
                <text x="304" y="516">Fmt</text>
                <text x="388" y="516">CDDL</text>
              </g>
            </svg>
          </artwork>
          <artwork type="ascii-art" align="center" pn="section-2-2.1.2">
               .-----.
         .----+ UJCS |&lt;-------------------------.
        |     '-----'                            |
        |                                        |
        |      .-----.                           |
        +-----+ UCCS |&lt;-----------------------.  |
        |     '-----'                          | |
        |                                      | |
        |      .------.                        | |
        +-----+  JWT  |&lt;------.                | |
        |     '------'      .--+---.           | |
        |                  | Crypto |&lt;------.  | |
        |      .------.     '--+---'         | | |
        +-----+  CWT  |&lt;------'              | | |
        |     '------'                   .---+-+-+----.
        |                                | Claims-Set +--.
        |      .------.                  '---+---+----'   |
        +-----+ BUN-J |&lt;------.              | ^ |        v
        |     '------'      .--+---.         | | |     .------.
        |                  | Bundle |&lt;------'  | |    | Digest |
        |      .------.     '--+---'           | v     '--+---'
        +-----+ BUN-C |&lt;------'  ^         .---+----.     |
        |     '------'           |         | submod |&lt;---'
        |                        |         '--------'
        v                        |             ^
.--------------.                 |             |
| Nested-Token +-----------------+------------'
'--------------'

                .-------.     .---------.   .------.
     Legend:   | Process |   | Wire Fmt |   | CDDL |
                '-------'    '---------'    '------'
</artwork>
        </artset>
      </figure>
    </section>
    <section anchor="a-media-type-parameter-for-eat-profiles" numbered="true" removeInRFC="false" toc="include" pn="section-3">
      <name slugifiedName="name-a-media-type-parameter-for-">A Media Type Parameter for EAT Profiles</name>
      <t indent="0" pn="section-3-1">EAT is an open and flexible format.  To improve interoperability, <xref section="6" sectionFormat="of" target="RFC9711" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9711#section-6" derivedContent="EAT"/> defines the concept of EAT profiles.  Profiles are used to constrain
the parameters that producers and consumers of a specific EAT profile need to
understand in order to interoperate, e.g., the number and type of
claims, which serialisation format, the supported signature schemes, etc.  EATs
carry an in-band profile identifier using the "eat_profile" claim (see
<xref section="4.3.2" sectionFormat="of" target="RFC9711" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9711#section-4.3.2" derivedContent="EAT"/>).  The value of the "eat_profile" claim is either an
OID or a URI.</t>
      <t indent="0" pn="section-3-2">The media types defined in this document include an optional "eat_profile"
parameter that can be used to mirror the "eat_profile" claim of the transported
EAT.  Exposing the EAT profile at the API layer allows API routers to dispatch
payloads directly to the profile-specific processor without having to snoop
into the request bodies.  This design also provides a finer-grained and
scalable type system that matches the inherent extensibility of EAT.  The
expectation being that a certain EAT profile automatically obtains a media type
derived from the base (e.g., <tt>application/eat+cwt</tt>) by populating the
"eat_profile" parameter with the corresponding OID or URL.</t>
      <t indent="0" pn="section-3-3">When the parameterised version of the EAT media type is used in HTTP (for
example, with the "Content-Type" and "Accept" headers) and the value is an
absolute URI (<xref section="4.3" sectionFormat="of" target="RFC3986" format="default" derivedLink="https://rfc-editor.org/rfc/rfc3986#section-4.3" derivedContent="URI"/>), the <tt>parameter-value</tt> (<xref section="A" sectionFormat="of" target="RFC9110" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9110#appendix-A" derivedContent="HTTP"/>) uses the <tt>quoted-string</tt> encoding, for example:</t>
      <t indent="5" pn="section-3-4"><tt>application/eat+jwt; eat_profile="tag:evidence.example,2022"</tt></t>
      <t indent="0" pn="section-3-5">Instead, when the EAT profile is an OID, the <tt>token</tt> encoding
      (i.e., without quotes) can be used. For example:</t>
      <t indent="5" pn="section-3-6"><tt>application/eat+cwt; eat_profile=2.999.1</tt>.</t>
    </section>
    <section anchor="examples" numbered="true" removeInRFC="false" toc="include" pn="section-4">
      <name slugifiedName="name-examples">Examples</name>
      <t indent="0" pn="section-4-1">The example in <xref target="fig-rest-req" format="default" sectionFormat="of" derivedContent="Figure 3"/> illustrates the usage of EAT media types for
transporting attestation evidence as well as negotiating the acceptable format
of the attestation result.</t>
      <figure anchor="fig-rest-req" align="left" suppress-title="false" pn="figure-3">
        <name slugifiedName="name-example-rest-verification-a">Example REST Verification API (request)</name>
        <sourcecode type="http-message" markers="false" pn="section-4-2.1">
NOTE: '\' line wrapping per RFC 8792

POST /challenge-response/v1/session/1234567890 HTTP/1.1
Host: verifier.example
Accept: application/eat+cwt; eat_profile="tag:ar4si.example,2021"
Content-Type: application/eat+cwt; \
              eat_profile="tag:evidence.example,2022"

[ CBOR-encoded EAT w/ eat_profile="tag:evidence.example,2022" ]
</sourcecode>
      </figure>
      <t indent="0" pn="section-4-3">The example in <xref target="fig-rest-rsp" format="default" sectionFormat="of" derivedContent="Figure 4"/> illustrates the usage of EAT media types for
transporting attestation results.</t>
      <figure anchor="fig-rest-rsp" align="left" suppress-title="false" pn="figure-4">
        <name slugifiedName="name-example-rest-verification-ap">Example REST Verification API (response)</name>
        <sourcecode type="http-message" markers="false" pn="section-4-4.1">
NOTE: '\' line wrapping per RFC 8792

HTTP/1.1 200 OK
Content-Type: application/eat+cwt; \
              eat_profile="tag:ar4si.example,2021"

[ CBOR-encoded EAT w/ eat_profile="tag:ar4si.example,2021" ]
</sourcecode>
      </figure>
      <t indent="0" pn="section-4-5">In both cases, a tag URI <xref target="RFC4151" format="default" sectionFormat="of" derivedContent="TAG"/> identifying the profile is carried as an
explicit parameter.</t>
    </section>
    <section anchor="seccons" numbered="true" removeInRFC="false" toc="include" pn="section-5">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-5-1">Media types only provide clues to the processing application. The application
must verify that the received data matches the expected format, regardless of
the advertised media type, and stop further processing on failure. Failing to
do so could expose the user to security risks, such as privilege escalation
and cross-protocol attacks.</t>
      <t indent="0" pn="section-5-2">The security considerations of <xref target="RFC9711" format="default" sectionFormat="of" derivedContent="EAT"/> and <xref target="RFC9781" format="default" sectionFormat="of" derivedContent="UCCS"/> apply in full.</t>
      <t indent="0" pn="section-5-3">When using <tt>application/eat-ucs+json</tt> and <tt>application/eat-ucs+cbor</tt> in particular, the reader should review <xref section="3" sectionFormat="of" target="RFC9781" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9781#section-3" derivedContent="UCCS"/>, which contains a detailed discussion about the characteristics of a "Secure Channel" for conveyance of such messages.</t>
    </section>
    <section anchor="iana-considerations" numbered="true" removeInRFC="false" toc="include" pn="section-6">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <section anchor="cwt-structured-syntax-suffix" numbered="true" removeInRFC="false" toc="include" pn="section-6.1">
        <name slugifiedName="name-cwt-structured-syntax-suffi"><tt>+cwt</tt> Structured Syntax Suffix</name>
        <t indent="0" pn="section-6.1-1">IANA has registered <tt>+cwt</tt> in the
"Structured Syntax Suffixes" registry <xref target="STRUCT-SYNTAX" format="default" sectionFormat="of" derivedContent="STRUCT-SYNTAX"/> in
the manner described in <xref target="RFC6838" format="default" sectionFormat="of" derivedContent="MEDIATYPES"/>.  <tt>+cwt</tt> can be used to indicate that the
media type is encoded as a CWT.</t>
        <section anchor="registry-contents" numbered="true" removeInRFC="false" toc="include" pn="section-6.1.1">
          <name slugifiedName="name-registry-contents">Registry Contents</name>
          <dl spacing="normal" newline="false" indent="3" pn="section-6.1.1-1">
            <dt pn="section-6.1.1-1.1">Name:</dt>
            <dd pn="section-6.1.1-1.2">
              <t indent="0" pn="section-6.1.1-1.2.1">CBOR Web Token (CWT)</t>
            </dd>
            <dt pn="section-6.1.1-1.3">+suffix:</dt>
            <dd pn="section-6.1.1-1.4">
              <t indent="0" pn="section-6.1.1-1.4.1"><tt>+cwt</tt></t>
            </dd>
            <dt pn="section-6.1.1-1.5">References:</dt>
            <dd pn="section-6.1.1-1.6">
              <t indent="0" pn="section-6.1.1-1.6.1"><xref target="RFC8392" format="default" sectionFormat="of" derivedContent="CWT"/></t>
            </dd>
            <dt pn="section-6.1.1-1.7">Encoding Considerations:</dt>
            <dd pn="section-6.1.1-1.8">
              <t indent="0" pn="section-6.1.1-1.8.1">binary</t>
            </dd>
            <dt pn="section-6.1.1-1.9">Interoperability Considerations:</dt>
            <dd pn="section-6.1.1-1.10">
              <t indent="0" pn="section-6.1.1-1.10.1">N/A</t>
            </dd>
            <dt pn="section-6.1.1-1.11">Fragment Identifier Considerations:</dt>
            <dd pn="section-6.1.1-1.12">
              <t indent="0" pn="section-6.1.1-1.12.1">The syntax and semantics of fragment identifiers specified for <tt>+cwt</tt> SHOULD be
as specified for <tt>application/cwt</tt>.  (At the time of publication, there
is no fragment identification syntax defined for <tt>application/cwt</tt>.)</t>
            </dd>
            <dt pn="section-6.1.1-1.13">Security Considerations:</dt>
            <dd pn="section-6.1.1-1.14">
              <t indent="0" pn="section-6.1.1-1.14.1">See <xref section="8" sectionFormat="of" target="RFC8392" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8392#section-8" derivedContent="CWT"/></t>
            </dd>
            <dt pn="section-6.1.1-1.15">Contact:</dt>
            <dd pn="section-6.1.1-1.16">
              <t indent="0" pn="section-6.1.1-1.16.1">RATS WG mailing list (rats@ietf.org), or IETF Security Area (saag@ietf.org)</t>
            </dd>
            <dt pn="section-6.1.1-1.17">Author/Change Controller:</dt>
            <dd pn="section-6.1.1-1.18">
              <t indent="0" pn="section-6.1.1-1.18.1">Remote ATtestation ProcedureS (RATS) Working Group.
The IETF has change control over this registration.</t>
            </dd>
          </dl>
        </section>
      </section>
      <section anchor="media-type" numbered="true" removeInRFC="false" toc="include" pn="section-6.2">
        <name slugifiedName="name-media-types">Media Types</name>
        <t indent="0" pn="section-6.2-1">IANA has registered the following media types in the
"Media Types" registry <xref target="MEDIA-TYPES" format="default" sectionFormat="of" derivedContent="MEDIA-TYPES"/>.</t>
        <table align="center" anchor="new-media-type" pn="table-1">
          <name slugifiedName="name-new-media-types">New Media Types</name>
          <thead>
            <tr>
              <th align="left" colspan="1" rowspan="1">Name</th>
              <th align="left" colspan="1" rowspan="1">Template</th>
              <th align="left" colspan="1" rowspan="1">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left" colspan="1" rowspan="1">EAT CWT</td>
              <td align="left" colspan="1" rowspan="1">application/eat+cwt</td>
              <td align="left" colspan="1" rowspan="1">RFC 9782, <xref target="media-type-eat-cwt" format="default" sectionFormat="of" derivedContent="Section 6.3"/></td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">EAT JWT</td>
              <td align="left" colspan="1" rowspan="1">application/eat+jwt</td>
              <td align="left" colspan="1" rowspan="1">RFC 9782, <xref target="media-type-eat-jwt" format="default" sectionFormat="of" derivedContent="Section 6.4"/></td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">Detached EAT Bundle CBOR</td>
              <td align="left" colspan="1" rowspan="1">application/eat-bun+cbor</td>
              <td align="left" colspan="1" rowspan="1">RFC 9782, <xref target="media-type-deb-cbor" format="default" sectionFormat="of" derivedContent="Section 6.5"/></td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">Detached EAT Bundle JSON</td>
              <td align="left" colspan="1" rowspan="1">application/eat-bun+json</td>
              <td align="left" colspan="1" rowspan="1">RFC 9782, <xref target="media-type-deb-json" format="default" sectionFormat="of" derivedContent="Section 6.6"/></td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">EAT UCCS</td>
              <td align="left" colspan="1" rowspan="1">application/eat-ucs+cbor</td>
              <td align="left" colspan="1" rowspan="1">RFC 9782, <xref target="media-type-ucs-cbor" format="default" sectionFormat="of" derivedContent="Section 6.7"/></td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">EAT UJCS</td>
              <td align="left" colspan="1" rowspan="1">application/eat-ucs+json</td>
              <td align="left" colspan="1" rowspan="1">RFC 9782, <xref target="media-type-ucs-json" format="default" sectionFormat="of" derivedContent="Section 6.8"/></td>
            </tr>
          </tbody>
        </table>
      </section>
      <section anchor="media-type-eat-cwt" numbered="true" removeInRFC="false" toc="include" pn="section-6.3">
        <name slugifiedName="name-application-eatcwt-registra">application/eat+cwt Registration</name>
        <dl spacing="normal" newline="false" indent="3" pn="section-6.3-1">
          <dt pn="section-6.3-1.1">Type name:</dt>
          <dd pn="section-6.3-1.2">
            <t indent="0" pn="section-6.3-1.2.1">application</t>
          </dd>
          <dt pn="section-6.3-1.3">Subtype name:</dt>
          <dd pn="section-6.3-1.4">
            <t indent="0" pn="section-6.3-1.4.1">eat+cwt</t>
          </dd>
          <dt pn="section-6.3-1.5">Required parameters:</dt>
          <dd pn="section-6.3-1.6">
            <t indent="0" pn="section-6.3-1.6.1">N/A</t>
          </dd>
          <dt pn="section-6.3-1.7">Optional parameters:</dt>
          <dd pn="section-6.3-1.8">
            <t indent="0" pn="section-6.3-1.8.1">"eat_profile" (EAT profile in string format.  OIDs must use the
dotted-decimal notation.  The parameter value is case insensitive.)</t>
          </dd>
          <dt pn="section-6.3-1.9">Encoding considerations:</dt>
          <dd pn="section-6.3-1.10">
            <t indent="0" pn="section-6.3-1.10.1">binary</t>
          </dd>
          <dt pn="section-6.3-1.11">Security considerations:</dt>
          <dd pn="section-6.3-1.12">
            <t indent="0" pn="section-6.3-1.12.1"><xref section="9" sectionFormat="of" target="RFC9711" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9711#section-9" derivedContent="EAT"/></t>
          </dd>
          <dt pn="section-6.3-1.13">Interoperability considerations:</dt>
          <dd pn="section-6.3-1.14">
            <t indent="0" pn="section-6.3-1.14.1">N/A</t>
          </dd>
          <dt pn="section-6.3-1.15">Published specification:</dt>
          <dd pn="section-6.3-1.16">
            <t indent="0" pn="section-6.3-1.16.1">RFC 9782</t>
          </dd>
          <dt pn="section-6.3-1.17">Applications that use this media type:</dt>
          <dd pn="section-6.3-1.18">
            <t indent="0" pn="section-6.3-1.18.1">Attesters, Verifiers, Endorsers and Reference-Value providers, and Relying
Parties that need to transfer EAT payloads over HTTP(S), CoAP(S), and other
transports.</t>
          </dd>
          <dt pn="section-6.3-1.19">Fragment identifier considerations:</dt>
          <dd pn="section-6.3-1.20">
            <t indent="0" pn="section-6.3-1.20.1">N/A</t>
          </dd>
          <dt pn="section-6.3-1.21">Person &amp; email address to contact for further information:</dt>
          <dd pn="section-6.3-1.22">
            <t indent="0" pn="section-6.3-1.22.1">RATS WG mailing list (rats@ietf.org)</t>
          </dd>
          <dt pn="section-6.3-1.23">Intended usage:</dt>
          <dd pn="section-6.3-1.24">
            <t indent="0" pn="section-6.3-1.24.1">COMMON</t>
          </dd>
          <dt pn="section-6.3-1.25">Restrictions on usage:</dt>
          <dd pn="section-6.3-1.26">
            <t indent="0" pn="section-6.3-1.26.1">none</t>
          </dd>
          <dt pn="section-6.3-1.27">Author/Change controller:</dt>
          <dd pn="section-6.3-1.28">
            <t indent="0" pn="section-6.3-1.28.1">IETF</t>
          </dd>
          <dt pn="section-6.3-1.29">Provisional registration:</dt>
          <dd pn="section-6.3-1.30">
            <t indent="0" pn="section-6.3-1.30.1">no</t>
          </dd>
        </dl>
      </section>
      <section anchor="media-type-eat-jwt" numbered="true" removeInRFC="false" toc="include" pn="section-6.4">
        <name slugifiedName="name-application-eatjwt-registra">application/eat+jwt Registration</name>
        <dl spacing="normal" newline="false" indent="3" pn="section-6.4-1">
          <dt pn="section-6.4-1.1">Type name:</dt>
          <dd pn="section-6.4-1.2">
            <t indent="0" pn="section-6.4-1.2.1">application</t>
          </dd>
          <dt pn="section-6.4-1.3">Subtype name:</dt>
          <dd pn="section-6.4-1.4">
            <t indent="0" pn="section-6.4-1.4.1">eat+jwt</t>
          </dd>
          <dt pn="section-6.4-1.5">Required parameters:</dt>
          <dd pn="section-6.4-1.6">
            <t indent="0" pn="section-6.4-1.6.1">N/A</t>
          </dd>
          <dt pn="section-6.4-1.7">Optional parameters:</dt>
          <dd pn="section-6.4-1.8">
            <t indent="0" pn="section-6.4-1.8.1">"eat_profile" (EAT profile in string format.  OIDs must use the
dotted-decimal notation.  The parameter value is case insensitive.)</t>
          </dd>
          <dt pn="section-6.4-1.9">Encoding considerations:</dt>
          <dd pn="section-6.4-1.10">
            <t indent="0" pn="section-6.4-1.10.1">8bit</t>
          </dd>
          <dt pn="section-6.4-1.11">Security considerations:</dt>
          <dd pn="section-6.4-1.12">
            <t indent="0" pn="section-6.4-1.12.1"><xref section="9" sectionFormat="of" target="RFC9711" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9711#section-9" derivedContent="EAT"/> and <xref target="BCP225" format="default" sectionFormat="of" derivedContent="BCP225"/></t>
          </dd>
          <dt pn="section-6.4-1.13">Interoperability considerations:</dt>
          <dd pn="section-6.4-1.14">
            <t indent="0" pn="section-6.4-1.14.1">N/A</t>
          </dd>
          <dt pn="section-6.4-1.15">Published specification:</dt>
          <dd pn="section-6.4-1.16">
            <t indent="0" pn="section-6.4-1.16.1">RFC 9782</t>
          </dd>
          <dt pn="section-6.4-1.17">Applications that use this media type:</dt>
          <dd pn="section-6.4-1.18">
            <t indent="0" pn="section-6.4-1.18.1">Attesters, Verifiers, Endorsers and Reference-Value providers, and Relying
Parties that need to transfer EAT payloads over HTTP(S), CoAP(S), and other
transports.</t>
          </dd>
          <dt pn="section-6.4-1.19">Fragment identifier considerations:</dt>
          <dd pn="section-6.4-1.20">
            <t indent="0" pn="section-6.4-1.20.1">N/A</t>
          </dd>
          <dt pn="section-6.4-1.21">Person &amp; email address to contact for further information:</dt>
          <dd pn="section-6.4-1.22">
            <t indent="0" pn="section-6.4-1.22.1">RATS WG mailing list (rats@ietf.org)</t>
          </dd>
          <dt pn="section-6.4-1.23">Intended usage:</dt>
          <dd pn="section-6.4-1.24">
            <t indent="0" pn="section-6.4-1.24.1">COMMON</t>
          </dd>
          <dt pn="section-6.4-1.25">Restrictions on usage:</dt>
          <dd pn="section-6.4-1.26">
            <t indent="0" pn="section-6.4-1.26.1">none</t>
          </dd>
          <dt pn="section-6.4-1.27">Author/Change controller:</dt>
          <dd pn="section-6.4-1.28">
            <t indent="0" pn="section-6.4-1.28.1">IETF</t>
          </dd>
          <dt pn="section-6.4-1.29">Provisional registration:</dt>
          <dd pn="section-6.4-1.30">
            <t indent="0" pn="section-6.4-1.30.1">no</t>
          </dd>
        </dl>
      </section>
      <section anchor="media-type-deb-cbor" numbered="true" removeInRFC="false" toc="include" pn="section-6.5">
        <name slugifiedName="name-application-eat-buncbor-reg">application/eat-bun+cbor Registration</name>
        <dl spacing="normal" newline="false" indent="3" pn="section-6.5-1">
          <dt pn="section-6.5-1.1">Type name:</dt>
          <dd pn="section-6.5-1.2">
            <t indent="0" pn="section-6.5-1.2.1">application</t>
          </dd>
          <dt pn="section-6.5-1.3">Subtype name:</dt>
          <dd pn="section-6.5-1.4">
            <t indent="0" pn="section-6.5-1.4.1">eat-bun+cbor</t>
          </dd>
          <dt pn="section-6.5-1.5">Required parameters:</dt>
          <dd pn="section-6.5-1.6">
            <t indent="0" pn="section-6.5-1.6.1">N/A</t>
          </dd>
          <dt pn="section-6.5-1.7">Optional parameters:</dt>
          <dd pn="section-6.5-1.8">
            <t indent="0" pn="section-6.5-1.8.1">"eat_profile" (EAT profile in string format.  OIDs must use the
dotted-decimal notation.  The parameter value is case insensitive.)</t>
          </dd>
          <dt pn="section-6.5-1.9">Encoding considerations:</dt>
          <dd pn="section-6.5-1.10">
            <t indent="0" pn="section-6.5-1.10.1">binary</t>
          </dd>
          <dt pn="section-6.5-1.11">Security considerations:</dt>
          <dd pn="section-6.5-1.12">
            <t indent="0" pn="section-6.5-1.12.1"><xref section="9" sectionFormat="of" target="RFC9711" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9711#section-9" derivedContent="EAT"/></t>
          </dd>
          <dt pn="section-6.5-1.13">Interoperability considerations:</dt>
          <dd pn="section-6.5-1.14">
            <t indent="0" pn="section-6.5-1.14.1">N/A</t>
          </dd>
          <dt pn="section-6.5-1.15">Published specification:</dt>
          <dd pn="section-6.5-1.16">
            <t indent="0" pn="section-6.5-1.16.1">RFC 9782</t>
          </dd>
          <dt pn="section-6.5-1.17">Applications that use this media type:</dt>
          <dd pn="section-6.5-1.18">
            <t indent="0" pn="section-6.5-1.18.1">Attesters, Verifiers, Endorsers and Reference-Value providers, and Relying
Parties that need to transfer EAT payloads over HTTP(S), CoAP(S), and other
transports.</t>
          </dd>
          <dt pn="section-6.5-1.19">Fragment identifier considerations:</dt>
          <dd pn="section-6.5-1.20">
            <t indent="0" pn="section-6.5-1.20.1">N/A</t>
          </dd>
          <dt pn="section-6.5-1.21">Person &amp; email address to contact for further information:</dt>
          <dd pn="section-6.5-1.22">
            <t indent="0" pn="section-6.5-1.22.1">RATS WG mailing list (rats@ietf.org)</t>
          </dd>
          <dt pn="section-6.5-1.23">Intended usage:</dt>
          <dd pn="section-6.5-1.24">
            <t indent="0" pn="section-6.5-1.24.1">COMMON</t>
          </dd>
          <dt pn="section-6.5-1.25">Restrictions on usage:</dt>
          <dd pn="section-6.5-1.26">
            <t indent="0" pn="section-6.5-1.26.1">none</t>
          </dd>
          <dt pn="section-6.5-1.27">Author/Change controller:</dt>
          <dd pn="section-6.5-1.28">
            <t indent="0" pn="section-6.5-1.28.1">IETF</t>
          </dd>
          <dt pn="section-6.5-1.29">Provisional registration:</dt>
          <dd pn="section-6.5-1.30">
            <t indent="0" pn="section-6.5-1.30.1">no</t>
          </dd>
        </dl>
      </section>
      <section anchor="media-type-deb-json" numbered="true" removeInRFC="false" toc="include" pn="section-6.6">
        <name slugifiedName="name-application-eat-bunjson-reg">application/eat-bun+json Registration</name>
        <dl spacing="normal" newline="false" indent="3" pn="section-6.6-1">
          <dt pn="section-6.6-1.1">Type name:</dt>
          <dd pn="section-6.6-1.2">
            <t indent="0" pn="section-6.6-1.2.1">application</t>
          </dd>
          <dt pn="section-6.6-1.3">Subtype name:</dt>
          <dd pn="section-6.6-1.4">
            <t indent="0" pn="section-6.6-1.4.1">eat-bun+json</t>
          </dd>
          <dt pn="section-6.6-1.5">Required parameters:</dt>
          <dd pn="section-6.6-1.6">
            <t indent="0" pn="section-6.6-1.6.1">N/A</t>
          </dd>
          <dt pn="section-6.6-1.7">Optional parameters:</dt>
          <dd pn="section-6.6-1.8">
            <t indent="0" pn="section-6.6-1.8.1">"eat_profile" (EAT profile in string format.  OIDs must use the
dotted-decimal notation.  The parameter value is case insensitive.)</t>
          </dd>
          <dt pn="section-6.6-1.9">Encoding considerations:</dt>
          <dd pn="section-6.6-1.10">
            <t indent="0" pn="section-6.6-1.10.1">Same as <xref target="RFC8259" format="default" sectionFormat="of" derivedContent="JSON"/></t>
          </dd>
          <dt pn="section-6.6-1.11">Security considerations:</dt>
          <dd pn="section-6.6-1.12">
            <t indent="0" pn="section-6.6-1.12.1"><xref section="9" sectionFormat="of" target="RFC9711" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9711#section-9" derivedContent="EAT"/></t>
          </dd>
          <dt pn="section-6.6-1.13">Interoperability considerations:</dt>
          <dd pn="section-6.6-1.14">
            <t indent="0" pn="section-6.6-1.14.1">N/A</t>
          </dd>
          <dt pn="section-6.6-1.15">Published specification:</dt>
          <dd pn="section-6.6-1.16">
            <t indent="0" pn="section-6.6-1.16.1">RFC 9782</t>
          </dd>
          <dt pn="section-6.6-1.17">Applications that use this media type:</dt>
          <dd pn="section-6.6-1.18">
            <t indent="0" pn="section-6.6-1.18.1">Attesters, Verifiers, Endorsers and Reference-Value providers, and Relying
Parties that need to transfer EAT payloads over HTTP(S), CoAP(S), and other
transports.</t>
          </dd>
          <dt pn="section-6.6-1.19">Fragment identifier considerations:</dt>
          <dd pn="section-6.6-1.20">
            <t indent="0" pn="section-6.6-1.20.1">N/A</t>
          </dd>
          <dt pn="section-6.6-1.21">Person &amp; email address to contact for further information:</dt>
          <dd pn="section-6.6-1.22">
            <t indent="0" pn="section-6.6-1.22.1">RATS WG mailing list (rats@ietf.org)</t>
          </dd>
          <dt pn="section-6.6-1.23">Intended usage:</dt>
          <dd pn="section-6.6-1.24">
            <t indent="0" pn="section-6.6-1.24.1">COMMON</t>
          </dd>
          <dt pn="section-6.6-1.25">Restrictions on usage:</dt>
          <dd pn="section-6.6-1.26">
            <t indent="0" pn="section-6.6-1.26.1">none</t>
          </dd>
          <dt pn="section-6.6-1.27">Author/Change controller:</dt>
          <dd pn="section-6.6-1.28">
            <t indent="0" pn="section-6.6-1.28.1">IETF</t>
          </dd>
          <dt pn="section-6.6-1.29">Provisional registration:</dt>
          <dd pn="section-6.6-1.30">
            <t indent="0" pn="section-6.6-1.30.1">no</t>
          </dd>
        </dl>
      </section>
      <section anchor="media-type-ucs-cbor" numbered="true" removeInRFC="false" toc="include" pn="section-6.7">
        <name slugifiedName="name-application-eat-ucscbor-reg">application/eat-ucs+cbor Registration</name>
        <dl spacing="normal" newline="false" indent="3" pn="section-6.7-1">
          <dt pn="section-6.7-1.1">Type name:</dt>
          <dd pn="section-6.7-1.2">
            <t indent="0" pn="section-6.7-1.2.1">application</t>
          </dd>
          <dt pn="section-6.7-1.3">Subtype name:</dt>
          <dd pn="section-6.7-1.4">
            <t indent="0" pn="section-6.7-1.4.1">eat-ucs+cbor</t>
          </dd>
          <dt pn="section-6.7-1.5">Required parameters:</dt>
          <dd pn="section-6.7-1.6">
            <t indent="0" pn="section-6.7-1.6.1">N/A</t>
          </dd>
          <dt pn="section-6.7-1.7">Optional parameters:</dt>
          <dd pn="section-6.7-1.8">
            <t indent="0" pn="section-6.7-1.8.1">"eat_profile" (EAT profile in string format.  OIDs must use the
dotted-decimal notation.  The parameter value is case insensitive.)</t>
          </dd>
          <dt pn="section-6.7-1.9">Encoding considerations:</dt>
          <dd pn="section-6.7-1.10">
            <t indent="0" pn="section-6.7-1.10.1">binary</t>
          </dd>
          <dt pn="section-6.7-1.11">Security considerations:</dt>
          <dd pn="section-6.7-1.12">
            <t indent="0" pn="section-6.7-1.12.1">Sections <xref target="RFC9781" section="3" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9781#section-3" derivedContent="UCCS"/> and <xref target="RFC9781" section="7" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9781#section-7" derivedContent="UCCS"/> of <xref target="RFC9781" format="default" sectionFormat="of" derivedContent="UCCS"/></t>
          </dd>
          <dt pn="section-6.7-1.13">Interoperability considerations:</dt>
          <dd pn="section-6.7-1.14">
            <t indent="0" pn="section-6.7-1.14.1">N/A</t>
          </dd>
          <dt pn="section-6.7-1.15">Published specification:</dt>
          <dd pn="section-6.7-1.16">
            <t indent="0" pn="section-6.7-1.16.1">RFC 9782</t>
          </dd>
          <dt pn="section-6.7-1.17">Applications that use this media type:</dt>
          <dd pn="section-6.7-1.18">
            <t indent="0" pn="section-6.7-1.18.1">Attesters, Verifiers, Endorsers and Reference-Value providers, and Relying
Parties that need to transfer EAT payloads over HTTP(S), CoAP(S), and other
transports.</t>
          </dd>
          <dt pn="section-6.7-1.19">Fragment identifier considerations:</dt>
          <dd pn="section-6.7-1.20">
            <t indent="0" pn="section-6.7-1.20.1">N/A</t>
          </dd>
          <dt pn="section-6.7-1.21">Person &amp; email address to contact for further information:</dt>
          <dd pn="section-6.7-1.22">
            <t indent="0" pn="section-6.7-1.22.1">RATS WG mailing list (rats@ietf.org)</t>
          </dd>
          <dt pn="section-6.7-1.23">Intended usage:</dt>
          <dd pn="section-6.7-1.24">
            <t indent="0" pn="section-6.7-1.24.1">COMMON</t>
          </dd>
          <dt pn="section-6.7-1.25">Restrictions on usage:</dt>
          <dd pn="section-6.7-1.26">
            <t indent="0" pn="section-6.7-1.26.1">none</t>
          </dd>
          <dt pn="section-6.7-1.27">Author/Change controller:</dt>
          <dd pn="section-6.7-1.28">
            <t indent="0" pn="section-6.7-1.28.1">IETF</t>
          </dd>
          <dt pn="section-6.7-1.29">Provisional registration:</dt>
          <dd pn="section-6.7-1.30">
            <t indent="0" pn="section-6.7-1.30.1">no</t>
          </dd>
        </dl>
      </section>
      <section anchor="media-type-ucs-json" numbered="true" removeInRFC="false" toc="include" pn="section-6.8">
        <name slugifiedName="name-application-eat-ucsjson-reg">application/eat-ucs+json Registration</name>
        <dl spacing="normal" newline="false" indent="3" pn="section-6.8-1">
          <dt pn="section-6.8-1.1">Type name:</dt>
          <dd pn="section-6.8-1.2">
            <t indent="0" pn="section-6.8-1.2.1">application</t>
          </dd>
          <dt pn="section-6.8-1.3">Subtype name:</dt>
          <dd pn="section-6.8-1.4">
            <t indent="0" pn="section-6.8-1.4.1">eat-ucs+json</t>
          </dd>
          <dt pn="section-6.8-1.5">Required parameters:</dt>
          <dd pn="section-6.8-1.6">
            <t indent="0" pn="section-6.8-1.6.1">N/A</t>
          </dd>
          <dt pn="section-6.8-1.7">Optional parameters:</dt>
          <dd pn="section-6.8-1.8">
            <t indent="0" pn="section-6.8-1.8.1">"eat_profile" (EAT profile in string format.  OIDs must use the
dotted-decimal notation.  The parameter value is case insensitive.)</t>
          </dd>
          <dt pn="section-6.8-1.9">Encoding considerations:</dt>
          <dd pn="section-6.8-1.10">
            <t indent="0" pn="section-6.8-1.10.1">Same as <xref target="RFC8259" format="default" sectionFormat="of" derivedContent="JSON"/></t>
          </dd>
          <dt pn="section-6.8-1.11">Security considerations:</dt>
          <dd pn="section-6.8-1.12">
            <t indent="0" pn="section-6.8-1.12.1">Sections <xref target="RFC9781" section="3" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9781#section-3" derivedContent="UCCS"/> and <xref target="RFC9781" section="7" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9781#section-7" derivedContent="UCCS"/> of <xref target="RFC9781" format="default" sectionFormat="of" derivedContent="UCCS"/></t>
          </dd>
          <dt pn="section-6.8-1.13">Interoperability considerations:</dt>
          <dd pn="section-6.8-1.14">
            <t indent="0" pn="section-6.8-1.14.1">N/A</t>
          </dd>
          <dt pn="section-6.8-1.15">Published specification:</dt>
          <dd pn="section-6.8-1.16">
            <t indent="0" pn="section-6.8-1.16.1">RFC 9782</t>
          </dd>
          <dt pn="section-6.8-1.17">Applications that use this media type:</dt>
          <dd pn="section-6.8-1.18">
            <t indent="0" pn="section-6.8-1.18.1">Attesters, Verifiers, Endorsers and Reference-Value providers, and Relying
Parties that need to transfer EAT payloads over HTTP(S), CoAP(S), and other
transports.</t>
          </dd>
          <dt pn="section-6.8-1.19">Fragment identifier considerations:</dt>
          <dd pn="section-6.8-1.20">
            <t indent="0" pn="section-6.8-1.20.1">N/A</t>
          </dd>
          <dt pn="section-6.8-1.21">Person &amp; email address to contact for further information:</dt>
          <dd pn="section-6.8-1.22">
            <t indent="0" pn="section-6.8-1.22.1">RATS WG mailing list (rats@ietf.org)</t>
          </dd>
          <dt pn="section-6.8-1.23">Intended usage:</dt>
          <dd pn="section-6.8-1.24">
            <t indent="0" pn="section-6.8-1.24.1">COMMON</t>
          </dd>
          <dt pn="section-6.8-1.25">Restrictions on usage:</dt>
          <dd pn="section-6.8-1.26">
            <t indent="0" pn="section-6.8-1.26.1">none</t>
          </dd>
          <dt pn="section-6.8-1.27">Author/Change controller:</dt>
          <dd pn="section-6.8-1.28">
            <t indent="0" pn="section-6.8-1.28.1">IETF</t>
          </dd>
          <dt pn="section-6.8-1.29">Provisional registration:</dt>
          <dd pn="section-6.8-1.30">
            <t indent="0" pn="section-6.8-1.30.1">no</t>
          </dd>
        </dl>
      </section>
      <section anchor="coap-content-format-registrations" numbered="true" removeInRFC="false" toc="include" pn="section-6.9">
        <name slugifiedName="name-coap-content-format-registr">CoAP Content-Format Registrations</name>
        <t indent="0" pn="section-6.9-1">IANA has registered the following Content-Format numbers in the "CoAP
Content-Formats" registry, within the "Constrained RESTful Environments
(CoRE) Parameters" registry group <xref target="CORE-PARAMS" format="default" sectionFormat="of" derivedContent="CORE-PARAMS"/>:</t>
        <table align="center" pn="table-2">
          <name slugifiedName="name-new-content-formats">New Content-Formats</name>
          <thead>
            <tr>
              <th align="left" colspan="1" rowspan="1">Content Type</th>
              <th align="left" colspan="1" rowspan="1">Content Coding</th>
              <th align="left" colspan="1" rowspan="1">ID</th>
              <th align="left" colspan="1" rowspan="1">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left" colspan="1" rowspan="1">application/eat+cwt</td>
              <td align="left" colspan="1" rowspan="1">-</td>
              <td align="left" colspan="1" rowspan="1">263</td>
              <td align="left" colspan="1" rowspan="1">RFC 9782</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">application/eat+jwt</td>
              <td align="left" colspan="1" rowspan="1">-</td>
              <td align="left" colspan="1" rowspan="1">264</td>
              <td align="left" colspan="1" rowspan="1">RFC 9782</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">application/eat-bun+cbor</td>
              <td align="left" colspan="1" rowspan="1">-</td>
              <td align="left" colspan="1" rowspan="1">265</td>
              <td align="left" colspan="1" rowspan="1">RFC 9782</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">application/eat-bun+json</td>
              <td align="left" colspan="1" rowspan="1">-</td>
              <td align="left" colspan="1" rowspan="1">266</td>
              <td align="left" colspan="1" rowspan="1">RFC 9782</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">application/eat-ucs+cbor</td>
              <td align="left" colspan="1" rowspan="1">-</td>
              <td align="left" colspan="1" rowspan="1">267</td>
              <td align="left" colspan="1" rowspan="1">RFC 9781</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">application/eat-ucs+json</td>
              <td align="left" colspan="1" rowspan="1">-</td>
              <td align="left" colspan="1" rowspan="1">268</td>
              <td align="left" colspan="1" rowspan="1">RFC 9782</td>
            </tr>
          </tbody>
        </table>
      </section>
    </section>
  </middle>
  <back>
    <displayreference target="RFC9711" to="EAT"/>
    <displayreference target="RFC9781" to="UCCS"/>
    <displayreference target="I-D.irtf-t2trg-rest-iot" to="REST-IoT"/>
    <displayreference target="RFC3986" to="URI"/>
    <displayreference target="RFC4151" to="TAG"/>
    <displayreference target="RFC6838" to="MEDIATYPES"/>
    <displayreference target="RFC8259" to="JSON"/>
    <displayreference target="RFC8392" to="CWT"/>
    <displayreference target="RFC9110" to="HTTP"/>
    <displayreference target="RFC9334" to="RATS-ARCH"/>
    <displayreference target="BCP56" to="BUILD-W-HTTP"/>
    <references anchor="sec-combined-references" pn="section-7">
      <name slugifiedName="name-references">References</name>
      <references anchor="sec-normative-references" pn="section-7.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <referencegroup anchor="BCP225" target="https://www.rfc-editor.org/info/bcp225" derivedAnchor="BCP225">
          <reference anchor="RFC8725" target="https://www.rfc-editor.org/info/rfc8725" quoteTitle="true">
            <front>
              <title>JSON Web Token Best Current Practices</title>
              <author fullname="Y. Sheffer" initials="Y." surname="Sheffer"/>
              <author fullname="D. Hardt" initials="D." surname="Hardt"/>
              <author fullname="M. Jones" initials="M." surname="Jones"/>
              <date month="February" year="2020"/>
              <abstract>
                <t indent="0">JSON Web Tokens, also known as JWTs, are URL-safe JSON-based security tokens that contain a set of claims that can be signed and/or encrypted. JWTs are being widely used and deployed as a simple security token format in numerous protocols and applications, both in the area of digital identity and in other application areas. This Best Current Practices document updates RFC 7519 to provide actionable guidance leading to secure implementation and deployment of JWTs.</t>
              </abstract>
            </front>
            <seriesInfo name="BCP" value="225"/>
            <seriesInfo name="RFC" value="8725"/>
            <seriesInfo name="DOI" value="10.17487/RFC8725"/>
          </reference>
        </referencegroup>
        <reference anchor="CORE-PARAMS" target="https://www.iana.org/assignments/core-parameters" quoteTitle="true" derivedAnchor="CORE-PARAMS">
          <front>
            <title>CoAP Content-Formats</title>
            <author>
              <organization showOnFrontPage="true">IANA</organization>
            </author>
          </front>
        </reference>
        <reference anchor="RFC8392" target="https://www.rfc-editor.org/info/rfc8392" quoteTitle="true" derivedAnchor="CWT">
          <front>
            <title>CBOR Web Token (CWT)</title>
            <author fullname="M. Jones" initials="M." surname="Jones"/>
            <author fullname="E. Wahlstroem" initials="E." surname="Wahlstroem"/>
            <author fullname="S. Erdtman" initials="S." surname="Erdtman"/>
            <author fullname="H. Tschofenig" initials="H." surname="Tschofenig"/>
            <date month="May" year="2018"/>
            <abstract>
              <t indent="0">CBOR Web Token (CWT) is a compact means of representing claims to be transferred between two parties. The claims in a CWT are encoded in the Concise Binary Object Representation (CBOR), and CBOR Object Signing and Encryption (COSE) is used for added application-layer security protection. A claim is a piece of information asserted about a subject and is represented as a name/value pair consisting of a claim name and a claim value. CWT is derived from JSON Web Token (JWT) but uses CBOR rather than JSON.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8392"/>
          <seriesInfo name="DOI" value="10.17487/RFC8392"/>
        </reference>
        <reference anchor="RFC9711" target="https://www.rfc-editor.org/info/rfc9711" quoteTitle="true" derivedAnchor="EAT">
          <front>
            <title>The Entity Attestation Token (EAT)</title>
            <author fullname="Laurence Lundblade" initials="L." surname="Lundblade">
              <organization showOnFrontPage="true">Security Theory LLC</organization>
            </author>
            <author fullname="Giridhar Mandyam" initials="G." surname="Mandyam">
              <organization showOnFrontPage="true">Mediatek USA</organization>
            </author>
            <author fullname="Jeremy O'Donoghue" initials="J." surname="O'Donoghue">
    </author>
            <author fullname="Carl Wallace" initials="C." surname="Wallace">
              <organization showOnFrontPage="true">Red Hound Software, Inc.</organization>
            </author>
            <date month="April" year="2025"/>
          </front>
          <seriesInfo name="RFC" value="9711"/>
          <seriesInfo name="DOI" value="10.17487/RFC9711"/>
        </reference>
        <reference anchor="RFC9110" target="https://www.rfc-editor.org/info/rfc9110" quoteTitle="true" derivedAnchor="HTTP">
          <front>
            <title>HTTP Semantics</title>
            <author fullname="R. Fielding" initials="R." role="editor" surname="Fielding"/>
            <author fullname="M. Nottingham" initials="M." role="editor" surname="Nottingham"/>
            <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke"/>
            <date month="June" year="2022"/>
            <abstract>
              <t indent="0">The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes.</t>
              <t indent="0">This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="97"/>
          <seriesInfo name="RFC" value="9110"/>
          <seriesInfo name="DOI" value="10.17487/RFC9110"/>
        </reference>
        <reference anchor="RFC8259" target="https://www.rfc-editor.org/info/rfc8259" quoteTitle="true" derivedAnchor="JSON">
          <front>
            <title>The JavaScript Object Notation (JSON) Data Interchange Format</title>
            <author fullname="T. Bray" initials="T." role="editor" surname="Bray"/>
            <date month="December" year="2017"/>
            <abstract>
              <t indent="0">JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data.</t>
              <t indent="0">This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience-based interoperability guidance.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="90"/>
          <seriesInfo name="RFC" value="8259"/>
          <seriesInfo name="DOI" value="10.17487/RFC8259"/>
        </reference>
        <reference anchor="MEDIA-TYPES" target="https://www.iana.org/assignments/media-types" quoteTitle="true" derivedAnchor="MEDIA-TYPES">
          <front>
            <title>Media Types</title>
            <author>
              <organization showOnFrontPage="true">IANA</organization>
            </author>
          </front>
        </reference>
        <reference anchor="RFC6838" target="https://www.rfc-editor.org/info/rfc6838" quoteTitle="true" derivedAnchor="MEDIATYPES">
          <front>
            <title>Media Type Specifications and Registration Procedures</title>
            <author fullname="N. Freed" initials="N." surname="Freed"/>
            <author fullname="J. Klensin" initials="J." surname="Klensin"/>
            <author fullname="T. Hansen" initials="T." surname="Hansen"/>
            <date month="January" year="2013"/>
            <abstract>
              <t indent="0">This document defines procedures for the specification and registration of media types for use in HTTP, MIME, and other Internet protocols. This memo documents an Internet Best Current Practice.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="13"/>
          <seriesInfo name="RFC" value="6838"/>
          <seriesInfo name="DOI" value="10.17487/RFC6838"/>
        </reference>
        <reference anchor="STRUCT-SYNTAX" target="https://www.iana.org/assignments/media-type-structured-suffix" quoteTitle="true" derivedAnchor="STRUCT-SYNTAX">
          <front>
            <title>Structured Syntax Suffixes</title>
            <author>
              <organization showOnFrontPage="true">IANA</organization>
            </author>
          </front>
        </reference>
        <reference anchor="RFC9781" target="https://www.rfc-editor.org/info/rfc9781" quoteTitle="true" derivedAnchor="UCCS">
          <front>
            <title>A Concise Binary Object Representation (CBOR) Tag for Unprotected CBOR Web Token Claims Sets (UCCS)</title>
            <author fullname="Henk Birkholz" initials="H." surname="Birkholz">
              <organization showOnFrontPage="true">Fraunhofer SIT</organization>
            </author>
            <author fullname="Jeremy O'Donoghue" initials="J." surname="O'Donoghue">
              <organization showOnFrontPage="true">Qualcomm Technologies Inc.</organization>
            </author>
            <author fullname="Nancy Cam-Winget" initials="N." surname="Cam-Winget">
              <organization showOnFrontPage="true">Cisco Systems</organization>
            </author>
            <author fullname="Carsten Bormann" initials="C." surname="Bormann">
              <organization showOnFrontPage="true">Universität Bremen TZI</organization>
            </author>
            <date month="April" year="2025"/>
          </front>
          <seriesInfo name="RFC" value="9781"/>
          <seriesInfo name="DOI" value="10.17487/RFC9781"/>
        </reference>
        <reference anchor="RFC3986" target="https://www.rfc-editor.org/info/rfc3986" quoteTitle="true" derivedAnchor="URI">
          <front>
            <title>Uniform Resource Identifier (URI): Generic Syntax</title>
            <author fullname="T. Berners-Lee" initials="T." surname="Berners-Lee"/>
            <author fullname="R. Fielding" initials="R." surname="Fielding"/>
            <author fullname="L. Masinter" initials="L." surname="Masinter"/>
            <date month="January" year="2005"/>
            <abstract>
              <t indent="0">A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="66"/>
          <seriesInfo name="RFC" value="3986"/>
          <seriesInfo name="DOI" value="10.17487/RFC3986"/>
        </reference>
      </references>
      <references anchor="sec-informative-references" pn="section-7.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <referencegroup anchor="BCP56" target="https://www.rfc-editor.org/info/bcp56" derivedAnchor="BUILD-W-HTTP">
          <reference anchor="RFC9205" target="https://www.rfc-editor.org/info/rfc9205" quoteTitle="true">
            <front>
              <title>Building Protocols with HTTP</title>
              <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
              <date month="June" year="2022"/>
              <abstract>
                <t indent="0">Applications often use HTTP as a substrate to create HTTP-based APIs. This document specifies best practices for writing specifications that use HTTP to define new application protocols. It is written primarily to guide IETF efforts to define application protocols using HTTP for deployment on the Internet but might be applicable in other situations.</t>
                <t indent="0">This document obsoletes RFC 3205.</t>
              </abstract>
            </front>
            <seriesInfo name="BCP" value="56"/>
            <seriesInfo name="RFC" value="9205"/>
            <seriesInfo name="DOI" value="10.17487/RFC9205"/>
          </reference>
        </referencegroup>
        <reference anchor="RFC9334" target="https://www.rfc-editor.org/info/rfc9334" quoteTitle="true" derivedAnchor="RATS-ARCH">
          <front>
            <title>Remote ATtestation procedureS (RATS) Architecture</title>
            <author fullname="H. Birkholz" initials="H." surname="Birkholz"/>
            <author fullname="D. Thaler" initials="D." surname="Thaler"/>
            <author fullname="M. Richardson" initials="M." surname="Richardson"/>
            <author fullname="N. Smith" initials="N." surname="Smith"/>
            <author fullname="W. Pan" initials="W." surname="Pan"/>
            <date month="January" year="2023"/>
            <abstract>
              <t indent="0">In network protocol exchanges, it is often useful for one end of a communication to know whether the other end is in an intended operating state. This document provides an architectural overview of the entities involved that make such tests possible through the process of generating, conveying, and evaluating evidentiary Claims. It provides a model that is neutral toward processor architectures, the content of Claims, and protocols.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="9334"/>
          <seriesInfo name="DOI" value="10.17487/RFC9334"/>
        </reference>
        <reference anchor="I-D.irtf-t2trg-rest-iot" target="https://datatracker.ietf.org/doc/html/draft-irtf-t2trg-rest-iot-16" quoteTitle="true" derivedAnchor="REST-IoT">
          <front>
            <title>Guidance on RESTful Design for Internet of Things Systems</title>
            <author fullname="Ari Keränen" initials="A." surname="Keränen">
              <organization showOnFrontPage="true">Ericsson</organization>
            </author>
            <author fullname="Matthias Kovatsch" initials="M." surname="Kovatsch">
              <organization showOnFrontPage="true">Siemens</organization>
            </author>
            <author fullname="Klaus Hartke" initials="K." surname="Hartke"/>
            <date day="23" month="April" year="2025"/>
            <abstract>
              <t indent="0">This document gives guidance for designing Internet of Things (IoT) systems that follow the principles of the Representational State Transfer (REST) architectural style. This document is a product of the IRTF Thing-to-Thing Research Group (T2TRG).</t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-irtf-t2trg-rest-iot-16"/>
          <refcontent>Work in Progress</refcontent>
        </reference>
        <reference anchor="RFC4151" target="https://www.rfc-editor.org/info/rfc4151" quoteTitle="true" derivedAnchor="TAG">
          <front>
            <title>The 'tag' URI Scheme</title>
            <author fullname="T. Kindberg" initials="T." surname="Kindberg"/>
            <author fullname="S. Hawke" initials="S." surname="Hawke"/>
            <date month="October" year="2005"/>
            <abstract>
              <t indent="0">This document describes the "tag" Uniform Resource Identifier (URI) scheme. Tag URIs (also known as "tags") are designed to be unique across space and time while being tractable to humans. They are distinct from most other URIs in that they have no authoritative resolution mechanism. A tag may be used purely as an entity identifier. Furthermore, using tags has some advantages over the common practice of using "http" URIs as identifiers for non-HTTP-accessible resources. This memo provides information for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4151"/>
          <seriesInfo name="DOI" value="10.17487/RFC4151"/>
        </reference>
      </references>
    </references>
    <section numbered="false" anchor="acknowledgments" removeInRFC="false" toc="include" pn="section-appendix.a">
      <name slugifiedName="name-acknowledgments">Acknowledgments</name>
      <t indent="0" pn="section-appendix.a-1">Thank you <contact fullname="Carl Wallace"/>, <contact fullname="Carsten Bormann"/>, <contact fullname="Dave Thaler"/>,
      <contact fullname="Deb Cooley"/>, <contact fullname="Éric Vyncke"/>,
      <contact fullname="Francesca Palombini"/>, <contact fullname="Jouni       Korhonen"/>, <contact fullname="Kathleen Moriarty"/>, <contact fullname="Michael Richardson"/>, <contact fullname="Murray Kucherawy"/>,
      <contact fullname="Orie Steele"/>, <contact fullname="Paul Howard"/>,
      <contact fullname="Roman Danyliw"/>, and <contact fullname="Tim       Hollebeek"/> for your comments and suggestions.</t>
    </section>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.b">
      <name slugifiedName="name-authors-addresses">Authors' Addresses</name>
      <author initials="L." surname="Lundblade" fullname="Laurence Lundblade">
        <organization showOnFrontPage="true">Security Theory LLC</organization>
        <address>
          <email>lgl@securitytheory.com</email>
        </address>
      </author>
      <author initials="H." surname="Birkholz" fullname="Henk Birkholz">
        <organization abbrev="Fraunhofer SIT" showOnFrontPage="true">Fraunhofer Institute for Secure Information Technology</organization>
        <address>
          <postal>
            <street>Rheinstrasse 75</street>
            <city>Darmstadt</city>
            <code>64295</code>
            <country>Germany</country>
          </postal>
          <email>henk.birkholz@ietf.contact</email>
        </address>
      </author>
      <author initials="T." surname="Fossati" fullname="Thomas Fossati">
        <organization showOnFrontPage="true">Linaro</organization>
        <address>
          <email>thomas.fossati@linaro.org</email>
        </address>
      </author>
    </section>
  </back>
</rfc>
