<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="std" ipr="trust200902" docName="draft-ietf-cose-typ-header-parameter-05" number="9596" updates="" obsoletes="" submissionType="IETF" consensus="true" tocInclude="true" tocDepth="5" symRefs="true" sortRefs="true" xml:lang="en" prepTime="2024-06-11T14:38:49" indexInclude="true" scripts="Common,Latin">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-cose-typ-header-parameter-05" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc9596" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="COSE &quot;typ&quot; (type) Header Parameter">CBOR Object Signing and Encryption (COSE) "typ" (type) Header Parameter</title>
    <seriesInfo name="RFC" value="9596" stream="IETF"/>
    <author fullname="Michael B. Jones" initials="M.B." surname="Jones">
      <organization showOnFrontPage="true">Self-Issued Consulting</organization>
      <address>
        <email>michael_b_jones@hotmail.com</email>
        <uri>https://self-issued.info/</uri>
      </address>
    </author>
    <author fullname="Orie Steele" initials="O." surname="Steele">
      <organization showOnFrontPage="true">Transmute</organization>
      <address>
        <email>orie@transmute.industries</email>
      </address>
    </author>
    <date month="06" year="2024"/>
    <area>SEC</area>
    <workgroup>cose</workgroup>
    <keyword>Explicit Typing</keyword>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">
	This specification adds the equivalent of the JSON Object Signing and Encryption (JOSE)
  "typ" (type) header parameter to
	CBOR Object Signing and Encryption (COSE).
	This enables the benefits of explicit typing (as defined in RFC 8725, "JSON Web Token Best Current Practices")
	to be brought to COSE objects.
	The syntax of the COSE type header parameter value is the same as the existing COSE content type header parameter.
      </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/rfc9596" 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) 2024 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-requirements-notation-and-c">Requirements Notation and Conventions</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-cose-typ-type-header-parame">COSE "typ" (type) Header Parameter</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-security-considerations">Security Considerations</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-iana-considerations">IANA Considerations</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.4.2">
              <li pn="section-toc.1-1.4.2.1">
                <t indent="0" pn="section-toc.1-1.4.2.1.1"><xref derivedContent="4.1" format="counter" sectionFormat="of" target="section-4.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-cose-header-parameter-regis">COSE Header Parameter Registrations</xref></t>
              </li>
            </ul>
          </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-references">References</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.5.2">
              <li pn="section-toc.1-1.5.2.1">
                <t indent="0" pn="section-toc.1-1.5.2.1.1"><xref derivedContent="5.1" format="counter" sectionFormat="of" target="section-5.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.2">
                <t indent="0" pn="section-toc.1-1.5.2.2.1"><xref derivedContent="5.2" format="counter" sectionFormat="of" target="section-5.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.6">
            <t indent="0" pn="section-toc.1-1.6.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgements">Acknowledgements</xref></t>
          </li>
          <li pn="section-toc.1-1.7">
            <t indent="0" pn="section-toc.1-1.7.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">
	CBOR Object Signing and Encryption (COSE) <xref target="RFC9052" format="default" sectionFormat="of" derivedContent="RFC9052"/> defines header parameters
	that parallel many of those defined by the JSON Object Signing and Encryption (JOSE) specifications 
	<xref target="RFC7515" format="default" sectionFormat="of" derivedContent="RFC7515"/> <xref target="RFC7516" format="default" sectionFormat="of" derivedContent="RFC7516"/>.
	However, one way in which COSE does not provide equivalent functionality to JOSE is that
	it does not define an equivalent of the "typ" (type) header parameter,
	which is used for declaring the type of the entire JOSE data structure.
	The security benefits of having "typ" (type) are described in
  <xref target="RFC8725" sectionFormat="of" section="3.11" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8725#section-3.11" derivedContent="RFC8725"/>,
	which recommends its use for "explicit typing" --
	using "typ" values to distinguish between
	different kinds of JSON Web Tokens (JWTs) <xref target="RFC7519" format="default" sectionFormat="of" derivedContent="RFC7519"/>.
      </t>
      <t indent="0" pn="section-1-2">
	This specification adds the equivalent of the JOSE "typ" (type) header parameter to COSE
	so that the benefits of explicit typing
	can be brought to COSE objects.
	The syntax of the COSE type header parameter value is the same as the existing COSE content type header parameter,
	allowing both unsigned integers as registered in the "CoAP Content-Formats" registry <xref target="CoAP.ContentFormats" format="default" sectionFormat="of" derivedContent="CoAP.ContentFormats"/> 
	and string media type values <xref target="MediaTypes" format="default" sectionFormat="of" derivedContent="MediaTypes"/> to be used.
      </t>
      <t indent="0" pn="section-1-3">
	The term "COSE object" is used as defined in <xref target="RFC9052" format="default" sectionFormat="of" derivedContent="RFC9052"/>.
	An example of a COSE object is a COSE_Sign1 structure,
	as described in <xref target="RFC9052" sectionFormat="of" section="4.2" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9052#section-4.2" derivedContent="RFC9052"/>.
      </t>
      <section anchor="rnc" numbered="true" removeInRFC="false" toc="include" pn="section-1.1">
        <name slugifiedName="name-requirements-notation-and-c">Requirements Notation and Conventions</name>
        <t indent="0" pn="section-1.1-1">
    The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
    "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>",
    "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>",
    "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
    "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be
    interpreted as described in BCP 14 <xref target="RFC2119" format="default" sectionFormat="of" derivedContent="RFC2119"/> <xref target="RFC8174" format="default" sectionFormat="of" derivedContent="RFC8174"/> when, and only when, they appear in all capitals, as
    shown here.
        </t>
      </section>
    </section>
    <section anchor="typ" numbered="true" removeInRFC="false" toc="include" pn="section-2">
      <name slugifiedName="name-cose-typ-type-header-parame">COSE "typ" (type) Header Parameter</name>
      <t indent="0" pn="section-2-1">
	The "typ" (type) header parameter
	is used by COSE applications to declare the
	type of this complete COSE object, as compared to the content type header parameter,
  which declares the type of the COSE object payload.
	This is intended for use by the application when
	more than one kind of COSE object could be present in
	an application data structure that can contain a COSE object;
	the application can use this value to disambiguate among
	the different kinds of COSE objects that might be present.
	It will typically not be used by applications when
	the kind of COSE object is already known.
	Use of this header parameter is <bcp14>OPTIONAL</bcp14>.
      </t>
      <t indent="0" pn="section-2-2">
	The syntax of this header parameter value is the same as the content type header parameter
	defined in <xref target="RFC9052" sectionFormat="of" section="3.1" format="default" derivedLink="https://rfc-editor.org/rfc/rfc9052#section-3.1" derivedContent="RFC9052"/>;
	it is either
	an unsigned integer as registered in the "CoAP Content-Formats" registry  <xref target="CoAP.ContentFormats" format="default" sectionFormat="of" derivedContent="CoAP.ContentFormats"/> 
	or a string content type value.
	Content type values have a media type name <xref target="MediaTypes" format="default" sectionFormat="of" derivedContent="MediaTypes"/>
	and <bcp14>MAY</bcp14> include media type parameters.
      </t>
      <t indent="0" pn="section-2-3">
	The "typ" (type) header parameter is ignored by COSE implementations
	(libraries implementing <xref target="RFC9052" format="default" sectionFormat="of" derivedContent="RFC9052"/> and this specification),
	other than being passed through to applications using those implementations.
	Any processing of this parameter is performed by the COSE application
	using application-specific processing rules.
	For instance, an application might verify that the "typ" value
	is a particular application-chosen media type and reject the data structure if it is not.
      </t>
      <t indent="0" pn="section-2-4">
  The "typ" parameter <bcp14>MUST NOT</bcp14> be present in unprotected headers.
      </t>
      <t indent="0" pn="section-2-5">
  The "typ" parameter does not describe the content of unprotected headers.
  Changes to unprotected headers do not change the type of the COSE object.
      </t>
    </section>
    <section anchor="Security" numbered="true" removeInRFC="false" toc="include" pn="section-3">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-3-1">
	The case for explicit typing of COSE objects is equivalent to the case made for explicit typing
	in <xref target="RFC8725" section="3.11" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8725#section-3.11" derivedContent="RFC8725"/>:
  Explicit typing can prevent confusion between different kinds of COSE objects.
      </t>
      <t indent="0" pn="section-3-2">
	COSE applications employing explicit typing should reject COSE objects
	with a type header parameter value different than values that they expect in that application context.
	They should also reject COSE objects without a type header parameter when one is expected.
      </t>
    </section>
    <section anchor="IANA" numbered="true" removeInRFC="false" toc="include" pn="section-4">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <section anchor="cose-algorithms-registrations" numbered="true" removeInRFC="false" toc="include" pn="section-4.1">
        <name slugifiedName="name-cose-header-parameter-regis">COSE Header Parameter Registrations</name>
        <t indent="0" pn="section-4.1-1">
	  IANA has registered the following value in the
	  IANA "COSE Header Parameters" registry <xref target="COSE.HeaderParameters" format="default" sectionFormat="of" derivedContent="COSE.HeaderParameters"/>.
        </t>
        <table anchor="iana-tab" align="center" pn="table-1">
          <name/>
          <thead>
            <tr>
              <th align="left" colspan="1" rowspan="1">Name</th>
              <th align="left" colspan="1" rowspan="1">Label</th>
              <th align="left" colspan="1" rowspan="1">Value Type</th>
              <th align="left" colspan="1" rowspan="1">Value Registry</th>
              <th align="left" colspan="1" rowspan="1">Description</th>
              <th align="left" colspan="1" rowspan="1">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left" colspan="1" rowspan="1">typ (type)</td>
              <td align="left" colspan="1" rowspan="1">16</td>
              <td align="left" colspan="1" rowspan="1">uint / tstr</td>
              <td align="left" colspan="1" rowspan="1">
                <xref target="CoAP.ContentFormats" format="default" sectionFormat="of" derivedContent="CoAP.ContentFormats"/> or <xref target="MediaTypes" format="default" sectionFormat="of" derivedContent="MediaTypes"/> registry</td>
              <td align="left" colspan="1" rowspan="1">Content type of the complete COSE object</td>
              <td align="left" colspan="1" rowspan="1">
                <xref target="typ" format="default" sectionFormat="of" derivedContent="Section 2"/> of RFC 9596</td>
            </tr>
          </tbody>
        </table>
      </section>
    </section>
  </middle>
  <back>
    <references pn="section-5">
      <name slugifiedName="name-references">References</name>
      <references pn="section-5.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" quoteTitle="true" derivedAnchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t indent="0">In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" quoteTitle="true" derivedAnchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t indent="0">RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
        <reference anchor="RFC8725" target="https://www.rfc-editor.org/info/rfc8725" quoteTitle="true" derivedAnchor="RFC8725">
          <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>
        <reference anchor="RFC9052" target="https://www.rfc-editor.org/info/rfc9052" quoteTitle="true" derivedAnchor="RFC9052">
          <front>
            <title>CBOR Object Signing and Encryption (COSE): Structures and Process</title>
            <author fullname="J. Schaad" initials="J." surname="Schaad"/>
            <date month="August" year="2022"/>
            <abstract>
              <t indent="0">Concise Binary Object Representation (CBOR) is a data format designed for small code size and small message size. There is a need to be able to define basic security services for this data format. This document defines the CBOR Object Signing and Encryption (COSE) protocol. This specification describes how to create and process signatures, message authentication codes, and encryption using CBOR for serialization. This specification additionally describes how to represent cryptographic keys using CBOR.</t>
              <t indent="0">This document, along with RFC 9053, obsoletes RFC 8152.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="96"/>
          <seriesInfo name="RFC" value="9052"/>
          <seriesInfo name="DOI" value="10.17487/RFC9052"/>
        </reference>
      </references>
      <references pn="section-5.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="CoAP.ContentFormats" target="https://www.iana.org/assignments/core-parameters" quoteTitle="true" derivedAnchor="CoAP.ContentFormats">
          <front>
            <title>CoAP Content-Formats</title>
            <author>
              <organization showOnFrontPage="true">IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
        <reference anchor="COSE.HeaderParameters" target="https://www.iana.org/assignments/cose" quoteTitle="true" derivedAnchor="COSE.HeaderParameters">
          <front>
            <title>COSE Header Parameters</title>
            <author>
              <organization showOnFrontPage="true">IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
        <reference anchor="MediaTypes" target="https://www.iana.org/assignments/media-types" quoteTitle="true" derivedAnchor="MediaTypes">
          <front>
            <title>Media Types</title>
            <author>
              <organization showOnFrontPage="true">IANA</organization>
            </author>
            <date/>
          </front>
        </reference>
        <reference anchor="RFC7515" target="https://www.rfc-editor.org/info/rfc7515" quoteTitle="true" derivedAnchor="RFC7515">
          <front>
            <title>JSON Web Signature (JWS)</title>
            <author fullname="M. Jones" initials="M." surname="Jones"/>
            <author fullname="J. Bradley" initials="J." surname="Bradley"/>
            <author fullname="N. Sakimura" initials="N." surname="Sakimura"/>
            <date month="May" year="2015"/>
            <abstract>
              <t indent="0">JSON Web Signature (JWS) represents content secured with digital signatures or Message Authentication Codes (MACs) using JSON-based data structures. Cryptographic algorithms and identifiers for use with this specification are described in the separate JSON Web Algorithms (JWA) specification and an IANA registry defined by that specification. Related encryption capabilities are described in the separate JSON Web Encryption (JWE) specification.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7515"/>
          <seriesInfo name="DOI" value="10.17487/RFC7515"/>
        </reference>
        <reference anchor="RFC7516" target="https://www.rfc-editor.org/info/rfc7516" quoteTitle="true" derivedAnchor="RFC7516">
          <front>
            <title>JSON Web Encryption (JWE)</title>
            <author fullname="M. Jones" initials="M." surname="Jones"/>
            <author fullname="J. Hildebrand" initials="J." surname="Hildebrand"/>
            <date month="May" year="2015"/>
            <abstract>
              <t indent="0">JSON Web Encryption (JWE) represents encrypted content using JSON-based data structures. Cryptographic algorithms and identifiers for use with this specification are described in the separate JSON Web Algorithms (JWA) specification and IANA registries defined by that specification. Related digital signature and Message Authentication Code (MAC) capabilities are described in the separate JSON Web Signature (JWS) specification.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7516"/>
          <seriesInfo name="DOI" value="10.17487/RFC7516"/>
        </reference>
        <reference anchor="RFC7519" target="https://www.rfc-editor.org/info/rfc7519" quoteTitle="true" derivedAnchor="RFC7519">
          <front>
            <title>JSON Web Token (JWT)</title>
            <author fullname="M. Jones" initials="M." surname="Jones"/>
            <author fullname="J. Bradley" initials="J." surname="Bradley"/>
            <author fullname="N. Sakimura" initials="N." surname="Sakimura"/>
            <date month="May" year="2015"/>
            <abstract>
              <t indent="0">JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature (JWS) structure or as the plaintext of a JSON Web Encryption (JWE) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7519"/>
          <seriesInfo name="DOI" value="10.17487/RFC7519"/>
        </reference>
      </references>
    </references>
    <section anchor="Acknowledgements" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.a">
      <name slugifiedName="name-acknowledgements">Acknowledgements</name>
      <t indent="0" pn="section-appendix.a-1">
	We would like to thank
        <contact fullname="Henk Birkholz"/>,
<contact fullname="Carsten Bormann"/>,
<contact fullname="Susan Hares"/>,
<contact fullname="Dan Harkins"/>,
<contact fullname="Murray Kucherawy"/>,
<contact fullname="Marco Tiloca"/>,
<contact fullname="Gunter Van de Velde"/>,
<contact fullname="Éric Vyncke"/>,
	and
<contact fullname="Dale Worley"/>
	for their valuable contributions to this specification.
      </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 fullname="Michael B. Jones" initials="M.B." surname="Jones">
        <organization showOnFrontPage="true">Self-Issued Consulting</organization>
        <address>
          <email>michael_b_jones@hotmail.com</email>
          <uri>https://self-issued.info/</uri>
        </address>
      </author>
      <author fullname="Orie Steele" initials="O." surname="Steele">
        <organization showOnFrontPage="true">Transmute</organization>
        <address>
          <email>orie@transmute.industries</email>
        </address>
      </author>
    </section>
  </back>
</rfc>
