<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="info" consensus="true" docName="draft-foudil-securitytxt-12" indexInclude="true" ipr="trust200902" number="9116" prepTime="2022-04-27T12:24:03" scripts="Common,Latin" sortRefs="true" submissionType="IETF" symRefs="true" tocDepth="3" tocInclude="true" xml:lang="en">
  <link href="https://datatracker.ietf.org/doc/draft-foudil-securitytxt-12" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc9116" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="security.txt">A File Format to Aid in Security Vulnerability Disclosure</title>
    <seriesInfo name="RFC" value="9116" stream="IETF"/>
    <author initials="E." surname="Foudil" fullname="Edwin Foudil">
      <organization showOnFrontPage="true"/>
      <address>
        <email>contact@edoverflow.com</email>
      </address>
    </author>
    <author initials="Y." surname="Shafranovich" fullname="Yakov Shafranovich">
      <organization showOnFrontPage="true">Nightwatch Cybersecurity</organization>
      <address>
        <email>yakov+ietf@nightwatchcybersecurity.com</email>
      </address>
    </author>
    <date month="04" year="2022"/>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">When security vulnerabilities are discovered by
researchers, proper reporting channels are often lacking. As a result,
vulnerabilities may be left unreported. This document defines a machine-parsable format
("security.txt") to help organizations describe their vulnerability disclosure practices
to make it easier for researchers to report vulnerabilities.</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 document is not an Internet Standards Track specification; it is
            published for informational purposes.  
        </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).  Not all documents
            approved by the IESG are candidates for any level of Internet
            Standard; see 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/rfc9116" 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) 2022 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-motivation-prior-work-and-s">Motivation, Prior Work, and Scope</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-terminology">Terminology</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-the-specification">The Specification</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-comments">Comments</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-line-separator">Line Separator</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-digital-signature">Digital Signature</xref></t>
              </li>
              <li pn="section-toc.1-1.2.2.4">
                <t indent="0" pn="section-toc.1-1.2.2.4.1"><xref derivedContent="2.4" format="counter" sectionFormat="of" target="section-2.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-extensibility">Extensibility</xref></t>
              </li>
              <li pn="section-toc.1-1.2.2.5">
                <t indent="0" pn="section-toc.1-1.2.2.5.1"><xref derivedContent="2.5" format="counter" sectionFormat="of" target="section-2.5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-field-definitions">Field Definitions</xref></t>
                <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.2.2.5.2">
                  <li pn="section-toc.1-1.2.2.5.2.1">
                    <t indent="0" pn="section-toc.1-1.2.2.5.2.1.1"><xref derivedContent="2.5.1" format="counter" sectionFormat="of" target="section-2.5.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgments">Acknowledgments</xref></t>
                  </li>
                  <li pn="section-toc.1-1.2.2.5.2.2">
                    <t indent="0" pn="section-toc.1-1.2.2.5.2.2.1"><xref derivedContent="2.5.2" format="counter" sectionFormat="of" target="section-2.5.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-canonical">Canonical</xref></t>
                  </li>
                  <li pn="section-toc.1-1.2.2.5.2.3">
                    <t indent="0" pn="section-toc.1-1.2.2.5.2.3.1"><xref derivedContent="2.5.3" format="counter" sectionFormat="of" target="section-2.5.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-contact">Contact</xref></t>
                  </li>
                  <li pn="section-toc.1-1.2.2.5.2.4">
                    <t indent="0" pn="section-toc.1-1.2.2.5.2.4.1"><xref derivedContent="2.5.4" format="counter" sectionFormat="of" target="section-2.5.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-encryption">Encryption</xref></t>
                  </li>
                  <li pn="section-toc.1-1.2.2.5.2.5">
                    <t indent="0" pn="section-toc.1-1.2.2.5.2.5.1"><xref derivedContent="2.5.5" format="counter" sectionFormat="of" target="section-2.5.5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-expires">Expires</xref></t>
                  </li>
                  <li pn="section-toc.1-1.2.2.5.2.6">
                    <t indent="0" pn="section-toc.1-1.2.2.5.2.6.1"><xref derivedContent="2.5.6" format="counter" sectionFormat="of" target="section-2.5.6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-hiring">Hiring</xref></t>
                  </li>
                  <li pn="section-toc.1-1.2.2.5.2.7">
                    <t indent="0" pn="section-toc.1-1.2.2.5.2.7.1"><xref derivedContent="2.5.7" format="counter" sectionFormat="of" target="section-2.5.7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-policy">Policy</xref></t>
                  </li>
                  <li pn="section-toc.1-1.2.2.5.2.8">
                    <t indent="0" pn="section-toc.1-1.2.2.5.2.8.1"><xref derivedContent="2.5.8" format="counter" sectionFormat="of" target="section-2.5.8"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-preferred-languages">Preferred-Languages</xref></t>
                  </li>
                </ul>
              </li>
              <li pn="section-toc.1-1.2.2.6">
                <t indent="0" pn="section-toc.1-1.2.2.6.1"><xref derivedContent="2.6" format="counter" sectionFormat="of" target="section-2.6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-example-of-an-unsigned-secu">Example of an Unsigned "security.txt" File</xref></t>
              </li>
              <li pn="section-toc.1-1.2.2.7">
                <t indent="0" pn="section-toc.1-1.2.2.7.1"><xref derivedContent="2.7" format="counter" sectionFormat="of" target="section-2.7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-example-of-a-signed-securit">Example of a Signed "security.txt" File</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-location-of-the-securitytxt">Location of the security.txt File</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.3.2">
              <li pn="section-toc.1-1.3.2.1">
                <t indent="0" pn="section-toc.1-1.3.2.1.1"><xref derivedContent="3.1" format="counter" sectionFormat="of" target="section-3.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-scope-of-the-file">Scope of the File</xref></t>
              </li>
            </ul>
          </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-file-format-description-and">File Format Description and ABNF Grammar</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>
            <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-compromised-files-and-incid">Compromised Files and Incident Response</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-redirects">Redirects</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.3">
                <t indent="0" pn="section-toc.1-1.5.2.3.1"><xref derivedContent="5.3" format="counter" sectionFormat="of" target="section-5.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-incorrect-or-stale-informat">Incorrect or Stale Information</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.4">
                <t indent="0" pn="section-toc.1-1.5.2.4.1"><xref derivedContent="5.4" format="counter" sectionFormat="of" target="section-5.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-intentionally-malformed-fil">Intentionally Malformed Files, Resources, and Reports</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.5">
                <t indent="0" pn="section-toc.1-1.5.2.5.1"><xref derivedContent="5.5" format="counter" sectionFormat="of" target="section-5.5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-no-implied-permission-for-t">No Implied Permission for Testing</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.6">
                <t indent="0" pn="section-toc.1-1.5.2.6.1"><xref derivedContent="5.6" format="counter" sectionFormat="of" target="section-5.6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-multi-user-environments">Multi-User Environments</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.7">
                <t indent="0" pn="section-toc.1-1.5.2.7.1"><xref derivedContent="5.7" format="counter" sectionFormat="of" target="section-5.7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-protecting-data-in-transit">Protecting Data in Transit</xref></t>
              </li>
              <li pn="section-toc.1-1.5.2.8">
                <t indent="0" pn="section-toc.1-1.5.2.8.1"><xref derivedContent="5.8" format="counter" sectionFormat="of" target="section-5.8"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-spam-and-spurious-reports">Spam and Spurious Reports</xref></t>
              </li>
            </ul>
          </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-well-known-uris-registry">Well-Known URIs Registry</xref></t>
              </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-registry-for-securitytxt-fi">Registry for security.txt Fields</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-2">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" toc="include" removeInRFC="false" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <section anchor="motivation" numbered="true" toc="include" removeInRFC="false" pn="section-1.1">
        <name slugifiedName="name-motivation-prior-work-and-s">Motivation, Prior Work, and Scope</name>
        <t indent="0" pn="section-1.1-1">Many security researchers encounter situations where they are unable
to report security vulnerabilities to organizations because there are
no reporting channels to contact the owner of a particular
resource, and no information is available about the vulnerability disclosure practices
of such owner.</t>
        <t indent="0" pn="section-1.1-2">As per <xref target="RFC2142" section="4" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc2142#section-4" derivedContent="RFC2142"/>, there is an existing convention
of using the &lt;SECURITY@domain&gt; email address for communications regarding
security issues. That convention provides only a single, email-based
channel of communication per domain and does not provide
a way for domain owners to publish information about their security disclosure
practices.</t>
        <t indent="0" pn="section-1.1-3">There are also contact conventions prescribed for Internet Service Providers (ISPs)
in <xref target="RFC3013" section="2" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc3013#section-2" derivedContent="RFC3013"/>, for Computer Security Incident Response Teams (CSIRTs)
in <xref target="RFC2350" section="3.2" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc2350#section-3.2" derivedContent="RFC2350"/>, and for site operators in <xref target="RFC2196" section="5.2" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc2196#section-5.2" derivedContent="RFC2196"/>. As per <xref target="RFC7485" format="default" sectionFormat="of" derivedContent="RFC7485"/>, there is also contact information provided by
Regional Internet Registries (RIRs) and domain registries for owners of IP
addresses, Autonomous System Numbers (ASNs), and domain names. However, none of
these tackle the issue of how security researchers can locate contact information
and vulnerability disclosure practices for organizations in order to report
vulnerabilities.</t>
        <t indent="0" pn="section-1.1-4">In this document, we define a richer, machine-parsable, and more extensible way
for organizations to communicate information about their security disclosure
practices and ways to contact them. Other details of vulnerability disclosure
are outside the scope of this document. Readers are encouraged to consult other
documents such as <xref target="ISO.29147.2018" format="default" sectionFormat="of" derivedContent="ISO.29147.2018"/> or <xref target="CERT.CVD" format="default" sectionFormat="of" derivedContent="CERT.CVD"/>.</t>
        <t indent="0" pn="section-1.1-5">As per <xref target="CERT.CVD" format="default" sectionFormat="of" derivedContent="CERT.CVD"/>, "vulnerability response" refers to reports of product vulnerabilities,
