<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="bcp" consensus="true" docName="draft-ietf-mediaman-toplevel-06" number="9694" ipr="trust200902" obsoletes="" updates="6838" submissionType="IETF" xml:lang="en" tocInclude="true" tocDepth="4" symRefs="true" sortRefs="true" prepTime="2025-03-17T21:07:03" indexInclude="true" scripts="Common,Latin">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-mediaman-toplevel-06" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc9694" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="New Top-level Media Types">Guidelines for the Definition of New Top-Level Media Types</title>
    <seriesInfo name="RFC" value="9694" stream="IETF"/>
    <seriesInfo name="BCP" value="13" stream="IETF"/>
    <author fullname="Martin J. Dürst" initials="M.J." surname="Dürst">
      <organization showOnFrontPage="true">Aoyama Gakuin University</organization>
      <address>
        <postal>
          <street>Fuchinobe 5-10-1, Chuo-ku, Sagamihara</street>
          <region>Kanagawa</region>
          <code>252-5258</code>
          <country>Japan</country>
        </postal>
        <phone>+81 42 759 6329</phone>
        <email>duerst@it.aoyama.ac.jp</email>
        <uri>https://www.sw.it.aoyama.ac.jp/Dürst/</uri>
      </address>
    </author>
    <date month="03" year="2025"/>
    <area>ART</area>
    <workgroup>mediaman</workgroup>
    <keyword>Media Type</keyword>
    <keyword>Top-Level</keyword>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">This document defines best practices for defining new top-level media types.
        It also introduces a registry for top-level media types,
        and contains a short history of top-level media types.
        It updates RFC 6838.</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 memo documents an Internet Best Current Practice.
        </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 BCPs 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/rfc9694" 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-background">Background</xref></t>
              </li>
              <li pn="section-toc.1-1.1.2.2">
                <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.2.2.1"><xref derivedContent="1.2" format="counter" sectionFormat="of" target="section-1.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-requirements-language">Requirements Language</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.2">
            <t indent="0" 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-rules-and-criteria-for-the-">Rules and Criteria for the Registration of New Top-Level Media Types</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.2.2">
              <li pn="section-toc.1-1.2.2.1">
                <t indent="0" pn="section-toc.1-1.2.2.1.1"><xref derivedContent="2.1" format="counter" sectionFormat="of" target="section-2.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-required-criteria">Required Criteria</xref></t>
              </li>
              <li pn="section-toc.1-1.2.2.2">
                <t indent="0" pn="section-toc.1-1.2.2.2.1"><xref derivedContent="2.2" format="counter" sectionFormat="of" target="section-2.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-additional-considerations">Additional Considerations</xref></t>
              </li>
              <li pn="section-toc.1-1.2.2.3">
                <t indent="0" pn="section-toc.1-1.2.2.3.1"><xref derivedContent="2.3" format="counter" sectionFormat="of" target="section-2.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-negative-criteria">Negative Criteria</xref></t>
              </li>
            </ul>
          </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-top-level-media-type-histor">Top-Level Media Type History</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-registration-of-top-level-m">Registration of Top-level Media Types</xref></t>
              </li>
              <li pn="section-toc.1-1.4.2.2">
                <t indent="0" pn="section-toc.1-1.4.2.2.1"><xref derivedContent="4.2" format="counter" sectionFormat="of" target="section-4.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-initialization-of-the-regis">Initialization of the Registry of Top-Level Media Types</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-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="" format="none" sectionFormat="of" target="section-6"/><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-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="" format="none" 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="" format="none" 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-authors-address">Author's Address</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <t indent="0" pn="section-1-1">This document defines best practices for defining new top-level media types.
        Top-level media types ('top-level types' for short) appear to the left of the slash in a media type,
        examples being 'text/...', 'application/...', 'image/...', and so on.
        Please note that top-level types are different from trees
        (standards tree, vendor tree, personal tree), which (except for the standards tree)
        are indicated immediately to the right of the slash with a prefix of '.../vnd.' or '.../prs.'.
        Section <xref target="RFC6838" sectionFormat="bare" section="4.2.7" format="default" derivedLink="https://rfc-editor.org/rfc/rfc6838#section-4.2.7" derivedContent="RFC6838"/> of RFC 6838 <xref target="RFC6838" format="default" sectionFormat="of" derivedContent="RFC6838"/>
        only summarily gives criteria for defining additional top-level media types.
        This document provides more detailed criteria for defining additional top-level media types.
        It therefore updates RFC 6838 <xref target="RFC6838" format="default" sectionFormat="of" derivedContent="RFC6838"/>.</t>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-1.1">
        <name slugifiedName="name-background">Background</name>
        <t indent="0" pn="section-1.1-1">New top-level types are rare enough and different enough from each other
          that each application needs to be evaluated separately.
        The main protocol extension point for media types are subtypes below each of the main types.
        For formats that do not fit below any other top-level type,
        the 'application' top-level type can always be used.</t>
        <t indent="0" pn="section-1.1-2">The main function of media types and subtypes is
          the dispatch of data formats to application code.
          In most cases, this requires and is done using the full type
          (i.e., including the subtype, and often some parameters).
          The top-level type can occasionally serve as a fallback for the tentative dispatch
          to applications handling a very wide range of related formats.
          Please note that assumptions about the correctness of a media type
          must be made carefully, as it could be under the control of an attacker.</t>
        <t indent="0" pn="section-1.1-3">In some older scenarios, it may also have been possible to identify a device
          (e.g., a phone for audio messages, a printer or fax device for images,
          a video recorder for videos, a computer for 'application' subtypes).
          However, the current hardware landscape,
          where computers and smartphones can handle a very wide variety of media,
          makes such a scenario look somewhat far-fetched.</t>
        <t indent="0" pn="section-1.1-4">The top-level type can be used for user-directed information.
          Besides direct inspection of the type string by the user,
          this includes using different types of default icons
          for different top-level types.</t>
      </section>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-1.2">
        <name slugifiedName="name-requirements-language">Requirements Language</name>
        <t indent="0" pn="section-1.2-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 numbered="true" removeInRFC="false" toc="include" pn="section-2">
      <name slugifiedName="name-rules-and-criteria-for-the-">Rules and Criteria for the Registration of New Top-Level Media Types</name>
      <t indent="0" pn="section-2-1">This section describes the rules and criteria for new top-level media types,
        including criteria already defined in RFC 6838 <xref target="RFC6838" format="default" sectionFormat="of" derivedContent="RFC6838"/>.</t>
      <section numbered="true" removeInRFC="false" toc="include" pn="section-2.1">
        <name slugifiedName="name-required-criteria">Required Criteria</name>
        <t indent="0" pn="section-2.1-1">The following is the list of required criteria for the definition of a new top-level type.
           Motivations for the requirements are also included.</t>
        <ul bare="false" empty="false" indent="3" spacing="normal" pn="section-2.1-2">
          <li pn="section-2.1-2.1">Every new top-level type <bcp14>MUST</bcp14> be defined in a Standards Track RFC
              (see Section <xref target="RFC8126" sectionFormat="bare" section="4.9" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8126#section-4.9" derivedContent="RFC8126"/> of RFC 8126 <xref target="RFC8126" format="default" sectionFormat="of" derivedContent="RFC8126"/>).
              This will ensure there is sufficient community interest, review,
              and consensus appropriate for a new top-level type.</li>
          <li pn="section-2.1-2.2">The IANA Considerations section of an RFC defining a new top-level type
              <bcp14>MUST</bcp14> request that IANA add this new top-level type to the registry
              of top-level types.</li>
          <li pn="section-2.1-2.3">The criteria for what types do and do not fall
              under the new top-level type <bcp14>MUST</bcp14> be defined clearly.
              Clear criteria are expected to help expert reviewers evaluate
              whether or not a subtype belongs below the new type,
              and whether the registration template for a subtype
              contains the appropriate information.
              Criteria that cannot be defined clearly
              are a strong indication that whatever is being
              talked about is not suitable as a top-level type.</li>
          <li pn="section-2.1-2.4">Any RFC defining a new top-level type <bcp14>MUST</bcp14> clearly document the security considerations
              applying to all or a significant subset of subtypes.</li>
          <li pn="section-2.1-2.5">At a minimum, one subtype <bcp14>MUST</bcp14> be described.
              A top-level type without any subtypes serves no purpose.
              Please note that the 'example' top-level describes the subtype 'example'.</li>
        </ul>
      </section>
      <section numbered="true" removeInRFC="false" toc="include" pn="section-2.2">
        <name slugifiedName="name-additional-considerations">Additional Considerations</name>
        <ul bare="false" empty="false" indent="3" spacing="normal" pn="section-2.2-1">
          <li pn="section-2.2-1.1">Existing wide use of an unregistered top-level type may be an indication of a need, and therefore may be an argument for formally defining this new top-level type.</li>
          <li pn="section-2.2-1.2">On the other hand, the use of unregistered top-level types is highly discouraged.</li>
          <li pn="section-2.2-1.3">Use of an IETF WG to define a new top-level type is not needed,
              but may be advisable in some cases. There are examples of new top-level type definitions
              without a WG (RFC 2077 <xref target="RFC2077" format="default" sectionFormat="of" derivedContent="RFC2077"/>),
              with a short, dedicated WG (RFC 8081 <xref target="RFC8081" format="default" sectionFormat="of" derivedContent="RFC8081"/>),
              and with a WG that included other related work
              (RFC 9695 <xref target="RFC9695" format="default" sectionFormat="of" derivedContent="RFC9695"/>).</li>
          <li pn="section-2.2-1.4">The document defining the new top-level type should include
          initial registrations of actual subtypes.  The exception may be a
          top-level type similar to 'example'. This will help show the need
          for the new top-level type, allow checking the appropriateness
          of the definition of the new top-level type, avoid separate
          work for registering an initial slate of subtypes, and provide
          examples of what is considered a valid subtype for future subtype
          registrations.</li>
          <li pn="section-2.2-1.5">The registration and actual use of a certain number of subtypes under the new top-level type should be expected.
              The existence of a single subtype should not be enough;
              it should be clear that new similar types may appear in the future.
              Otherwise, the creation of a new top-level type is most probably not justified.</li>
          <li pn="section-2.2-1.6">The proposers of the new top-level type and the wider user community should be willing to commit
              to emitting and consuming the new top-level type in environments that they control.</li>
          <li pn="section-2.2-1.7">Desirability for common parameters: The fact that a group of (potential) types have
            (mostly) common parameters may be an indication that they belong under a common new top-level type.</li>
          <li pn="section-2.2-1.8">Top-level types can help humans with understanding and debugging.
            Therefore, evaluating how a new top-level type helps humans understand types
            may be crucial. But as often with humans, opinions may widely differ.</li>
          <li pn="section-2.2-1.9">Common restrictions may apply to all subtypes of a top-level type.
            Examples are the restriction to CRLF line endings for subtypes of type 'text'
            (at least in the context of electronic mail), or on subtypes of type 'multipart'.</li>
          <li pn="section-2.2-1.10">Top-level types are also used frequently in dispatching code.
            For example, "multipart/*" is frequently handled as multipart/mixed, without understanding of a specific subtype.
            The top-level types 'image', 'audio', and 'video' are also often handled generically.
            Documents with these top-level types can be passed to applications handling a wide variety
            of image, audio, or video formats. HTML-generating applications can select different HTML elements
            (e.g., &lt;img&gt; or &lt;audio&gt;) for including data of different top-level types.
            Applications can select different icons to represent unknown types in different top-level types.</li>
        </ul>
      </section>
      <section numbered="true" removeInRFC="false" toc="include" pn="section-2.3">
        <name slugifiedName="name-negative-criteria">Negative Criteria</name>
        <t indent="0" pn="section-2.3-1">This subsection lists negative criteria for top-level types; 
          it identifies criteria that are explicitly not reasons for a top-level type registration.</t>
        <ul bare="false" empty="false" indent="3" spacing="normal" pn="section-2.3-2">
          <li pn="section-2.3-2.1">A top-level type is not a pointer into another registration space that offers
            duplicate registrations for existing media types. Example: a top-level type
            of 'oid', leading to types of the form oid/nnnnn, where nnnnn is an OID (Object Identifier) designating a 
             specific media format.</li>
          <li pn="section-2.3-2.2">A top-level type <bcp14>MUST NOT</bcp14> be defined for the mapping of other protocol elements
            to media types.
            For example, while there may be some merit to a mapping from media types
            to URIs, e.g., in the context of RDF (Resource Description Framework) <xref target="RDF" format="default" sectionFormat="of" derivedContent="RDF"/>, there is very limited merit in a reverse mapping,
            and even less merit in creating a top-level type for such a mapping.
            The same applies to other protocol elements such as file extensions or URI schemes.
            If a mapping is needed, the recommended solution is to choose a
            single type/subtype and put the additional information in an appropriately
            named parameter.
            As an example, information on a file extension '.dcat' can be encoded as
            'application/octet-string; filename=foo.dcat'.</li>
          <li pn="section-2.3-2.3">Media types are not a general type system.
            A top-level type <bcp14>MUST NOT</bcp14> be defined if its main or only purpose is
            to map other type systems, e.g., in programming languages or ontologies.</li>
          <li pn="section-2.3-2.4">A new top-level type <bcp14>SHOULD NOT</bcp14> generate aliases for existing widely used types or subtypes.</li>
          <li pn="section-2.3-2.5">Top-level types with an "X-" prefix cannot be registered, and <bcp14>SHOULD NOT</bcp14> be used.
            This is in line with RFC 6648 <xref target="RFC6648" format="default" sectionFormat="of" derivedContent="RFC6648"/>.</li>
        </ul>
      </section>
    </section>
    <section numbered="true" removeInRFC="false" toc="include" pn="section-3">
      <name slugifiedName="name-top-level-media-type-histor">Top-Level Media Type History</name>
      <t indent="0" pn="section-3-1">This section briefly describes the history of top-level types.
        The emphasis is on the aspects of the history that are relevant
        to the adoption of new top-level types.</t>
      <t indent="0" pn="section-3-2">RFC 1341 <xref target="RFC1341" format="default" sectionFormat="of" derivedContent="RFC1341"/> first defined the
      structuring of content types into (top-level) type and subtype, and introduced
      the 'text', 'multipart', 'message', 'image', 'audio', 'video', and 'application' top-level types.
      That specification also allowed top-level types starting with 'X-'.
      With respect to new top-level types, it said the following:</t>
      <blockquote pn="section-3-3">An initial set of seven Content-Types  is  defined  by  this
        document.   This  set  of  top-level names is intended to be
        substantially complete.  It is expected  that  additions  to
        the   larger   set  of  supported  types  can  generally  be
        accomplished by  the  creation  of  new  subtypes  of  these
        initial  types.   In the future, more top-level types may be
        defined only by an extension to this standard.   If  another
        primary  type is to be used for any reason, it must be given
        a name starting  with  "X-"  to  indicate  its  non-standard
        status  and  to  avoid  a  potential  conflict with a future
        official name.</blockquote>
      <t indent="0" pn="section-3-4">RFC 1437 <xref target="RFC1437" format="default" sectionFormat="of" derivedContent="RFC1437"/> defined the first additional top-level type; however, it was not registered because RFC 1437 is an April Fools RFC that was published purely for entertainment purposes.</t>
      <t indent="0" pn="section-3-5">RFC 2046 <xref target="RFC2046" format="default" sectionFormat="of" derivedContent="RFC2046"/> discouraged
      the use of "X-" for (new) top-level types, with the following words:</t>
      <blockquote pn="section-3-6">In general, the use of "X-" top-level types is strongly discouraged.
        Implementors should invent subtypes of the existing types whenever
        possible. In many cases, a subtype of "application" will be more
        appropriate than a new top-level type.</blockquote>
      <t indent="0" pn="section-3-7">RFC 2048 <xref target="RFC2048" format="default" sectionFormat="of" derivedContent="RFC2048"/>, published
        at the same time as RFC 2046 <xref target="RFC2046" format="default" sectionFormat="of" derivedContent="RFC2046"/>,
        defined requirements for the definition of new top-level types:</t>
      <blockquote pn="section-3-8">In some cases a new media type may not "fit" under any currently
        defined top-level content type. Such cases are expected to be quite
        rare. However, if such a case arises a new top-level type can be
        defined to accommodate it. Such a definition must be done via
        standards-track RFC; no other mechanism can be used to define
        additional top-level content types.</blockquote>
      <t indent="0" pn="section-3-9">The 'model' top-level type was introduced by RFC 2077 <xref target="RFC2077" format="default" sectionFormat="of" derivedContent="RFC2077"/> in 1997.</t>
      <t indent="0" pn="section-3-10">RFC 4735 <xref target="RFC4735" format="default" sectionFormat="of" derivedContent="RFC4735"/> introduced the
      'example' top-level type for use in documentation examples.</t>
      <t indent="0" pn="section-3-11">The 'font' top-level type was defined in
        RFC 8081 <xref target="RFC8081" format="default" sectionFormat="of" derivedContent="RFC8081"/>,
        a work of the 'justfont' IETF WG, in 2017.
        This was formalizing the widespread use of the unofficial 'font' top-level type
        that people were using in preference to official, registered types.
      </t>
      <t indent="0" pn="section-3-12">RFC 9695 <xref target="RFC9695" format="default" sectionFormat="of" derivedContent="RFC9695"/> defines a new 'haptics' top-level type. RFC 9695 and this document were developed in parallel, and RFC 9695 was used to cross-check the considerations and procedures defined in this document.</t>
      <t indent="0" pn="section-3-13">The "Chemical file format" Wikipedia page <xref target="CHEMICAL" format="default" sectionFormat="of" derivedContent="CHEMICAL"/>
   reports the unofficial use of a 'chemical' top-level type.  This top-level type was proposed by Peter Murray-Rust and Henry Rzepa at a
   workshop at the First WWW conference in May 1994 <xref target="CHEMIME" format="default" sectionFormat="of" derivedContent="CHEMIME"/>.
        It is in widespread use but remains unregistered.</t>
      <t indent="0" pn="section-3-14">Some Linux desktop logic uses what looks like a top-level type
        of 'x-scheme-handler' to map URI schemes to applications.
        In addition, the type 'inode/directory' is used.
        However, this is a purely local, system-specific use,
        and is not intended for exchange. If exchange or standardization
        are desired, different types (in all cases, properly registered) are strongly recommended.      As an example, 'x-scheme-handler/http' should be changed to something like 'application/scheme-handler; scheme=http'.
    As another example, the type 'inode/directory' should be
    changed to 'multipart/inode-directory' or
    'application/inode-directory.
</t>
      <t indent="0" pn="section-3-15">The document that previously defined the requirements for new top-level
        media types was RFC 6838 <xref target="RFC6838" format="default" sectionFormat="of" derivedContent="RFC6838"/>.
        Of particular relevance to the work in the current document are
        Sections <xref target="RFC6838" section="4.2.5" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc6838#section-4.2.5" derivedContent="RFC6838"/> (Application Media Types) and
        <xref target="RFC6838" section="4.2.7" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc6838#section-4.2.7" derivedContent="RFC6838"/> (Additional Top-Level Types) of <xref target="RFC6838" format="default" sectionFormat="of" derivedContent="RFC6838"/>.
        These two sections are not strictly aligned, because the first says
        that anything that doesn't go under a more specific type
        can go under the 'application' top-level type,
        while the later section allows for new top-level types.</t>
    </section>
    <section anchor="IANA" numbered="true" toc="include" removeInRFC="false" pn="section-4">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <section anchor="IANAregister" numbered="true" toc="include" removeInRFC="false" pn="section-4.1">
        <name slugifiedName="name-registration-of-top-level-m">Registration of Top-level Media Types</name>
        <t indent="0" pn="section-4.1-1">Registrations of new top-level types follow the "Standards Action" policy
        (see Section <xref target="RFC8126" sectionFormat="bare" section="4.9" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8126#section-4.9" derivedContent="RFC8126"/> of RFC 8126 <xref target="RFC8126" format="default" sectionFormat="of" derivedContent="RFC8126"/>).  </t>
        <t indent="0" pn="section-4.1-2">Registrations of new top-level types have to provide
          the name of the top-level type,
          the defining specification (RFC, or the respective draft during the approval process),
          and, if applicable, some comments.

          The defining specification has to contain an "IANA Considerations" section requesting addition
          to the registry of top-level media types, and has to document security considerations for the top-level type they register.</t>
        <t indent="0" pn="section-4.1-3">The comments field is empty or contains short comments about the usage of the type.
          Comments can be added or updated by the experts for subtype registrations
          under the respective top-level type, and by IANA itself.</t>
        <t indent="0" pn="section-4.1-4">There should be at least one subtype, except for registrations that are
          for demonstration purposes only (e.g. the example top-level type).</t>
      </section>
      <section anchor="IANAinitial" numbered="true" toc="include" removeInRFC="false" pn="section-4.2">
        <name slugifiedName="name-initialization-of-the-regis">Initialization of the Registry of Top-Level Media Types</name>
        <t indent="0" pn="section-4.2-1">IANA has created the <eref target="https://www.iana.org/assignments/top-level-media-types" brackets="none">"Top-Level Media Types" registry</eref> and populated it with the values in <xref target="tab1" format="default" sectionFormat="of" derivedContent="Table 1"/>.  IANA also added a pointer to this registry from the <eref target="https://www.iana.org/assignments/media-types" brackets="none">"Media Types" registry group</eref>, and they added pointers to this document and to the "Top-Level Media Types" registry in the application for a media 
type at <eref brackets="angle" target="https://www.iana.org/form/media-types"/>.
        </t>
        <t indent="0" pn="section-4.2-2">For each top-level media type, the registry contains the name of the type,
        a pointer to the RFC defining the type, a pointer to IANA's registry of subtypes
        for that type, and a comment field.</t>
        <t indent="0" pn="section-4.2-3">The initial state of the registry is as follows:</t>
        <table anchor="tab1" align="center" pn="table-1">
          <name slugifiedName="name-initial-values-for-the-regi">Initial Values for the Registry of Top-level Media Types</name>
          <thead>
            <tr>
              <th align="left" colspan="1" rowspan="1">Name</th>
              <th align="left" colspan="1" rowspan="1">Defining RFC</th>
              <th align="left" colspan="1" rowspan="1">Registry of Subtypes</th>
              <th align="left" colspan="1" rowspan="1">Comments</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left" colspan="1" rowspan="1">application</td>
              <td align="left" colspan="1" rowspan="1">
                <xref target="RFC2046" format="default" sectionFormat="of" derivedContent="RFC2046"/></td>
              <td align="left" colspan="1" rowspan="1">[Application Media Types]</td>
              <td align="left" colspan="1" rowspan="1">-</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">audio</td>
              <td align="left" colspan="1" rowspan="1">
                <xref target="RFC2046" format="default" sectionFormat="of" derivedContent="RFC2046"/></td>
              <td align="left" colspan="1" rowspan="1">[Audio Media Types]</td>
              <td align="left" colspan="1" rowspan="1">-</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">example</td>
              <td align="left" colspan="1" rowspan="1">
                <xref target="RFC4735" format="default" sectionFormat="of" derivedContent="RFC4735"/></td>
              <td align="left" colspan="1" rowspan="1">[Example Media Types]</td>
              <td align="left" colspan="1" rowspan="1">no registrations, for examples only</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">font</td>
              <td align="left" colspan="1" rowspan="1">
                <xref target="RFC8081" format="default" sectionFormat="of" derivedContent="RFC8081"/></td>
              <td align="left" colspan="1" rowspan="1">[Font Media Types]</td>
              <td align="left" colspan="1" rowspan="1">-</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">haptics</td>
              <td align="left" colspan="1" rowspan="1">
                <xref target="RFC9695" format="default" sectionFormat="of" derivedContent="RFC9695"/> </td>
              <td align="left" colspan="1" rowspan="1">[Haptics Media Types]</td>
              <td align="left" colspan="1" rowspan="1">-</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">image</td>
              <td align="left" colspan="1" rowspan="1">
                <xref target="RFC2046" format="default" sectionFormat="of" derivedContent="RFC2046"/></td>
              <td align="left" colspan="1" rowspan="1">[Image Media Types]</td>
              <td align="left" colspan="1" rowspan="1">-</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">message</td>
              <td align="left" colspan="1" rowspan="1">
                <xref target="RFC2046" format="default" sectionFormat="of" derivedContent="RFC2046"/></td>
              <td align="left" colspan="1" rowspan="1">[Message Media Types] 	</td>
              <td align="left" colspan="1" rowspan="1">-</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">model</td>
              <td align="left" colspan="1" rowspan="1">
                <xref target="RFC2077" format="default" sectionFormat="of" derivedContent="RFC2077"/></td>
              <td align="left" colspan="1" rowspan="1">[Model Media Types]</td>
              <td align="left" colspan="1" rowspan="1">-</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">multipart</td>
              <td align="left" colspan="1" rowspan="1">
                <xref target="RFC2046" format="default" sectionFormat="of" derivedContent="RFC2046"/></td>
              <td align="left" colspan="1" rowspan="1">[Multipart Media Types]</td>
              <td align="left" colspan="1" rowspan="1">-</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">text</td>
              <td align="left" colspan="1" rowspan="1">
                <xref target="RFC2046" format="default" sectionFormat="of" derivedContent="RFC2046"/></td>
              <td align="left" colspan="1" rowspan="1">[Text Media Types]</td>
              <td align="left" colspan="1" rowspan="1">requires CRLF for newlines</td>
            </tr>
            <tr>
              <td align="left" colspan="1" rowspan="1">video</td>
              <td align="left" colspan="1" rowspan="1">
                <xref target="RFC2046" format="default" sectionFormat="of" derivedContent="RFC2046"/></td>
              <td align="left" colspan="1" rowspan="1">[Video Media Types]</td>
              <td align="left" colspan="1" rowspan="1">-</td>
            </tr>
          </tbody>
        </table>
      </section>
    </section>
    <section anchor="Security" numbered="true" toc="include" removeInRFC="false" pn="section-5">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-5-1">This document itself is not expected to introduce any security issues.
        The security issues related to introducing a new top-level media type <bcp14>MUST</bcp14> be evaluated
        and documented carefully.</t>
    </section>
    <section anchor="Acknowledgements" numbered="false" toc="include" removeInRFC="false" pn="section-6">
      <name slugifiedName="name-acknowledgements">Acknowledgements</name>
      <t indent="0" pn="section-6-1">Continuous encouragement for writing this document came from <contact fullname="Harald Alvestrand"/>.
      Further encouragement was provided by <contact fullname="Murray S. Kucherawy"/>. Both Harald and
      Murray also provided ideas for actual text. Without them, this memo would
      never have reached even the first draft stage.
      <contact fullname="Alexey Melnikov"/> provided the difficult to find pointer
      to RFC 2077 <xref target="RFC2077" format="default" sectionFormat="of" derivedContent="RFC2077"/>
      and examples for applications dispatching on top-level types.
      Additional information and comments were received from
      <contact fullname="Chris Lilley"/>, <contact fullname="Graham Kline"/>, <contact fullname="Henry S. Rzepa"/>, <contact fullname="Francesca Palombini"/>, <contact fullname="Zaheduzzaman Sarker"/>,
      <contact fullname="Amanda Baber"/>, <contact fullname="Paul Wouters"/>, <contact fullname="Roman Danyliw"/>, <contact fullname="John Scudder"/>, <contact fullname="Radia Perlman"/>, <contact fullname="Lars Eggert"/>,
      and <contact fullname="Antoine Fressancourt"/>.
      Inspiration for negative criteria or examples was provided by <contact fullname="Phillip Hallam-Baker"/>,
      <contact fullname="Donald E. Eastlake 3rd"/>, <contact fullname="Petter Reinholdtsen"/>, and <contact fullname="Christian Heller"/>.</t>
    </section>
  </middle>
  <back>
    <references pn="section-7">
      <name slugifiedName="name-references">References</name>
      <references pn="section-7.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="RFC6838" target="https://www.rfc-editor.org/info/rfc6838" quoteTitle="true" derivedAnchor="RFC6838">
          <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="RFC8126" target="https://www.rfc-editor.org/info/rfc8126" quoteTitle="true" derivedAnchor="RFC8126">
          <front>
            <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <date month="June" year="2017"/>
            <abstract>
              <t indent="0">Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
              <t indent="0">To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t>
              <t indent="0">This is the third edition of this document; it obsoletes RFC 5226.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="26"/>
          <seriesInfo name="RFC" value="8126"/>
          <seriesInfo name="DOI" value="10.17487/RFC8126"/>
        </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>
      </references>
      <references pn="section-7.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="CHEMICAL" target="https://en.wikipedia.org/w/index.php?title=Chemical_file_format&amp;oldid=1235421631" quoteTitle="true" derivedAnchor="CHEMICAL">
          <front>
            <title>Chemical file format</title>
            <author initials="" surname="" fullname="">
              <organization showOnFrontPage="true">Wikipedia</organization>
            </author>
            <date month="July" day="19" year="2024"/>
          </front>
        </reference>
        <reference anchor="CHEMIME" target="https://pubs.acs.org/doi/10.1021/ci9803233" quoteTitle="true" derivedAnchor="CHEMIME">
          <front>
            <title>The Application of Chemical Multipurpose Internet Mail Extensions (Chemical MIME) Internet Standards to Electronic Mail and World Wide Web Information Exchange</title>
            <author initials="H.S." surname="Rzepa" fullname="Henry S. Rzepa">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="P." surname="Murray-Rust" fullname="Peter Murray-Rust">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="B." surname="Whitaker" fullname="Benjamin Whitaker">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="1998" month="August" day="14"/>
          </front>
          <seriesInfo name="DOI" value="10.1021/ci9803233"/>
          <refcontent>Journal of Chemical Information Computer Science, vol. 38, no. 6, pp. 976-982</refcontent>
        </reference>
        <reference anchor="RDF" target="https://www.w3.org/TR/2014/REC-rdf11-concepts-20140225/" quoteTitle="true" derivedAnchor="RDF">
          <front>
            <title>RDF 1.1 Concepts and Abstract Syntax</title>
            <author initials="R." surname="Cyganiak" fullname="Richard Cyganiak">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="D." surname="Wood" fullname="David Wood">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="M." surname="Lanthaler" fullname="Markus Lanthaler">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2014" month="February" day="25"/>
          </front>
          <refcontent>W3C Recommendation</refcontent>
        </reference>
        <reference anchor="RFC1341" target="https://www.rfc-editor.org/info/rfc1341" quoteTitle="true" derivedAnchor="RFC1341">
          <front>
            <title>MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies</title>
            <author fullname="N. Borenstein" initials="N." surname="Borenstein"/>
            <author fullname="N. Freed" initials="N." surname="Freed"/>
            <date month="June" year="1992"/>
            <abstract>
              <t indent="0">This document redefines the format of message bodies to allow multi-part textual and non-textual message bodies to be represented and exchanged without loss of information. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="1341"/>
          <seriesInfo name="DOI" value="10.17487/RFC1341"/>
        </reference>
        <reference anchor="RFC1437" target="https://www.rfc-editor.org/info/rfc1437" quoteTitle="true" derivedAnchor="RFC1437">
          <front>
            <title>The Extension of MIME Content-Types to a New Medium</title>
            <author fullname="N. Borenstein" initials="N." surname="Borenstein"/>
            <author fullname="M. Linimon" initials="M." surname="Linimon"/>
            <date month="April" year="1993"/>
            <abstract>
              <t indent="0">This document defines one particular type of MIME data, the matter- transport/sentient-life-form type. This memo provides information for the Internet community. It does not specify an Internet standard.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="1437"/>
          <seriesInfo name="DOI" value="10.17487/RFC1437"/>
        </reference>
        <reference anchor="RFC2046" target="https://www.rfc-editor.org/info/rfc2046" quoteTitle="true" derivedAnchor="RFC2046">
          <front>
            <title>Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</title>
            <author fullname="N. Freed" initials="N." surname="Freed"/>
            <author fullname="N. Borenstein" initials="N." surname="Borenstein"/>
            <date month="November" year="1996"/>
            <abstract>
              <t indent="0">This second document defines the general structure of the MIME media typing system and defines an initial set of media types. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="2046"/>
          <seriesInfo name="DOI" value="10.17487/RFC2046"/>
        </reference>
        <reference anchor="RFC2048" target="https://www.rfc-editor.org/info/rfc2048" quoteTitle="true" derivedAnchor="RFC2048">
          <front>
            <title>Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures</title>
            <author fullname="N. Freed" initials="N." surname="Freed"/>
            <author fullname="J. Klensin" initials="J." surname="Klensin"/>
            <author fullname="J. Postel" initials="J." surname="Postel"/>
            <date month="November" year="1996"/>
            <abstract>
              <t indent="0">This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages. This fourth document, RFC 2048, specifies various IANA registration procedures for some MIME facilities. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="2048"/>
          <seriesInfo name="DOI" value="10.17487/RFC2048"/>
        </reference>
        <reference anchor="RFC2077" target="https://www.rfc-editor.org/info/rfc2077" quoteTitle="true" derivedAnchor="RFC2077">
          <front>
            <title>The Model Primary Content Type for Multipurpose Internet Mail Extensions</title>
            <author fullname="S. Nelson" initials="S." surname="Nelson"/>
            <author fullname="C. Parks" initials="C." surname="Parks"/>
            <author>
              <organization showOnFrontPage="true">Mitra</organization>
            </author>
            <date month="January" year="1997"/>
            <abstract>
              <t indent="0">The purpose of this memo is to propose an update to Internet RFC 2045 to include a new primary content-type to be known as "model". [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="2077"/>
          <seriesInfo name="DOI" value="10.17487/RFC2077"/>
        </reference>
        <reference anchor="RFC4735" target="https://www.rfc-editor.org/info/rfc4735" quoteTitle="true" derivedAnchor="RFC4735">
          <front>
            <title>Example Media Types for Use in Documentation</title>
            <author fullname="T. Taylor" initials="T." surname="Taylor"/>
            <date month="October" year="2006"/>
            <abstract>
              <t indent="0">This document is registration for the 'example' media type and 'example' subtypes within the standards tree. The 'example/*' and '*/example' media types are defined for documentation purposes only. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4735"/>
          <seriesInfo name="DOI" value="10.17487/RFC4735"/>
        </reference>
        <reference anchor="RFC6648" target="https://www.rfc-editor.org/info/rfc6648" quoteTitle="true" derivedAnchor="RFC6648">
          <front>
            <title>Deprecating the "X-" Prefix and Similar Constructs in Application Protocols</title>
            <author fullname="P. Saint-Andre" initials="P." surname="Saint-Andre"/>
            <author fullname="D. Crocker" initials="D." surname="Crocker"/>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <date month="June" year="2012"/>
            <abstract>
              <t indent="0">Historically, designers and implementers of application protocols have often distinguished between standardized and unstandardized parameters by prefixing the names of unstandardized parameters with the string "X-" or similar constructs. In practice, that convention causes more problems than it solves. Therefore, this document deprecates the convention for newly defined parameters with textual (as opposed to numerical) names in application protocols. This memo documents an Internet Best Current Practice.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="178"/>
          <seriesInfo name="RFC" value="6648"/>
          <seriesInfo name="DOI" value="10.17487/RFC6648"/>
        </reference>
        <reference anchor="RFC8081" target="https://www.rfc-editor.org/info/rfc8081" quoteTitle="true" derivedAnchor="RFC8081">
          <front>
            <title>The "font" Top-Level Media Type</title>
            <author fullname="C. Lilley" initials="C." surname="Lilley"/>
            <date month="February" year="2017"/>
            <abstract>
              <t indent="0">This memo serves to register and document the "font" top-level media type, under which subtypes for representation formats for fonts may be registered. This document also serves as a registration application for a set of intended subtypes, which are representative of some existing subtypes already in use, and currently registered under the "application" tree by their separate registrations.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8081"/>
          <seriesInfo name="DOI" value="10.17487/RFC8081"/>
        </reference>
        <reference anchor="RFC9695" target="https://www.rfc-editor.org/info/rfc9695" quoteTitle="true" derivedAnchor="RFC9695">
          <front>
            <title abbrev="The 'haptics' Top-Level Media Type">The 'haptics' Top-Level Media Type</title>
            <author fullname="Yeshwant K. Muthusamy" surname="Muthusamy" initials="Y. K.">
              <organization showOnFrontPage="true">Immersion Corporation</organization>
            </author>
            <author fullname="Chris Ullrich" surname="Ullrich" initials="C.">
              <organization showOnFrontPage="true">Immersion Corporation</organization>
            </author>
            <date month="March" year="2025"/>
          </front>
          <seriesInfo name="RFC" value="9695"/>
          <seriesInfo name="DOI" value="10.17487/RFC9695"/>
        </reference>
      </references>
    </references>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.a">
      <name slugifiedName="name-authors-address">Author's Address</name>
      <author fullname="Martin J. Dürst" initials="M.J." surname="Dürst">
        <organization showOnFrontPage="true">Aoyama Gakuin University</organization>
        <address>
          <postal>
            <street>Fuchinobe 5-10-1, Chuo-ku, Sagamihara</street>
            <region>Kanagawa</region>
            <code>252-5258</code>
            <country>Japan</country>
          </postal>
          <phone>+81 42 759 6329</phone>
          <email>duerst@it.aoyama.ac.jp</email>
          <uri>https://www.sw.it.aoyama.ac.jp/Dürst/</uri>
        </address>
      </author>
    </section>
  </back>
</rfc>