which is related to but distinct from reports of network intrusions and compromised
websites ("incident response"). The mechanism defined in this document is intended
to be used for the former ("vulnerability response"). If implementors want
to utilize this mechanism for incident response, they should be aware of additional
security considerations discussed in <xref target="compromise" format="default" sectionFormat="of" derivedContent="Section 5.1"/>.</t>
        <t indent="0" pn="section-1.1-6">The "security.txt" file is intended to be complementary and not a substitute
or replacement for other public resources maintained by organizations regarding
their security disclosure practices.</t>
      </section>
      <section anchor="terminology" numbered="true" toc="include" removeInRFC="false" pn="section-1.2">
        <name slugifiedName="name-terminology">Terminology</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>
        <t indent="0" pn="section-1.2-2">The term "researcher" corresponds
to the terms "finder" and "reporter" in <xref target="ISO.29147.2018" format="default" sectionFormat="of" derivedContent="ISO.29147.2018"/> and <xref target="CERT.CVD" format="default" sectionFormat="of" derivedContent="CERT.CVD"/>.
The term "organization" corresponds to the term "vendor"
in <xref target="ISO.29147.2018" format="default" sectionFormat="of" derivedContent="ISO.29147.2018"/> and <xref target="CERT.CVD" format="default" sectionFormat="of" derivedContent="CERT.CVD"/>.</t>
        <t indent="0" pn="section-1.2-3">The term "implementors" includes all parties involved in
the vulnerability disclosure process.</t>
      </section>
    </section>
    <section anchor="the-specification" numbered="true" toc="include" removeInRFC="false" pn="section-2">
      <name slugifiedName="name-the-specification">The Specification</name>
      <t indent="0" pn="section-2-1">This document defines a text file to be placed in a known location
that provides information about vulnerability disclosure practices of a particular organization.
The format of this file is machine parsable and <bcp14>MUST</bcp14> follow the ABNF grammar defined in
<xref target="abnf" format="default" sectionFormat="of" derivedContent="Section 4"/>. This file is intended to help security researchers when
disclosing security vulnerabilities.</t>
      <t indent="0" pn="section-2-2">By convention, the file is named "security.txt". The location and scope are described
in <xref target="location" format="default" sectionFormat="of" derivedContent="Section 3"/>.</t>
      <t indent="0" pn="section-2-3">This text file contains multiple fields with different values. A field contains a "name", which is the first part of a field all the way up
to the colon (for example: "Contact:") and follows the syntax defined for "field-name" in <xref target="RFC5322" section="3.6.8" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc5322#section-3.6.8" derivedContent="RFC5322"/>. Field names are case insensitive (as per <xref target="RFC5234" section="2.3" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc5234#section-2.3" derivedContent="RFC5234"/>).
The "value" comes after the field name (for example: "mailto:security@example.com") and follows the syntax
defined for "unstructured" in <xref target="RFC5322" section="3.2.5" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc5322#section-3.2.5" derivedContent="RFC5322"/>. The file <bcp14>MAY</bcp14> also contain blank lines.</t>
      <t indent="0" pn="section-2-4">A field <bcp14>MUST</bcp14> always consist of a name and a value
(for example: "Contact: mailto:security@example.com"). A "security.txt" file
can have an unlimited number of fields. Each field <bcp14>MUST</bcp14> appear on
its own line. Unless otherwise specified by the field definition,
multiple values <bcp14>MUST NOT</bcp14> be chained together for a single field.
Unless otherwise indicated in a definition of a particular field, a field <bcp14>MAY</bcp14> appear
multiple times.</t>
      <t indent="0" pn="section-2-5">Implementors should be aware that some of the fields may
contain URIs using percent-encoding (as per <xref target="RFC3986" section="2.1" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc3986#section-2.1" derivedContent="RFC3986"/>).</t>
      <section anchor="comments" numbered="true" toc="include" removeInRFC="false" pn="section-2.1">
        <name slugifiedName="name-comments">Comments</name>
        <t indent="0" pn="section-2.1-1">Any line beginning with the "#" (%x23) symbol <bcp14>MUST</bcp14> be interpreted as a comment. The content of the comment may contain any ASCII or Unicode characters in the
	%x21-7E and %x80-FFFFF ranges plus the tab (%x09) and space (%x20) characters.</t>
        <t indent="0" pn="section-2.1-2">Example:</t>
        <artwork name="" type="" align="left" alt="" pn="section-2.1-3">
# This is a comment.
</artwork>
      </section>
      <section anchor="line-separator" numbered="true" toc="include" removeInRFC="false" pn="section-2.2">
        <name slugifiedName="name-line-separator">Line Separator</name>
        <t indent="0" pn="section-2.2-1">Every line <bcp14>MUST</bcp14> end with either a carriage return and line feed
characters (CRLF / %x0D %x0A) or just a line feed character (LF / %x0A).</t>
      </section>
      <section anchor="signature" numbered="true" toc="include" removeInRFC="false" pn="section-2.3">
        <name slugifiedName="name-digital-signature">Digital Signature</name>
        <t indent="0" pn="section-2.3-1">It is <bcp14>RECOMMENDED</bcp14> that a "security.txt" file be digitally signed
using an OpenPGP cleartext signature as described in <xref target="RFC4880" section="7" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc4880#section-7" derivedContent="RFC4880"/>. When digital signatures are used, it is also
<bcp14>RECOMMENDED</bcp14> that organizations use the "Canonical" field (as per <xref target="canonical" format="default" sectionFormat="of" derivedContent="Section 2.5.2"/>),
thus allowing the digital signature to authenticate the location of the file.</t>
        <t indent="0" pn="section-2.3-2">When it comes to verifying the key used to generate the signature, it is always
the security researcher's responsibility to make sure the key being
used is indeed one they trust.</t>
      </section>
      <section anchor="extensibility" numbered="true" toc="include" removeInRFC="false" pn="section-2.4">
        <name slugifiedName="name-extensibility">Extensibility</name>
        <t indent="0" pn="section-2.4-1">Like many other formats and protocols, this format may need to be changed
over time to fit the ever-changing landscape of the Internet. Therefore,
extensibility is provided via an IANA registry for fields as defined
in <xref target="registry" format="default" sectionFormat="of" derivedContent="Section 6.2"/>. Any fields registered via that process <bcp14>MUST</bcp14> be
considered optional. To encourage extensibility and interoperability,
researchers <bcp14>MUST</bcp14> ignore any fields they do not explicitly support.</t>
        <t indent="0" pn="section-2.4-2">In general, implementors should "be conservative in what you do,
be liberal in what you accept from others" (as per <xref target="RFC0793" format="default" sectionFormat="of" derivedContent="RFC0793"/>).</t>
      </section>
      <section anchor="field-definitions" numbered="true" toc="include" removeInRFC="false" pn="section-2.5">
        <name slugifiedName="name-field-definitions">Field Definitions</name>
        <t indent="0" pn="section-2.5-1">Unless otherwise stated, all fields <bcp14>MUST</bcp14> be considered optional.</t>
        <section anchor="acknowledgments" numbered="true" toc="include" removeInRFC="false" pn="section-2.5.1">
          <name slugifiedName="name-acknowledgments">Acknowledgments</name>
          <t indent="0" pn="section-2.5.1-1">The "Acknowledgments" field indicates a link to a page where security
researchers are recognized for their reports. The page being referenced
should list security researchers that reported security vulnerabilities
and collaborated to remediate them. Organizations should be careful
to limit the vulnerability information being published in order
to prevent future attacks.</t>
          <t indent="0" pn="section-2.5.1-2">If this field indicates a web URI, then it <bcp14>MUST</bcp14> begin with "https://"
(as per <xref target="RFC7230" section="2.7.2" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc7230#section-2.7.2" derivedContent="RFC7230"/>).</t>
          <t indent="0" pn="section-2.5.1-3">Example:</t>
          <artwork name="" type="" align="left" alt="" pn="section-2.5.1-4">
Acknowledgments: https://example.com/hall-of-fame.html
</artwork>
          <t indent="0" pn="section-2.5.1-5">Example security acknowledgments page:</t>
          <artwork name="" type="" align="left" alt="" pn="section-2.5.1-6">
We would like to thank the following researchers:

(2017-04-15) Frank Denis - Reflected cross-site scripting
(2017-01-02) Alice Quinn  - SQL injection
(2016-12-24) John Buchner - Stored cross-site scripting
(2016-06-10) Anna Richmond - A server configuration issue
</artwork>
        </section>
        <section anchor="canonical" numbered="true" toc="include" removeInRFC="false" pn="section-2.5.2">
          <name slugifiedName="name-canonical">Canonical</name>
          <t indent="0" pn="section-2.5.2-1">The "Canonical" field indicates the canonical URIs where the "security.txt" file is located,
which is usually something like "https://example.com/.well-known/security.txt".
If this field indicates a web URI, then it <bcp14>MUST</bcp14> begin with "https://"
(as per <xref target="RFC7230" section="2.7.2" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc7230#section-2.7.2" derivedContent="RFC7230"/>).</t>
          <t indent="0" pn="section-2.5.2-2">While this field indicates that a "security.txt" retrieved from a given URI
is intended to apply to that URI, it <bcp14>MUST NOT</bcp14> be interpreted to apply to
all canonical URIs listed within the file. Researchers <bcp14>SHOULD</bcp14> use an additional
trust mechanism such as a digital signature (as per <xref target="signature" format="default" sectionFormat="of" derivedContent="Section 2.3"/>) to make the
determination that a particular canonical URI is applicable.</t>
          <t indent="0" pn="section-2.5.2-3">If this field appears within a "security.txt" file and the URI used to
retrieve that file is not listed within any canonical fields,
then the contents of the file <bcp14>SHOULD NOT</bcp14> be trusted.</t>
          <artwork name="" type="" align="left" alt="" pn="section-2.5.2-4">
Canonical: https://www.example.com/.well-known/security.txt
Canonical: https://someserver.example.com/.well-known/security.txt
</artwork>
        </section>
        <section anchor="contact" numbered="true" toc="include" removeInRFC="false" pn="section-2.5.3">
          <name slugifiedName="name-contact">Contact</name>
          <t indent="0" pn="section-2.5.3-1">The "Contact" field indicates a method that researchers
should use for reporting security
vulnerabilities such as an email address, a phone number, and/or a
web page with contact information. This field <bcp14>MUST</bcp14>
always be present in a "security.txt" file. If this field indicates a web URI,
then it <bcp14>MUST</bcp14> begin with "https://" (as per <xref target="RFC7230" section="2.7.2" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc7230#section-2.7.2" derivedContent="RFC7230"/>).
Security email addresses should use the conventions defined in <xref target="RFC2142" section="4" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc2142#section-4" derivedContent="RFC2142"/>.</t>
          <t indent="0" pn="section-2.5.3-2">The value <bcp14>MUST</bcp14> follow the URI syntax described in <xref target="RFC3986" section="3" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc3986#section-3" derivedContent="RFC3986"/>.
This means that "mailto" and "tel" URI schemes must be used
when specifying email addresses and telephone numbers, as defined in <xref target="RFC6068" format="default" sectionFormat="of" derivedContent="RFC6068"/>
and <xref target="RFC3966" format="default" sectionFormat="of" derivedContent="RFC3966"/>. When the value of this field is an email address,
	  it is <bcp14>RECOMMENDED</bcp14> that encryption be used (as per <xref target="encryption" format="default" sectionFormat="of" derivedContent="Section 2.5.4"/>).</t>
          <t indent="0" pn="section-2.5.3-3">These <bcp14>SHOULD</bcp14> be listed in order of preference, with the first occurrence being the preferred
method of contact, the second occurrence being the second most preferred method of contact, etc. In the example below, the first email address
("security@example.com") is the preferred method of contact.</t>
          <artwork name="" type="" align="left" alt="" pn="section-2.5.3-4">
Contact: mailto:security@example.com
Contact: mailto:security%2Buri%2Bencoded@example.com
Contact: tel:+1-201-555-0123
Contact: https://example.com/security-contact.html
</artwork>
        </section>
        <section anchor="encryption" numbered="true" toc="include" removeInRFC="false" pn="section-2.5.4">
          <name slugifiedName="name-encryption">Encryption</name>
          <t indent="0" pn="section-2.5.4-1">The "Encryption" field indicates an encryption key that
security researchers should use for encrypted communication. Keys <bcp14>MUST NOT</bcp14>
appear in this field. Instead, the value of this field
<bcp14>MUST</bcp14> be a URI pointing to a location where the key can be retrieved.
If this field indicates a web URI, then it <bcp14>MUST</bcp14> begin with "https://"
(as per <xref target="RFC7230" section="2.7.2" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc7230#section-2.7.2" derivedContent="RFC7230"/>).</t>
          <t indent="0" pn="section-2.5.4-2">When it comes to verifying the authenticity of the key, it is always the security
researcher's responsibility to make sure the key being specified is indeed one
they trust. Researchers must not assume that this key is
used to generate the digital signature referenced in <xref target="signature" format="default" sectionFormat="of" derivedContent="Section 2.3"/>.</t>
          <t indent="0" pn="section-2.5.4-3">Example of an OpenPGP key available from a web server:</t>
          <artwork name="" type="" align="left" alt="" pn="section-2.5.4-4">
Encryption: https://example.com/pgp-key.txt
</artwork>
          <t indent="0" pn="section-2.5.4-5">Example of an OpenPGP key available from an OPENPGPKEY DNS record:</t>
          <artwork name="" type="" align="left" alt="" pn="section-2.5.4-6">
Encryption: dns:5d2d37ab76d47d36._openpgpkey.example.com?type=OPENPGPKEY
</artwork>
          <t indent="0" pn="section-2.5.4-7">Example of an OpenPGP key being referenced by its fingerprint:</t>
          <artwork name="" type="" align="left" alt="" pn="section-2.5.4-8">
Encryption: openpgp4fpr:5f2de5521c63a801ab59ccb603d49de44b29100f
</artwork>
        </section>
        <section anchor="expires" numbered="true" toc="include" removeInRFC="false" pn="section-2.5.5">
          <name slugifiedName="name-expires">Expires</name>
          <t indent="0" pn="section-2.5.5-1">The "Expires" field indicates the date and time after which the data contained in the "security.txt"
file is considered stale and should not be used (as per <xref target="stale" format="default" sectionFormat="of" derivedContent="Section 5.3"/>). The value of this field is formatted
according to the Internet profiles of <xref target="ISO.8601-1" format="default" sectionFormat="of" derivedContent="ISO.8601-1"/> and <xref target="ISO.8601-2" format="default" sectionFormat="of" derivedContent="ISO.8601-2"/> as defined in <xref target="RFC3339" format="default" sectionFormat="of" derivedContent="RFC3339"/>. It is <bcp14>RECOMMENDED</bcp14> that the value
of this field be less than a year into the future to avoid staleness.</t>
          <t indent="0" pn="section-2.5.5-2">This field <bcp14>MUST</bcp14> always be present and <bcp14>MUST NOT</bcp14> appear more than once.</t>
          <artwork name="" type="" align="left" alt="" pn="section-2.5.5-3">
Expires: 2021-12-31T18:37:07z
</artwork>
        </section>
        <section anchor="hiring" numbered="true" toc="include" removeInRFC="false" pn="section-2.5.6">
          <name slugifiedName="name-hiring">Hiring</name>
          <t indent="0" pn="section-2.5.6-1">The "Hiring" field is used for linking to the vendor's security-related job positions.
If this field indicates a web URI, then it <bcp14>MUST</bcp14> begin with "https://"
(as per <xref target="RFC7230" section="2.7.2" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc7230#section-2.7.2" derivedContent="RFC7230"/>).</t>
          <artwork name="" type="" align="left" alt="" pn="section-2.5.6-2">
Hiring: https://example.com/jobs.html
</artwork>
        </section>
        <section anchor="policy" numbered="true" toc="include" removeInRFC="false" pn="section-2.5.7">
          <name slugifiedName="name-policy">Policy</name>
          <t indent="0" pn="section-2.5.7-1">The "Policy" field indicates a link to where the vulnerability disclosure policy is located.
This can help security researchers understand
the organization's vulnerability reporting practices.
If this field indicates a web URI, then it <bcp14>MUST</bcp14> begin with "https://"
(as per <xref target="RFC7230" section="2.7.2" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc7230#section-2.7.2" derivedContent="RFC7230"/>).</t>
          <t indent="0" pn="section-2.5.7-2">Example:</t>
          <artwork name="" type="" align="left" alt="" pn="section-2.5.7-3">
Policy: https://example.com/disclosure-policy.html
</artwork>
        </section>
        <section anchor="preflang" numbered="true" toc="include" removeInRFC="false" pn="section-2.5.8">
          <name slugifiedName="name-preferred-languages">Preferred-Languages</name>
          <t indent="0" pn="section-2.5.8-1">The "Preferred-Languages" field can be used to indicate a set of natural languages that
are preferred when submitting security reports. This set <bcp14>MAY</bcp14> list multiple
values, separated by commas. If this field is included, then at least
one value <bcp14>MUST</bcp14> be listed. The values within this set are language tags
(as defined in <xref target="RFC5646" format="default" sectionFormat="of" derivedContent="RFC5646"/>). If this field is absent, security researchers
may assume that English is the language to be used (as per <xref target="RFC2277" section="4.5" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc2277#section-4.5" derivedContent="RFC2277"/>).</t>
          <t indent="0" pn="section-2.5.8-2">The order in which they appear is not an indication of priority;
the listed languages are intended to have equal priority.</t>
          <t indent="0" pn="section-2.5.8-3">This field <bcp14>MUST NOT</bcp14> appear more than once.</t>
          <t indent="0" pn="section-2.5.8-4">Example (English, Spanish and French):</t>
          <artwork name="" type="" align="left" alt="" pn="section-2.5.8-5">
Preferred-Languages: en, es, fr
</artwork>
        </section>
      </section>
      <section anchor="example-of-an-unsigned-securitytxt-file" numbered="true" toc="include" removeInRFC="false" pn="section-2.6">
        <name slugifiedName="name-example-of-an-unsigned-secu">Example of an Unsigned "security.txt" File</name>
        <artwork name="" type="" align="left" alt="" pn="section-2.6-1">
# Our security address
Contact: mailto:security@example.com

# Our OpenPGP key
Encryption: https://example.com/pgp-key.txt

# Our security policy
Policy: https://example.com/security-policy.html

# Our security acknowledgments page
Acknowledgments: https://example.com/hall-of-fame.html

Expires: 2021-12-31T18:37:07z
</artwork>
      </section>
      <section anchor="example-of-a-signed-securitytxt-file" numbered="true" toc="include" removeInRFC="false" pn="section-2.7">
        <name slugifiedName="name-example-of-a-signed-securit">Example of a Signed "security.txt" File</name>
        <artwork name="" type="" align="left" alt="" pn="section-2.7-1">
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

# Canonical URI
Canonical: https://example.com/.well-known/security.txt

# Our security address
Contact: mailto:security@example.com

# Our OpenPGP key
Encryption: https://example.com/pgp-key.txt

# Our security policy
Policy: https://example.com/security-policy.html

# Our security acknowledgments page
Acknowledgments: https://example.com/hall-of-fame.html

Expires: 2021-12-31T18:37:07z
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.2

[signature]
-----END PGP SIGNATURE-----
</artwork>
      </section>
    </section>
    <section anchor="location" numbered="true" toc="include" removeInRFC="false" pn="section-3">
      <name slugifiedName="name-location-of-the-securitytxt">Location of the security.txt File</name>
      <t indent="0" pn="section-3-1">For web-based services, organizations <bcp14>MUST</bcp14> place the "security.txt" file under the "/.well-known/" path, e.g., https://example.com/.well-known/security.txt
as per <xref target="RFC8615" format="default" sectionFormat="of" derivedContent="RFC8615"/> of a domain name or IP address. For legacy compatibility, a "security.txt" file might be placed at the top-level path
or redirect (as per <xref target="RFC7231" section="6.4" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc7231#section-6.4" derivedContent="RFC7231"/>) to the "security.txt" file under the "/.well-known/" path. If a "security.txt" file
is present in both locations, the one in the "/.well-known/" path <bcp14>MUST</bcp14> be used.</t>
      <t indent="0" pn="section-3-2">The file <bcp14>MUST</bcp14> be accessed via HTTP 1.0 or a higher version,
and the file access <bcp14>MUST</bcp14> use the "https" scheme (as per <xref target="RFC7230" section="2.7.2" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc7230#section-2.7.2" derivedContent="RFC7230"/>).
It <bcp14>MUST</bcp14> have a Content-Type of "text/plain"
with the default charset parameter set to "utf-8" (as per <xref target="RFC2046" section="4.1.3" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc2046#section-4.1.3" derivedContent="RFC2046"/>).</t>
      <t indent="0" pn="section-3-3">Retrieval of "security.txt" files and resources indicated within such files may result in a redirect (as per <xref target="RFC7231" section="6.4" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc7231#section-6.4" derivedContent="RFC7231"/>). Researchers should perform additional analysis (as per <xref target="redirects" format="default" sectionFormat="of" derivedContent="Section 5.2"/>) to make sure these redirects
are not malicious or pointing to resources controlled by an attacker.</t>
      <section anchor="scope-of-the-file" numbered="true" toc="include" removeInRFC="false" pn="section-3.1">
        <name slugifiedName="name-scope-of-the-file">Scope of the File</name>
        <t indent="0" pn="section-3.1-1">A "security.txt" file <bcp14>MUST</bcp14> only apply to the domain
or IP address in the URI used to retrieve it, not to any of its subdomains or parent domains.
A "security.txt" file <bcp14>MAY</bcp14> also apply to products and services provided by the organization publishing the file.</t>
        <t indent="0" pn="section-3.1-2">As per <xref target="motivation" format="default" sectionFormat="of" derivedContent="Section 1.1"/>, this specification is intended for a vulnerability response.
If implementors want to use this for an incident response, they should be aware of additional security considerations discussed in <xref target="compromise" format="default" sectionFormat="of" derivedContent="Section 5.1"/>.</t>
        <t indent="0" pn="section-3.1-3">Organizations <bcp14>SHOULD</bcp14> use the policy directive (as per <xref target="policy" format="default" sectionFormat="of" derivedContent="Section 2.5.7"/>)
to provide additional details regarding the scope and details of their vulnerability disclosure process.</t>
        <t indent="0" pn="section-3.1-4">Some examples appear below:</t>
        <artwork name="" type="" align="left" alt="" pn="section-3.1-5">
# The following only applies to example.com.
https://example.com/.well-known/security.txt

# This only applies to subdomain.example.com.
https://subdomain.example.com/.well-known/security.txt

# This security.txt file applies to IPv4 address of 192.0.2.0.
https://192.0.2.0/.well-known/security.txt

# This security.txt file applies to IPv6 address of 2001:db8:8:4::2.
https://[2001:db8:8:4::2]/.well-known/security.txt
</artwork>
      </section>
    </section>
    <section anchor="abnf" numbered="true" toc="include" removeInRFC="false" pn="section-4">
      <name slugifiedName="name-file-format-description-and">File Format Description and ABNF Grammar</name>
      <t indent="0" keepWithNext="true" pn="section-4-1">The file format of the "security.txt" file <bcp14>MUST</bcp14> be plain text (MIME type "text/plain") as defined
      in <xref target="RFC2046" section="4.1.3" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc2046#section-4.1.3" derivedContent="RFC2046"/> and <bcp14>MUST</bcp14> be encoded using UTF-8 <xref target="RFC3629" format="default" sectionFormat="of" derivedContent="RFC3629"/> in Net-Unicode form <xref target="RFC5198" format="default" sectionFormat="of" derivedContent="RFC5198"/>.</t>
      <t indent="0" pn="section-4-2">The format of this file <bcp14>MUST</bcp14> follow the ABNF definition below (which incorporates the core ABNF rules from
      <xref target="RFC5234" format="default" sectionFormat="of" derivedContent="RFC5234"/> and uses the case-sensitive string support from <xref target="RFC7405" format="default" sectionFormat="of" derivedContent="RFC7405"/>).</t>
      <sourcecode type="abnf" markers="false" pn="section-4-3">
body             =  signed / unsigned

unsigned       =  *line (contact-field eol) ; one or more required
                  *line (expires-field eol) ; exactly one required
                  *line [lang-field eol] *line ; exactly one optional
                  ; order of fields within the file is not important
                  ; except that if contact-field appears more
                  ; than once, the order of those indicates
                  ; priority (see Section 3.5.3)

; signed is the production that should match the OpenPGP clearsigned
; document
signed           =  cleartext-header
                    1*(hash-header)
                    CRLF
                    cleartext
                    signature

cleartext-header =  %s"-----BEGIN PGP SIGNED MESSAGE-----" CRLF

hash-header      =  %s"Hash: " hash-alg *("," hash-alg) CRLF

hash-alg         =  token
                      ; imported from RFC 2045; see RFC 4880 Section
                      ; 10.3.3 for a pointer to the registry of
                      ; valid values

;cleartext       =  1*( UTF8-octets [CR] LF)
                      ; dash-escaped per RFC 4880 Section 7.1

cleartext        =  *((line-dash / line-from / line-nodash) [CR] LF)

line-dash        =  ("- ") "-" *UTF8-char-not-cr
                       ; MUST include initial "- "

line-from        =  ["- "] "From " *UTF8-char-not-cr
                      ; SHOULD include initial "- "

line-nodash      =  ["- "] *UTF8-char-not-cr
                      ; MAY include initial "- "

UTF8-char-not-dash =  UTF8-1-not-dash / UTF8-2 / UTF8-3 / UTF8-4
UTF8-1-not-dash  =  %x00-2C / %x2E-7F
UTF8-char-not-cr =  UTF8-1-not-cr / UTF8-2 / UTF8-3 / UTF8-4
UTF8-1-not-cr    =  %x00-0C / %x0E-7F

; UTF8 rules from RFC 3629
UTF8-octets      =  *( UTF8-char )
UTF8-char        =  UTF8-1 / UTF8-2 / UTF8-3 / UTF8-4
UTF8-1           =  %x00-7F
UTF8-2           =  %xC2-DF UTF8-tail
UTF8-3           =  %xE0 %xA0-BF UTF8-tail / %xE1-EC 2( UTF8-tail ) /
                    %xED %x80-9F UTF8-tail / %xEE-EF 2( UTF8-tail )
UTF8-4           =  %xF0 %x90-BF 2( UTF8-tail ) /
                    %xF1-F3 3( UTF8-tail ) /
                    %xF4 %x80-8F 2( UTF8-tail )
UTF8-tail        =  %x80-BF

signature        =  armor-header
                    armor-keys
                    CRLF
                    signature-data
                    armor-tail

armor-header     =  %s"-----BEGIN PGP SIGNATURE-----" CRLF

armor-keys       =  *(token ": " *( VCHAR / WSP ) CRLF)
                      ; Armor Header Keys from RFC 4880

armor-tail       =  %s"-----END PGP SIGNATURE-----" CRLF

signature-data   =  1*(1*(ALPHA / DIGIT / "=" / "+" / "/") CRLF)
                      ; base64; see RFC 4648
                      ; includes RFC 4880 checksum

line             =  [ (field / comment) ] eol

eol              =  *WSP [CR] LF

field            =  ; optional fields
                    ack-field /
                    can-field /
                    contact-field / ; optional repeated instances
                    encryption-field /
                    hiring-field /
                    policy-field /
                    ext-field

fs               =  ":"

comment          =  "#" *(WSP / VCHAR / %x80-FFFFF)

ack-field        =  "Acknowledgments" fs SP uri

can-field        =  "Canonical" fs SP uri

contact-field    =  "Contact" fs SP uri

expires-field    =  "Expires" fs SP date-time

encryption-field =  "Encryption" fs SP uri

hiring-field     =  "Hiring" fs SP uri

lang-field       =  "Preferred-Languages" fs SP lang-values

policy-field     =  "Policy" fs SP uri

date-time        =  &lt; imported from Section 5.6 of [RFC3339] &gt;

lang-tag         =  &lt; Language-Tag from Section 2.1 of [RFC5646] &gt;

lang-values      =  lang-tag *(*WSP "," *WSP lang-tag)

uri              =  &lt; URI as per Section 3 of [RFC3986] &gt;

ext-field        =  field-name fs SP unstructured

field-name       =  &lt; imported from Section 3.6.8 of [RFC5322] &gt;

unstructured     =  &lt; imported from Section 3.2.5 of [RFC5322] &gt;

token            =  &lt; imported from Section 5.1 of [RFC2045] &gt;

ALPHA            =  %x41-5A / %x61-7A   ; A-Z / a-z

BIT              =  "0" / "1"

CHAR             =  %x01-7F
                      ; any 7-bit US-ASCII character,
                      ;  excluding NUL

CR               =  %x0D
                      ; carriage return

CRLF             =  CR LF
                      ; Internet standard newline

CTL              =  %x00-1F / %x7F
                      ; controls

DIGIT            =  %x30-39
                      ; 0-9

DQUOTE           =  %x22
                      ; " (Double Quote)

HEXDIG           =  DIGIT / "A" / "B" / "C" / "D" / "E" / "F"

HTAB             =  %x09
                      ; horizontal tab

LF               =  %x0A
                      ; linefeed

LWSP             =  *(WSP / CRLF WSP)
                      ; Use of this linear-white-space rule
                      ;  permits lines containing only white
                      ;  space that are no longer legal in
                      ;  mail headers and have caused
                      ;  interoperability problems in other
                      ;  contexts.
                      ; Do not use when defining mail
                      ;  headers and use with caution in
                      ;  other contexts.

OCTET            =  %x00-FF
                      ; 8 bits of data

SP               =  %x20

VCHAR            =  %x21-7E
                      ; visible (printing) characters

WSP              =  SP / HTAB
                      ; white space
</sourcecode>
      <t indent="0" pn="section-4-4">"ext-field" refers to extension fields, which are discussed in <xref target="extensibility" format="default" sectionFormat="of" derivedContent="Section 2.4"/>.</t>
    </section>
    <section anchor="security-considerations" numbered="true" toc="include" removeInRFC="false" pn="section-5">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-5-1">Because of the use of URIs and well-known resources, security considerations of
<xref target="RFC3986" format="default" sectionFormat="of" derivedContent="RFC3986"/> and <xref target="RFC8615" format="default" sectionFormat="of" derivedContent="RFC8615"/> apply here, in addition to the
considerations outlined below.</t>
      <section anchor="compromise" numbered="true" toc="include" removeInRFC="false" pn="section-5.1">
        <name slugifiedName="name-compromised-files-and-incid">Compromised Files and Incident Response</name>
        <t indent="0" pn="section-5.1-1">An attacker that has compromised a website is able to compromise
the "security.txt" file as well or set up a redirect to their own site.
This can result in security reports not being received by the organization
or being sent to the attacker.</t>
        <t indent="0" pn="section-5.1-2">To protect against this, organizations should use the "Canonical" field to indicate the locations
of the file (as per <xref target="canonical" format="default" sectionFormat="of" derivedContent="Section 2.5.2"/>), digitally sign their "security.txt"
files (as per <xref target="signature" format="default" sectionFormat="of" derivedContent="Section 2.3"/>), and regularly monitor the file and
the referenced resources to detect tampering.</t>
        <t indent="0" pn="section-5.1-3">Security researchers should validate the "security.txt" file, including verifying
the digital signature and checking any available historical records before using the information
contained in the file. If the "security.txt" file looks suspicious or compromised,
it should not be used.</t>
        <t indent="0" pn="section-5.1-4">While it is not recommended, implementors may choose to use the information published
within a "security.txt" file for an incident response. In such cases, extreme caution
should be taken before trusting such information, since
it may have been compromised by an attacker. Researchers should use additional methods
to verify such data including out-of-band verification of the Pretty Good Privacy (PGP) signature, DNSSEC-based approaches, etc.</t>
      </section>
      <section anchor="redirects" numbered="true" toc="include" removeInRFC="false" pn="section-5.2">
        <name slugifiedName="name-redirects">Redirects</name>
        <t indent="0" pn="section-5.2-1">When retrieving the file and any resources referenced in the file, researchers should record
any redirects since they can lead to a different domain or IP address controlled by an attacker. Further
inspection of such redirects is recommended before using the information contained within the file.</t>
      </section>
      <section anchor="stale" numbered="true" toc="include" removeInRFC="false" pn="section-5.3">
        <name slugifiedName="name-incorrect-or-stale-informat">Incorrect or Stale Information</name>
        <t indent="0" pn="section-5.3-1">If information and resources referenced in a "security.txt" file are incorrect
or not kept up to date, this can result in security reports not being received
by the organization or sent to incorrect contacts, thus exposing possible
security issues to third parties. Not having a "security.txt" file may be preferable
to having stale information in this file. Organizations must use
the "Expires" field (see <xref target="expires" format="default" sectionFormat="of" derivedContent="Section 2.5.5"/>) to indicate to researchers when
the data in the file is no longer valid.</t>
        <t indent="0" pn="section-5.3-2">Organizations should ensure that information in this file and any referenced
resources such as web pages, email addresses, and telephone numbers
are kept current, are accessible, are controlled by the organization,
and are kept secure.</t>
      </section>
      <section anchor="intentionally-malformed-files-resources-and-reports" numbered="true" toc="include" removeInRFC="false" pn="section-5.4">
        <name slugifiedName="name-intentionally-malformed-fil">Intentionally Malformed Files, Resources, and Reports</name>
        <t indent="0" pn="section-5.4-1">It is possible for compromised or malicious sites to create files that are extraordinarily
large or otherwise malformed in an attempt to discover or exploit weaknesses
in the parsing code. 

Researchers should make sure that any such code
is robust against large or malformed files and fields, and they may choose to have the code not parse files larger than 32 KBs, those with fields longer than 2,048 characters, or those containing more than 1,000 lines. The ABNF grammar (as defined in
<xref target="abnf" format="default" sectionFormat="of" derivedContent="Section 4"/>) can also be used as a way to verify these files.</t>
        <t indent="0" pn="section-5.4-2">The same concerns apply to any other resources referenced within "security.txt"
files, as well as any security reports received as a result of publishing
this file. Such resources and reports may be hostile, malformed, or malicious.</t>
      </section>
      <section anchor="no-implied-permission-for-testing" numbered="true" toc="include" removeInRFC="false" pn="section-5.5">
        <name slugifiedName="name-no-implied-permission-for-t">No Implied Permission for Testing</name>
        <t indent="0" pn="section-5.5-1">The presence of a "security.txt" file might be interpreted by researchers
as providing permission to do security testing against the domain or IP address
where it is published or against products and services provided by the organization publishing
the file.
This might result in increased testing against an organization by researchers. On the other hand, a decision not
to publish a "security.txt" file might be interpreted by the
organization operating that website to be a way to signal to researchers
that permission to test that particular site or project is denied. This might result in pushback against
researchers reporting security issues to that organization.</t>
        <t indent="0" pn="section-5.5-2">Therefore, researchers shouldn't assume that the presence or absence of
a "security.txt" file grants or denies permission for security testing.
Any such permission may be indicated in the company's vulnerability disclosure policy
(as per <xref target="policy" format="default" sectionFormat="of" derivedContent="Section 2.5.7"/>) or a new field (as per <xref target="extensibility" format="default" sectionFormat="of" derivedContent="Section 2.4"/>).</t>
      </section>
      <section anchor="multi-user-environments" numbered="true" toc="include" removeInRFC="false" pn="section-5.6">
        <name slugifiedName="name-multi-user-environments">Multi-User Environments</name>
        <t indent="0" pn="section-5.6-1">In multi-user / multi-tenant environments, it may be possible for a user to take
over the location of the "security.txt" file. Organizations should reserve
the "security.txt" namespace at the root to ensure no third party can create a page with
the "security.txt" AND "/.well-known/security.txt" names.</t>
      </section>
      <section anchor="protecting-data-in-transit" numbered="true" toc="include" removeInRFC="false" pn="section-5.7">
        <name slugifiedName="name-protecting-data-in-transit">Protecting Data in Transit</name>
        <t indent="0" pn="section-5.7-1">To protect a "security.txt" file from being tampered with in transit, implementors <bcp14>MUST</bcp14> use
HTTPS (as per <xref target="RFC7230" section="2.7.2" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc7230#section-2.7.2" derivedContent="RFC7230"/>) when serving the file itself and for retrieval of any web URIs
referenced in it (except when otherwise noted in this specification). As part of the TLS
handshake, researchers should validate the provided X.509 certificate
in accordance with <xref target="RFC6125" format="default" sectionFormat="of" derivedContent="RFC6125"/> and the following considerations:</t>
        <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.7-2">
          <li pn="section-5.7-2.1">Matching is performed only against the DNS-ID identifiers.</li>
          <li pn="section-5.7-2.2">DNS domain names in server certificates <bcp14>MAY</bcp14> contain the wildcard
character '*' as the complete leftmost label within the identifier.</li>
        </ul>
        <t indent="0" pn="section-5.7-3">The certificate may also be checked for revocation via the Online Certificate Status
Protocol (OCSP) <xref target="RFC6960" format="default" sectionFormat="of" derivedContent="RFC6960"/>, certificate revocation lists (CRLs), or similar mechanisms.</t>
        <t indent="0" pn="section-5.7-4">In cases where the "security.txt" file cannot be served via HTTPS (such as localhost) or is
being served with an invalid certificate, additional human validation is recommended since
the contents may have been modified while in transit.</t>
        <t indent="0" pn="section-5.7-5">As an additional layer of protection, it is also recommended that
organizations digitally sign their "security.txt" file with OpenPGP (as per <xref target="signature" format="default" sectionFormat="of" derivedContent="Section 2.3"/>).
Also, to protect security reports from being tampered with or observed while in transit,
organizations should specify encryption keys (as per <xref target="encryption" format="default" sectionFormat="of" derivedContent="Section 2.5.4"/>) unless
HTTPS is being used for report submission.</t>
        <t indent="0" pn="section-5.7-6">However, the determination of validity of such keys is out of scope
for this specification. Security researchers need to establish other secure means to
verify them.</t>
      </section>
      <section anchor="spam-and-spurious-reports" numbered="true" toc="include" removeInRFC="false" pn="section-5.8">
        <name slugifiedName="name-spam-and-spurious-reports">Spam and Spurious Reports</name>
        <t indent="0" pn="section-5.8-1">Similar to concerns in <xref target="RFC2142" format="default" sectionFormat="of" derivedContent="RFC2142"/>, denial-of-service attacks via spam reports
would become easier once a "security.txt" file is published by
an organization. In addition, there is an increased likelihood of reports
being sent in an automated fashion and/or as a result of automated scans without
human analysis. Attackers can also use this file as a way to spam unrelated
third parties by listing their resources and/or contact information.</t>
        <t indent="0" pn="section-5.8-2">Organizations need to weigh the advantages of publishing this file versus
the possible disadvantages and increased resources required to analyze
	security reports.</t>
        <t indent="0" pn="section-5.8-3">Security researchers should review all information within the "security.txt"
file before submitting reports in an automated fashion or reports resulting from automated scans.</t>
      </section>
    </section>
    <section anchor="iana-considerations" numbered="true" toc="include" removeInRFC="false" pn="section-6">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <t indent="0" pn="section-6-1">Implementors should be aware that any resources referenced within
a "security.txt" file <bcp14>MUST NOT</bcp14> point to the Well-Known URIs namespace unless
they are registered with IANA (as per <xref target="RFC8615" format="default" sectionFormat="of" derivedContent="RFC8615"/>).</t>
      <section anchor="well-known-uris-registry" numbered="true" toc="include" removeInRFC="false" pn="section-6.1">
        <name slugifiedName="name-well-known-uris-registry">Well-Known URIs Registry</name>
        <t indent="0" pn="section-6.1-1">IANA has updated the "Well-Known URIs" registry with the following additional
	values (using the template from <xref target="RFC8615" format="default" sectionFormat="of" derivedContent="RFC8615"/>):</t>
        <dl spacing="compact" indent="3" newline="false" pn="section-6.1-2">
          <dt pn="section-6.1-2.1">URI suffix:</dt>
          <dd pn="section-6.1-2.2">security.txt</dd>
          <dt pn="section-6.1-2.3">Change controller:</dt>
          <dd pn="section-6.1-2.4">IETF</dd>
          <dt pn="section-6.1-2.5">Specification document(s):</dt>
          <dd pn="section-6.1-2.6">RFC 9116</dd>
          <dt pn="section-6.1-2.7">Status:</dt>
          <dd pn="section-6.1-2.8">permanent</dd>
        </dl>
      </section>
      <section anchor="registry" numbered="true" toc="include" removeInRFC="false" pn="section-6.2">
        <name slugifiedName="name-registry-for-securitytxt-fi">Registry for security.txt Fields</name>
        <t indent="0" pn="section-6.2-1">IANA has created the "security.txt Fields" registry in
accordance with <xref target="RFC8126" format="default" sectionFormat="of" derivedContent="RFC8126"/>. This registry contains fields for
use in "security.txt" files, defined by this specification.</t>
        <t indent="0" pn="section-6.2-2">New registrations or updates <bcp14>MUST</bcp14> be published in accordance with the
"Expert Review" guidelines as described in Sections 
<xref target="RFC8126" section="4.5" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8126#section-4.5" derivedContent="RFC8126"/> and <xref target="RFC8126" section="5" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8126#section-5" derivedContent="RFC8126"/> of <xref target="RFC8126" format="default" sectionFormat="of" derivedContent="RFC8126"/>. Any new field thus registered is considered optional
by this specification unless a new version of this specification is published.</t>
        <t indent="0" pn="section-6.2-3">Designated experts should determine whether a proposed registration or update
provides value to organizations and researchers using this format and makes sense in the context of industry-accepted vulnerability disclosure processes
such as <xref target="ISO.29147.2018" format="default" sectionFormat="of" derivedContent="ISO.29147.2018"/> and <xref target="CERT.CVD" format="default" sectionFormat="of" derivedContent="CERT.CVD"/>.</t>
        <t indent="0" pn="section-6.2-4">New registrations and updates <bcp14>MUST</bcp14> contain the following information:</t>
        <ol spacing="normal" type="1" indent="adaptive" start="1" pn="section-6.2-5">
	  <li pn="section-6.2-5.1" derivedCounter="1.">Name of the field being registered or updated</li>
          <li pn="section-6.2-5.2" derivedCounter="2.">Short description of the field</li>
          <li pn="section-6.2-5.3" derivedCounter="3.">Whether the field can appear more than once</li>
          <li pn="section-6.2-5.4" derivedCounter="4.">
            <t indent="0" pn="section-6.2-5.4.1"> New or updated status, which <bcp14>MUST</bcp14> be one of the following:</t>
            <dl spacing="compact" indent="3" newline="false" pn="section-6.2-5.4.2">
              <dt pn="section-6.2-5.4.2.1">current:</dt>
              <dd pn="section-6.2-5.4.2.2">The field is in current use.</dd>
              <dt pn="section-6.2-5.4.2.3">deprecated:</dt>
              <dd pn="section-6.2-5.4.2.4">The field has been in use, but new usage is discouraged.</dd>
              <dt pn="section-6.2-5.4.2.5">historic:</dt>
              <dd pn="section-6.2-5.4.2.6">The field is no longer in current use.</dd>
            </dl>
          </li>
          <li pn="section-6.2-5.5" derivedCounter="5.">Change controller</li>
          <li pn="section-6.2-5.6" derivedCounter="6.">The document in which the specification of the field is published (if available)</li>
        </ol>
        <t indent="0" pn="section-6.2-6">Existing registrations may be marked historic or deprecated, as appropriate, by a future update to this document.</t>
        <t indent="0" pn="section-6.2-7">The initial registry contains these values:</t>
        <dl spacing="compact" indent="3" newline="false" pn="section-6.2-8">
          <dt pn="section-6.2-8.1">Field Name:</dt>
          <dd pn="section-6.2-8.2">Acknowledgments</dd>
          <dt pn="section-6.2-8.3">Description:</dt>
          <dd pn="section-6.2-8.4">link to page where security researchers are recognized</dd>
          <dt pn="section-6.2-8.5">Multiple Appearances:</dt>
          <dd pn="section-6.2-8.6">yes</dd>
          <dt pn="section-6.2-8.7">Status:</dt>
          <dd pn="section-6.2-8.8">current</dd>
          <dt pn="section-6.2-8.9">Change controller:</dt>
          <dd pn="section-6.2-8.10">IETF</dd>
          <dt pn="section-6.2-8.11">Reference:</dt>
          <dd pn="section-6.2-8.12">RFC 9116</dd>
        </dl>
        <dl spacing="compact" indent="3" newline="false" pn="section-6.2-9">
          <dt pn="section-6.2-9.1">Field Name:</dt>
          <dd pn="section-6.2-9.2">Canonical</dd>
          <dt pn="section-6.2-9.3">Description:</dt>
          <dd pn="section-6.2-9.4">canonical URI for this file</dd>
          <dt pn="section-6.2-9.5">Multiple Appearances:</dt>
          <dd pn="section-6.2-9.6">yes</dd>
          <dt pn="section-6.2-9.7">Status:</dt>
          <dd pn="section-6.2-9.8">current</dd>
          <dt pn="section-6.2-9.9">Change controller:</dt>
          <dd pn="section-6.2-9.10">IETF</dd>
          <dt pn="section-6.2-9.11">Reference:</dt>
          <dd pn="section-6.2-9.12">RFC 9116</dd>
        </dl>
        <dl spacing="compact" indent="3" newline="false" pn="section-6.2-10">
          <dt pn="section-6.2-10.1">Field Name:</dt>
          <dd pn="section-6.2-10.2">Contact</dd>
          <dt pn="section-6.2-10.3">Description:</dt>
          <dd pn="section-6.2-10.4">contact information to use for reporting vulnerabilities</dd>
          <dt pn="section-6.2-10.5">Multiple Appearances:</dt>
          <dd pn="section-6.2-10.6">yes</dd>
          <dt pn="section-6.2-10.7">Status:</dt>
          <dd pn="section-6.2-10.8">current</dd>
          <dt pn="section-6.2-10.9">Change controller:</dt>
          <dd pn="section-6.2-10.10">IETF</dd>
          <dt pn="section-6.2-10.11">Reference:</dt>
          <dd pn="section-6.2-10.12">RFC 9116</dd>
        </dl>
        <dl spacing="compact" indent="3" newline="false" pn="section-6.2-11">
          <dt pn="section-6.2-11.1">Field Name:</dt>
          <dd pn="section-6.2-11.2">Expires</dd>
          <dt pn="section-6.2-11.3">Description:</dt>
          <dd pn="section-6.2-11.4">date and time after which this file is considered stale</dd>
          <dt pn="section-6.2-11.5">Multiple Appearances:</dt>
          <dd pn="section-6.2-11.6">no</dd>
          <dt pn="section-6.2-11.7">Status:</dt>
          <dd pn="section-6.2-11.8">current</dd>
          <dt pn="section-6.2-11.9">Change controller:</dt>
          <dd pn="section-6.2-11.10">IETF</dd>
          <dt pn="section-6.2-11.11">Reference:</dt>
          <dd pn="section-6.2-11.12">RFC 9116</dd>
        </dl>
        <dl spacing="compact" indent="3" newline="false" pn="section-6.2-12">
          <dt pn="section-6.2-12.1">Field Name:</dt>
          <dd pn="section-6.2-12.2">Encryption</dd>
          <dt pn="section-6.2-12.3">Description:</dt>
          <dd pn="section-6.2-12.4">link to a key to be used for encrypted communication</dd>
          <dt pn="section-6.2-12.5">Multiple Appearances:</dt>
          <dd pn="section-6.2-12.6">yes</dd>
          <dt pn="section-6.2-12.7">Status:</dt>
          <dd pn="section-6.2-12.8">current</dd>
          <dt pn="section-6.2-12.9">Change controller:</dt>
          <dd pn="section-6.2-12.10">IETF</dd>
          <dt pn="section-6.2-12.11">Reference:</dt>
          <dd pn="section-6.2-12.12">RFC 9116</dd>
        </dl>
        <dl spacing="compact" indent="3" newline="false" pn="section-6.2-13">
          <dt pn="section-6.2-13.1">Field Name:</dt>
          <dd pn="section-6.2-13.2">Hiring</dd>
          <dt pn="section-6.2-13.3">Description:</dt>
          <dd pn="section-6.2-13.4">link to the vendor's security-related job positions</dd>
          <dt pn="section-6.2-13.5">Multiple Appearances:</dt>
          <dd pn="section-6.2-13.6">yes</dd>
          <dt pn="section-6.2-13.7">Status:</dt>
          <dd pn="section-6.2-13.8">current</dd>
          <dt pn="section-6.2-13.9">Change controller:</dt>
          <dd pn="section-6.2-13.10">IETF</dd>
          <dt pn="section-6.2-13.11">Reference:</dt>
          <dd pn="section-6.2-13.12">RFC 9116</dd>
        </dl>
        <dl spacing="compact" indent="3" newline="false" pn="section-6.2-14">
          <dt pn="section-6.2-14.1">Field Name:</dt>
          <dd pn="section-6.2-14.2">Policy</dd>
          <dt pn="section-6.2-14.3">Description:</dt>
          <dd pn="section-6.2-14.4">link to security policy page</dd>
          <dt pn="section-6.2-14.5">Multiple Appearances:</dt>
          <dd pn="section-6.2-14.6">yes</dd>
          <dt pn="section-6.2-14.7">Status:</dt>
          <dd pn="section-6.2-14.8">current</dd>
          <dt pn="section-6.2-14.9">Change controller:</dt>
          <dd pn="section-6.2-14.10">IETF</dd>
          <dt pn="section-6.2-14.11">Reference:</dt>
          <dd pn="section-6.2-14.12">RFC 9116</dd>
        </dl>
        <dl spacing="compact" indent="3" newline="false" pn="section-6.2-15">
          <dt pn="section-6.2-15.1">Field Name:</dt>
          <dd pn="section-6.2-15.2">Preferred-Languages</dd>
          <dt pn="section-6.2-15.3">Description:</dt>
          <dd pn="section-6.2-15.4">list of preferred languages for security reports</dd>
          <dt pn="section-6.2-15.5">Multiple Appearances:</dt>
          <dd pn="section-6.2-15.6">no</dd>
          <dt pn="section-6.2-15.7">Status:</dt>
          <dd pn="section-6.2-15.8">current</dd>
          <dt pn="section-6.2-15.9">Change controller:</dt>
          <dd pn="section-6.2-15.10">IETF</dd>
          <dt pn="section-6.2-15.11">Reference:</dt>
          <dd pn="section-6.2-15.12">RFC 9116</dd>
        </dl>
      </section>
    </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="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 initials="N." surname="Freed" fullname="N. Freed">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="N." surname="Borenstein" fullname="N. Borenstein">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="1996" month="November"/>
            <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="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 initials="S." surname="Bradner" fullname="S. Bradner">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="1997" month="March"/>
            <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="RFC2142" target="https://www.rfc-editor.org/info/rfc2142" quoteTitle="true" derivedAnchor="RFC2142">
          <front>
            <title>Mailbox Names for Common Services, Roles and Functions</title>
            <author initials="D." surname="Crocker" fullname="D. Crocker">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="1997" month="May"/>
            <abstract>
              <t indent="0">This specification enumerates and describes Internet mail addresses (mailbox name @ host reference) to be used when contacting personnel at an organization. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="2142"/>
          <seriesInfo name="DOI" value="10.17487/RFC2142"/>
        </reference>
        <reference anchor="RFC2277" target="https://www.rfc-editor.org/info/rfc2277" quoteTitle="true" derivedAnchor="RFC2277">
          <front>
            <title>IETF Policy on Character Sets and Languages</title>
            <author initials="H." surname="Alvestrand" fullname="H. Alvestrand">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="1998" month="January"/>
            <abstract>
              <t indent="0">This document is the current policies being applied by the Internet Engineering Steering Group (IESG) towards the standardization efforts in the Internet Engineering Task Force (IETF) in order to help Internet protocols fulfill these requirements.  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="18"/>
          <seriesInfo name="RFC" value="2277"/>
          <seriesInfo name="DOI" value="10.17487/RFC2277"/>
        </reference>
        <reference anchor="RFC3339" target="https://www.rfc-editor.org/info/rfc3339" quoteTitle="true" derivedAnchor="RFC3339">
          <front>
            <title>Date and Time on the Internet: Timestamps</title>
            <author initials="G." surname="Klyne" fullname="G. Klyne">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="C." surname="Newman" fullname="C. Newman">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2002" month="July"/>
            <abstract>
              <t indent="0">This document defines a date and time format for use in Internet protocols that is a profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3339"/>
          <seriesInfo name="DOI" value="10.17487/RFC3339"/>
        </reference>
        <reference anchor="RFC3629" target="https://www.rfc-editor.org/info/rfc3629" quoteTitle="true" derivedAnchor="RFC3629">
          <front>
            <title>UTF-8, a transformation format of ISO 10646</title>
            <author initials="F." surname="Yergeau" fullname="F. Yergeau">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2003" month="November"/>
            <abstract>
              <t indent="0">ISO/IEC 10646-1 defines a large character set called the Universal Character Set (UCS) which encompasses most of the world's writing systems.  The originally proposed encodings of the UCS, however, were not compatible with many current applications and protocols, and this has led to the development of UTF-8, the object of this memo.  UTF-8 has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values.  This memo obsoletes and replaces RFC 2279.</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="63"/>
          <seriesInfo name="RFC" value="3629"/>
          <seriesInfo name="DOI" value="10.17487/RFC3629"/>
        </reference>
        <reference anchor="RFC3966" target="https://www.rfc-editor.org/info/rfc3966" quoteTitle="true" derivedAnchor="RFC3966">
          <front>
            <title>The tel URI for Telephone Numbers</title>
            <author initials="H." surname="Schulzrinne" fullname="H. Schulzrinne">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2004" month="December"/>
            <abstract>
              <t indent="0">This document specifies the URI (Uniform Resource Identifier) scheme "tel".  The "tel" URI describes resources identified by telephone numbers.  This document obsoletes RFC 2806.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="3966"/>
          <seriesInfo name="DOI" value="10.17487/RFC3966"/>
        </reference>
        <reference anchor="RFC3986" target="https://www.rfc-editor.org/info/rfc3986" quoteTitle="true" derivedAnchor="RFC3986">
          <front>
            <title>Uniform Resource Identifier (URI): Generic Syntax</title>
            <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="R." surname="Fielding" fullname="R. Fielding">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="L." surname="Masinter" fullname="L. Masinter">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2005" month="January"/>
            <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>
        <reference anchor="RFC4880" target="https://www.rfc-editor.org/info/rfc4880" quoteTitle="true" derivedAnchor="RFC4880">
          <front>
            <title>OpenPGP Message Format</title>
            <author initials="J." surname="Callas" fullname="J. Callas">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="L." surname="Donnerhacke" fullname="L. Donnerhacke">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="H." surname="Finney" fullname="H. Finney">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="D." surname="Shaw" fullname="D. Shaw">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="R." surname="Thayer" fullname="R. Thayer">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2007" month="November"/>
            <abstract>
              <t indent="0">This document is maintained in order to publish all necessary information needed to develop interoperable applications based on the OpenPGP format.  It is not a step-by-step cookbook for writing an application.  It describes only the format and methods needed to read, check, generate, and write conforming packets crossing any network.  It does not deal with storage and implementation questions. It does, however, discuss implementation issues necessary to avoid security flaws.</t>
              <t indent="0">OpenPGP software uses a combination of strong public-key and symmetric cryptography to provide security services for electronic communications and data storage.  These services include confidentiality, key management, authentication, and digital signatures.  This document specifies the message formats used in OpenPGP.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4880"/>
          <seriesInfo name="DOI" value="10.17487/RFC4880"/>
        </reference>
        <reference anchor="RFC5198" target="https://www.rfc-editor.org/info/rfc5198" quoteTitle="true" derivedAnchor="RFC5198">
          <front>
            <title>Unicode Format for Network Interchange</title>
            <author initials="J." surname="Klensin" fullname="J. Klensin">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="M." surname="Padlipsky" fullname="M. Padlipsky">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2008" month="March"/>
            <abstract>
              <t indent="0">The Internet today is in need of a standardized form for the transmission of internationalized "text" information, paralleling the specifications for the use of ASCII that date from the early days of the ARPANET.  This document specifies that format, using UTF-8 with normalization and specific line-ending sequences.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5198"/>
          <seriesInfo name="DOI" value="10.17487/RFC5198"/>
        </reference>
        <reference anchor="RFC5234" target="https://www.rfc-editor.org/info/rfc5234" quoteTitle="true" derivedAnchor="RFC5234">
          <front>
            <title>Augmented BNF for Syntax Specifications: ABNF</title>
            <author initials="D." surname="Crocker" fullname="D. Crocker" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="P." surname="Overell" fullname="P. Overell">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2008" month="January"/>
            <abstract>
              <t indent="0">Internet technical specifications often need to define a formal syntax.  Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications.  The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power.  The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges.  This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="STD" value="68"/>
          <seriesInfo name="RFC" value="5234"/>
          <seriesInfo name="DOI" value="10.17487/RFC5234"/>
        </reference>
        <reference anchor="RFC5322" target="https://www.rfc-editor.org/info/rfc5322" quoteTitle="true" derivedAnchor="RFC5322">
          <front>
            <title>Internet Message Format</title>
            <author initials="P." surname="Resnick" fullname="P. Resnick" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2008" month="October"/>
            <abstract>
              <t indent="0">This document specifies the Internet Message Format (IMF), a syntax for text messages that are sent between computer users, within the framework of "electronic mail" messages.  This specification is a revision of Request For Comments (RFC) 2822, which itself superseded Request For Comments (RFC) 822, "Standard for the Format of ARPA Internet Text Messages", updating it to reflect current practice and incorporating incremental changes that were specified in other RFCs.  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5322"/>
          <seriesInfo name="DOI" value="10.17487/RFC5322"/>
        </reference>
        <reference anchor="RFC5646" target="https://www.rfc-editor.org/info/rfc5646" quoteTitle="true" derivedAnchor="RFC5646">
          <front>
            <title>Tags for Identifying Languages</title>
            <author initials="A." surname="Phillips" fullname="A. Phillips" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="M." surname="Davis" fullname="M. Davis" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2009" month="September"/>
            <abstract>
              <t indent="0">This document describes the structure, content, construction, and semantics of language tags for use in cases where it is desirable to indicate the language used in an information object.  It also describes how to register values for use in language tags and the creation of user-defined extensions for private interchange.  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="47"/>
          <seriesInfo name="RFC" value="5646"/>
          <seriesInfo name="DOI" value="10.17487/RFC5646"/>
        </reference>
        <reference anchor="RFC6068" target="https://www.rfc-editor.org/info/rfc6068" quoteTitle="true" derivedAnchor="RFC6068">
          <front>
            <title>The 'mailto' URI Scheme</title>
            <author initials="M." surname="Duerst" fullname="M. Duerst">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="L." surname="Masinter" fullname="L. Masinter">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="J." surname="Zawinski" fullname="J. Zawinski">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2010" month="October"/>
            <abstract>
              <t indent="0">This document defines the format of Uniform Resource Identifiers (URIs) to identify resources that are reached using Internet mail. It adds better internationalization and compatibility with Internationalized Resource Identifiers (IRIs; RFC 3987) to the previous syntax of 'mailto' URIs (RFC 2368).  [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6068"/>
          <seriesInfo name="DOI" value="10.17487/RFC6068"/>
        </reference>
        <reference anchor="RFC6125" target="https://www.rfc-editor.org/info/rfc6125" quoteTitle="true" derivedAnchor="RFC6125">
          <front>
            <title>Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)</title>
            <author initials="P." surname="Saint-Andre" fullname="P. Saint-Andre">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="J." surname="Hodges" fullname="J. Hodges">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2011" month="March"/>
            <abstract>
              <t indent="0">Many application technologies enable secure communication between two entities by means of Internet Public Key Infrastructure Using X.509 (PKIX) certificates in the context of Transport Layer Security (TLS). This document specifies procedures for representing and verifying the identity of application services in such interactions.   [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6125"/>
          <seriesInfo name="DOI" value="10.17487/RFC6125"/>
        </reference>
        <reference anchor="RFC6960" target="https://www.rfc-editor.org/info/rfc6960" quoteTitle="true" derivedAnchor="RFC6960">
          <front>
            <title>X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP</title>
            <author initials="S." surname="Santesson" fullname="S. Santesson">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="M." surname="Myers" fullname="M. Myers">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="R." surname="Ankney" fullname="R. Ankney">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="A." surname="Malpani" fullname="A. Malpani">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="S." surname="Galperin" fullname="S. Galperin">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="C." surname="Adams" fullname="C. Adams">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2013" month="June"/>
            <abstract>
              <t indent="0">This document specifies a protocol useful in determining the current status of a digital certificate without requiring Certificate Revocation Lists (CRLs). Additional mechanisms addressing PKIX operational requirements are specified in separate documents.  This document obsoletes RFCs 2560 and 6277.  It also updates RFC 5912.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="6960"/>
          <seriesInfo name="DOI" value="10.17487/RFC6960"/>
        </reference>
        <reference anchor="RFC7230" target="https://www.rfc-editor.org/info/rfc7230" quoteTitle="true" derivedAnchor="RFC7230">
          <front>
            <title>Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</title>
            <author initials="R." surname="Fielding" fullname="R. Fielding" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="J." surname="Reschke" fullname="J. Reschke" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2014" month="June"/>
            <abstract>
              <t indent="0">The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems.  This document provides an overview of HTTP architecture and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the HTTP/1.1 message syntax and parsing requirements, and describes related security concerns for implementations.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7230"/>
          <seriesInfo name="DOI" value="10.17487/RFC7230"/>
        </reference>
        <reference anchor="RFC7231" target="https://www.rfc-editor.org/info/rfc7231" quoteTitle="true" derivedAnchor="RFC7231">
          <front>
            <title>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</title>
            <author initials="R." surname="Fielding" fullname="R. Fielding" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="J." surname="Reschke" fullname="J. Reschke" role="editor">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2014" month="June"/>
            <abstract>
              <t indent="0">The Hypertext Transfer Protocol (HTTP) is a stateless \%application- level protocol for distributed, collaborative, hypertext information systems.  This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7231"/>
          <seriesInfo name="DOI" value="10.17487/RFC7231"/>
        </reference>
        <reference anchor="RFC7405" target="https://www.rfc-editor.org/info/rfc7405" quoteTitle="true" derivedAnchor="RFC7405">
          <front>
            <title>Case-Sensitive String Support in ABNF</title>
            <author initials="P." surname="Kyzivat" fullname="P. Kyzivat">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2014" month="December"/>
            <abstract>
              <t indent="0">This document extends the base definition of ABNF (Augmented Backus-Naur Form) to include a way to specify US-ASCII string literals that are matched in a case-sensitive manner.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7405"/>
          <seriesInfo name="DOI" value="10.17487/RFC7405"/>
        </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 initials="B." surname="Leiba" fullname="B. Leiba">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2017" month="May"/>
            <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="RFC8615" target="https://www.rfc-editor.org/info/rfc8615" quoteTitle="true" derivedAnchor="RFC8615">
          <front>
            <title>Well-Known Uniform Resource Identifiers (URIs)</title>
            <author initials="M." surname="Nottingham" fullname="M. Nottingham">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2019" month="May"/>
            <abstract>
              <t indent="0">This memo defines a path prefix for "well-known locations", "/.well-known/", in selected Uniform Resource Identifier (URI) schemes.</t>
              <t indent="0">In doing so, it obsoletes RFC 5785 and updates the URI schemes defined in RFC 7230 to reserve that space.  It also updates RFC 7595 to track URI schemes that support well-known URIs in their registry.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="8615"/>
          <seriesInfo name="DOI" value="10.17487/RFC8615"/>
        </reference>
      </references>
      <references pn="section-7.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="CERT.CVD" quoteTitle="true" derivedAnchor="CERT.CVD">
          <front>
            <title>The CERT Guide to Coordinated Vulnerability Disclosure</title>
            <author>
              <organization showOnFrontPage="true">Software Engineering Institute</organization>
            </author>
            <date year="2017" month="August"/>
          </front>
          <refcontent>Carnegie Mellon University, CMU/SEI-2017-SR-022</refcontent>
        </reference>
        <reference anchor="ISO.29147.2018" quoteTitle="true" derivedAnchor="ISO.29147.2018">
          <front>
            <title>Information technology - Security techniques - Vulnerability disclosure</title>
            <author>
              <organization showOnFrontPage="true">ISO</organization>
            </author>
            <date year="2018" month="October"/>
          </front>
          <seriesInfo name="ISO/IEC" value="29147:2018"/>
        </reference>
        <reference anchor="ISO.8601-1" quoteTitle="true" derivedAnchor="ISO.8601-1">
          <front>
            <title>Date and time - Representations for information interchange - Part 1: Basic rules</title>
            <author>
              <organization showOnFrontPage="true">ISO</organization>
            </author>
            <date month="February" year="2019"/>
          </front>
          <seriesInfo name="ISO" value="8601-1:2019"/>
        </reference>
        <reference anchor="ISO.8601-2" quoteTitle="true" derivedAnchor="ISO.8601-2">
          <front>
            <title>Date and time - Representations for information interchange - Part 2: Extensions</title>
            <author>
              <organization showOnFrontPage="true">ISO</organization>
            </author>
            <date month="February" year="2019"/>
          </front>
          <seriesInfo name="ISO" value="8601-2:2019"/>
        </reference>
        <reference anchor="RFC0793" target="https://www.rfc-editor.org/info/rfc793" quoteTitle="true" derivedAnchor="RFC0793">
          <front>
            <title>Transmission Control Protocol</title>
            <author initials="J." surname="Postel" fullname="J. Postel">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="1981" month="September"/>
          </front>
          <seriesInfo name="STD" value="7"/>
          <seriesInfo name="RFC" value="793"/>
          <seriesInfo name="DOI" value="10.17487/RFC0793"/>
        </reference>
        <reference anchor="RFC2196" target="https://www.rfc-editor.org/info/rfc2196" quoteTitle="true" derivedAnchor="RFC2196">
          <front>
            <title>Site Security Handbook</title>
            <author initials="B." surname="Fraser" fullname="B. Fraser">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="1997" month="September"/>
            <abstract>
              <t indent="0">This handbook is a guide to developing computer security policies and procedures for sites that have systems on the Internet.  The purpose of this handbook is to provide practical guidance to administrators trying to secure their information and services.  The subjects covered include policy content and formation, a broad range of technical system and network security topics, and security incident response.  This memo provides information for the Internet community.  It does not specify an Internet standard of any kind.</t>
            </abstract>
          </front>
          <seriesInfo name="FYI" value="8"/>
          <seriesInfo name="RFC" value="2196"/>
          <seriesInfo name="DOI" value="10.17487/RFC2196"/>
        </reference>
        <reference anchor="RFC2350" target="https://www.rfc-editor.org/info/rfc2350" quoteTitle="true" derivedAnchor="RFC2350">
          <front>
            <title>Expectations for Computer Security Incident Response</title>
            <author initials="N." surname="Brownlee" fullname="N. Brownlee">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="E." surname="Guttman" fullname="E. Guttman">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="1998" month="June"/>
          </front>
          <seriesInfo name="BCP" value="21"/>
          <seriesInfo name="RFC" value="2350"/>
          <seriesInfo name="DOI" value="10.17487/RFC2350"/>
        </reference>
        <reference anchor="RFC3013" target="https://www.rfc-editor.org/info/rfc3013" quoteTitle="true" derivedAnchor="RFC3013">
          <front>
            <title>Recommended Internet Service Provider Security Services and Procedures</title>
            <author initials="T." surname="Killalea" fullname="T. Killalea">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2000" month="November"/>
            <abstract>
              <t indent="0">The purpose of this document is to express what the engineering community as represented by the IETF expects of Internet Service Providers (ISPs) with respect to security.  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="46"/>
          <seriesInfo name="RFC" value="3013"/>
          <seriesInfo name="DOI" value="10.17487/RFC3013"/>
        </reference>
        <reference anchor="RFC7485" target="https://www.rfc-editor.org/info/rfc7485" quoteTitle="true" derivedAnchor="RFC7485">
          <front>
            <title>Inventory and Analysis of WHOIS Registration Objects</title>
            <author initials="L." surname="Zhou" fullname="L. Zhou">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="N." surname="Kong" fullname="N. Kong">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="S." surname="Shen" fullname="S. Shen">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="S." surname="Sheng" fullname="S. Sheng">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="A." surname="Servin" fullname="A. Servin">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2015" month="March"/>
            <abstract>
              <t indent="0">WHOIS output objects from registries, including both Regional Internet Registries (RIRs) and Domain Name Registries (DNRs), were collected and analyzed.  This document describes the process and results of the statistical analysis of existing WHOIS information. The purpose of this document is to build an object inventory to facilitate discussions of data objects included in Registration Data Access Protocol (RDAP) responses.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7485"/>
          <seriesInfo name="DOI" value="10.17487/RFC7485"/>
        </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 initials="M." surname="Cotton" fullname="M. Cotton">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="B." surname="Leiba" fullname="B. Leiba">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="T." surname="Narten" fullname="T. Narten">
              <organization showOnFrontPage="true"/>
            </author>
            <date year="2017" month="June"/>
            <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>
      </references>
    </references>
    <section anchor="contributors" numbered="false" toc="include" removeInRFC="false" pn="section-appendix.a">
      <name slugifiedName="name-acknowledgments-2">Acknowledgments</name>
      <t indent="0" pn="section-appendix.a-1">The authors would like to acknowledge the help provided during the
development of this document by <contact fullname="Tom Hudson"/>, <contact fullname="Jobert Abma"/>,
<contact fullname="Gerben Janssen van Doorn"/>, <contact fullname="Austin Heap"/>, <contact fullname="Stephane Bortzmeyer"/>, <contact fullname="Max Smith"/>, <contact fullname="Eduardo Vela"/>, and <contact fullname="Krzysztof Kotowicz"/>.</t>
      <t indent="0" pn="section-appendix.a-2">The authors would also like to acknowledge the feedback provided by multiple members of the IETF's
LAST CALL, SAAG, and SECDISPATCH lists.</t>
      <t indent="0" pn="section-appendix.a-3"><contact fullname="Yakov Shafranovich"/> would like to also thank L.T.S. (for everything).</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="E." surname="Foudil" fullname="Edwin Foudil">
        <organization showOnFrontPage="true"/>
        <address>
          <email>contact@edoverflow.com</email>
        </address>
      </author>
      <author initials="Y." surname="Shafranovich" fullname="Yakov Shafranovich">
        <organization showOnFrontPage="true">Nightwatch Cybersecurity</organization>
        <address>
          <email>yakov+ietf@nightwatchcybersecurity.com</email>
        </address>
      </author>
    </section>
  </back>
</rfc>
